Re: ClamAV execusion died without error messages
In response to Ming Tang mtan...@comcast.net: I did not find any other error messages in log files. The following lines appeared in the section for kernel log messages in daily email message for Security Run Output. pid 840 (freshclam), uid 1#: exited on signal 11 This is a segmentation violation. It means the program is trying to access memory that it never allocated (i.e., it's trying to access memory belonging to another process). This generally happens in 1 of 3 cases: 1) The program is a virus, etc trying to steal data from other programs. 2) The program was written poorly and has memory management bugs. 3) Your hardware (RAM) is buggy and memory bits are flipping by accident causing unpredictable memory access. http://en.wikipedia.org/wiki/Segmentation_violation pid 875 (clamd), uid 1#: exited on signal 10 This is a more unusual error, but still related to memory: http://en.wikipedia.org/wiki/Bus_error This error is more difficult to create using software than a segfault. My theory at this point is that you either a) downloaded precompiled packages that are not supported by your hardware. b) built these from ports with funky CFLAGS settings My recommendation would be to start out by deinstalling clam, and rebuilding it from ports, ensuring that your /etc/make.conf settings are all set to defaults. If the problem persists, install a program like memtest86, or use some other RAM tester to ensure that your hardware is solid. HTH -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ClamAV execusion died without error messages
I did not find any other error messages in log files. The following lines appeared in the section for kernel log messages in daily email message for Security Run Output. pid 840 (freshclam), uid 1#: exited on signal 11 pid 875 (clamd), uid 1#: exited on signal 10 I am not sure what they mean exactly. Thanks. - Ming -Original Message- From: Bill Moran [mailto:wmo...@potentialtech.com] Sent: Sunday, March 01, 2009 6:37 PM To: Ming Tang Cc: freebsd-questions@freebsd.org Subject: Re: ClamAV execusion died without error messages Ming Tang mtan...@comcast.net wrote: Bill, Thank you for the response. I tried and did not figure out where is the problem. I am attaching the command line prompts and clamd.log and freshclam.log content here. ns1# ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ./clamav-clamd.sh start Starting clamav_clamd. LibClamAV Warning: ** LibClamAV Warning: *** The virus database is older than 7 days! *** LibClamAV Warning: *** Please update it as soon as possible.*** LibClamAV Warning: ** ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ns1# cat clamd.log +++ Started at Sat Feb 28 10:43:36 2009 clamd daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) Running as user clamav (UID 1#, GID 1#) Log file size limited to 1048576 bytes. Reading databases from /var/db/clamav Not loading PUA signatures. Loaded 455125 signatures. LOCAL: Removing stale socket file /var/run/clamav/clamd.sock LOCAL: Unix socket file /var/run/clamav/clamd.sock LOCAL: Setting connection queue length to 15 Limits: Global size limit set to 104857600 bytes. Limits: File size limit set to 26214400 bytes. Limits: Recursion level limit set to 16. Limits: Files limit set to 1. Archive support enabled. Algorithmic detection enabled. Portable Executable support enabled. ELF support enabled. Mail files support enabled. OLE2 support enabled. PDF support enabled. HTML support enabled. Self checking every 1800 seconds. .. ns1# ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ./clamav-freshclam.sh start Starting clamav_freshclam. ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ns1# cat freshclam1.log -- freshclam daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) That's certainly strange. Try starting the processes manually instead of using the rc scripts, and see if they exit with an error of some sort. Also, I seem to remember having difficult with permissions under some circumstances, where the processes couldn't write to directories they needed -- check that both clamd and freshclam are running as the same user/group. See if you're getting core files anywhere (check /var/log/messages for coredump messages). Audit your config files and make sure nothing is out of sorts. Sorry I can't give you any more specific information, but I've not seen the problem you're having. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ClamAV execusion died without error messages
Ming Tang mtan...@comcast.net wrote: Bill, Thank you for the response. I tried and did not figure out where is the problem. I am attaching the command line prompts and clamd.log and freshclam.log content here. ns1# ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ./clamav-clamd.sh start Starting clamav_clamd. LibClamAV Warning: ** LibClamAV Warning: *** The virus database is older than 7 days! *** LibClamAV Warning: *** Please update it as soon as possible.*** LibClamAV Warning: ** ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ns1# cat clamd.log +++ Started at Sat Feb 28 10:43:36 2009 clamd daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) Running as user clamav (UID 1#, GID 1#) Log file size limited to 1048576 bytes. Reading databases from /var/db/clamav Not loading PUA signatures. Loaded 455125 signatures. LOCAL: Removing stale socket file /var/run/clamav/clamd.sock LOCAL: Unix socket file /var/run/clamav/clamd.sock LOCAL: Setting connection queue length to 15 Limits: Global size limit set to 104857600 bytes. Limits: File size limit set to 26214400 bytes. Limits: Recursion level limit set to 16. Limits: Files limit set to 1. Archive support enabled. Algorithmic detection enabled. Portable Executable support enabled. ELF support enabled. Mail files support enabled. OLE2 support enabled. PDF support enabled. HTML support enabled. Self checking every 1800 seconds. .. ns1# ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ./clamav-freshclam.sh start Starting clamav_freshclam. ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ns1# cat freshclam1.log -- freshclam daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) That's certainly strange. Try starting the processes manually instead of using the rc scripts, and see if they exit with an error of some sort. Also, I seem to remember having difficult with permissions under some circumstances, where the processes couldn't write to directories they needed -- check that both clamd and freshclam are running as the same user/group. See if you're getting core files anywhere (check /var/log/messages for coredump messages). Audit your config files and make sure nothing is out of sorts. Sorry I can't give you any more specific information, but I've not seen the problem you're having. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ClamAV execusion died without error messages
Bill, Thank you for the response. I tried and did not figure out where is the problem. I am attaching the command line prompts and clamd.log and freshclam.log content here. ns1# ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ./clamav-clamd.sh start Starting clamav_clamd. LibClamAV Warning: ** LibClamAV Warning: *** The virus database is older than 7 days! *** LibClamAV Warning: *** Please update it as soon as possible.*** LibClamAV Warning: ** ns1# ./clamav-clamd.sh status clamav_clamd is not running. ns1# ns1# cat clamd.log +++ Started at Sat Feb 28 10:43:36 2009 clamd daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) Running as user clamav (UID 1#, GID 1#) Log file size limited to 1048576 bytes. Reading databases from /var/db/clamav Not loading PUA signatures. Loaded 455125 signatures. LOCAL: Removing stale socket file /var/run/clamav/clamd.sock LOCAL: Unix socket file /var/run/clamav/clamd.sock LOCAL: Setting connection queue length to 15 Limits: Global size limit set to 104857600 bytes. Limits: File size limit set to 26214400 bytes. Limits: Recursion level limit set to 16. Limits: Files limit set to 1. Archive support enabled. Algorithmic detection enabled. Portable Executable support enabled. ELF support enabled. Mail files support enabled. OLE2 support enabled. PDF support enabled. HTML support enabled. Self checking every 1800 seconds. .. ns1# ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ./clamav-freshclam.sh start Starting clamav_freshclam. ns1# ./clamav-freshclam.sh status clamav_freshclam is not running. ns1# ns1# cat freshclam1.log -- freshclam daemon 0.94.1 (OS: freebsd5.4, ARCH: i386, CPU: i386) Thanks. - Ming -Original Message- From: Bill Moran [mailto:wmo...@potentialtech.com] Sent: Friday, February 27, 2009 1:57 PM To: mtan...@comcast.net Cc: freebsd-questions@freebsd.org Subject: Re: ClamAV execusion died without error messages In response to mtan...@comcast.net: My server is currently running on FreeBSD 5.4-RELEASE #0. I installed the port software, P5-Mail-ClamAV with sendmail along with others: Spamassassin and Milter etc. Everything was compiled fine, and sendmail is working with Spamassin too. However, when I execute clamav-clamd.sh, clamav-freshclam.sh, both software start for a very short momonet and died without any complaims. I could not see any clamav items running by executing 'ps -axw'. My last executed piece software, clamav-milter.sh is complaining missing and waiting for a socket, clam-milter.sorc. I did configuration for sendmail, but very littler on clamav. Can anyone familiar with Clamav helps to provide a clue on what is going wrong? The rc script isn't going to tell you anything. Look at your clamd.conf to see where it's logging to, then look at the log files to see what's going wrong. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ClamAV execusion died without error messages
In response to mtan...@comcast.net: My server is currently running on FreeBSD 5.4-RELEASE #0. I installed the port software, P5-Mail-ClamAV with sendmail along with others: Spamassassin and Milter etc. Everything was compiled fine, and sendmail is working with Spamassin too. However, when I execute clamav-clamd.sh, clamav-freshclam.sh, both software start for a very short momonet and died without any complaims. I could not see any clamav items running by executing 'ps -axw'. My last executed piece software, clamav-milter.sh is complaining missing and waiting for a socket, clam-milter.sorc. I did configuration for sendmail, but very littler on clamav. Can anyone familiar with Clamav helps to provide a clue on what is going wrong? The rc script isn't going to tell you anything. Look at your clamd.conf to see where it's logging to, then look at the log files to see what's going wrong. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
