On Thu, Oct 23, 2014 at 05:28:21PM +0200, Laurens Van Acker wrote:
> Hi Viktor
>
> This is my master.cf:
> dnsblog unix - - n - 0 dnsblog
>
> Number of processes:
>
> # ps -Al | wc -l
> 159
That's all processes, how about dnsblog processes? On linux:
pgrep -x dnsblog | wc -l
> How do I get the number of pending unaccepted connections?
Depends on your OS.
# netstat -anp --unix
might work on Linux when run as root. You'll want to look
at things trying to connect to /var/spool/postfix/private/dnsblog
> Oct 23 17:15:54 uk01 postfix/anvil[16202]: statistics: max connection rate
> 2/60s for (smtpd:5.134.1.44) at Oct 23 17:07:01
> Oct 23 17:15:54 uk01 postfix/anvil[16202]: statistics: max connection count
> 1 for (smtpd:192.64.236.99) at Oct 23 17:06:25
> Oct 23 17:15:54 uk01 postfix/anvil[16202]: statistics: max cache size 4 at
> Oct 23 17:08:56
> Oct 23 17:17:01 uk01 postfix/postscreen[16541]: CONNECT from
> [5.134.1.44]:48628 to [109.74.192.6]:25
> Oct 23 17:17:01 uk01 postfix/postscreen[16541]: warning: psc_dnsbl_request:
> connect to private/dnsblog service: Resource temporarily unavailable
The process that is supposed to be accepting connections on this
socket is stuck. Possibly a kernel bug. On a busy system, there
should be one dbsblog process holding an exclusive lock on:
/var/spool/postfix/pid/unix.dbsblog
this process should be blocked in an accept(2) system call. If
clients are trying to connect, but that process remains blocked,
your kernel is buggy.
--
Viktor.
