On Thu, 22 Jan 2004, Everton da Silva Marques wrote:
> On Thu, Jan 22, 2004 at 06:37:14PM +0100, Tomasz Kojm wrote: > > On Thu, 22 Jan 2004 08:29:53 +0100 > > Marc Balmer <[EMAIL PROTECTED]> wrote: > > > > > Tomasz Kojm wrote: > > > > > > >>clamd hangs at leats twice a day, does no longer respond to network > > > >>connections. It has to be killed and restarted. It has become > > > >>unusable on OpenBSD. > > > > > > > > Sorry, we're not telepathic - we need backtraces, logs, etc. > > > > > > If there only was an error message. clamd still runs, according to > > > ps, to does no longer handle the network protocol. > > > > Please try to attach gdb to the broken clamd process next time. > > I often see a very similar problem in clamav 0.65 under Solaris 7. > clamd writes the following to logs: > > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > Thu Jan 22 11:23:51 2004 -> ERROR: accept() failed. > > An work-around is to stop clamd and restart it. > > I'll try to attach gdb to clamd next time. > Try increasing MaxConnectionQueueLength or if you use Unix sockets (LocalSocket) use TCPAddr/TCPSocket instead. Solaris unix sockets are known to have problems. -- Igor ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
