Micah wrote: >>>>> Jul 2 11:31:07 buffy amavisd-new[2975]: (02975-29) Decoding of part-00001 >>>>> (bzip compressed data, version: 7, compression block size 200k) failed, >>>>> leaving it unpacked: Error running decompressor /usr/bin/bzip2 -d on >>>>> part-00001, exit status 2 at /usr/sbin/amavisd-new line 4208. >>>> >>>>> and >>>> >>>>> Jul 2 11:31:07 buffy amavisd-new[2975]: (02975-29) TROUBLE in check_mail: >>>>> decoding2-get-file-types FAILED: 'file' utility (/usr/bin/file) failed, >>>>> status=255 (65280 ) at /usr/sbin/amavisd-new line 3853. >>>> >>>>> I have searched around and found some suggestions, but none of them seem >>>>> to >>>>> work for 2.3.3. How can I make these go away? >> >>>> The second error indicates you are using an incompatible >>>> version of Net::Server. You most likely need to downgrade >>>> to 0.90. Also, the line number above indicates to me you are running >>>> 20030616-p10. Since the newest version of Net::Server on Debian is >>>> 0.90, I will assume you installed a newer version from CPAN. If so, >>>> you can downgrade to 0.90 by doing: >> >>> I'm running libnet-server-perl version 0.87-3 (from debian stable), and >>> amavisd-new 20030616p10-5 (from backports.org). You are saying that I need >>> to downgrade to 0.90, but perhaps you mean to say that I need to *upgrade*? >> >>> I'll attempt to upgrade to 0.90 from testing, and if this solves the problem >>> I will see if I can get the backports.org version updated to depend on this >>> (after also backporting it). >> >> I would hesitate doing that. 0.87-3 from stable is OK. At this point
> [stuff about polluting stable deleted, appreciate the info, I'm a > debian developer so I think I can handle it] > I installed 0.90 and let it sit for a while to see if the errors would > go away, but they did not. >> You may have libnet-server-perl 0.87-3 installed, but if you installed >> Net::Server from CPAN, you may actually be using that instead of the >> Debian supplied module. Run amavisd-new in debug mode and look for the >> version >> amavisd-new reports it is actually using. >> >> Jul 8 15:01:59 sarge31.example.com >> /usr/local/sbin/amavisd-new[1409]: Module Net::Server 0.87 > When I installed 0.90 it showed up in the amavisd-new logs as 0.90, > because it didn't seem to help, I downgraded it back to 0.87 and thats > what shows up in the amavisd-new logs now. >> Do this also, Run: >> updatedb >> locate /Net/Server.pm >> >> You should only have one (this is the Debian version): >> /usr/share/perl5/Net/Server.pm > Only have one. >> If you are in fact using a compatible version of Net::Server, then >> this patch for amavisd-new 20030616p10, interpolated from >> http://archive.netbsd.se/?ml=amavis-user&a=2005-11&m=1526878 >> might prevent amavisd-new from dying when a corrupt archive is >> decoded (and instead only log the error). Messages like that may >> become corrupt as a result of bounce DSNs truncating the original message. >> >> --- amavisd-new.orig 2006-07-09 13:34:44.000000000 -0600 >> +++ amavisd-new 2006-07-09 13:43:50.000000000 -0600 >> @@ -4205,8 +4205,9 @@ >> die sprintf('Error running decompressor %s on %s, DIED on signal %d', >> $decompressor, $part, WTERMSIG($rv)); >> } elsif (WEXITSTATUS($rv) != 0) { >> - die sprintf('Error running decompressor %s on %s, exit status %d', >> + my($msg) = sprintf('Error running decompressor %s on %s, exit status >> %d', >> $decompressor, $part, WEXITSTATUS($rv)); >> + if ($rv == 2) { do_log(0,$msg) } else { die $msg } >> } >> 1; >> } > Thanks for the patch, but unfortunately... I'm still getting errors: > Jul 29 22:15:21 buffy amavisd-new[6277]: (06277-33) Decoding of > part-00002 (gzip compressed data, from Unix) failed, leaving it > unpacked: Error running decompressor /bin/gzip -d on part-00002, exit > status 2 at /usr/sbin/amavisd-new line 4208. > Jul 29 22:15:21 buffy amavisd-new[6277]: (06277-33) TROUBLE in > check_mail: decoding2-get-file-types FAILED: 'file' utility > (/usr/bin/file) failed, status=255 (65280 ) at /usr/sbin/amavisd-new > line 3853. Are you using a version of file(1) that is at least from 'stable' (I have 4.12-1). Are these errors crashing amavisd-new? What other errors are there (if any) that are related to this message? Are we seeing the complete picture? Is the evidence preserved where it may be tested on another system? I could be wrong but I'm thinking if these do not crash amavisd-new then this is mostly an annoyance that may likely be solved by upgrading amavisd-new. These may provide food for thought: http://www200.pair.com/mecham/spam/debian-amavisd-new_2.4.1.html http://www200.pair.com/mecham/spam/upgrade242.html This post has a suggestion also, but I question whether Sarge in particular has an issue with this, and while the workaround mentioned would probably work, whether it is the best way to fix the situation. http://archives.neohapsis.com/archives/postfix/2006-01/0090.html I wonder if installing file(1) from testing may offer any relief. Gary V ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
