Bug#577499: [Pkg-clamav-devel] Bug#577499: Bug#577499: Me too
This one time, at band camp, Gordon Haverland said: > After the 4 dpkg-reconfigure runs, things seem to be working. > That was the end result mentioned above. That nothing in > /etc/clamav changed after the fresh re-install (after purging) was > interesting. What it looks like happened was: Due to a bug in our maintainer scripts, debconf put a bad value in the config file. This made clamd a bit wobbly and made freshclam unable to talk to it. You updated the config file manually. From here on, configuration did not change. The dpkg-reconfigure runs were to ensure that we didn't further screw up your configuration files - we passed that test, at least, by not writing more garbage into them. The reason it's all working now is that you have (by way of running dpkg-reconfigure in the right order) restarted both clamd and freshclam now that the correct config file is in place. You should be ok now, and thanks for helping us debug this. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#577499: [Pkg-clamav-devel] Bug#577499: Me too
[...] > > After the 4 dpkg-reconfigure runs, things seem to be working. > That was the end result mentioned above. That nothing in > /etc/clamav changed after the fresh re-install (after purging) was > interesting. > > It is hard to see the config files as being broken, if they > weren't changed by any of the dpkg-reconfigure runs. > > As I asked, I could easily purge them all again, and reinstall > again, to check other things (/var/run ?). Something must have > changed, in order for things to be working now, but not after the > initial install. > [...] If you had upgraded from 0.96+dfsg-1, things were kind of expectedly broken, because it was broken in 0.96+dfsg-1 and 0.96+dfsg-2 happily imported those files. Nothing but purge or manual fix would repair this. Best, Michael pgpGFBoZ1KWQL.pgp Description: PGP signature
Bug#577499: [Pkg-clamav-devel] Bug#577499: Me too
On April 24, 2010, Michael Tautschnig wrote: > > On April 24, 2010, Stephen Gran wrote: > > > This one time, at band camp, Gordon Haverland said: > > > > with the dfsg-2 update that came out, I seen > > > > LocalSocketGroup 20 thing with my computer. I set it to > > > > 125 (which is the group clamav is on this computer). > > > > Clamav started, but I started getting messages from > > > > freshclam (cron jobs) about some missing argument. > > > > Trying to fix things, I then got a message about > > > > freshclam not being able to contact clamd via > > > > /var/run/clamav/clamd.ctl. > > > > > > > > So, this morning, I purged all of clamav and reinstalled > > > > it. This message about clamd.ctl persists. > > > > > > Can you set LocalSocketGroup to clamav in the config file, > > > run dpkg-reconfigure and see what it is in the file > > > afterwards? > > > > LocalSocketGroup was already set to clamav, and the mode is > > 666. > > > > dpkg-reconfigure for clamav didn't appear to do anything, no > > files altered in /etc/clamav > > > > dpkg-reconfigure clamav-base asked questions, no files > > changed. > > > > dpkg-reconfigure clamav-daemon asked questions, no files > > changed. > > > > dpkg-reconfigure clamav-freshclam asked questions, no files > > changed. It appears that freshclam updated properly, and was > > able to contact the daemon as part of how dpkg-reconfigure > > finished for freshclam. It would seem that the reconfigures > > did something, but none of the changed were in /etc/clamav. > > > > Want me to purge, reinstall and check something else? > > Could you attach your (broken) config files? It should then be > pretty easy for us to reproduce the problem. My problem, > however, is that I'm not all that sure anymore what your > actual problem is. Is it just that freshclam cannot use the > socket? Which user are you running freshclam as? Is it the > same user that is used for clamd? After the 4 dpkg-reconfigure runs, things seem to be working. That was the end result mentioned above. That nothing in /etc/clamav changed after the fresh re-install (after purging) was interesting. It is hard to see the config files as being broken, if they weren't changed by any of the dpkg-reconfigure runs. As I asked, I could easily purge them all again, and reinstall again, to check other things (/var/run ?). Something must have changed, in order for things to be working now, but not after the initial install. Gord #Automatically Generated by clamav-base postinst #To reconfigure clamd run #dpkg-reconfigure clamav-base #Please read /usr/share/doc/clamav-base/README.Debian.gz for details LocalSocket /var/run/clamav/clamd.ctl FixStaleSocket true LocalSocketGroup clamav LocalSocketMode 666 # TemporaryDirectory is not set to its default /tmp here to make overriding # the default with environment variables TMPDIR/TMP/TEMP possible User clamav AllowSupplementaryGroups true ScanMail true ScanArchive true ArchiveBlockEncrypted false MaxDirectoryRecursion 15 FollowDirectorySymlinks false FollowFileSymlinks false ReadTimeout 180 MaxThreads 12 MaxConnectionQueueLength 15 StreamMaxLength 10M LogSyslog false LogFacility LOG_LOCAL6 LogClean false LogVerbose false PidFile /var/run/clamav/clamd.pid DatabaseDirectory /var/lib/clamav SelfCheck 3600 Foreground false Debug false ScanPE true ScanOLE2 true ScanHTML true DetectBrokenExecutables false ExitOnOOM false LeaveTemporaryFiles false AlgorithmicDetection true ScanELF true IdleTimeout 30 PhishingSignatures true PhishingScanURLs true PhishingAlwaysBlockSSLMismatch false PhishingAlwaysBlockCloak false DetectPUA false ScanPartialMessages false HeuristicScanPrecedence false StructuredDataDetection false CommandReadTimeout 5 SendBufTimeout 200 MaxQueue 100 LogFile /var/log/clamav/clamav.log LogTime true LogFileUnlock false LogFileMaxSize 0 Bytecode true BytecodeSecurity TrustSigned BytecodeTimeout 6 OfficialDatabaseOnly false CrossFilesystems true # Automatically created by the clamav-freshclam postinst # Comments will get lost when you reconfigure the clamav-freshclam package DatabaseOwner clamav UpdateLogFile /var/log/clamav/freshclam.log LogVerbose false LogSyslog false LogFacility LOG_LOCAL6 LogFileMaxSize 0 LogTime true Foreground false Debug false MaxAttempts 5 DatabaseDirectory /var/lib/clamav/ DNSDatabaseInfo current.cvd.clamav.net AllowSupplementaryGroups false PidFile /var/run/clamav/freshclam.pid ConnectTimeout 30 ReceiveTimeout 30 ScriptedUpdates yes CompressLocalDatabase no Bytecode true NotifyClamd /etc/clamav/clamd.conf DatabaseMirror db.ca.clamav.net DatabaseMirror database.clamav.net
Bug#577499: [Pkg-clamav-devel] Bug#577499: Me too
> On April 24, 2010, Stephen Gran wrote: > > This one time, at band camp, Gordon Haverland said: > > > with the dfsg-2 update that came out, I seen LocalSocketGroup > > > 20 thing with my computer. I set it to 125 (which is the > > > group clamav is on this computer). Clamav started, but I > > > started getting messages from freshclam (cron jobs) about > > > some missing argument. Trying to fix things, I then got a > > > message about freshclam not being able to contact clamd via > > > /var/run/clamav/clamd.ctl. > > > > > > So, this morning, I purged all of clamav and reinstalled it. > > > This message about clamd.ctl persists. > > > > Can you set LocalSocketGroup to clamav in the config file, run > > dpkg-reconfigure and see what it is in the file afterwards? > > LocalSocketGroup was already set to clamav, and the mode is 666. > > dpkg-reconfigure for clamav didn't appear to do anything, no files > altered in /etc/clamav > > dpkg-reconfigure clamav-base asked questions, no files changed. > > dpkg-reconfigure clamav-daemon asked questions, no files changed. > > dpkg-reconfigure clamav-freshclam asked questions, no files > changed. It appears that freshclam updated properly, and was able > to contact the daemon as part of how dpkg-reconfigure finished for > freshclam. It would seem that the reconfigures did something, but > none of the changed were in /etc/clamav. > > Want me to purge, reinstall and check something else? > Could you attach your (broken) config files? It should then be pretty easy for us to reproduce the problem. My problem, however, is that I'm not all that sure anymore what your actual problem is. Is it just that freshclam cannot use the socket? Which user are you running freshclam as? Is it the same user that is used for clamd? Best, Michael pgpnaiY7GOKTA.pgp Description: PGP signature
Bug#577499: [Pkg-clamav-devel] Bug#577499: Me too
On April 24, 2010, Stephen Gran wrote: > This one time, at band camp, Gordon Haverland said: > > with the dfsg-2 update that came out, I seen LocalSocketGroup > > 20 thing with my computer. I set it to 125 (which is the > > group clamav is on this computer). Clamav started, but I > > started getting messages from freshclam (cron jobs) about > > some missing argument. Trying to fix things, I then got a > > message about freshclam not being able to contact clamd via > > /var/run/clamav/clamd.ctl. > > > > So, this morning, I purged all of clamav and reinstalled it. > > This message about clamd.ctl persists. > > Can you set LocalSocketGroup to clamav in the config file, run > dpkg-reconfigure and see what it is in the file afterwards? LocalSocketGroup was already set to clamav, and the mode is 666. dpkg-reconfigure for clamav didn't appear to do anything, no files altered in /etc/clamav dpkg-reconfigure clamav-base asked questions, no files changed. dpkg-reconfigure clamav-daemon asked questions, no files changed. dpkg-reconfigure clamav-freshclam asked questions, no files changed. It appears that freshclam updated properly, and was able to contact the daemon as part of how dpkg-reconfigure finished for freshclam. It would seem that the reconfigures did something, but none of the changed were in /etc/clamav. Want me to purge, reinstall and check something else? Gord -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#577499: [Pkg-clamav-devel] Bug#577499: Me too
This one time, at band camp, Gordon Haverland said: > with the dfsg-2 update that came out, I seen LocalSocketGroup 20 > thing with my computer. I set it to 125 (which is the group > clamav is on this computer). Clamav started, but I started > getting messages from freshclam (cron jobs) about some missing > argument. Trying to fix things, I then got a message about > freshclam not being able to contact clamd via > /var/run/clamav/clamd.ctl. > > So, this morning, I purged all of clamav and reinstalled it. This > message about clamd.ctl persists. Can you set LocalSocketGroup to clamav in the config file, run dpkg-reconfigure and see what it is in the file afterwards? Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#577499: Me too
with the dfsg-2 update that came out, I seen LocalSocketGroup 20 thing with my computer. I set it to 125 (which is the group clamav is on this computer). Clamav started, but I started getting messages from freshclam (cron jobs) about some missing argument. Trying to fix things, I then got a message about freshclam not being able to contact clamd via /var/run/clamav/clamd.ctl. So, this morning, I purged all of clamav and reinstalled it. This message about clamd.ctl persists. Gord -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
