spamd makes an error on bootup. "error creating a dns resolver socket network not reachable at /usr/perl5/vendor_perl/mail/spamassassin/dnsresolver.pm at line 202" version 3.0.4. works correct. 3.0.1 and 3.0.1_r1 both dont work. i can start spamd after the bootprocess manually without errors. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 73287 [details] log file
(In reply to comment #0) > version 3.0.4. works correct. 3.0.1 and 3.0.1_r1 both dont work. > i can start spamd after the bootprocess manually without errors. 3.0.1 is not in portage any more...
hm.... nope. its in there... just synced again and its in there.
oh... lol i mean 3.1.0. ;)
I know this is tough to capture - but is spamd being started up prior to all of your network devices finishing up? I have a problem on my laptop for instance where dhcp doesn't always return immediately, so things like ntp (and I would suspect sa if I had it on there) can't start properly.
spamd starts after net (if the order is linear after everything gets an [ok] during boot, not simulatious). the order is: starting eth0 bringing up eth0 mounting networkfs starting privoxy starting spamd error
Ah, you have IPV6! Please emerge dev-perl/IO-Socket-INET6 and dev-perl/Socket6 (actually a dep of the first). Yes, this should be use flag enabled, just been running a bit ragged of late (sorry).
i dont have ipv6 support in my kernel. still emerge those components?
no, i actually misread the test. Here's the dealio: spamd is failing to open a socket, so you're getting the default failure message. This means that either something else is listening on that socket already (ick), or that it simply can't open it yet. Now the socket it is trying to open is to your dns resolver as set in resolv.conf (most likely). I originally asked about dhcp in the event that maybe your resolv.conf wasn't getting updated prior to spamd starting up. The ipv6 question was me on a wrong tangent. Now the localport spamd is trying to start on isn't quite random, but there's a good chance that it isn't conflicting with anything else, so either IO::Socket::INET is failing all together, or Net::DNS::Resolver isn't getting a response back to give to spamd's startup (but it does once everything on your box has settled down). Since spamd can start at all, I'd like to eliminate whether Net::DNS::Resolver is loading properly, but unfortunately this all points back to your dns server not responding or being contacted correctly. If you'd like, you can add a -D to the startup options for spamassassin (/etc/conf.d/spamd, SPAMD_OPTIONS should do it) to enable debugging output. I'm actually not sure where this will be tossed or how verbose it can get, but it should give a deep enough error report to be able to move forward.
Created attachment 73446 [details] log file with -D umm.... i just added spamd : facility = "*" program = "/usr/sbin/spamd" logdor = "/var/log/mail" to metalog to catch the output. hope its correct.
btw, i use adsl-setup/start to log in and iirc i used "server" for dns adress. but the entries in resolv.conf are real, correct dns server from my provider. (i also tried to input in adsl-setup ip adresses from my dns server (instead of "server") and didnt help) [and as i said 3.0.4 works so there is something in 3.1.0 that is not working corrrectly on my system]
I'm adding myself to the upstream bug on this (http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4694) - seems to be a known problem in sa. I've never marked a gentoo bug as upstream, so if it inappropriately closes it before we have a resolution, we can reset this to open :)
Bah, this is *your* bug on sa's bugzilla :)
yeah, i asked sa first. ;) there is also another one on the forum having that problem and a post from one who had it but could resolve it. http://forums.gentoo.org/viewtopic-t-403619.html seems i have to stick with 3.0.4 so if there is a delay what should i do? move the initialising upwards on boot? how do i do that?
(In reply to comment #14) > yeah, i asked sa first. ;) > there is also another one on the forum having that problem and a post from one > who had it but could resolve it. > http://forums.gentoo.org/viewtopic-t-403619.html > seems i have to stick with 3.0.4 The solution in the forum post is similar to what I mentioned - looks like dns isn't being completely configured before spamd is started up. > > so if there is a delay what should i do? move the initialising upwards on boot? > how do i do that? I've got nothing elegant to offer so far. Work arounds would be starting spamd in /etc/conf.d/local.start (since its the last thing run), or adding a slight delay to the startup of spamd (I still believe that your dns server isn't done being available to you even though net.eth0 has been assigned an ip already).
hmmm.... i tried to start spamd when i am not connected to the internet, same error. after connecting (adsl-start) spamd starts without error. thats totally crazy. why dont i have that problem with 3.0.4??
okay, i wrote /etc/init.d/spamd start in local and i get the error message "failed to start local" on bootup. i guess i HAVE TO connect to the inet before i can start spamd. thats idiotic. <_< seems i have to add a line to adsl-start to start spamd. <_<
Correct me if I'm wrong, but until you connect to the internet, you don't have the ability to verify dns entries. the new versions of sa verify a working dns server. ergo, no dns server, no sa.
