Hi Victor
So I have 10 sockets listening, but I have more lists to check. Does that
can be a reason?
I have also seen that if I remove some lists I get less of those errors and
if I add some I have more.
Can I higher the number of sockets listening for requests?
My main:
postscreen_dnsbl_sites =
zen.spamhaus.org*2
cbl.abuseat.org*2
b.barracudacentral.org*2
dyna.spamrats.com
bl.spameatingmonkey.net
bl.spamcop.net
free.v4BL.org*2
dnsbl-1.uceprotect.net
dnsbl.sorbs.net
all.s5h.net
swl.spamhaus.org*-4
whitelist.surriel.com*-4
wl.mailspike.net=127.0.0.[17;18]*-3
wl.mailspike.net=127.0.0.[19;20]*-6
So as you can see it are 13 lists and I only have 10 sockets listening.
# pgrep -x dnsblog | wc -l
Sometimes it gives me 0 and sometimes 10. I guess it depends on if there are
mails coming in or not.
The locks seem to be owned by dnsblog itself:
# lsof /var/spool/postfix/pid/unix.dnsblog
#
# fuser /var/spool/postfix/pid/unix.dnsblog
/var/spool/postfix/pid/unix.dnsblog: 17452 17453 17454 17455 17456 17457
17458 17459 17460 17461
#
# ps 17452
PID TTY STAT TIME COMMAND
17452 ? S 0:00 dnsblog -z -t unix -u
# ps 17453
PID TTY STAT TIME COMMAND
17453 ? S 0:00 dnsblog -z -t unix -u
#
# ps 17455
PID TTY STAT TIME COMMAND
17455 ? S 0:00 dnsblog -z -t unix -u
#
Kind regards
Laurens
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Viktor Dukhovni
Sent: donderdag 23 oktober 2014 18:07
To: [email protected]
Subject: Re: warning: psc_dnsbl_request: connect to private/dnsblog service:
Resource temporarily unavailable
On Thu, Oct 23, 2014 at 05:53:01PM +0200, Laurens Van Acker wrote:
> # pgrep -x dnsblog | wc -l
> 0
Seems unlikely, below nestat reports dnsblog processes
> The lock file is there:
>
> # ls /var/spool/postfix/pid/
> ... unix.dnsblog ...
Which process has it locked?
> # netstat -anp --unix | grep dnsblog
> unix 2 [ ACC ] STREAM LISTENING 526425 10764/master
private/dnsblog
> unix 2 [ ] DGRAM 717894 17046/dnsblog
> unix 2 [ ] DGRAM 716334 17041/dnsblog
> unix 2 [ ] DGRAM 717846 17038/dnsblog
> unix 2 [ ] DGRAM 716310 17037/dnsblog
> unix 2 [ ] DGRAM 717882 17044/dnsblog
> unix 2 [ ] DGRAM 716322 17039/dnsblog
> unix 2 [ ] DGRAM 716346 17043/dnsblog
> unix 2 [ ] DGRAM 717858 17040/dnsblog
> unix 2 [ ] DGRAM 717870 17042/dnsblog
> unix 2 [ ] DGRAM 716360 17045/dnsblog
> unix 2 [ ] DGRAM 716520 17053/dnsblog
She DGRAM socket is likely the syslog socket. I'm not seeing any dnsblog
processes listening on the actual dnsblog socket.
You have to dig deeper, but may lack the skill to do so... I can't
spoon-feed you through this one step at a time. :-(
--
Viktor.
