clamav-users May 2014 archive
Main Archive Page > Month Archives  > clamav-users archives
clamav-users: Re: [clamav-users] Version 0.98.3 hard loops on &q

Re: [clamav-users] Version 0.98.3 hard loops on "clamdscan -V"

From: Philippe Ratté <pratte_at_nospam>
Date: Fri May 09 2014 - 19:39:33 GMT
To: 'ClamAV users ML' <clamav-users@lists.clamav.net>

Shawn,

The patch seems to fix the problem :) So far so good; I'll keep on monitoring it

Thanks a bunch for the quick fix!

Phil

> -----Message d'origine-----
> De : clamav-users-bounces@lists.clamav.net [mailto:clamav-users-
> bounces@lists.clamav.net] De la part de Shawn Webb
> Envoyé : Friday, May 09, 2014 3:17 PM
> À : ClamAV users ML
> Objet : Re: [clamav-users] Version 0.98.3 hard loops on "clamdscan -V"
>
> On Fri, May 9, 2014 at 3:02 PM, Philippe Ratté
> <pratte@cybergeneration.com>wrote:
>
> > Hello,
> >
> > This may not be related; however I am also having some loop issues with
> > 0.98.3
> >
> > I'm using qmail-scanner, and everything works fine with 0.98.1
> >
> > Now, using 0.98.3, I've got some clamdscan processes that are looping
> > non-stop opening '/etc/services':
> >
> > # strace -p 13472 -s 5120
> > [...]
> > open("/etc/services", O_RDONLY) = 3
> > fcntl64(3, F_GETFD) = 0
> > fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
> > fstat64(3, {st_mode=S_IFREG|0644, st_size=362031, ...}) = 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0)
> > = 0xb7fde000
> > read(3, "# /etc/services:\n# $Id: services,v 1.42 2006/02/23 13:09:23
> > pknirsch Exp $\n#\n# Network services, Internet style\n#\n# Note that it
> is
> > presently the policy of IANA to assign a single well-known\n# port
> number
> > for both TCP and UDP; hence, most entries here have two entries\n# even
> if
> > the protocol doesn\'t support UDP operations.\n# Updated from RFC 1700,
> > ``Assigned Numbers\'\' (October 1994). Not all ports\n# are included,
> only
> > the more common ones.\n#\n# The latest IANA port assignments can be
> gotten
> > from\n#\thttp://www.iana.org/assignments/port-numbers\n# The Well Known
> > Ports are those from 0 through 1023.\n# The Registered Ports are those
> from
> > 1024 through 49151\n# The Dynamic and/or Private Ports are those from
> 49152
> > through 65535\n#\n# Each line describes one service, and is of the
> form:\n#
> > \n# service-name port/protocol [aliases ...]
> >
> > Any ideas?
> >
> > Thanks!
> >
> > > -----Message d'origine-----
> > > De : clamav-users-bounces@lists.clamav.net [mailto:clamav-users-
> > > bounces@lists.clamav.net] De la part de Eric Shubert
> > > Envoyé : Friday, May 09, 2014 2:49 PM
> > > À : clamav-users@lists.clamav.net
> > > Objet : Re: [clamav-users] Version 0.98.3 hard loops on "clamdscan -V"
> > >
> > > On 05/09/2014 04:41 AM, Shawn Webb wrote:
> > > > On Thu, May 8, 2014 at 10:35 PM, Eric Shubert <ejs@shubes.net>
> wrote:
> > > >
> > > >> Immediately after upgrading from 0.98 to 0.98.3,
> > > >> when "clamdscan --stdout -V" is run (via simscanmk -g),
> > > >> the clamdscan appears to go into a hard loop (eats a lot of cpu
> > > endlessly).
> > > >>
> > > >> Here are non-default config settings:
> > > >> [root@qmt-cos5 etc]# grep -v ^# clamd.conf | grep -v ^$
> > > >> LogClean yes
> > > >> LogVerbose yes
> > > >> LocalSocket /tmp/clamd.socket
> > > >> FixStaleSocket yes
> > > >> Foreground yes
> > > >> ScanMail yes
> > > >>
> > > >> Any ideas?
> > > >> Thanks.
> > > >
> > > >
> > > > Hey Eric,
> > > >
> > > > I'm having a bit of trouble reproducing the issue here. What OS and
> > what
> > > > version of the OS are you using? What architecture (x86, x64)? What
> > > happens
> > > > if you run the clamdscan command manually? Can you paste to a
> pastebin
> > > > service the output of clamconf and your config.log file?
> > > >
> > > > Thanks,
> > > >
> > > > Shawn
> > > > _______________________________________________
> > >
> > > Hey Shawn. Sorry I didn't include more details.
> > > CentOS 5.10, i386.
> > >
> > > I get the same result (looping) when I run "clamdscan --stdout -V"
> > > manually.
> > >
> > > However, if I start clamd, wait for it to load everything, then run
> > > clamdscan, then clamdscan works. When I stop clamd, try clamdscan
> again,
> > > then it loops again.
> > >
> > > So it appears that when clamd is running, clamdscan works. When clamd
> > > isn't running, clamdscan appears to go into a hard loop (presumably
> > > waiting for something that never happens).
> > >
> > > clamconf is at http://pastebin.com/dJAJF8T1
> > >
> > > I don't appear to have any config.log. How do I get that?
> >
>
> Hey Eric and Philippe,
>
> Can you both apply the patch from this bug ticket?
> https://bugzilla.clamav.net/show_bug.cgi?id=10987
>
> I'm wondering if it's related.
>
> Thanks,
>
> Shawn
> _______________________________________________
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> http://www.clamav.net/support/ml

_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/support/ml