connect(AF_INET) to spamd at 127.0.0.1 failed
I've seen this a couple of times the last few days in my syslog. Tonight, I saw it after updating to 3.0.4: Jun 11 19:38:21 cpollock spamd[7668]: server killed by SIGTERM, shutting down Jun 11 19:38:22 cpollock spamassassin: spamd shutdown succeeded Jun 11 19:53:32 cpollock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Jun 11 19:53:33 cpollock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused Prior to upgrading from .0.3 to .0.4 I ran #service spamassassin stop, and also shut down fetchmail so that nothing was processed, when the update was finished I started spamassassin and fetchmail. The below is 'not' when I started SA Jun 11 19:55:10 cpollock spamd[26754]: spamd starting Jun 11 19:55:11 cpollock spamd[26754]: server started on port 48373/tcp (running version 3.0.4) Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26760 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26761 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26762 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26763 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26764 This is where I started SA and fetchmail Jun 11 19:57:21 cpollock spamd[27144]: spamd starting Jun 11 19:57:21 cpollock spamassassin: spamd startup succeeded Jun 11 19:57:30 cpollock fetchmail[27167]: starting fetchmail 6.2.5 daemon Jun 11 19:57:33 cpollock spamd[27146]: server started on port 783/tcp (running version 3.0.4) But between 19:55 and 19:57 there is this: Jun 11 19:55:12 cpollock spamd[26760]: processing message 9PS291LhupY for root:0. Jun 11 19:55:12 cpollock spamd[26760]: identified spam (15.6/5.0) for root:0 in 0.4 seconds, 3131 bytes. Jun 11 19:55:12 cpollock spamd[26760]: result: Y 15 - ALL_NATURAL,DATE_IN_FUTURE_03_06,DIET_1,DRUGS_ERECTILE,DRUGS_PAIN,EXCUSE_12, EXCUSE_4,FORGED_YAHOO_RCVD,FROM_ENDS_IN_NUMS,FROM_HAS_MIXED_NUMS, INVALID_DATE,INVALID_MSGID,NORMAL_HTTP_TO_IP,NO_REAL_NAME,SELECTED_YOU, SUBJ_FREE_CAP,UNDISC_RECIPS scantime=0.4,size=3131,mid=9PS291LhupY,autolearn=spam I do 'not' have autolearn enabled. Any ideas what may have happened? Googling the error in the first lines seems to mention something about spamassassin as a server and spamd not running. Spamd is most certainly running as shown in running processes. Sorry for the long msg with log cuts but not sure what, if anything is amiss. Thanks Chris -- Chris Registered Linux User 283774 http://counter.li.org 21:16:05 up 13 days, 8:56, 3 users, load average: 1.46, 1.19, 1.16 Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk Linus? Whose that? -- clueless newbie on #Linux
Re: connect(AF_INET) to spamd at 127.0.0.1 failed
Chris wrote: I've seen this a couple of times the last few days in my syslog. Tonight, I saw it after updating to 3.0.4: Jun 11 19:38:21 cpollock spamd[7668]: server killed by SIGTERM, shutting down Jun 11 19:38:22 cpollock spamassassin: spamd shutdown succeeded Jun 11 19:53:32 cpollock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused Jun 11 19:53:33 cpollock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused is it possible that you had some incoming mail that was trying to connect to spamd even after you shut it down for upgrading? Prior to upgrading from .0.3 to .0.4 I ran #service spamassassin stop, and also shut down fetchmail so that nothing was processed, when the update was finished I started spamassassin and fetchmail. The below is 'not' when I started SA Jun 11 19:55:10 cpollock spamd[26754]: spamd starting Jun 11 19:55:11 cpollock spamd[26754]: server started on port 48373/tcp (running version 3.0.4) Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26760 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26761 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26762 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26763 Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26764 Did these appear during the installation process? if so, if you ran 'make test' these are probably the results of that. This is where I started SA and fetchmail Jun 11 19:57:21 cpollock spamd[27144]: spamd starting Jun 11 19:57:21 cpollock spamassassin: spamd startup succeeded Jun 11 19:57:30 cpollock fetchmail[27167]: starting fetchmail 6.2.5 daemon Jun 11 19:57:33 cpollock spamd[27146]: server started on port 783/tcp (running version 3.0.4) But between 19:55 and 19:57 there is this: Jun 11 19:55:12 cpollock spamd[26760]: processing message 9PS291LhupY for root:0. Jun 11 19:55:12 cpollock spamd[26760]: identified spam (15.6/5.0) for root:0 in 0.4 seconds, 3131 bytes. Jun 11 19:55:12 cpollock spamd[26760]: result: Y 15 - ALL_NATURAL,DATE_IN_FUTURE_03_06,DIET_1,DRUGS_ERECTILE,DRUGS_PAIN,EXCUSE_12, EXCUSE_4,FORGED_YAHOO_RCVD,FROM_ENDS_IN_NUMS,FROM_HAS_MIXED_NUMS, INVALID_DATE,INVALID_MSGID,NORMAL_HTTP_TO_IP,NO_REAL_NAME,SELECTED_YOU, SUBJ_FREE_CAP,UNDISC_RECIPS scantime=0.4,size=3131,mid=9PS291LhupY,autolearn=spam again, this is probably the results of the 'make test' and actually running tests against spamd. I use spamassassin in such a way that I do not use spamd (nor need it) yet during the 'make test' part of my CPAN install, i see spamd messages in my maillog (as a result). I do 'not' have autolearn enabled. Any ideas what may have happened? Googling the error in the first lines seems to mention something about spamassassin as a server and spamd not running. Spamd is most certainly running as shown in running processes. Sorry for the long msg with log cuts but not sure what, if anything is amiss. Thanks Chris alan
Re: connect(AF_INET) to spamd at 127.0.0.1 failed
On Saturday 11 June 2005 11:02 pm, alan premselaar wrote: Chris wrote: I've seen this a couple of times the last few days in my syslog. Tonight, I saw it after updating to 3.0.4: Jun 11 19:38:21 cpollock spamd[7668]: server killed by SIGTERM, shutting down Jun 11 19:38:22 cpollock spamassassin: spamd shutdown succeeded Jun 11 19:53:33 cpollock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused is it possible that you had some incoming mail that was trying to connect to spamd even after you shut it down for upgrading? Shouldn't have been since I also shut down fetchmail at the same time. Prior to upgrading from .0.3 to .0.4 I ran #service spamassassin stop, and also shut down fetchmail so that nothing was processed, when the update was finished I started spamassassin and fetchmail. The below is 'not' when I started SA Jun 11 19:55:10 cpollock spamd[26754]: spamd starting Jun 11 19:55:11 cpollock spamd[26754]: server started on port 48373/tcp (running version 3.0.4) Jun 11 19:55:11 cpollock spamd[26754]: server successfully spawned child process, pid 26760 Did these appear during the installation process? if so, if you ran 'make test' these are probably the results of that. I'd probably have to say they did. I install w/cpan via webmin. This is where I started SA and fetchmail Jun 11 19:57:21 cpollock spamd[27144]: spamd starting Jun 11 19:57:21 cpollock spamassassin: spamd startup succeeded Jun 11 19:57:30 cpollock fetchmail[27167]: starting fetchmail 6.2.5 daemon Jun 11 19:57:33 cpollock spamd[27146]: server started on port 783/tcp (running version 3.0.4) Jun 11 19:55:12 cpollock spamd[26760]: processing message 9PS291LhupY for root:0. Jun 11 19:55:12 cpollock spamd[26760]: identified spam (15.6/5.0) for root:0 in 0.4 seconds, 3131 bytes. Jun 11 19:55:12 cpollock spamd[26760]: result: Y 15 - ALL_NATURAL,DATE_IN_FUTURE_03_06,DIET_1,DRUGS_ERECTILE,DRUGS_PAIN,EXCUSE_ 12, EXCUSE_4,FORGED_YAHOO_RCVD,FROM_ENDS_IN_NUMS,FROM_HAS_MIXED_NUMS, INVALID_DATE,INVALID_MSGID,NORMAL_HTTP_TO_IP,NO_REAL_NAME,SELECTED_YOU, SUBJ_FREE_CAP,UNDISC_RECIPS scantime=0.4,size=3131,mid=9PS291LhupY,autolearn=spam again, this is probably the results of the 'make test' and actually running tests against spamd. I use spamassassin in such a way that I do not use spamd (nor need it) yet during the 'make test' part of my CPAN install, i see spamd messages in my maillog (as a result). alan You're probably correct in all of the above alan, I just don't remember seeing it before. Then the only really odd thing is the connect(AF_INET) to spamd at 127.0.0.1 failed error. -- Chris Registered Linux User 283774 http://counter.li.org 23:08:41 up 13 days, 10:49, 1 user, load average: 0.17, 0.29, 0.34 Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
SpamAssassin 3.0.3 errors - connect(AF_INET) to spamd at 127.0.0.1 failed - attempt 2
I sent this in on Friday last week and didn't attract any responses. Any insight would be appreciated. I've seen this behaviour once since then, despite my cronjob restarting spamd every 4 hours. Should I just open a bug report? I'm running spamassassin 3.0.3 as a proxy on three mail servers. This morning at 2am one of the three (but not the other two) started spewing a lot of spamc[8000]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3) and did not identify any messages as spam until a user complained and I restarted spamd a few minutes ago. Any ideas as to what's going on and what I can do to keep it from happening again? As a kludge for now I'm going to have cron restart spamd every few hours. Mick
SpamAssassin 3.0.3 errors - connect(AF_INET) to spamd at 127.0.0.1 failed
I'm running spamassassin 3.0.3 as a proxy on three mail servers. This morning at 2am one of the three (but not the other two) started spewing a lot of spamc[8000]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3) and did not identify any messages as spam until a user complained and I restarted spamd a few minutes ago. Any ideas as to what's going on and what I can do to keep it from happening again? As a kludge for now I'm going to have cron restart spamd every few hours. Mick
