[Bug 246590] New: clamav-0.90-0.1.i586.rpm is broken
https://bugzilla.novell.com/show_bug.cgi?id=246590 Summary: clamav-0.90-0.1.i586.rpm is broken Product: openSUSE 10.2 Version: Final Platform: 32bit OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team@suse.de ReportedBy: win@huber-und-boehm.de QAContact: qa@suse.de Hi all, freshclam just told me my clamav-0.88.7-1.1 is outdated. I should upgrade to Version 0.90. I should read http://www.clamav.net/faq.html. So I got and installed clamav-0.90-0.1.i586.rpm from ftp://ftp.suse.com/pub/projects/clamav/clamav-0.90/10.2-i386. "rcclamd stop" does not remove clamd's socket /var/lib/clamav/clamd-socket. "rcclamd start" tries to start clamd, but clamd stops immediatly and croaks in the log file ... ERROR: Socket file /var/lib/clamav/clamd-socket exists. Either remove it, or configure a different one. Removing this socket and running "rcclamd start" starts clamd fine. But it won't start again at the next boot. So clamd perhaps should remove and recreate the socket if it does not belong to another running instance of clamd (which should not happen due to log file locking), Hope this is not off topic here. I reverted to the previous version of clamav (and hope I did not got fooled yielding in some open back doors or such nasty things), Regards, Winfried -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246590 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |win@huber-und-boehm.de ------- Comment #1 from max@novell.com 2007-02-19 02:09 MST ------- (In reply to comment #0)
So clamd perhaps should remove and recreate the socket if it does not belong to another running instance of clamd
There is a new parameter called FixStaleSocket in /etc/clamd.conf, which should be set to yes by default and is supposed to do exactly this. Did you switch this off, or does it even happen with this parameter switched on? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246590 win@huber-und-boehm.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|win@huber-und-boehm.de | Resolution| |FIXED ------- Comment #2 from win@huber-und-boehm.de 2007-02-19 02:36 MST ------- shame on me, you're right :-( I should have seen this! Sorry for the noise... It might be helpful to add a hint "see the parameter FixStaleSocket in /etc/clamd.conf" to the error message in clamav's log file, Thanks again and sorry... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=246590 ------- Comment #3 from max@novell.com 2007-02-19 02:43 MST ------- No problem. Your report still gave me a useful hint, because after a clean shutdown (i.e. rcclamd stop) clamd is not supposed to leave a stale socket behind. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com