-- Török Edvin said the following on 8/12/07 3:26 PM:
> 
> It would be mroe useful if you could get a backtrace of all running threads.
> Use a debugger (like gdb) to do that.
> In case of gdb, just attach to the running process, and do a 'thread
> apply all bt'.
> 

I'm noticing hang issues again with 0.91.2 on Solaris 10 x86. It doesn't 
appear to be associated with a particularly malformed message because 
when it starts hanging, if I restart it, things resume normally for a 
while. The incoming queue clears out.

Just recently I happened to be checking the incoming queue and noticed this:

7F10A960A     15939 Thu Aug 30 10:49:59  [EMAIL PROTECTED]
(host mf2.utdallas.edu[10.110.20.30] said: 451 4.5.0 Error in 
processing, id=22597-01-42, virus_scan FAILED: virus_scan: ALL VIRUS 
SCANNERS FAILED: ClamAV-clamd av-scanner FAILED: CODE(0x8134730) Too 
many retries to talk to /var/amavis/clamd.sock (timed out) at (eval 58) 
line 310. at (eval 58) line 511.; ClamAV-clamscan av-scanner FAILED: 
/usr/local/bin/clamscan collect_results - reading aborted: timed out at 
/opt/amavisd/amavisd line 2778. at (eval 58) line 511. (in reply to end 
of DATA command))
                                          [EMAIL PROTECTED]

I tried the gdb bt bit, but doesn't show the stack trace that I'm used 
to seeing:

# gdb /usr/local/sbin/clamd 22426
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.10"...
Attaching to program `/local/sbin/clamd', process 22426
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP 1]
0xfebf0857 in ?? ()
(gdb) thread apply all bt

Thread 11 (LWP 13):
#0  0xfebf047b in ?? ()
#1  0xfebeab3b in ?? ()
#2  0x00000000 in ?? ()

....

And a bunch more of that. I know when clam is compiled gcc is supplied 
the -g, so not sure why all the "??".

This gdb session was done in the global zone. Not sure if it'll work in 
the zone where clamd is actually running, but I'll try that next time.

Amos

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html

Reply via email to