[antispam-f] Re: NSQ - failure to restart
- From: Frank de Bruijn <antispam@xxxxxxxxx>
- To: antispam@xxxxxxxxxxxxx
- Date: Tue, 22 Apr 2008 22:44:28 +0200
In article <4f942a68bbsteve.pampling@xxxxxxxxxxxxx>,
Steven Pampling <steve.pampling@xxxxxxxxxxxxx> wrote:
> Under certain obscure circumstances the NSQ resource can fail and a
> restart of Antispam does not cure the problem.
Kicking your upstream nameserver might.
> Symptom: may (but not always) give a No zones error.
This means NSQ has tried to get a test message from the DNSBL zones and
failed. That doesn't have to be because all the BL providers are down.
It could very well be a 'hiccup' in the DNS somewhere between your
computer and the server(s) that provide(s) the info.
> When this happens the cure seems to be to navigate to the NSQ
> resource directory and forcibly reload the NSQ module.
That may work. The command
*nsqcache -c1
might as well (I really need to finish NSQ's docs...). This performs a
full 'close down' (including releasing event vectors, closing sockets
and releasing the dynamic area), followed by a reinitialisation of the
module.
Of course, even reloading the module won't help if the interruption of
the DNS that caused the 'No zones' error is still present.
> While I'm not sure of the trigger it appears to be triggered by a
> loss of connection while a download is in progress.
Immediately before the run is started, actually, and only if AntiSpam
sees Weight rules in the rules file.
> Since simply restarting Antispam does not cure the problem it seems
> the start of NSQ is conditional and perhaps should be made
> unconditional.
If you use Weight rules, NSQ has to get its info from somewhere. If it
can't, the Weight rules won't work.
I suppose I could create an option to ignore all Weight rules when this
happens. Problem is, I doubt AntiSpam would be able to do much message
checking at such a time anyway. You might get a failure of the normal
resolver at the same time, so if the POP3 server's address doesn't
happen to be cached somewhere, connecting to that server will fail as
well.
The strange thing is, two or three people have mentioned this since
DNSBL testing was added to AntiSpam, but I've never seen it happen
myself.
Regards,
Frank
Other related posts:
