I've been getting a lot of errors reporting spam to razor. I'm usually doing this through spamassassin -D --report. The default of 10 seconds often times out. When I cranked spamassassin's razor timeout up to 60 seconds, instead I started getting these "Bad file descriptor Died at" errors, which I haven't managed to replicate using razor-report directly as I haven't seen any documentation in the razor-report or razor-agent.conf man pages on how to increase the timeout.
These things lead me to be concerned that data is being lost because of these timeouts and errors, and users not bothering to look at logs. Then I looked at my logs, and noticed it wasn't even logging these errors. Here's part of the output from an error: Dec 18 10:52:26.856026 report[5494]: [ 8] preparing 2 queries Dec 18 10:52:26.856760 report[5494]: [ 8] sending 1 batches Dec 18 10:52:26.857213 report[5494]: [ 4] folly.cloudmark.com << 96 Dec 18 10:52:26.857478 report[5494]: [ 6] -a=r&e=1&s=DhKl5kzrpWW3Vh9VDVo--IN2FEUA a=r&e=4&ep4=7542-10&s=klzxceMABlXES8nDxlP6R7lR03wA . razor2 report failed: Bad file descriptor Died at /usr/local/local/share/perl/5.6.1/Mail/SpamAssassin/Reporter.pm line 120, <GEN0> line 1. Here's a snip from my ~/.razor/razor-agent.log log that includes the time range of that error, completely lacking any indication there was an error: Dec 18 10:25:22.713883 check[5021]: [ 1] [bootup] Logging initiated LogDebugLevel=3 to file:/home/darxus/.razor/razor-agent.log Dec 18 10:38:49.869591 report[5202]: [ 1] [bootup] Logging initiated LogDebugLevel=3 to file:/home/darxus/.razor/razor-agent.logDec 18 10:38:49.870880 report[5202]: [ 2] Razor-Agents v2.36 starting razor-report Dec 18 10:39:03.091916 report[5205]: [ 3] Sent report. Dec 18 10:46:33.151732 check[5321]: [ 1] [bootup] Logging initiated LogDebugLevel=3 to file:/home/darxus/.razor/razor-agent.log Dec 18 10:51:37.851683 check[5472]: [ 1] [bootup] Logging initiated LogDebugLevel=3 to file:/home/darxus/.razor/razor-agent.log Dec 18 10:53:01.101732 check[5517]: [ 1] [bootup] Logging initiated LogDebugLevel=3 to file:/home/darxus/.razor/razor-agent.log Dec 18 10:57:46.032163 check[5596]: [ 1] [bootup] Logging initiated LogDebugLevel=3 to file:/home/darxus/.razor/razor-agent.log Dec 18 10:57:58.992030 check[5596]: [ 3] mail 1 is not known spam. I manually did a razor-admin -discover, which switched me from joy to folly, which reduced the frequency of the errors, but I'm still seeing them often, and I'm still more concerned about the amount of data being lost. And I would've thought razor would automatically try another server when it fails to connect to one. -- "It's a dangerous business, Frodo, going out your front door. You step into the Road, and if you don't keep your feet, there is no knowing where you might be swept off to." - Gandalf http://www.ChaosReigns.com ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
