Re: filter-api socketpair leak?

> On 18 Apr 2016, at 14:08, Boudewijn Dijkstra > wrote: > >>> didn't change. How should I turn on said tracing? >> >> Add the flags to the smtpd startup, either manually or via rc.conf(8), >> e.g. smtpd -dv -Tall > > smtpd -v -Tall > doesn't seem to make it

Re: filter-api socketpair leak?

Op Sun, 17 Apr 2016 21:05:49 +0200 schreef Joerg Jung : On Fri, Apr 15, 2016 at 11:35:27AM +0200, Boudewijn Dijkstra wrote: But the amount of information written per session to /var/log/syslog oops I meant maillog didn't change. How should I turn on said tracing? Add the

Re: filter-api socketpair leak?

On Fri, Apr 15, 2016 at 11:35:27AM +0200, Boudewijn Dijkstra wrote: > > >5. Can you turn on tracing the filters and smtp session to see, where it > > stuck exactly? > > # smtpctl trace filter > smtpctl: invalid trace keyword: filter > # smtpctl trace filters > command succeeded > > Not sure

Re: filter-api socketpair leak?

On Thu, Apr 14, 2016 at 02:00:41PM +0200, Boudewijn Dijkstra wrote: > After some hours or days after starting smtpd I get: > > Apr 13 21:39:58 belisama spf[25177]: warn: filter-api:spf socketpair: Too > many open files > Apr 13 21:39:58 belisama delay[14001]: warn: session e6640a1435e43218: write

Re: filter-api socketpair leak?

Op Thu, 14 Apr 2016 20:11:48 +0200 schreef Joerg Jung : On Thu, Apr 14, 2016 at 02:00:41PM +0200, Boudewijn Dijkstra wrote: After some hours or days after starting smtpd I get: Apr 13 21:39:58 belisama spf[25177]: warn: filter-api:spf socketpair: Too many open files Apr 13

filter-api socketpair leak?

After some hours or days after starting smtpd I get: Apr 13 21:39:58 belisama spf[25177]: warn: filter-api:spf socketpair: Too many open files Apr 13 21:39:58 belisama delay[14001]: warn: session e6640a1435e43218: write out of sequence Apr 13 21:39:58 belisama last message repeated 95 times