Re: [Clamav-users] clamd problem
Oliver, Am/On Mon, 24 Sep 2007 13:21:50 +0200 schrieb/wrote Oliver Schwarz: look into the config file of clamav. there's an option which lets it fix stale sockets. thanks a lot, that did the trick :-) Thanks and all the best Matthias ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamd problem
Am/On Sun, 23 Sep 2007 20:33:57 -0700 schrieb/wrote Dennis Peterson: Matthias Schmidt wrote: Hello, I have a little problem with clamd: the process terminates, because: Socket file /tmp/clamd is in use by another process. now I have no glue, which other process could use the socket file from clamd. I set the permissions to 777 on the end, but didn't help. The original user and group is clamav. So it seams to be not a permission problem. This all runs on a Mac OS 10.4.10 Server with clamav 0.91.2 Run lsof to see what processes have the socket open. Use ktrace and kdump to see what is happening when the process is started. Explain how clamd is started and how it is restarted. What other processes use /tmp/clamd? (see lsof). that's the strange thing, the socket is not open when I start clamd by hand it works and the socket is owned by clamav as expected. Looks like it's a problem with launchctl or the associated plist. Thanks and all the best Matthias ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamd problem
matthias, use the launchctl unload command, then remove the socket file, then restart the server. usually this should clean out the problems. oliver Am 24.09.2007 um 12:10 schrieb Matthias Schmidt: Am/On Sun, 23 Sep 2007 20:33:57 -0700 schrieb/wrote Dennis Peterson: Matthias Schmidt wrote: Hello, I have a little problem with clamd: the process terminates, because: Socket file /tmp/clamd is in use by another process. now I have no glue, which other process could use the socket file from clamd. I set the permissions to 777 on the end, but didn't help. The original user and group is clamav. So it seams to be not a permission problem. This all runs on a Mac OS 10.4.10 Server with clamav 0.91.2 Run lsof to see what processes have the socket open. Use ktrace and kdump to see what is happening when the process is started. Explain how clamd is started and how it is restarted. What other processes use /tmp/clamd? (see lsof). that's the strange thing, the socket is not open when I start clamd by hand it works and the socket is owned by clamav as expected. Looks like it's a problem with launchctl or the associated plist. Thanks and all the best Matthias ___ Help us build a comprehensive ClamAV guide: visit http:// wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamd problem
Hello Oliver, Am/On Mon, 24 Sep 2007 12:20:08 +0200 schrieb/wrote Oliver Schwarz: matthias, use the launchctl unload command, then remove the socket file, then restart the server. usually this should clean out the problems. well, I just killed clamd and restarted it with launchctl load -w ... and now it works. The problem occurs after a restart of the box. best Matthias oliver Am 24.09.2007 um 12:10 schrieb Matthias Schmidt: Am/On Sun, 23 Sep 2007 20:33:57 -0700 schrieb/wrote Dennis Peterson: Matthias Schmidt wrote: Hello, I have a little problem with clamd: the process terminates, because: Socket file /tmp/clamd is in use by another process. now I have no glue, which other process could use the socket file from clamd. I set the permissions to 777 on the end, but didn't help. The original user and group is clamav. So it seams to be not a permission problem. This all runs on a Mac OS 10.4.10 Server with clamav 0.91.2 Run lsof to see what processes have the socket open. Use ktrace and kdump to see what is happening when the process is started. Explain how clamd is started and how it is restarted. What other processes use /tmp/clamd? (see lsof). that's the strange thing, the socket is not open when I start clamd by hand it works and the socket is owned by clamav as expected. Looks like it's a problem with launchctl or the associated plist. Thanks and all the best Matthias ___ Help us build a comprehensive ClamAV guide: visit http:// wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html Thanks and all the best Matthias ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamd problem
look into the config file of clamav. there's an option which lets it fix stale sockets. cheerio oliver Am 24.09.2007 um 12:38 schrieb Matthias Schmidt: Hello Oliver, Am/On Mon, 24 Sep 2007 12:20:08 +0200 schrieb/wrote Oliver Schwarz: matthias, use the launchctl unload command, then remove the socket file, then restart the server. usually this should clean out the problems. well, I just killed clamd and restarted it with launchctl load -w ... and now it works. The problem occurs after a restart of the box. best Matthias oliver Am 24.09.2007 um 12:10 schrieb Matthias Schmidt: Am/On Sun, 23 Sep 2007 20:33:57 -0700 schrieb/wrote Dennis Peterson: Matthias Schmidt wrote: Hello, I have a little problem with clamd: the process terminates, because: Socket file /tmp/clamd is in use by another process. now I have no glue, which other process could use the socket file from clamd. I set the permissions to 777 on the end, but didn't help. The original user and group is clamav. So it seams to be not a permission problem. This all runs on a Mac OS 10.4.10 Server with clamav 0.91.2 Run lsof to see what processes have the socket open. Use ktrace and kdump to see what is happening when the process is started. Explain how clamd is started and how it is restarted. What other processes use /tmp/clamd? (see lsof). that's the strange thing, the socket is not open when I start clamd by hand it works and the socket is owned by clamav as expected. Looks like it's a problem with launchctl or the associated plist. Thanks and all the best Matthias ___ Help us build a comprehensive ClamAV guide: visit http:// wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html ___ Help us build a comprehensive ClamAV guide: visit http:// wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html Thanks and all the best Matthias ___ Help us build a comprehensive ClamAV guide: visit http:// wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamd problem
Matthias Schmidt wrote: Hello, I have a little problem with clamd: the process terminates, because: Socket file /tmp/clamd is in use by another process. now I have no glue, which other process could use the socket file from clamd. I set the permissions to 777 on the end, but didn't help. The original user and group is clamav. So it seams to be not a permission problem. This all runs on a Mac OS 10.4.10 Server with clamav 0.91.2 Thanks and all the best Matthias Run lsof to see what processes have the socket open. Use ktrace and kdump to see what is happening when the process is started. Explain how clamd is started and how it is restarted. What other processes use /tmp/clamd? (see lsof). dp ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamd problem
Matthias Schmidt wrote the following on 9/23/2007 8:20 PM -0800: Hello, I have a little problem with clamd: the process terminates, because: Socket file /tmp/clamd is in use by another process. now I have no glue, which other process could use the socket file from clamd. I set the permissions to 777 on the end, but didn't help. The original user and group is clamav. So it seams to be not a permission problem. This all runs on a Mac OS 10.4.10 Server with clamav 0.91.2 I seen orphaned socket files left when clamd crashes. When clamd is stopped, check to see if there is still a orphaned socket file left in /tmp/clamd. If there is, delete it and then you should be able to start clamd. Bill ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] Clamd Problem.
On 17/12/05, Shahzad Abid [EMAIL PROTECTED] wrote: Hi All I am running clamd integrated with qmail on FC3, problem is that when i start clamd manually it starts working and a continues debug log is generated on the shell Konsole when I close that shell Konsole clamd stops working. I put clamd in startup, this hangs my system when i boot the system. Version of clamav? Did you uncomment either of the following lines in clamd.conf: # Don't fork into background. # Default: disabled #Foreground # Enable debug messages in libclamav. # Default: disabled #Debug -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] Clamd Problem.
[EMAIL PROTECTED](Rob MacGregor) 17.12.05 09:48 On 17/12/05, Shahzad Abid [EMAIL PROTECTED] wrote: Hi All I am running clamd integrated with qmail on FC3, problem is that when i start clamd manually it starts working and a continues debug log is generated on the shell Konsole when I close that shell Konsole clamd stops working. nohup would solve that but is only a workaround. I put clamd in startup, this hangs my system when i boot the system. Version of clamav? Did you uncomment either of the following lines in clamd.conf: # Don't fork into background. # Default: disabled #Foreground Beg your pardon. What is the meaning of disabled don't fork into background? Will it be forked or not? You have 0,3 sec to decide! ;-) Why don't you write: # Fork into background. # Default: enabled #Foreground (Assuming the oposit of the default is Foreground so it becomes easier to switch.) Almost good: # Enable debug messages in libclamav. # Default: disabled #Debug What is the meaning of disabled enabled debug messages in libclamav? Are debug messages generated or not? (it's not as hard as the above example) Why don't you write: # libclamav generates debug messages # Default: disabled #Debug Configuration of clamavd is difficult enough, why making it more complicate by using double negations? Rainer ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] Clamd Problem.
Rainer Zocholl said: [EMAIL PROTECTED](Rob MacGregor) 17.12.05 09:48 On 17/12/05, Shahzad Abid [EMAIL PROTECTED] wrote: Hi All I am running clamd integrated with qmail on FC3, problem is that when i start clamd manually it starts working and a continues debug log is generated on the shell Konsole when I close that shell Konsole clamd stops working. nohup would solve that but is only a workaround. And a distraction. I put clamd in startup, this hangs my system when i boot the system. Version of clamav? Did you uncomment either of the following lines in clamd.conf: # Don't fork into background. # Default: disabled #Foreground Beg your pardon. What is the meaning of disabled don't fork into background? Will it be forked or not? You have 0,3 sec to decide! ;-) The phrase Don't fork into background is not a verb phrase - it is a state. The state is either enabled or disabled. Having said that, I do get the impression that English may not be the first language of some of these hard working coders. I've taken this to mean Run as daemon - Default: yes. Again, we're talking about state. I don't care for implicit responses such that no response implies the default, but that's what we have Why don't you write: # Fork into background. # Default: enabled #Foreground or: # Run mode ::= Daemon or Foreground # Default is Daemon # Foreground Daemon Where the BNF allows (and I think should require) one of Daemon or Foreground. And where is the BNF, anyway? Notice that absent the comments in any of this, the keyword Foreground has no context and loses a great deal of clear purpose. That's a bad thing. Better? RunMode = Daemon # define run mode as foreground or background And yes - I do like optional studly caps as it becomes more readable, as in: TheVirtualBarAndGrill.com vs thevirtualbarandgrill.com dp dp ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] Clamd Problem.
Dennis Peterson wrote: # Run mode ::= Daemon or Foreground # Default is Daemon # Foreground Daemon Where the BNF allows (and I think should require) one of Daemon or Foreground. And where is the BNF, anyway? Notice that absent the comments in any of this, the keyword Foreground has no context and loses a great deal of clear purpose. That's a bad thing. Better? RunMode = Daemon # define run mode as foreground or background And yes - I do like optional studly caps as it becomes more readable, as in: I believe the syntax for that parameter (actually, all paramaters that used to be one word only) in development version (CVS) was changed to something like Foreground yes or Foreground no. -- Fajar ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] Clamd Problem.
Have done some further testing, the font doesn't display properly on a linux (FC3) box with gd-2.0.33 but if I use the PHP embedded gd it displays properly. -- Dale On Dec 17, 2005, at 10:58 , Fajar A. Nugraha wrote: Dennis Peterson wrote: # Run mode ::= Daemon or Foreground # Default is Daemon # Foreground Daemon Where the BNF allows (and I think should require) one of Daemon or Foreground. And where is the BNF, anyway? Notice that absent the comments in any of this, the keyword Foreground has no context and loses a great deal of clear purpose. That's a bad thing. Better? RunMode = Daemon # define run mode as foreground or background And yes - I do like optional studly caps as it becomes more readable, as in: I believe the syntax for that parameter (actually, all paramaters that used to be one word only) in development version (CVS) was changed to something like Foreground yes or Foreground no. -- Fajar ___ http://lurker.clamav.net/list/clamav-users.html ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] Clamd problem Solaris 8
Alex S Moore wrote: gcc -g -O2 -o .libs/clamd options.o cfgfile.o clamd.o tcpserver.o localserver.o session.o thrmgr.o Hi! I tried the latest snapshot with size 1kB (20040301) and had a compilation problem on Solaris 8!! Is this also a known problem?? I posted that problem earlier, and Tomasz replied Fixed, thanks. It's a problem on that particular snapshot only. This morning I built the latest cvs snapshot on Solaris 8, both sparc and x86 and had no problems. That would be a newer snapshot. It may not be the latest snapshot, Usually I have the most recent binary bulit from snapshot. Updated daily. http://www.clamav.or.id I don't have stables though. I still have my own build available. The more the merrier :) Regards, Fajar --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
