Re: 3.1.2 spamd dies without warning
On Tue, May 30, 2006 at 10:31:27AM -0400, [EMAIL PROTECTED] wrote: > BTW, can anybody tell me whether or not spamd re-reads the .pre files if > you just give it a SIG HUP, or do you have to kill and restart it (I did > that this time anyway)? A HUP should cause spamd to re-exec (basically killing itself off and restarting), reading in all the config files again. -- Randomly Generated Tagline: "You have to stay in shape. My grandmother, she started walking 5 miles a day when she was 60. She's 97 today and we don't know where the hell she is." - Ellen DeGeneres pgpQfs7H8PzLN.pgp Description: PGP signature
Re: 3.1.2 spamd dies without warning
Ok, I'm giving that a shot. The only changes I noted wrt DCC were licensing-related, but I hadn't run it in so long, I can't recall wether it was worth the trouble or not. I've already noticed CPU went way down after disabling it. :) BTW, can anybody tell me whether or not spamd re-reads the .pre files if you just give it a SIG HUP, or do you have to kill and restart it (I did that this time anyway)? Thanks again! On Tue, 30 May 2006, Justin Mason wrote: > > eek. There were changes made to the DCC support; could you try turning > that off again, to see if that may have been the culprit? > > --j. > > [EMAIL PROTECTED] writes: > > I upgraded from 3.0.4 yesterday without too much trouble...once I got > > 3.1.2 online, I noticed a nice reduction in false negatives, and cpu > > remained low (holiday here in US). > > > > This morning, spamd died with no warning, except of course a huge increase > > in spam. Nothing in /var/log/messages, and only this in maillog: > > > > May 30 08:19:27 mail spamd[83175]: spamd: result: Y 44 - > > BAYES_99,EXTRA_MPART_TY > > PE,HELO_DYNAMIC_HCC,HELO_DYNAMIC_IPADDR2,HTML_90_100,HTML_IMAGE_ONLY_08,HTML_MES > > SAGE,HTML_SHORT_LINK_IMG_1,INFO_TLD,MIME_HTML_MOSTLY,RAZOR2_CF_RANGE_51_100,RAZO > > R2_CF_RANGE_E4_51_100,RAZOR2_CHECK,RCVD_IN_NJABL_DUL,URIBL_JP_SURBL,URIBL_OB_SUR > > BL,URIBL_SC_SURBL,URIBL_WS_SURBL > > scantime=1.5,size=13627,user=simscan,uid=0,requ > > ired_score=6.0,rhost=localhost.pil.net,raddr=127.0.0.1,rport=2895,mid=<000c01c68 > > [EMAIL PROTECTED]>,bayes=0.9998609,autolearn=spam > > May 30 08:19:34 mail spamc[83329]: connect(AF_INET) to spamd at 127.0.0.1 > > failed, retrying (#1 of 3): Connection refused > > May 30 08:19:34 mail spamc[83359]: connect(AF_INET) to spamd at 127.0.0.1 > > failed, retrying (#1 of 3): Connection refused > > > > It took me about an hour and a half to notice it. I restarted spamd and > > it's going ok at moderate cpu use. Here are my flags with which I start > > spamd: > > > > /usr/local/bin/spamd -m 15 -d -x -r /var/run/spamd.pid > > > > The only changes I made with the upgrade were that I enabled SPF, DCC and > > Pyzor. When building the new version, it did complain about an outdated > > razor2 software, but as it was only a warning (and I'd never had problems > > with it before), I didn't bother to UG. > > > > Any ideas as to the possible cause? > > > > James Smallacombe PlantageNet, Inc. CEO and Janitor > > [EMAIL PROTECTED] > > http://3.am > > = > James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: 3.1.2 spamd dies without warning
eek. There were changes made to the DCC support; could you try turning that off again, to see if that may have been the culprit? --j. [EMAIL PROTECTED] writes: > I upgraded from 3.0.4 yesterday without too much trouble...once I got > 3.1.2 online, I noticed a nice reduction in false negatives, and cpu > remained low (holiday here in US). > > This morning, spamd died with no warning, except of course a huge increase > in spam. Nothing in /var/log/messages, and only this in maillog: > > May 30 08:19:27 mail spamd[83175]: spamd: result: Y 44 - > BAYES_99,EXTRA_MPART_TY > PE,HELO_DYNAMIC_HCC,HELO_DYNAMIC_IPADDR2,HTML_90_100,HTML_IMAGE_ONLY_08,HTML_MES > SAGE,HTML_SHORT_LINK_IMG_1,INFO_TLD,MIME_HTML_MOSTLY,RAZOR2_CF_RANGE_51_100,RAZO > R2_CF_RANGE_E4_51_100,RAZOR2_CHECK,RCVD_IN_NJABL_DUL,URIBL_JP_SURBL,URIBL_OB_SUR > BL,URIBL_SC_SURBL,URIBL_WS_SURBL > scantime=1.5,size=13627,user=simscan,uid=0,requ > ired_score=6.0,rhost=localhost.pil.net,raddr=127.0.0.1,rport=2895,mid=<000c01c68 > [EMAIL PROTECTED]>,bayes=0.9998609,autolearn=spam > May 30 08:19:34 mail spamc[83329]: connect(AF_INET) to spamd at 127.0.0.1 > failed, retrying (#1 of 3): Connection refused > May 30 08:19:34 mail spamc[83359]: connect(AF_INET) to spamd at 127.0.0.1 > failed, retrying (#1 of 3): Connection refused > > It took me about an hour and a half to notice it. I restarted spamd and > it's going ok at moderate cpu use. Here are my flags with which I start > spamd: > > /usr/local/bin/spamd -m 15 -d -x -r /var/run/spamd.pid > > The only changes I made with the upgrade were that I enabled SPF, DCC and > Pyzor. When building the new version, it did complain about an outdated > razor2 software, but as it was only a warning (and I'd never had problems > with it before), I didn't bother to UG. > > Any ideas as to the possible cause? > > James Smallacombe PlantageNet, Inc. CEO and Janitor > [EMAIL PROTECTED] > http://3.am > =
3.1.2 spamd dies without warning
I upgraded from 3.0.4 yesterday without too much trouble...once I got 3.1.2 online, I noticed a nice reduction in false negatives, and cpu remained low (holiday here in US). This morning, spamd died with no warning, except of course a huge increase in spam. Nothing in /var/log/messages, and only this in maillog: May 30 08:19:27 mail spamd[83175]: spamd: result: Y 44 - BAYES_99,EXTRA_MPART_TY PE,HELO_DYNAMIC_HCC,HELO_DYNAMIC_IPADDR2,HTML_90_100,HTML_IMAGE_ONLY_08,HTML_MES SAGE,HTML_SHORT_LINK_IMG_1,INFO_TLD,MIME_HTML_MOSTLY,RAZOR2_CF_RANGE_51_100,RAZO R2_CF_RANGE_E4_51_100,RAZOR2_CHECK,RCVD_IN_NJABL_DUL,URIBL_JP_SURBL,URIBL_OB_SUR BL,URIBL_SC_SURBL,URIBL_WS_SURBL scantime=1.5,size=13627,user=simscan,uid=0,requ ired_score=6.0,rhost=localhost.pil.net,raddr=127.0.0.1,rport=2895,mid=<000c01c68 [EMAIL PROTECTED]>,bayes=0.9998609,autolearn=spam May 30 08:19:34 mail spamc[83329]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused May 30 08:19:34 mail spamc[83359]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused It took me about an hour and a half to notice it. I restarted spamd and it's going ok at moderate cpu use. Here are my flags with which I start spamd: /usr/local/bin/spamd -m 15 -d -x -r /var/run/spamd.pid The only changes I made with the upgrade were that I enabled SPF, DCC and Pyzor. When building the new version, it did complain about an outdated razor2 software, but as it was only a warning (and I'd never had problems with it before), I didn't bother to UG. Any ideas as to the possible cause? James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
