Bug#340491: clamav-milter dying
This one time, at band camp, Eriberto said: Hello. I delayed to write this message. Excuse me. No problem, I'm a bit busy myself recently. Stephen Gran escreveu: This one time, at band camp, Eriberto said: Hello! I set --max-children=20. However the clamav-milter died again. The proccess runs 24h only. See the log in attach. I see nothing in the log indicating a problem, unfortunately. How familar are you with strace or ltrace? If you are familar with any of those, can you attach one of them to the running milter and send me the last couple of hundred lines after a crash. Note that the milter is threaded, so you'll want to run strace with -ff, and send the files relating to the last several threads before a crash. I don't know strace or ltrace. I will try to use them. However I am in vacance (30 days). I don't have contact with the systems. No problem - it can wait until you come back. gdb would also be nice - a stack trace after a crash would really help. If you're not familiar with any of these commands, let me know and I'll give you instructions. I observed the clamav without the -q and --quarantine-dir. It's works fine! You're saying it doesn't die when you don't use the --quarantine-dir option? That's really wierd, and smells like a leaking file descriptor bug or something. When you have time to debug this again, please run with --quarantine-dir, and take a look at the contents of the quarantine directory when it starts to choke. Are there tons of files? Is the disk full? What does an lsof | grep clamav-milter | wc -l say? Thanks, -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#340491: clamav-milter dying
Hello. I delayed to write this message. Excuse me. Stephen Gran escreveu: This one time, at band camp, Eriberto said: Hello! I set --max-children=20. However the clamav-milter died again. The proccess runs 24h only. See the log in attach. I see nothing in the log indicating a problem, unfortunately. How familar are you with strace or ltrace? If you are familar with any of those, can you attach one of them to the running milter and send me the last couple of hundred lines after a crash. Note that the milter is threaded, so you'll want to run strace with -ff, and send the files relating to the last several threads before a crash. I don't know strace or ltrace. I will try to use them. However I am in vacance (30 days). I don't have contact with the systems. gdb would also be nice - a stack trace after a crash would really help. If you're not familiar with any of these commands, let me know and I'll give you instructions. By the way, I see from the output you sent that max-children never gets above 2, and it looks like your mail load is about 700 messages in the period it was running. Is that about right? I just want to make sure I'm interpreting it correctly. All right. 700 messages. Also, please use reply-all to keep the bug log in the conversation. Thanks, I observed the clamav without the -q and --quarantine-dir. It's works fine! Regards, Eriberto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340491: clamav-milter dying
This one time, at band camp, Eriberto said: Hello! I set --max-children=20. However the clamav-milter died again. The proccess runs 24h only. See the log in attach. I see nothing in the log indicating a problem, unfortunately. How familar are you with strace or ltrace? If you are familar with any of those, can you attach one of them to the running milter and send me the last couple of hundred lines after a crash. Note that the milter is threaded, so you'll want to run strace with -ff, and send the files relating to the last several threads before a crash. gdb would also be nice - a stack trace after a crash would really help. If you're not familiar with any of these commands, let me know and I'll give you instructions. By the way, I see from the output you sent that max-children never gets above 2, and it looks like your mail load is about 700 messages in the period it was running. Is that about right? I just want to make sure I'm interpreting it correctly. Also, please use reply-all to keep the bug log in the conversation. Thanks, -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#340491: clamav-milter dying
On Mon, Nov 28, 2005 at 11:16:13AM -0200, Eriberto said: Hello! You have reason. parse error, here, sorry. What do you mean? The problem isn't clamd.conf. I have a i386 machine. Clamv-milter runs ok with default options. However, with -q it's hangs after some scans. Can you run it foregrounded with debug on for a while and send me the output after it hangs? I have libc6 installed. I sincerely hope so :) Also please use 'reply-all' to this message, to keep the bug log in the conversation. Thanks, -- -- | Stephen Gran | If the meanings of true and false | | [EMAIL PROTECTED] | were switched, then this sentence would | | http://www.lobefin.net/~steve | not be false. | -- signature.asc Description: Digital signature
Bug#340491: clamav-milter dying
On Mon, Nov 28, 2005 at 01:58:15PM -0200, Eriberto said: Hello! The start of the Clamav Milter: ipanema:~# /usr/sbin/clamav-milter -D --max-children=2 -ol -q --quarantine-dir=/mail/quarentena --pidfile /var/run/clamav/clamav-milter.pid local:/var/run/clamav/clamav-milter.ctl LibClamAV debug: Running as user clamav (UID 106, GID 106) /usr/sbin/clamav-milter: (-q !LogSyslog): warning - all interception message methods are off Please use ForeGround in clamd.conf (I know that earlier I said it was for clamd, and 90% of the time that's right. It's a pain :) I think I may see your problem, though - how much mail do you do? With --max-children=2, you are only going to be able to handle 2 messages at a time. If you do more than 2 messages at a time, clamav-milter will be busy, and can't get to the request in time. Also please use 'reply-all' to this message, to keep the bug log in the conversation. Please, I ask again. -- -- | Stephen Gran | Take Care of the Molehills, and the | | [EMAIL PROTECTED] | Mountains Will Take Care of Themselves. | | http://www.lobefin.net/~steve | -- Motto of the Federal Civil Service | -- signature.asc Description: Digital signature
Bug#340491: clamav-milter dying
This one time, at band camp, Stephen Gran said: This one time, at band camp, Eriberto said: Package: clamav-milter Version: 0.87.1-1 Clamav-milter crashes after scan a email. In /etc/clamav/clamd.conf has the lines: PidFile /var/run/clamav/clamd.pid LocalSocket /var/run/clamav/clamd.ctl However in /var/run/clamav the socket file is clamav-milter.ctl and the pid file is clamav-milter.pid. It's the problem. clamd.conf controls the behavior of clamd, perhaps unsurprisingly. /etc/default/clamav-milter contains the command line options used to start clamav-milter. However, this probably is not the cause of a crash. can you give me log messages that say it's crashing? Any debug output? A stack trace from gdb? An strace? Something? Also, what architecture is this - I have had another report of clamav-milter dying on sparc64. Is that the case for you as well? -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#340491: clamav-milter dying
Package: clamav-milter Version: 0.87.1-1 Clamav-milter crashes after scan a email. In /etc/clamav/clamd.conf has the lines: PidFile /var/run/clamav/clamd.pid LocalSocket /var/run/clamav/clamd.ctl However in /var/run/clamav the socket file is clamav-milter.ctl and the pid file is clamav-milter.pid. It's the problem. Best regards, João Eriberto Mota Filho
Bug#340491: clamav-milter dying
This one time, at band camp, Eriberto said: Package: clamav-milter Version: 0.87.1-1 Clamav-milter crashes after scan a email. In /etc/clamav/clamd.conf has the lines: PidFile /var/run/clamav/clamd.pid LocalSocket /var/run/clamav/clamd.ctl However in /var/run/clamav the socket file is clamav-milter.ctl and the pid file is clamav-milter.pid. It's the problem. clamd.conf controls the behavior of clamd, perhaps unsurprisingly. /etc/default/clamav-milter contains the command line options used to start clamav-milter. However, this probably is not the cause of a crash. can you give me log messages that say it's crashing? Any debug output? A stack trace from gdb? An strace? Something? -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
