Hi List, Since yesterday afternoon, the clamd daemon on 2 of our 3 mailrelays has suddenly stopped working. the process just seems to quit, nothing in the logfiles, I can start it up but after approx. 4 or 5 minutes, the process quits again.
This is on 2 mailrelays that are completely independent, and nothing has changed on the config, so I suspect something with a pattern update from freshclam ? we are running on solaris 10 intel (in root zone), version is 0.91.1 Anyone else encountered this ? I've set logverbose yes but not much comes in the clamd.log file, this is what is written in it If I restart the clamd process: +++ Started at Thu Aug 2 14:12:37 2007 clamd daemon 0.91.1 (OS: solaris2.10, ARCH: i386, CPU: i386) Running as user defang (UID 103, GID 101) Log file size limited to 1048576 bytes. Reading databases from /usr/local/share/clamav Loaded 142101 signatures. Unix socket file /var/spool/MIMEDefang/clamd.sock Setting connection queue length to 15 Archive: Archived file size limit set to 10485760 bytes. Archive: Recursion level limit set to 8. Archive: Files limit set to 1000. Archive: Compression ratio limit set to 250. Archive support enabled. Algorithmic detection enabled. Portable Executable support enabled. ELF support enabled. Mail files support enabled. Mail: Recursion level limit set to 64. OLE2 support enabled. PDF support disabled. HTML support enabled. Self checking every 1800 seconds. When the process quits, nothing else is written to it. Any ideas ? I tried with the development version, but same deal. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
