Re: ENOSR on UDP socket creation on Solaris 10 U4
- From: andrew@xxxxxxxxxxxxxxxxxxxx (Andrew Gabriel)
- Date: 09 Oct 2007 16:13:24 GMT
In article <72myus7lio.fsf@xxxxxxxxxxxxxxxxxxx>,
Alex Kiernan <alex.kiernan@xxxxxxxx> writes:
Anyone any ideas where/what to tweak to avoid getting ENOSR in
response to a SOCK_DGRAM socket create?
We're running PowerDNS recursor and are seeing occasional (once a
day?) errors:
startDoResolve problem: Making a socket for resolver: Out of stream resources
Which traces back to:
socket(PF_INET, SOCK_DGRAM, 0);
A quick (and inadequate) browse of the opensolaris source would
seem to imply this happens if sockfs times out the initial
response from the udp module, when it's asking for the
capabilities of the stream. A comment elsewhere implies this
can happen for tcp streams under system heavy load conditions.
It may be that the same is true for udp too. Could your system
be under heavy load?
--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]
.
- Follow-Ups:
- Re: ENOSR on UDP socket creation on Solaris 10 U4
- From: Alex Kiernan
- Re: ENOSR on UDP socket creation on Solaris 10 U4
- References:
- ENOSR on UDP socket creation on Solaris 10 U4
- From: Alex Kiernan
- ENOSR on UDP socket creation on Solaris 10 U4
- Prev by Date: Re: Problem getting console on v890 RSC
- Next by Date: Re: crontab referencing nonexistant file(system)
- Previous by thread: ENOSR on UDP socket creation on Solaris 10 U4
- Next by thread: Re: ENOSR on UDP socket creation on Solaris 10 U4
- Index(es):
Relevant Pages
|