Bug #116232 for IO-Socket-IP: 'new' throws misleading 'croak' when open files limit exceeded

Sat Jul 16 23:02:17 2016 starlight.2016q3 [...] binnacle.cx - Ticket created

Subject:	'new' throws misleading 'croak' when open files limit exceeded
Date:	Sat, 16 Jul 2016 22:53:08 -0400
To:	bug-IO-Socket-IP [...] rt.cpan.org
From:	starlight.2016q3 [...] binnacle.cx

While stress testing a high-capacity event-driven script that issues larger numbers of asynchronous Net::DNS::Resolver queries (in select-driven bgsend/bgread style) hit upon the default 1024 open files limit (ulimit -HSn). At line 936 of DNS-1.06/Resolver/Base.pm a call to IO::Socket::IP->new() fails with the error "Unrecognised protocol udp at Net/DNS/Resolver/Base.pm line 936" which is actually thrown from IO/Socket/IP-0.37.pm line 425 The error is misleading and without some previous experience I would not have quickly figured out the cause. Running the stress test after ulimit -HSn 10240 worked correctly and without error. The problem appears to be some kind of secondary consequence of the resource exhaustion, though I did not rigorously hunt down the precise chain of cause-and-effect. Possibly the call to socket() lacks complete error checking or contains a mistake.

Tue Aug 02 12:21:43 2016 leonerd-cpan [...] leonerd.org.uk - Correspondence added

On Sat Jul 16 23:02:17 2016, starlight.2016q3@binnacle.cx wrote: Show quoted text

> While stress testing a high-capacity event-driven > script that issues larger numbers of asynchronous > Net::DNS::Resolver queries (in select-driven > bgsend/bgread style) hit upon the default > 1024 open files limit (ulimit -HSn). > > At line 936 of DNS-1.06/Resolver/Base.pm a call > to IO::Socket::IP->new() fails with the error > > "Unrecognised protocol udp at Net/DNS/Resolver/Base.pm line 936" > > which is actually thrown from > > IO/Socket/IP-0.37.pm line 425 > > The error is misleading and without some previous > experience I would not have quickly figured out > the cause. Running the stress test after > > ulimit -HSn 10240 > > worked correctly and without error. The problem > appears to be some kind of secondary consequence > of the resource exhaustion, though I did not > rigorously hunt down the precise chain of > cause-and-effect. Possibly the call to socket() > lacks complete error checking or contains a mistake. >

I believe this may be a repeat of https://rt.cpan.org/Ticket/Display.html?id=115036 -- Paul Evans

Tue Aug 02 12:21:44 2016 The RT System itself - Status changed from 'new' to 'open'

Tue Aug 02 13:50:13 2016 starlight.2016q3 [...] binnacle.cx - Correspondence added

Subject:	Re: [rt.cpan.org #116232] 'new' throws misleading 'croak' when open files limit exceeded
Date:	Tue, 02 Aug 2016 13:49:05 -0400
To:	bug-IO-Socket-IP [...] rt.cpan.org
From:	starlight.2016q3 [...] binnacle.cx

At 12:21 8/2/2016 -0400, you wrote: Show quoted text

> >I believe this may be a repeat of > > https://rt.cpan.org/Ticket/Display.html?id=115036

I agree they seem either closely related or are the same issue. But since the exhibited behavior is quite different perhaps both tickets should stay active until corrected.