Bug 23182 – clamd doesnt start after crash

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Martin Klebermass 2003-06-20 09:42:02 UTC]

When the server crashes the file /tmp/clam.sock already exists. 
A Test if the file exists before clam is started with the init script would be good, and  
on demand  remove the sock file before starting clam. 

Reproducible: Always
Steps to Reproduce:
1. Start Clamd 
2. Hit reset ;) 
3. try to start Clamd again 
Actual Results:  
clamd doenst start 

Expected Results:  
remove the clam.sock file and then start clam.

[Comment 1 klavs klavsen 2003-08-07 01:44:05 UTC]

Just hit this same issue.

I propose something like this in the start() function:

                if [ -e "/var/amavisd/clamd" ]; then
                    rm -f /var/amavisd/clamd
                fi
and ofcourse you should replace the hardlink to the socket file with something defined in the conf file.

[Comment 2 Dominik Stadler (RETIRED) 2003-12-05 08:58:43 UTC]

This bug seems to be the same as Bug 32448

[Comment 3 J Sacksteder 2004-02-26 07:40:21 UTC]

Please uncomment the 'FixStaleSocket' line in default /etc/clamav.conf file. If(when) clamd crashes, it fails to release the /tmp/clamd local socket. Making the option default to being enabled would eliminate this. 

The workaround is to manually delete /tmp/clamd and restart /etc/init.d/clamd.

[Comment 4 Hanno Böck 2004-03-02 07:13:11 UTC]

This is fixed in latest versions.