Re: relayd[66834]: relayd: socketpair: Too many open files

Just wanted to report back that as advertised 6.0-current from 2016-01-05 solved the problem described below. Thanks Theo, Reyk, Peter, et al. On Tue, Jan 3, 2017 at 1:16 PM, Kevin wrote: > Hey gang, > > So I'm putting a new firewall in place and have run into issues with >

Re: relayd[66834]: relayd: socketpair: Too many open files

On Thu, Jan 5, 2017 at 10:07 AM, Peter Faiman wrote: > Hmm. The default number of files is 128 for daemons, but it's strange > you'd hit that JUST starting up. > > Can you try starting relayd with -v -d to see if it logs anything of > interest? > # /usr/sbin/relayd -vvv

Re: relayd[66834]: relayd: socketpair: Too many open files

On Thu, Jan 5, 2017 at 10:19 AM, Peter Faiman wrote: > Ah yes I see those lines now, thank you. > > Kevin, what version of OpenBSD are you using? You mentioned this is a new > project so I assume 6.0? > >From my dmesg: OpenBSD 6.0-stable (GENERIC.MP )

Re: relayd[66834]: relayd: socketpair: Too many open files

Ah yes I see those lines now, thank you. Kevin, what version of OpenBSD are you using? You mentioned this is a new project so I assume 6.0? Peter On Jan 5, 2017, at 10:08, Theo de Raadt wrote: >> Hmm. The default number of files is 128 for daemons, but it's strange you'd

Re: relayd[66834]: relayd: socketpair: Too many open files

> Hmm. The default number of files is 128 for daemons, but it's strange you'd > hit that JUST starting up. > > Can you try starting relayd with -v -d to see if it logs anything of > interest? > > Can you binary search ulimits until you find the lowest it will start with? > > Reading the source

Re: relayd[66834]: relayd: socketpair: Too many open files

Hmm. The default number of files is 128 for daemons, but it's strange you'd hit that JUST starting up. Can you try starting relayd with -v -d to see if it logs anything of interest? Can you binary search ulimits until you find the lowest it will start with? Reading the source it looks like

Re: relayd[66834]: relayd: socketpair: Too many open files

Nope. I was hoping for another solution, especially given that: 1. the only thing runnings on this machine are pf and relayd 2. there's zero traffic going to it at present 3. there's only one site being load balanced it seems like it shouldn't be necessary. I'm open to it, if that's

Re: relayd[66834]: relayd: socketpair: Too many open files

Have you modified your open file limits in /etc/login.conf? Especially in the daemon section? Peter > On Jan 5, 2017, at 08:50, Kevin wrote: > >> On Tue, Jan 3, 2017 at 1:16 PM, Kevin wrote: >> >> Hey gang, >> >> So I'm putting a new firewall in place and

Re: relayd[66834]: relayd: socketpair: Too many open files

On Tue, Jan 3, 2017 at 1:16 PM, Kevin wrote: > Hey gang, > > So I'm putting a new firewall in place and have run into issues with > getting relayd to start using: > > # /etc/rc.d/relayd start > > When I try starting it like that inevitably I get: > > relayd(failed) > >

Re: relayd[66834]: relayd: socketpair: Too many open files

Tiny detail omitted previously (mea culpa): this is on a vultr.com machine. OpenBSD 6.0-stable (GENERIC.MP) #0: Wed Dec 28 14:13:24 PST 2016 ksmith@template:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 788381696 (751MB) avail mem = 760070144 (724MB) mpath0 at root scsibus0 at

Re: relayd[66834]: relayd: socketpair: Too many open files

dmesg please > Am 03.01.2017 um 22:16 schrieb Kevin : > > Hey gang, > > So I'm putting a new firewall in place and have run into issues with > getting relayd to start using: > > # /etc/rc.d/relayd start > > When I try starting it like that inevitably I get: > >

relayd[66834]: relayd: socketpair: Too many open files

Hey gang, So I'm putting a new firewall in place and have run into issues with getting relayd to start using: # /etc/rc.d/relayd start When I try starting it like that inevitably I get: relayd(failed) checking the log files tells me: relayd: socketpair: Too many open files Having