| View previous topic :: View next topic |
| Author |
Message |
MasquedAvenger
Guru
Joined: 21 Aug 2003
Posts: 559
Location: Southern California
|
 Posted: Tue Jun 26, 2007 7:20 pm Post subject: Clamd only creates a socket on reboot |
 |
|
Hey everyone. I have clamd set to start when the machine starts using its init script, and have it configured to create a socket in /var/run/clamav. After a couple days, the clamd daemon was killed for whatever reason, so I restarted the init script (and saw clamd tell me it was running as user amavis), but the pid and socket files weren't there. I did this a few times, then finally gave up and rebooted. After a reboot, when the init script started, the socket and the pid file were there as expected.
My question is, why can't the socket be re-created without a reboot? I thought that was very odd, to say the least. This is a server. I really can't reboot everytime the daemon decides to die 
Any ideas? Thanks 
James
_________________
"There are no uninteresting things; only uninterested people." --G.K. Chesterton |
|
| Back to top |
|
 |
magic919
Advocate
Joined: 17 Jun 2005
Posts: 2182
Location: Berkshire, UK
|
| Posted: Tue Jun 26, 2007 8:24 pm Post subject: |
|
|
Why do you think it cannot create the socket? I'm not convinced. Why do you say the daemon was killed? Do you check for presence of process or PID or socket when you decide it has been killed?
I never have to reboot any of mine for the sake of ClamAV. I don't run amavis though. |
|
| Back to top |
|
|
MasquedAvenger
Guru
Joined: 21 Aug 2003
Posts: 559
Location: Southern California
|
| Posted: Tue Jun 26, 2007 11:06 pm Post subject: |
|
|
| magic919 wrote: | Why do you think it cannot create the socket? I'm not convinced. Why do you say the daemon was killed? Do you check for presence of process or PID or socket when you decide it has been killed?
I never have to reboot any of mine for the sake of ClamAV. I don't run amavis though. |
I don't know why it can't create a socket. That's the purpose of this thread  I have no idea why the daemon was killed, other than when I checked on the machine a few days later, it was no longer running after having been started when the system first booted up (I checked to verify that the process was indeed no longer running.) As well, while the socket and the pid file existed in /var/run/clamav while the process was running, when it was not running, neither did the socket or the pid file exist. I tried starting the init script, verified that the process was indeed running (I used ps), and also verified that the socket still does not exist, nor the pid file, even though the daemon was restarted. It does exist, however, after the process starts after a reboot.
I wouldn'tve posted this in the first place unless I had checked everything I thought possible.
James
_________________
"There are no uninteresting things; only uninterested people." --G.K. Chesterton |
|
| Back to top |
|
|
magic919
Advocate
Joined: 17 Jun 2005
Posts: 2182
Location: Berkshire, UK
|
| Posted: Wed Jun 27, 2007 4:53 am Post subject: |
|
|
Maybe you need to re-read my reply. I am actually trying to help you after all.
I am asking where is the evidence that the problem is that ClamAV cannot create a socket. The mere lack of a socket does not prove it. And so on.
Perhaps you should look at strace. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
