Atomicorp

Scott,

Updated to spamassassin 3.2.1-1.fc6.art that was straight forward. I got one error complaining about v310.pre saved as v310.pre.rpmnew, no biggy at all.

However about 5 minutes after I updated, watchdog emails me saying spamassassin is down.

Services in plesk shows it is running fine. Start it, stop it or restart works perfectly.

However watchdog is not impressed with this version of spamassassin. According to watchdog spamassassin has a red X and is stopped.

Do we know how to patch watchdog to fix this bug?

One thing watchdog is great for is finding spamassassin has stopped and restarts it.

Now it wont and switches itself off from monitoring spamassassin.

Any idea's and a fix - please?

Cheers!

David

PS - Additional info

I proved this 100%. I downloaded ARTs last spamassassin 3.1.8-1.fc6.art.i386.rpm and forced a downgrade of spamassassin with:

rpm -Uvh --oldpackage spamassassin-3.1.8-1.fc6.art.i386.rpm

After it replaced the version and restarted spamassassin, I went back to watchdog and reenabled checking of spamassassin. I only had to wait 5 seconds and hit reload, it says spamassassin is okay.

Looks like the 3.2.1-1.fc6.art is no good for watchdog. I hope there is a fix soon...

Im not getting that on my systems (centos4), so it sounds like something localized to fc6 at least. Permissions problem maybe? Im not sure really, since I dont have any visibility into watchdog. Ive got an alternate system in ASL called psmon that does the same thing, so if you're using that you could disable watchdog from monitoring SA and use that instead.

Scott,

Thanks I think I will try. Does the psmon like watchdog have the ability to restart services itself and email?

Could it be used to replace watchdog and look after more services?

Lastly the ASL webpage says it supports up to FC5, what about FC6?

Thanks!

David

Yeah it can watch anything you want, its a free-form configuration, Im using in ASL for that reason since Ive got so many different pieces involved now, and on that topic version the in development 2.0 version supports fedora 6.

Hi Scott,
Many thanks I will want to give it a run. So its configurable to automatically restart services?
With regards to ASL I am thinking of taking up the service. My question is FC6 supported now, or its about to be?
Now can I get hold of Version 2.0 psmon to test it?
Cheers!

Yep FC6 is supported just fine right now. In fact thats what I do all the kernel development and testing on. PSMON configs look like this:

<Process xinetd>
spawncmd /sbin/service xinetd restart
pidfile /var/run/xinetd.pid
</Process>

Very trivial to add a service to be monitored. It can work the other way too, watching for processes that either shouldnt be running, or are using too many resources.

Hi,

Same problem here, Centos 4, spamassassin 3.2.1 1.el4.art

When watchdog monitoring is enabled spamassassin shuts down frequently.

Monitoring disabled, spamassassin works just fine.

Arjen

Hi Guys,

Did anyone come up with a fix for this?

I'm also on Centos4 64bit.
My spamassassin monitoring broke during the same update. Now several updates later it is still the same.

Spamassassin does work and can be stopped and started in the server/services section in Plesk as normal.

Go to modules however and Watchdog shows it as not running.
I haven't done anything other than the usual yum updates and Plesk is now on 8.2.

Sorry its still broken but swsoft is aware of this issue.

Considering the issue I posted to swsoft in June and I still don't see a hotfix - don't hold your breath.

swsoft got back and admited watchdog is broken and it won't work with several versions of spamassassin.

I have a feeling you won't see it fixed until Plesk 9

I just rolled back to spamassassin 3.1.8-1.fc6.art (it runs fine under watchdog)

The issue you have is if watchdog can't monitor spamassassin and it stops, you get a flood of spam until you login and restart spamd.

I would rather have a older version that automatically restarts than get floods of spam. I find it crashes about 2 to 3 times a week.

Thanks for the info. I'm not too worried about it as spamassassin seems to work pretty good for me, more of an annoyance really. Thanks again.

If SpamAssassin crashes 2-3 times a week I'd try and find out why it's doing that. Using watchdog to restart it is only fighting the symptoms, not the root of the problem. SpamAssassin really shouldn't be crashing that often.

We have been having SpamAssassin crash on a regular occasion.
Perhaps 2-3 per day minimum.

We are running Fedora 4 and Plesk 8.1.1 (was failing since 8.1 or 8.0).

The only thing I have found that might work would be:
http://www.inertramblings.com/2006/09/2 ... der-plesk/

The best I can figure is that the crashing maybe caused by a misconnection from to many connections.

SpamAssassin doesn't have a lot to do with your IMAP server, it is part of the SMTP chain.

Just a heads up guys.
The Watchdog monitoring for SpamAssassin seems to have been fixed with the latest Plesk 8.2.1 update.

EDIT:

Scrap that, it seemed to be working initially but it's back to the usual now. Sorry for the false hope.

Correct it IS still broken. Swsoft told me plesk 9.