Random "bind: Can't assign requested address" messages on OS X

[eric@…]

I get these "bind: Can't assign requested address" messages when I start bitlbee in daemon mode on OS X. I'm sure that there is no other process listening to this port (checked it with "lsof -i 4") and address. Bzero'ing the sockaddr struct in bitlbee.c before calling bind() fixes the problem:

--- bitlbee.c 2006-06-24 16:00:43.000000000 +0200 +++ bitlbee.c.bzero 2006-07-12 10:49:18.000000000 +0200 @@ -63,6 +63,7 @@

log_error( "socket" ); return( -1 );

}

+ bzero((char *) &listen_addr, sizeof(listen_addr));

listen_addr.sin_family = AF_INET; listen_addr.sin_port = htons( global.conf->port ); listen_addr.sin_addr.s_addr = inet_addr( global.conf->iface );

[wilmer]

Thanks for the fix. Can you verify if the current development version also fixes the problem? If you got the time you can get a snapshot using bzr from ​http://code.bitlbee.org/bitlbee/. (Or use /hgweb to generate a tarball) I worked a lot on the daemon code and also added a ForkDaemon mode (which spawns a separate process for every client, which should be a lot more stable). The listening code should be much better there.

[wilmer]

Still seems to be broken. :-(

[bitlbee@…]

This should have been fixed by my patch in ​http://bugs.bitlbee.org/bitlbee/ticket/230. However, I failed by placing the memset in an if-block, but at least it works if you compile w/o ipv6-support :)

Sorry about the snag. Upping a new patch to the latest snapshot that sould remedy this in a couple of secs.

[wilmer]

I think Jelmer's getaddrinfo() change will have the same effect.