Hello list.

having upgraded to the current version 0.96.1 on a Suse Linux 10.3 the
clamd daemon won't start. I get the same error other users have
described some time ago:

==================
Tue May 25 15:57:27 2010 -> +++ Started at Tue May 25 15:57:27 2010
Tue May 25 15:57:27 2010 -> clamd daemon 0.96.1 (OS: linux-gnu, ARCH:
i386, CPU: i686)
Tue May 25 15:57:27 2010 -> Log file size limit disabled.
Tue May 25 15:57:27 2010 -> Reading databases from /usr/local/share/clamav
Tue May 25 15:57:27 2010 -> Not loading PUA signatures.
Tue May 25 15:57:34 2010 -> Loaded 787256 signatures.
Tue May 25 15:57:34 2010 -> LOCAL: Unix socket file /tmp/clamd.socket
Tue May 25 15:57:34 2010 -> LOCAL: Setting connection queue length to 15
Tue May 25 15:57:34 2010 -> ERROR: daemonize() failed
Tue May 25 15:57:34 2010 -> Closing the main socket.
Tue May 25 15:57:34 2010 -> Socket file removed.
===================

In some other thread was a hint to "inusufficient memory2 but in my
machine there seems a lot free:
===================

h830101:/var/log # cat /proc/meminfo
MemTotal:      5122676 kB
MemFree:       4886028 kB
Buffers:             0 kB
Cached:              0 kB
SwapCached:          0 kB
Active:              0 kB
Inactive:            0 kB
HighTotal:     3068392 kB
HighFree:      3068392 kB
LowTotal:      2054284 kB
LowFree:       1817636 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
AnonPages:           0 kB
Mapped:         236648 kB
Slab:                0 kB
PageTables:          0 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:         0 kB
Committed_AS:   420200 kB
VmallocTotal:        0 kB
VmallocUsed:         0 kB
VmallocChunk:        0 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

==========================

Where to look now?

Mike

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to