Re: amavisd-new crashing
On Sat, 12 Sep 2009, GalaxyPC.Net Administrator wrote: Eric, I battled this all morning and found some helpful posts on the amavisd-new sourceforge lists. In the decoders section of amavisd.conf, look for the following lines. Comment out one at a time, reloading amavisd each time, of course, until you are able to flush your queue successfully. In my case it was 'asc', but in yours I would try 'uue' first. There were suggestions on SF to comment all the 'ascii' lines out. ['asc', \do_ascii], ['uue', \do_ascii], ['hqx', \do_ascii], ['ync', \do_ascii], Yep, I had the same problem on two different machines (one 8.0 one 7.2), and the same fix. The problem is actually in Convert::UUlib, rather than specifically in amavisd-new... commenting out those lines removes all calls to Convert::UUlib thus working around the problem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: amavisd-new crashing
Eric, I battled this all morning and found some helpful posts on the amavisd-new sourceforge lists. In the decoders section of amavisd.conf, look for the following lines. Comment out one at a time, reloading amavisd each time, of course, until you are able to flush your queue successfully. In my case it was 'asc', but in yours I would try 'uue' first. There were suggestions on SF to comment all the 'ascii' lines out. ['asc', \do_ascii], ['uue', \do_ascii], ['hqx', \do_ascii], ['ync', \do_ascii], Good luck, Russ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: amavisd-new crashing
Decided to check the core dump that perl left behind but this is all i see(minus a couple thousand lines above this point with no more detail than given here: #1345 0x102454ff in ?? () #1346 0x1424448d in ?? () #1347 0x5440f750 in ?? () #1348 0x0002 in ?? () #1349 0x688e0375 in ?? () #1350 0x0158b814 in ?? () #1351 0xcd50 in ?? () #1352 0x90feeb80 in ?? () #1353 0x282d9b04 in ?? () #1354 0x0001 in ?? () #1355 0xbfbfeeb8 in ?? () #1356 0x0004 in ?? () Cannot access memory at address 0xbfc0 (gdb) Sean wrote: On Thu, 10 Sep 2009, Eric Sheesley wrote: [mail.log snipped] What's in /var/log/messages? Or dmesg? I started having amavisd-new cause perl to coredump, apparently deep in the middle of Converter::UULib when a coredump was forced. Regards, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
amavisd-new crashing
For the past week or so I've had 2-3 different emails that, as they are attempting to be delivered end up crashing amavisd-new(just one instance, not the whole daemon) leading the the error: queue file write error from postfix. Both messages appear to have been 8bitmime encoded from a quick glance, but no other common points. These emails will continually crash amavis every 15 minutes as the servers attempt delivery. I've used portmanager to rebuild amavis and all dependencies with no change. Any ideas on what could be wrong? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: amavisd-new crashing
Eric Sheesley wrote: For the past week or so I've had 2-3 different emails that, as they are attempting to be delivered end up crashing amavisd-new(just one instance, not the whole daemon) leading the the error: queue file write error from postfix. Both messages appear to have been 8bitmime encoded from a quick glance, but no other common points. These emails will continually crash amavis every 15 minutes as the servers attempt delivery. I've used portmanager to rebuild amavis and all dependencies with no change. Any ideas on what could be wrong? Hi, Both amavis and Postfix can be made to provide rather substantial logging, that's what I would have done in your case. Or do you already have some logs to share? Also, did you check that you did not run out of memory? HTH, -- per ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: amavisd-new crashing
Here is one sample of the log(level 5 logging on). not very descriptive about the problem, at least i don't see it. Sep 10 19:00:07 rogue postfix/smtpd[77645]: connect from tx2ehsobe003.messaging.microsoft.com[65.55.88.13] Sep 10 19:00:07 rogue postfix/smtpd[77645]: NOQUEUE: client=tx2ehsobe003.messaging.microsoft.com[65.55.88.13] Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com - mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT) Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type: text/plain, size: 3607 B, name: Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection with proxy 127.0.0.1:10024 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5 (100%)100, rundown: 0 (0%)100 Sep 10 19:00:08 rogue postfix/cleanup[78042]: 4EDE850837: message-id=20090910230008.4ede850...@rogue.shadowlair.com Sep 10 19:00:08 rogue postfix/smtpd[77645]: disconnect from tx2ehsobe003.messaging.microsoft.com[65.55.88.13] Per olof Ljungmark wrote: Eric Sheesley wrote: For the past week or so I've had 2-3 different emails that, as they are attempting to be delivered end up crashing amavisd-new(just one instance, not the whole daemon) leading the the error: queue file write error from postfix. Both messages appear to have been 8bitmime encoded from a quick glance, but no other common points. These emails will continually crash amavis every 15 minutes as the servers attempt delivery. I've used portmanager to rebuild amavis and all dependencies with no change. Any ideas on what could be wrong? Hi, Both amavis and Postfix can be made to provide rather substantial logging, that's what I would have done in your case. Or do you already have some logs to share? Also, did you check that you did not run out of memory? HTH, -- per ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: amavisd-new crashing
Actually, the directory is set to vscan as it should be(amavis runs as that) and that user has rw privs. If you notice below, the pid of the processes is different between the area where content-type is mentioned and the bdb is referenced. For some reason there is a very brutal crash before any real checks are run. I've rebuilt amavis and all dependencies using portmanager with no change. Any other thoughts or methods of debugging. One of the emails causing this was sent by a friend, so not even malicious, just causing a crash. Chuck Swiger wrote: Hi-- On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote: Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com - mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT) Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type: text/plain, size: 3607 B, name: Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection with proxy 127.0.0.1:10024 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5 (100%)100, rundown: 0 (0%)100 It sounds like amavisd can't open a BerkeleyDB database (probably the nanny/cache/snmp stuff). Make sure that /var/amavis/db exists and is writable by the amavisd or vscan user, whatever you are running amavisd as: # ls -l /var/amavis/db total 556 -rw-r- 1 vscan vscan 24576 Sep 9 19:01 __db.001 -rw-r- 1 vscan vscan 131072 Sep 9 18:44 __db.002 -rw-r- 1 vscan vscan 270336 Sep 10 11:43 __db.003 -rw-r- 1 vscan vscan 360448 Sep 9 18:44 __db.004 -rw-r- 1 vscan vscan4096 Sep 9 14:20 cache-expiry.db -rw-r- 1 vscan vscan 90112 Sep 10 14:01 cache.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 nanny.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 snmp.db Regards, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: amavisd-new crashing
Another sample attached: Sep 10 20:15:41 rogue postfix/smtpd[59483]: connect from mail-vw0-f180.google.com[209.85.212.180] Sep 10 20:15:41 rogue postfix/smtpd[59483]: NOQUEUE: client=mail-vw0-f180.google.com[209.85.212.180] Sep 10 20:15:41 rogue amavis[77720]: (77720-02) ESMTP::10024 /var/amavis/tmp/amavis-20090910T192517-77720: deadsen...@gmail.com - e...@shadowlair.com Received: from rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for mya...@shadowlair.com; Thu, 10 Sep 2009 20:15:41 -0400 (EDT) Sep 10 20:15:41 rogue amavis[77720]: (77720-02) dkim: VALID Author+Sender+MailFrom signature by i...@gmail.com, From: deadsen...@gmail.com, a=rsa-sha256, c=relaxed/relaxed, s=gamma, d=gmail.com Sep 10 20:15:41 rogue amavis[77720]: (77720-02) dkim: VALID Author+Sender+MailFrom signature by i=deadsen...@gmail.com, From: deadsen...@gmail.com, a=rsa-sha1, c=nofws, s=gamma, d=gmail.com Sep 10 20:15:41 rogue amavis[77720]: (77720-02) Checking: 2UIxlfrQ4TAm [209.85.212.180] deadsen...@gmail.com - mya...@shadowlair.com Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p003 1 Content-Type: multipart/alternative Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p001 1/1 Content-Type: text/plain, size: 3383 B, name: Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p002 1/2 Content-Type: text/html, size: 5031 B, name: Sep 10 20:15:41 rogue postfix/smtpd[59483]: warning: lost connection with proxy 127.0.0.1:10024 Sep 10 20:15:41 rogue amavis[59998]: TIMING [total 6 ms] - bdb-open: 6 (100%)100, rundown: 0 (0%)100 Sep 10 20:15:41 rogue postfix/cleanup[59992]: 8EA9F5083B: message-id=20090911001541.8ea9f50...@rogue.shadowlair.com Sep 10 20:15:41 rogue postfix/smtpd[59483]: disconnect from mail-vw0-f180.google.com[209.85.212.180] Chuck Swiger wrote: Hi-- On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote: Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com - mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT) Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type: text/plain, size: 3607 B, name: Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection with proxy 127.0.0.1:10024 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5 (100%)100, rundown: 0 (0%)100 It sounds like amavisd can't open a BerkeleyDB database (probably the nanny/cache/snmp stuff). Make sure that /var/amavis/db exists and is writable by the amavisd or vscan user, whatever you are running amavisd as: # ls -l /var/amavis/db total 556 -rw-r- 1 vscan vscan 24576 Sep 9 19:01 __db.001 -rw-r- 1 vscan vscan 131072 Sep 9 18:44 __db.002 -rw-r- 1 vscan vscan 270336 Sep 10 11:43 __db.003 -rw-r- 1 vscan vscan 360448 Sep 9 18:44 __db.004 -rw-r- 1 vscan vscan4096 Sep 9 14:20 cache-expiry.db -rw-r- 1 vscan vscan 90112 Sep 10 14:01 cache.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 nanny.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 snmp.db Regards, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: amavisd-new crashing
Hi-- On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote: Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com - mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT) Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type: text/plain, size: 3607 B, name: Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection with proxy 127.0.0.1:10024 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5 (100%)100, rundown: 0 (0%)100 It sounds like amavisd can't open a BerkeleyDB database (probably the nanny/cache/snmp stuff). Make sure that /var/amavis/db exists and is writable by the amavisd or vscan user, whatever you are running amavisd as: # ls -l /var/amavis/db total 556 -rw-r- 1 vscan vscan 24576 Sep 9 19:01 __db.001 -rw-r- 1 vscan vscan 131072 Sep 9 18:44 __db.002 -rw-r- 1 vscan vscan 270336 Sep 10 11:43 __db.003 -rw-r- 1 vscan vscan 360448 Sep 9 18:44 __db.004 -rw-r- 1 vscan vscan4096 Sep 9 14:20 cache-expiry.db -rw-r- 1 vscan vscan 90112 Sep 10 14:01 cache.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 nanny.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 snmp.db Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
