[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
kdc not binding correctly
I had a feeling I previously reported this, but then it come good or
something.
...well it has gone bad again ;-)
Heimdal 0.5.1, Debian version.
snoopy:unstable:~# /usr/lib/heimdal-servers/kdc
[...]
2003-03-03T15:43:51 listening on IPv4:127.0.0.1 port 88/udp
2003-03-03T15:43:51 listening on IPv4:192.168.87.1 port 88/udp
2003-03-03T15:43:51 listening on IPv4:203.12.237.110 port 88/udp
2003-03-03T15:43:51 listening on IPv4:203.12.237.97 port 88/udp
2003-03-03T15:43:51 listening on IPv4:127.0.0.1 port 88/tcp
2003-03-03T15:43:51 listening on IPv4:192.168.87.1 port 88/tcp
2003-03-03T15:43:51 listening on IPv4:203.12.237.110 port 88/tcp
2003-03-03T15:43:51 listening on IPv4:203.12.237.97 port 88/tcp
2003-03-03T15:43:51 listening on IPv4:127.0.0.1 port 750/udp
2003-03-03T15:43:51 listening on IPv4:192.168.87.1 port 750/udp
2003-03-03T15:43:51 listening on IPv4:203.12.237.110 port 750/udp
2003-03-03T15:43:51 listening on IPv4:203.12.237.97 port 750/udp
2003-03-03T15:43:51 listening on IPv4:127.0.0.1 port 750/tcp
2003-03-03T15:43:51 bind IPv4:192.168.87.1/750: Address already in use
2003-03-03T15:43:51 listening on IPv4:203.12.237.110 port 750/tcp
2003-03-03T15:43:51 bind IPv4:203.12.237.97/750: Address already in use
2003-03-03T15:43:51 listening on IPv4:127.0.0.1 port 4444/udp
2003-03-03T15:43:51 listening on IPv4:192.168.87.1 port 4444/udp
2003-03-03T15:43:51 listening on IPv4:203.12.237.110 port 4444/udp
2003-03-03T15:43:51 listening on IPv4:203.12.237.97 port 4444/udp
2003-03-03T15:43:51 listening on IPv4:127.0.0.1 port 4444/tcp
2003-03-03T15:43:51 bind IPv4:192.168.87.1/4444: Address already in use
2003-03-03T15:43:51 listening on IPv4:203.12.237.110 port 4444/tcp
2003-03-03T15:43:51 bind IPv4:203.12.237.97/4444: Address already in use
That is correct, but why does that not match this:
snoopy:unstable:~# netstat --tcp -a -p -n | grep kdc
tcp 0 0 226.106.44.64:4352 0.0.0.0:* LISTEN 12408/kdc
tcp 0 0 226.106.44.64:512 0.0.0.0:* LISTEN 12408/kdc
tcp 0 0 226.106.44.64:4192 0.0.0.0:* LISTEN 12408/kdc
tcp 0 0 226.106.44.64:4193 0.0.0.0:* LISTEN 12408/kdc
tcp 0 0 226.106.44.64:4194 0.0.0.0:* LISTEN 12408/kdc
tcp 0 0 203.12.237.110:750 0.0.0.0:* LISTEN 12408/kdc
tcp 0 0 203.12.237.110:4444 0.0.0.0:* LISTEN 12408/kdc
tcp 0 0 226.106.44.64:4191 0.0.0.0:* LISTEN 12408/kdc
strace has stuff like:
close(17) = 0
munmap(0x40014000, 4096) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 17
setsockopt(17, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(17, {sin_family=AF_INET, sin_port=htons(512), sin_addr=inet_addr("226.106.44.64")}}, 16) = -1 EADDRINUSE (Address already in use)
time(NULL) = 1046666733
open("/var/log/heimdal-kdc.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666) = 18
fstat64(18, {st_mode=S_IFREG|0644, st_size=8778, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40014000
fstat64(18, {st_mode=S_IFREG|0644, st_size=8778, ...}) = 0
_llseek(18, 8778, [8778], SEEK_SET) = 0
write(18, "2003-03-03T15:45:33 bind IPv4:20"..., 72) = 72
close(18) = 0
Has anyone else experienced similar problems?
Could the fact we are using libroken from kerberos4kth be a contributing
factor?
--
Brian May <bam@snoopy.apana.org.au>