[AMaViS-user] Solved? Re: Bad file descriptor errors with AMaVIS under

2006-11-17 Thread Bradley M Alexander
I believe I have found the problem, thanks to Mark's direction. I wrote a quick script to dump most of the information to a file (except the perlrun stuff) on all four of the servers and diffed them. All the three servers which failed also had %ENV: PERLIO=stdio while monitor did not. I

Re: [AMaViS-user] Bad file descriptor errors with AMaVIS under

2006-11-16 Thread Bradley M Alexander
It failed in much the same way. It reported the proper data, but then gave me the bad file descriptor: [EMAIL PROTECTED] ~]# ./testfile testfile result line from file(1): testfile: perl script text executable Error reading from file(1) utility: Bad file descriptor at ./testfile line 24, GEN0 line

Re: [AMaViS-user] Bad file descriptor errors with AMaVIS under

2006-11-15 Thread Bradley M Alexander
Thanks Mark and Gary, I guess I'll be rebuilding that server with sarge over the weekend... Thanks for finding it. --b - Original Message - From: Mark Martinec [EMAIL PROTECTED] To: amavis-user@lists.sourceforge.net Sent: Wednesday, November 15, 2006 12:10:58 PM GMT-0500 US/Eastern

Re: [AMaViS-user] Bad file descriptor errors with AMaVIS under

2006-11-14 Thread Bradley M Alexander
I downgraded both file and libmagic1 and had the same problem. However, thanks to your subsequent email, I did get a lot better data from amavisd. Unfortunately, the file is too large to attach to this email. Therefore, I am posting the file to my website,

Re: [AMaViS-user] Bad file descriptor errors with AMaVIS under

2006-11-14 Thread Bradley M Alexander
My box is running sid with a stock 2.6.16-2-686-smp kernel...And with libmagic1 and file backed off to sarge. --b - Original Message - From: Gary V [EMAIL PROTECTED] To: amavis-user@lists.sourceforge.net Sent: Tuesday, November 14, 2006 12:23:31 PM GMT-0500 US/Eastern Subject: Re:

Re: [AMaViS-user] Bad file descriptor errors with AMaVIS under

2006-11-14 Thread Bradley M Alexander
Thanks Mark, Here is the information: Nov 14 15:10:27 merrimac amavis[28922]: (28922-01) result line from file(1): p001: ASCII English text\n Nov 14 15:10:27 merrimac amavis[28922]: (28922-01) result line from file(1): p002: ASCII English text, with very long lines \n Nov 14 15:13:34 merrimac

[AMaViS-user] [EMAIL PROTECTED]: Re: Bad file descriptor errors with AMaVIS under Zimbra]

2006-11-10 Thread Bradley M Alexander
Okay, I am appending two files to this message. I hope this is not breaking protocol. I attempted to send as attachments, but mailman caught it as a suspicious header. Hopefully this will work out better... In the first, I modified debug from 1 to 5 in /opt/zimbra/conf/amavisd.conf, turned on

Re: [AMaViS-user] Bad file descriptor errors with AMaVIS under Zimbra

2006-11-09 Thread Bradley M Alexander
amavisd is not chrooted unless Zimbra is doing so...And I don't believe it is. And there is no amavis or vscan user. Everything is run as the zimbra user...That said, file works fine from the command line: [EMAIL PROTECTED] amavisd]$ file db/nanny.db db/nanny.db: Berkeley DB (Hash, version 8,