Bug#687210: lwresd: failed to add lwres socket: 127.0.0.1#921: address in use

2013-01-27 Thread Adam Conrad
This isn't a problem with the blacklist patch in eglibc, at least not as far as I can tell with this simple test case. Perhaps the offending service(s) in question are reimplementing a local version of bindresvport instead of using glibc's, and thus skipping the blacklist?

Bug#687210: lwresd: failed to add lwres socket: 127.0.0.1#921: address in use

2013-01-10 Thread Anders Boström
FW == Florian Weimer f...@deneb.enyo.de writes: Happened again for me today. This time rpcbind got port 921: eckert:~# netstat -lnp | grep 921 udp0 0 0.0.0.0:921 0.0.0.0:* 2018/rpcbind udp6 0 0 :::921 :::*

Bug#687210: lwresd: failed to add lwres socket: 127.0.0.1#921: address in use

2012-10-05 Thread Florian Weimer
* Anders Boström: Sometimes when I boot my computer, lwresd fail to start and normal hostname lookup don't work. I get this error message in /var/log/syslog: 2012-09-10T22:08:28.715361+02:00 eckert lwresd[3809]: failed to add lwres socket: 127.0.0.1#921: address in use eckert:~# netstat

Bug#687210: lwresd: failed to add lwres socket: 127.0.0.1#921: address in use

2012-09-10 Thread Anders Boström
Package: lwresd Version: 1:9.8.1.dfsg.P1-4.2 Severity: normal Hi! Sometimes when I boot my computer, lwresd fail to start and normal hostname lookup don't work. I get this error message in /var/log/syslog: 2012-09-10T22:08:28.715361+02:00 eckert lwresd[3809]: failed to add lwres socket: