-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Ihsan,
This means that the setsockopt function for the option SO_REUSEADDR
failed. This may be because the option is undefined in Solaris 10.
Otherwise, the setsockopt failed and returned the error E_INVAL.
What does SO_REUSEADDR do? It basically says the socket can use an
address already in use. This is useful if your server is being
restarted, while sockets may still be active on the port.
If SO_REUSEADDR failed, we try to set the SO_LINGER socket option. This
tells the socket to return immediately after a close(). For the client
it looks like if the connection was reset. For the server, we prevent
that binding the outgoing interface fails after a restart, because the
port could still be in use.
So, this isn't a fatal error. Even if we failed to set the SO_LINGER
option, we will still try to bind the interface.
Should we increase the verbosity for these log messages?
Kind regards,
Matthijs Mekking
NLnet Labs
Ihsan Dogan wrote:> Hello,
>
> I'm running NSD 3.2.1 on Solaris 10 (sparc) and I've noticed that
this
> messages shows up in syslog on a regular base:
>
> May 5 11:36:47 bender nsd[2005]: [ID 702911 daemon.warning] xfrd:
> setsockopt SO_REUSEADDR failed: Invalid argument
>
> As far NSD works as expected, I'm wondering how I should deal with this
> message.
>
>
>
>
> Ihsan
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQEcBAEBAgAGBQJKATlLAAoJEA8yVCPsQCW5xQoIALhZm5CAx6W66fltwl+9GHD3
UiJOrg0Z5Z3vxIwcoOULLtKJYM7ZNPOBnH04NXu9sLxPnIKtSkTbN8zl/y4Uptg4
wh85rY1cQ5g+F241AqrdhfenwIO8ctnCFrJOZ7Wu5YsnGyYhpOz3FHAtXAXacfFN
IFZ1jLRA2EGb3Gh9sWq+TrUOIoztZM3AK/sRTGeil2ORQXqlwLbzVA7j3yBtYr+2
WlC81q95dumcVJHeALdQj8yTulEbZZP43prNEmIwpR6r8EI3TgjDO0kmvl+Mz/te
JY5afbrbjUnocLSgzx63bKunzONspb0ZCZyhWf27eVM01H9e1FtUpECw1oMrfck=DYtD
-----END PGP SIGNATURE-----