watchdog says spamassassin is down bug STILL not fixed!

[nforde]

Parallels/Plesk really need to have a publicly accessible bug tracker (at least for current Plesk owners) so we can report and track bugs/issues.

It should also include bugs/issues related to the integration of Plesk with 3rd party applications, even if it isn't officially a bug in the Plesk programming.


A lot of people are wasting a lot of time discussing issues and workarounds for Plesk related issues and a bug/issue tracker would save everyone a lot of time.

 

[105547111]

Outstanding suggestion, if only they implement this........

 

[dash]

The fix does not work the file keeps getting changed back if you start and stop watchdog, I assume this is so if the server gets rebooted, so its not a stable fix.

As a hot solution you can download wdlib.php file and place it into the /usr/local/psa/admin/plib/modules/watchdog/ folder.
In this case there is no need to modify the config file.
Do not forget to make a backup of your original wdlib.php file.
please report back if there are some issues with it.

 

[dash]

Parallels/Plesk really need to have a publicly accessible bug tracker (at least for current Plesk owners) so we can report and track bugs/issues.

It should also include bugs/issues related to the integration of Plesk with 3rd party applications, even if it isn't officially a bug in the Plesk programming.


A lot of people are wasting a lot of time discussing issues and workarounds for Plesk related issues and a bug/issue tracker would save everyone a lot of time.

Aren't you afraid that clear reports will be buried in "mail does not works", "problem with autoinstaller", "nothing does not works", etc.?

 

[105547111]

dash,

The fix does NOT work on fedora 7!

Here is the new montrc file it makes:

if failed unixsocket /tmp/spamd_full.sock send "PING SPAMC/1.2\r\n\r\n" expect "SPAMD/[0-9]+(\.[0-9]+)* 0 PONG" with timeout 180 seconds then restart

But look at the log extract:

[EST Apr 11 08:08:06] GENERIC: receiving unexpected data [SPAMD/1.4 0 PONG

]
[EST Apr 11 08:08:06] 'psa_spamassassin' failed protocol test [generic] at UNIX[/tmp/spamd_full.sock].
[EST Apr 11 08:08:06] 'psa_spamassassin' trying to restart
[EST Apr 11 08:08:06] 'psa_spamassassin' stop: /usr/local/psa/admin/bin/spamd
[EST Apr 11 08:08:07] 'psa_spamassassin' start: /usr/local/psa/admin/bin/spamd

So better let support know the fix does not work on Fedora 7

It looks like there is a extra return or spaces after the pong in the log, but thats a straight copy and paste so that is the reponse its sending back.

I have attached the log.

 

[nforde]

Aren't you afraid that clear reports will be buried in "mail does not works", "problem with autoinstaller", "nothing does not works", etc.?

That happens with any bug tracking. It's up to the people in charge of it to filter out the dodgy bug reports. This is what's done with any bug tracker.

If it can work for hugely popular software like PHP (see http://bugs.php.net/) then it can work for Parallels/Plesk.

Having to submit bug reports via email is a bad, outdated method and doesn't allow the customers to know what's going on and whether things are bugs or not, and if they're scheduled to be fixed or not.

It's also a good bet that the internal bug tracking system for Plesk is pretty outdated or non-existent as well. Using a public bug tracking system forces the Plesk staff to use it, creating a much more structured bug fix allocation/scheduling system and ultimately a much more stable product and much happier customers.

Best of all, it would be very cheap and easy for them to implement since there are excellent opensource bug tracking options out there.