Socket Cache / Shared Sockets for Auth/Resolver

[JINMEI Tatuya / 神明達哉]

At Fri, 15 Feb 2013 13:31:15 -0500,
Jonathan Towne <jontow at slic.com> wrote:

> I'm curious about the socket cache features, as I'm getting an error trying to run both
> Auth and Resolver with listen_on of :: and 0.0.0.0 sharing the same port for both
> components.  This isn't an unreasonable configuration, but it does seem to be failing
> for me with the following error:

First off, BIND 10 currently doesn't support this mode of operation:
have both auth and resolver listen on the same address/port.  We know
there's a need for this, and will probably make it possible in our
schedule revision of the resolver, but it currently doesn't work.

> 2013-02-15 13:11:32.844 ERROR [b10-auth.server_common/30868] SRVCOMM_ADDRESS_FAIL failed to listen on addresses ("Cached socket not compatible with mode SAMEAPP and name b10-auth")

> It doesn't appear that the socket cache code is documented anywhere other than the code
> itself (which I looked at, but I'm no Python or C++ guy).  Please let me know what other
> information, if any, would be helpful to trouble this one.

In my poor memory (it was implemented quite some time ago), auth
requests the port so that it won't be used by any other BIND 10
applications.  I suspect at the time of the above log b10-resolver was
already using the port, and that's the reason for this error message.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.