Re: [qmailtoaster] Re: how to SA
Eric, Just an update on this.. I have cleaned all the accounts of this and fixed my irritating spam issue using spam assassin ruleset I had to write a rawbody rule that filtered the common statement within the html tags :) Once done set a score of 30 so it would just drop it. GOOD STUFF LOL thanks Dave On 06/21/2014 04:19 PM, Eric Shubert wrote: Duplicate messages in mailbox can result from: .) .qmail file in user's account that has 2 lines. This happens when the user's name is changed in qmailadmin (it's a bug). .) when scanning takes a long time, the sending smtp process (server or mail app) can time out before qmail-smtp acknowledges receipt. This happens most commonly with large emails submitted from Outlook that has insufficient timeout (should be max value). These are the conditions that come to mind for me regarding duplicates. HTH. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] supervise: fatal: unable to start log/run: file does not exist
I'm running Qmailtoaster utilities on CentOS6 VM on a XenServer. Data is stored on NFS. Over the weekend, the VM went into Read-Only file system due to a lag in communication. I had to manually run FSCK (there were errors and I told it to fix them) and reboot after restoring it to Read-Write mode. After doing so, I had errors from supervise. I managed to find information in the archives to let me fix the clamd/run error but the other one still persists and I have no idea what else I can do to fix it. I get a continuous stream of supervise: fatal: unable to start log/run: file does not exist. Running qmailctl stat results in the following: clamd: up (pid 12127) 6 seconds log: up (pid 12138) 1 seconds send: up (pid 8239) 1037 seconds smtp: up (pid 8245) 1037 seconds spamd: up (pid 11877) 96 seconds submission: up (pid 8244) 1037 seconds clamd/log: up (pid 8240) 1037 seconds send/log: up (pid 8277) 1032 seconds smtp/log: up (pid 8246) 1037 seconds spamd/log: up (pid 12139) 1 seconds submission/log: up (pid 8273) 1032 seconds Mail appears to be working okay inbound and outbound but the stream of error messages continues. I'm stumped. I really don't want to have to backup the database, rollback to an old snapshot, and restore the database but I might have to. I've tried starting up a copy of an old snapshot on another VM to check for differences but can't find anything obvious. Suggestions? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: how to SA
Would you care to share that SA rule? I've been getting some of those lately too. Perhaps we can get SA upstream to include that in their rules updates. Thanks. -- -Eric 'shubes' On 06/30/2014 07:05 AM, David wrote: Eric, Just an update on this.. I have cleaned all the accounts of this and fixed my irritating spam issue using spam assassin ruleset I had to write a rawbody rule that filtered the common statement within the html tags :) Once done set a score of 30 so it would just drop it. GOOD STUFF LOL thanks Dave On 06/21/2014 04:19 PM, Eric Shubert wrote: Duplicate messages in mailbox can result from: .) .qmail file in user's account that has 2 lines. This happens when the user's name is changed in qmailadmin (it's a bug). .) when scanning takes a long time, the sending smtp process (server or mail app) can time out before qmail-smtp acknowledges receipt. This happens most commonly with large emails submitted from Outlook that has insufficient timeout (should be max value). These are the conditions that come to mind for me regarding duplicates. HTH. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: supervise: fatal: unable to start log/run: file does not exist
On 06/30/2014 08:59 AM, Diana Calder wrote: I'm running Qmailtoaster utilities on CentOS6 VM on a XenServer. Data is stored on NFS. Over the weekend, the VM went into Read-Only file system due to a lag in communication. I had to manually run FSCK (there were errors and I told it to fix them) and reboot after restoring it to Read-Write mode. After doing so, I had errors from supervise. I managed to find information in the archives to let me fix the clamd/run error but the other one still persists and I have no idea what else I can do to fix it. I get a continuous stream of supervise: fatal: unable to start log/run: file does not exist. Running qmailctl stat results in the following: clamd: up (pid 12127) 6 seconds log: up (pid 12138) 1 seconds send: up (pid 8239) 1037 seconds smtp: up (pid 8245) 1037 seconds spamd: up (pid 11877) 96 seconds submission: up (pid 8244) 1037 seconds clamd/log: up (pid 8240) 1037 seconds send/log: up (pid 8277) 1032 seconds smtp/log: up (pid 8246) 1037 seconds spamd/log: up (pid 12139) 1 seconds submission/log: up (pid 8273) 1032 seconds Mail appears to be working okay inbound and outbound but the stream of error messages continues. I'm stumped. I really don't want to have to backup the database, rollback to an old snapshot, and restore the database but I might have to. I've tried starting up a copy of an old snapshot on another VM to check for differences but can't find anything obvious. Suggestions? You shouldn't have a /var/qmail/supervise/log directory. I think if you simply remove it (or move it aside to /root/ perhaps) then you'll be fine. Here's what I have in mine (COS6 with new packages): [root@tacs-mail ~]# ls -l /var/qmail/supervise/ total 20 drwx-T 4 qmaill qmail 4096 Apr 7 10:24 clamd drwx-T 4 qmaill qmail 4096 Mar 24 11:29 send drwx-T 4 qmaill qmail 4096 Mar 24 11:29 smtp drwx-T 4 qmaill qmail 4096 Apr 7 14:58 spamd drwx-T 4 qmaill qmail 4096 Mar 24 11:29 submission Note for posterity, clamav and spamd are very soon to be changed to use syslogd and initd instead of supervise and multilog. This is in preparation for COS7, which will be using systemd, at which point daemontools and ucscp-tcp will no longer be used by QMT. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] supervise: fatal: unable to start log/run: file does not exist
Hi Diana. Sounds like an error I have seen a couple of times in my QMT running in KVM : a run files is missing (/var/qmail/supervise/'smtp|clamd|spamd|send|submission' /run - and /var/qmail/supervise/ 'smtp|clamd|spamd|send|submission' /log/run ) Check to make sure the run files are present This is my /var/qmail/supervise/spamd/log/run file #!/bin/sh LOGSIZE=`cat /var/qmail/control/logsize` LOGCOUNT=`cat /var/qmail/control/logcount` exec /usr/bin/setuidgid qmaill /usr/bin/multilog t s$LOGSIZE n$LOGCOUNT /var/log/qmail/spamd Hope it helps Regards, Finn Den 30-06-2014 17:59, Diana Calder skrev: I'm running Qmailtoaster utilities on CentOS6 VM on a XenServer. Data is stored on NFS. Over the weekend, the VM went into Read-Only file system due to a lag in communication. I had to manually run FSCK (there were errors and I told it to fix them) and reboot after restoring it to Read-Write mode. After doing so, I had errors from supervise. I managed to find information in the archives to let me fix the clamd/run error but the other one still persists and I have no idea what else I can do to fix it. I get a continuous stream of supervise: fatal: unable to start log/run: file does not exist. Running qmailctl stat results in the following: clamd: up (pid 12127) 6 seconds log: up (pid 12138) 1 seconds send: up (pid 8239) 1037 seconds smtp: up (pid 8245) 1037 seconds spamd: up (pid 11877) 96 seconds submission: up (pid 8244) 1037 seconds clamd/log: up (pid 8240) 1037 seconds send/log: up (pid 8277) 1032 seconds smtp/log: up (pid 8246) 1037 seconds spamd/log: up (pid 12139) 1 seconds submission/log: up (pid 8273) 1032 seconds Mail appears to be working okay inbound and outbound but the stream of error messages continues. I'm stumped. I really don't want to have to backup the database, rollback to an old snapshot, and restore the database but I might have to. I've tried starting up a copy of an old snapshot on another VM to check for differences but can't find anything obvious. Suggestions? - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: supervise: fatal: unable to start log/run: file does not exist
Monday, June 30, 2014, 1:21:28 PM, Eric wrote: You shouldn't have a /var/qmail/supervise/log directory. I think if you simply remove it (or move it aside to /root/ perhaps) then you'll be fine. I DIDN'T have one when the errors started. I also checked an old snapshot of the Qmail server and it didn't have one either. Despite that, I tried creating one to see if it would resolve the problem. No such luck, so I removed it again. Here's what I have in mine (COS6 with new packages): [root@tacs-mail ~]# ls -l /var/qmail/supervise/ total 20 drwx-T 4 qmaill qmail 4096 Apr 7 10:24 clamd drwx-T 4 qmaill qmail 4096 Mar 24 11:29 send drwx-T 4 qmaill qmail 4096 Mar 24 11:29 smtp drwx-T 4 qmaill qmail 4096 Apr 7 14:58 spamd drwx-T 4 qmaill qmail 4096 Mar 24 11:29 submission Yes, I have the same directories actually present: [root@qmail ~]# ls -l /var/qmail/supervise total 20 drwx-T 4 qmaill qmail 4096 Jun 30 10:00 clamd drwx-T 4 qmaill qmail 4096 Mar 4 10:15 send drwx-T 4 qmaill qmail 4096 Apr 11 12:13 smtp drwx-T 4 qmaill qmail 4096 Jun 23 10:35 spamd drwx-T 4 qmaill qmail 4096 Apr 11 15:39 submission Still getting the same error: [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# supervise: fatal: unable to start log/run: file does not exist supervise: fatal: unable to start log/run: file does not exist *sigh* Even though mail seems to be working, all is obviously not well with the server. Memory stays maxed out at 8Gb and the CPU at 100%. Here's my qmail startup script: [root@qmail ~]# cat /etc/rc.d/init.d/qmail #!/bin/sh # # qmailStartup script for QmailToaster MTA # # chkconfig: 345 55 45 # description: Qmailtoaster MTA # # Udated May 19, 2006 # Nick Hemmesch n...@ndhsoft.com # # Source function library. if [ -f /etc/init.d/functions ]; then . /etc/init.d/functions elif [ -f /etc/rc.d/init.d/functions ]; then . /etc/rc.d/init.d/functions fi PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin export PATH case $1 in start) # have a silent kill in case someone tries to start the service when it # is already running $0 stop /dev/null 21 echo -n Starting qmail-toaster: svscan cd /var/qmail/supervise env - PATH=$PATH svscan echo $! /var/run/qmail-svscan.pid touch /var/lock/subsys/qmail echo . ;; stop) echo -n Stopping qmail-toaster: svscan kill `cat /var/run/qmail-svscan.pid` echo -n qmail svc -dx /var/qmail/supervise/* echo -n logging svc -dx /var/qmail/supervise/*/log echo . rm -rf /var/run/qmail-svscan.pid rm -rf /var/lock/subsys/qmail ;; stat) cd /var/qmail/supervise svstat * */log ;; doqueue|alrm) echo Sending ALRM signal to qmail-send. svc -a /var/qmail/supervise/send ;; queue) /var/qmail/bin/qmail-qstat /var/qmail/bin/qmail-qread ;; reload|hup) echo Sending HUP signal to qmail-send. svc -h /var/qmail/supervise/send ;; pause) echo Pausing qmail-send svc -p /var/qmail/supervise/send echo Pausing qmail-smtpd svc -p /var/qmail/supervise/smtp ;; cont) echo Continuing qmail-send svc -c /var/qmail/supervise/send echo Continuing qmail-smtpd svc -c /var/qmail/supervise/smtp ;; restart) echo Restarting qmail: echo * Stopping qmail-smtpd. svc -d /var/qmail/supervise/smtp echo * Sending qmail-send SIGTERM and restarting. svc -t /var/qmail/supervise/send echo * Restarting qmail-smtpd. svc -u /var/qmail/supervise/smtp ;; cdb) tcprules /etc/tcprules.d/tcp.smtp.cdb /etc/tcprules.d/tcp.smtp.tmp /etc/tcprules.d/tcp.smtp chmod 644 /etc/tcprules.d/tcp.smtp* echo Reloaded /etc/tcprules.d/tcp.smtp if [ -f /var/qmail/bin/qmail-badmimetypes ] ; then /var/qmail/bin/qmail-badmimetypes; echo Reloaded /var/qmail/control/badmimetypes.cdb; fi if [ -f /var/qmail/bin/qmail-badloadertypes ] ; then /var/qmail/bin/qmail-badloadertypes; echo Reloaded /var/qmail/control/badloadertypes.cdb; fi if [ -f /var/qmail/bin/simscanmk ] ; then /var/qmail/bin/simscanmk -g /dev/null 21; echo Reloaded /var/qmail/control/simversions.cdb; if [ -f /var/qmail/control/simcontrol ] ; then /var/qmail/bin/simscanmk /dev/null 21; echo Reloaded /var/qmail/control/simcontrol.cdb; fi fi ;; help) cat HELP stop -- stops mail service (smtp connections refused, nothing goes out) start -- starts mail service (smtp connection accepted, mail can go out) pause -- temporarily stops mail service (connections accepted, nothing leaves) cont -- continues paused mail service stat -- displays status of mail service cdb -- rebuild the tcpserver cdb file for smtp restart -- stops and restarts smtp, sends qmail-send a TERM restarts it doqueue -- sends qmail-send ALRM, scheduling queued messages for delivery reload -- sends qmail-send HUP, rereading locals and virtualdomains queue
[qmailtoaster] Re: supervise: fatal: unable to start log/run: file does not exist
Unfortunately, the error message doesn't appear to say which log file it's having a problem with. I'm going to guess it's clamav, since that's being moved. I probably need to have the clamav package remove some leftover stuff. First, verify that clamav is logging to /var/log/maillog. If it's not, then I wonder which clamav package you have installed. This should fix you up: # cd /var/qmail/supervise/clamd # mv log log.old I'm guessing that'll take care of things. Sorry I haven't tested the latest package better. I hope to get to that this week. Thanks. -- -Eric 'shubes' On 06/30/2014 10:50 AM, Diana Calder wrote: Monday, June 30, 2014, 1:21:28 PM, Eric wrote: You shouldn't have a /var/qmail/supervise/log directory. I think if you simply remove it (or move it aside to /root/ perhaps) then you'll be fine. I DIDN'T have one when the errors started. I also checked an old snapshot of the Qmail server and it didn't have one either. Despite that, I tried creating one to see if it would resolve the problem. No such luck, so I removed it again. Here's what I have in mine (COS6 with new packages): [root@tacs-mail ~]# ls -l /var/qmail/supervise/ total 20 drwx-T 4 qmaill qmail 4096 Apr 7 10:24 clamd drwx-T 4 qmaill qmail 4096 Mar 24 11:29 send drwx-T 4 qmaill qmail 4096 Mar 24 11:29 smtp drwx-T 4 qmaill qmail 4096 Apr 7 14:58 spamd drwx-T 4 qmaill qmail 4096 Mar 24 11:29 submission Yes, I have the same directories actually present: [root@qmail ~]# ls -l /var/qmail/supervise total 20 drwx-T 4 qmaill qmail 4096 Jun 30 10:00 clamd drwx-T 4 qmaill qmail 4096 Mar 4 10:15 send drwx-T 4 qmaill qmail 4096 Apr 11 12:13 smtp drwx-T 4 qmaill qmail 4096 Jun 23 10:35 spamd drwx-T 4 qmaill qmail 4096 Apr 11 15:39 submission Still getting the same error: [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# supervise: fatal: unable to start log/run: file does not exist supervise: fatal: unable to start log/run: file does not exist *sigh* Even though mail seems to be working, all is obviously not well with the server. Memory stays maxed out at 8Gb and the CPU at 100%. Here's my qmail startup script: [root@qmail ~]# cat /etc/rc.d/init.d/qmail #!/bin/sh # # qmailStartup script for QmailToaster MTA # # chkconfig: 345 55 45 # description: Qmailtoaster MTA # # Udated May 19, 2006 # Nick Hemmesch n...@ndhsoft.com # # Source function library. if [ -f /etc/init.d/functions ]; then . /etc/init.d/functions elif [ -f /etc/rc.d/init.d/functions ]; then . /etc/rc.d/init.d/functions fi PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin export PATH case $1 in start) # have a silent kill in case someone tries to start the service when it # is already running $0 stop /dev/null 21 echo -n Starting qmail-toaster: svscan cd /var/qmail/supervise env - PATH=$PATH svscan echo $! /var/run/qmail-svscan.pid touch /var/lock/subsys/qmail echo . ;; stop) echo -n Stopping qmail-toaster: svscan kill `cat /var/run/qmail-svscan.pid` echo -n qmail svc -dx /var/qmail/supervise/* echo -n logging svc -dx /var/qmail/supervise/*/log echo . rm -rf /var/run/qmail-svscan.pid rm -rf /var/lock/subsys/qmail ;; stat) cd /var/qmail/supervise svstat * */log ;; doqueue|alrm) echo Sending ALRM signal to qmail-send. svc -a /var/qmail/supervise/send ;; queue) /var/qmail/bin/qmail-qstat /var/qmail/bin/qmail-qread ;; reload|hup) echo Sending HUP signal to qmail-send. svc -h /var/qmail/supervise/send ;; pause) echo Pausing qmail-send svc -p /var/qmail/supervise/send echo Pausing qmail-smtpd svc -p /var/qmail/supervise/smtp ;; cont) echo Continuing qmail-send svc -c /var/qmail/supervise/send echo Continuing qmail-smtpd svc -c /var/qmail/supervise/smtp ;; restart) echo Restarting qmail: echo * Stopping qmail-smtpd. svc -d /var/qmail/supervise/smtp echo * Sending qmail-send SIGTERM and restarting. svc -t /var/qmail/supervise/send echo * Restarting qmail-smtpd. svc -u /var/qmail/supervise/smtp ;; cdb) tcprules /etc/tcprules.d/tcp.smtp.cdb /etc/tcprules.d/tcp.smtp.tmp /etc/tcprules.d/tcp.smtp chmod 644 /etc/tcprules.d/tcp.smtp* echo Reloaded /etc/tcprules.d/tcp.smtp if [ -f /var/qmail/bin/qmail-badmimetypes ] ; then /var/qmail/bin/qmail-badmimetypes; echo Reloaded /var/qmail/control/badmimetypes.cdb; fi if [ -f /var/qmail/bin/qmail-badloadertypes ] ; then /var/qmail/bin/qmail-badloadertypes; echo Reloaded /var/qmail/control/badloadertypes.cdb; fi if [ -f /var/qmail/bin/simscanmk ] ; then /var/qmail/bin/simscanmk -g /dev/null 21; echo Reloaded /var/qmail/control/simversions.cdb; if [ -f /var/qmail/control/simcontrol ] ; then /var/qmail/bin/simscanmk
Re: [qmailtoaster] /tmp/clamd.socket is in use by another process was Re: supervise: fatal: unable to start log/run: file does not exist
Monday, June 30, 2014, 3:05:30 PM, Eric wrote: Unfortunately, the error message doesn't appear to say which log file it's having a problem with. I'm going to guess it's clamav, since that's being moved. I probably need to have the clamav package remove some leftover stuff. First, verify that clamav is logging to /var/log/maillog. If it's not, then I wonder which clamav package you have installed. It was installed by the qmailtoaster install script when the one for COS6 was still running from the testing repos. It is logging to /var/log/maillog. This should fix you up: # cd /var/qmail/supervise/clamd # mv log log.old Done. But... I'm guessing that'll take care of things. Nope, no such luck. Same error. However, once I removed log.old it cleared up the error when I did a qmailctl start - so, that's one problem solved. Unfortunately, now it's throwing an error: ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. Tried rebooting the VM and I spotted this in the bootup messages: Starting qmail-toaster: svscan. Starting sshd: [ OK ] Starting xinetd: [ OK ] Starting ntpd: [ OK ] Starting Clam AntiVirus Daemon: ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. [ OK ] Starting freshclam: [ OK ] Starting mysqld: [ OK ] Starting Dovecot Imap: [ OK ] Starting vusaged: started Starting httpd: [ OK ] Starting crond: [ OK ] Renamed /tmp/clamd.socket and started qmailctl - looked okay. Rebooted to check and the socket file in use error is back. So, is clamd trying to start twice? Once via svscan and once on its own? I did run a yum update when I first saw the errors, on the offchance that it would fix the problem - maybe something odd happened there? More testing... [root@qmail ~]# /etc/init.d/clamd stop ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. [root@qmail ~]# /etc/init.d/clamd stop Stopping Clam AntiVirus Daemon: [ OK ] [root@qmail ~]# qmailctl stop Stopping qmail-toaster: svscan qmail logging. [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. qmailctl stop Stopping qmail-toaster: svscan qmail logging. [root@qmail ~]# /etc/init.d/clamd stop Stopping Clam AntiVirus Daemon: [ OK ] [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. qmailctl stat clamd: up (pid 2678) 8 seconds send: up (pid 2562) 82 seconds smtp: up (pid 2569) 82 seconds spamd: up (pid 2571) 82 seconds submission: up (pid 2566) 82 seconds send/log: up (pid 2568) 82 seconds smtp/log: up (pid 2570) 82 seconds submission/log: up (pid 2567) 82 seconds So, clamd keeps starting and stopping and restarting. *sigh* Now what? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] /tmp/clamd.socket is in use by another process was Re: supervise: fatal: unable to start log/run: file does not exist
Hi Diana. I've also had this thing happening to my system - check if You have clamd starting in the init.d directory - my issue was that I happended to get clamd installed by another repo file which put the clamd startup script under /etc/init.d (and linked to which ever rcX.d You are using - so check that out (clamd will be handled by QMT /var/qmail/supervise...) Hope this can be helpfull? Cheers Finn Den 30-06-2014 22:42, Diana Calder skrev: Monday, June 30, 2014, 3:05:30 PM, Eric wrote: Unfortunately, the error message doesn't appear to say which log file it's having a problem with. I'm going to guess it's clamav, since that's being moved. I probably need to have the clamav package remove some leftover stuff. First, verify that clamav is logging to /var/log/maillog. If it's not, then I wonder which clamav package you have installed. It was installed by the qmailtoaster install script when the one for COS6 was still running from the testing repos. It is logging to /var/log/maillog. This should fix you up: # cd /var/qmail/supervise/clamd # mv log log.old Done. But... I'm guessing that'll take care of things. Nope, no such luck. Same error. However, once I removed log.old it cleared up the error when I did a qmailctl start - so, that's one problem solved. Unfortunately, now it's throwing an error: ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. Tried rebooting the VM and I spotted this in the bootup messages: Starting qmail-toaster: svscan. Starting sshd: [ OK ] Starting xinetd: [ OK ] Starting ntpd: [ OK ] Starting Clam AntiVirus Daemon: ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. [ OK ] Starting freshclam: [ OK ] Starting mysqld: [ OK ] Starting Dovecot Imap: [ OK ] Starting vusaged: started Starting httpd: [ OK ] Starting crond: [ OK ] Renamed /tmp/clamd.socket and started qmailctl - looked okay. Rebooted to check and the socket file in use error is back. So, is clamd trying to start twice? Once via svscan and once on its own? I did run a yum update when I first saw the errors, on the offchance that it would fix the problem - maybe something odd happened there? More testing... [root@qmail ~]# /etc/init.d/clamd stop ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. [root@qmail ~]# /etc/init.d/clamd stop Stopping Clam AntiVirus Daemon: [ OK ] [root@qmail ~]# qmailctl stop Stopping qmail-toaster: svscan qmail logging. [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. qmailctl stop Stopping qmail-toaster: svscan qmail logging. [root@qmail ~]# /etc/init.d/clamd stop Stopping Clam AntiVirus Daemon: [ OK ] [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. qmailctl stat clamd: up (pid 2678) 8 seconds send: up (pid 2562) 82 seconds smtp: up (pid 2569) 82 seconds spamd: up (pid 2571) 82 seconds submission: up (pid 2566) 82 seconds send/log: up (pid 2568) 82 seconds smtp/log: up (pid 2570) 82 seconds submission/log: up (pid 2567) 82 seconds So, clamd keeps starting and stopping and restarting. *sigh* Now what? - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
