Nigel Horne wrote:
On Friday 13 May 2005 11:52, George Chelidze wrote:
George Chelidze wrote:
Hello,
System: RH 7.3, kernel: 2.4.24, gcc 2.96
I tried to upgrade to 0.85 this morning. Everything compiled just fine,
clamd started fine but clamav-milter doesn't start. It outputs the
following in debug mode:
LibClamAV debug: Running as user clamav (UID 101, GID 11)
LibClamAV debug: pingServer-1: sending VERSION
LibClamAV debug: Setting /tmp as global temporary directory
LibClamAV debug: Making /tmp/clamav-71886380fcea2de4
and then nothing. /tmp/clamav-71886380fcea2de4 has been created. Anyone
seeing the same on their systems? Any ideas?
Here are my config files:
clamav-milter starts this way:
daemon /usr/sbin/chroot /usr/local/clamav /sbin/clamav-milter
${CLAMAV_FLAGS}
clamav-milter.conf
CLAMAV_FLAGS="-c /etc/clamd.conf -nlPH unix:/ctl/clamav-milter.ctl
--external"
clamd.conf
LogFile /var/log/clamd.log
LogFileMaxSize 20M
LogTime
LogFacility LOG_MAIL
LogSyslog
PidFile /var/run/clamd.pid
TemporaryDirectory /tmp
DatabaseDirectory /bases
LocalSocket /ctl/clamd.ctl
FixStaleSocket
ExitOnOOM
MaxConnectionQueueLength 30
StreamMaxLength 10M
MaxThreads 64
ReadTimeout 180
IdleTimeout 30
MaxDirectoryRecursion 15
SelfCheck 3600
User clamav
ScanPE
ScanHTML
ScanOLE2
ScanMail
ScanArchive
ScanRAR
ArchiveMaxFileSize 10M
ArchiveMaxRecursion 5
ArchiveMaxFiles 1000
ArchiveMaxCompressionRatio 200
Found a problem:
/usr/local/clamav/var/log/clamd.log was owned by root:root mode 640
versions below 0.85 did not report any problems with that, while 0.85 did:
May 13 14:39:32 ns chroot: /var/log/clamd.log: Permission denied
May 13 14:39:32 ns clamav-milter: chroot startup succeeded
Clamav-milter versions prior to 0.85 tended to not notice that permissions
issue,
the error message is more likely to appear in 0.85. It is probable that the
issue
has been on your machine from the year dot, but never been reported...
Yes, I think this is the case. Thanks for your help.
I have changed it to clamav:clamav 640 and now everything works fine.
Thanks to Nigel who encouraged me to look at my logs once again. The
reason I failed to find these messages earlier was that they were found
in /var/log/boot.log.
--
George Chelidze
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
