Error could not bind to port 43. Is another irrd running?

Nick Hilliard nick at
Fri Aug 15 21:11:29 UTC 2014

On 15/08/2014 21:55, Randy Bush wrote:
> no one else had port 43.  the problem was that iird dropped privs before
> trying to get the privileged port. 

not sure if this is the correct mailing list for an irrd problem, but the
code looks like it drops privileges after it opens up a socket on port 43,
not before.  See IRRd/main.c, lines 333-346.

I just fired up a test irrd instance on an fbsd10 dev box of mine and it
seemed to work fine running as nonroot.  Is there something peculiar about
your environment?


More information about the irrtoolset mailing list