Issue after 9.5 upgrade

[JnascECSI]

I have 3 issues after upgrading to 9.5 this morning from the art plesk repo. All of a sudden i started getting beat up with the 3 ossec messages below and of course i have no clue on what could have caused these to start flooding my mail box. Any help would be great

Apr 24 08:26:53 inet3170 spamd[2950]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /var/qmail/mailnames///.spamassassin/auto-whitelist.lock.inet3170.xxxxxxxxxxxx.com.2950 for /var/qmail/mailnames///.spamassassin/auto-whitelist.lock: No such file or directory

Apr 24 08:02:35 inet3170 X-Qmail-Scanner-2.08st: [inet3170.xxxxxx.com127211055579013287] clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem - exit status 512/2

Apr 24 08:34:51 inet3170 X-Qmail-Scanner-2.08st: [inet3170.xxxxxxxx.com12721124907906894] Unable to close pipe to /var/qmail/bin/qmail-queue.orig [61] (#4.3.0) - Illegal seek

[JnascECSI]

Wow, Now getting these also...

Received From: inet3170->/var/log/messages
Rule: 1002 fired (level 2) -> "Unknown problem somewhere in the system."
Portion of the log(s):

Apr 24 09:40:38 inet3170 clamd[2572]: lstat() failed on: /var/www/vhosts/xxxxxxx.com/httpdocs/subpage4specials.html

[faris]

This is probably just clamd having fits. Try restarting it. If not then there's a chance that you updated clamd at the same time as you updated Plesk.

run /etc/crond.daily/freshclam to potentially cure directory permission problems then restart clamd

If that doesn't solve the problem run the qmail scanner reconfigurator (errr....qmail-scanner-reconfigure.sh or .pl or something?)

Or, if that doesn't help it may be that psa overwrote the qmail-scanner wrapper? Remove and re-install qmail-scanner in that case might solve it?

All these are just suggestions off the top of my head. Someone else may know exactly what to do, and all my suggestions may be a waste of time.

I'm assuming you have qmail-scanner installed of course. Of not, then maybe none of this will help.

Faris.

[mikeshinn]

Make sure clamd is running as root. lstat usually occurs if clamd cant read the file.

[scott]

ASL 2.2.6 from the testing channel is required for Plesk 9.5.x.

[JnascECSI]

Well i went and installed asl 2.2.6 from testing, re-installed qmail scanner and checked permissions on everything let it run for 24 hours and seems only issue i have left is the notification below still firing off. after qmail-scanner install i did run the reconfigure for it and said it was completed and all that jazz. Not sure if this issue requires spamassassin re-install or if i'm missing something. But it's killing my in-box every second with notifications.



Received From: inet3170->/var/log/psa/maillog
Rule: 1002 fired (level 2) -> "Unknown problem somewhere in the system."
Portion of the log(s):

Apr 26 07:40:30 inet3170 spamd[18967]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /var/qmail/mailnames///.spamassassin/auto-whitelist.lock.inet3170.xxxxxxxxxxxxx.com.18967 for /var/qmail/mailnames///.spamassassin/auto-whitelist.lock: No such file or directory

[faris]

We get there spamassassin errors too on one machine, but in a unrelated environment. I'd be curious to know the cause and cure.

Faris.

[JnascECSI]

Yes,
i'm still trying to figure out what's going on with these.... I went in and turned off all spam options in plesk, rebooted and then enabled them server wide and that made no change neither.

[mikeshinn]

Apr 26 07:40:30 inet3170 spamd[18967]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /var/qmail/mailnames///.spamassassin/auto-whitelist.lock.inet3170.xxxxxxxxxxxxx.com.18967 for /var/qmail/mailnames///.spamassassin/auto-whitelist.lock: No such file or director

Does that directory exist?

/var/qmail/mailnames///.spamassassin

[JnascECSI]

Mike,
looks to be there, i checked random domains and did'nt find any missing the /.spamassassin folder

/var/qmail/mailnames/xxxxxxx.com/emailname/.spamassassin

[mikeshinn]

Did you edit your error to remove the domain? If so, then check to make sure the permissions allow spammassasin to write to those domain .spamassassin directories. More than likely spamassassin is running as a user that cant write to them.

[JnascECSI]

Yes, i edited the error.

I found this which does'nt look right, is it me or should popuser have more permissions than what is listed? And could this be the problem?
Not sure what they should be and not really sure how and what it should have for permissions.

[xxxx@inet3170 ~]# ls -la /var/qmail/mailnames/domain.com/username/.spamassassin/
total 248
drwx------ 2 popuser popuser 4096 Apr 27 06:33 .
drwx------ 5 popuser popuser 4096 Apr 27 06:28 ..
-rw-r----- 1 popuser popuser 90112 Apr 27 06:33 auto-whitelist
-rw------- 1 popuser popuser 12288 Apr 27 06:33 bayes_seen
-rw------- 1 popuser popuser 172032 Apr 27 06:33 bayes_toks
-rw-r----- 1 popuser popuser 144 Apr 27 06:28 user_prefs
[root@inet3170 ~]#

[xetic]

Just curious if there are any updates to this...
I am using Plesk 9.5.2 w/ qmail (installed from atomic repos), CentOS 5.5, and latest updates from atomic repos
(mydom is my edit)

Code: Select all

Jun 22 17:35:40 plesk spamd[4626]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /var/qmail/mailnames/mydom.com/mail/.spamassassin/auto-whitelist.lock.mydom.com.4626 for /var/qmail/mailnames/mydom.com/mail/.spamassassin/auto-whitelist.lock: Permission denied

I found this which does'nt look right, is it me or should popuser have more permissions than what is listed? And could this be the problem?
Not sure what they should be and not really sure how and what it should have for permissions.

[xxxx@inet3170 ~]# ls -la /var/qmail/mailnames/domain.com/username/.spamassassin/
-rw-r----- 1 popuser popuser 90112 Apr 27 06:33 auto-whitelist
-rw------- 1 popuser popuser 12288 Apr 27 06:33 bayes_seen
-rw------- 1 popuser popuser 172032 Apr 27 06:33 bayes_toks
-rw-r----- 1 popuser popuser 144 Apr 27 06:28 user_prefs
[root@inet3170 ~]#

IMO that shoudl be fine, it has read / write access on everything and has read/write/execute permissions on the spamassassin directory:

Code: Select all

ls -la /var/qmail/mailnames/mydom.com/mail/
....
drwx------  2 popuser popuser 4096 Jun 22 06:56 .spamassassin

[xetic]

Noting there is a thread open @ parallels with a class file that seems to have resolved this issue for me:

http://forum.parallels.com/showthread.php?t=101248