[24600] in Kerberos

home help back first fref pref prev next nref lref last post

Re: KDC fails to start

daemon@ATHENA.MIT.EDU (Ken Raeburn)
Tue Sep 6 17:07:54 2005

In-Reply-To: <dfjjc5$g3$1@news.urz.uni-heidelberg.de>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9ACDE4FC-3F93-4146-B183-1D33F1BD95BE@mit.edu>
Content-Transfer-Encoding: 7bit
From: Ken Raeburn <raeburn@mit.edu>
Date: Tue, 6 Sep 2005 17:06:57 -0400
To: securenix <sequru@yahoo.com>
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu

On Sep 6, 2005, at 4:18, securenix wrote:
> krb5kdc: No such device - Cannot bind server socket to port 750  
> address
> fe80::20b:....
> krb5kdc: No such device - Cannot bind server socket to port 750  
> address
> fe80::20b:....

Odd... those should be eliminated based on the flags in /proc/net/ 
if_inet6, or perhaps some flags in getifaddrs if your system has it.   
I haven't run into it on our 2.6.9 kernels under RHEL 4.

Also any non-local IPv4 addresses should've been used as well.

Were you disconnected from the network at the time you did this?  If  
you have no addresses assigned (excluding loopback and link-local  
addresses), the KDC won't find any addresses to bind to, and won't  
start.

Ken
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post