search for: fisds0

...ils to start. A check of the log files shows it has been working right up until the system was rebooted Sunday night. The reboot itself was not the problem as there had been previous reboots after which krb5kdc was able to restart. Here are the log entries for that latest retry: Jun 10 16:29:38 fisds0.forsoft.com krb5kdc[12490](info): setting up network... Jun 10 16:29:38 fisds0.forsoft.com krb5kdc[12490](info): setting up network... Jun 10 16:29:38 fisds0.forsoft.com krb5kdc[12490](info): skipping unrecognized local address family 17 Jun 10 16:29:38 fisds0.forsoft.com krb5kdc[12490]...

...ues there were a large number (300+). I know my bad! After installing the updates I rebooted the system and it took forever to boot and once up there were problems connecting to some of our SAMBA shares. I checked the messages log file and found a multitude of entries similar to: Feb 17 19:46:18 fisds0 named[23187]: nss_ldap: failed to bind to LDAP server 127.0.0.1: Can't contact LDAP server Feb 17 19:46:18 fisds0 named[23187]: nss_ldap: reconnecting to LDAP server... These were being reported for named, nscd, smbd, statd, rquotad, etc. I did some google searching and found some refer...

...e bulk of our Windows workstations and DHCP is configured to update the DNS server and this appears to work fine (once I disabled all the "Register this connection's address in DNS" options on the workstations). I have found one suspicious entry in /var/log/messages: Apr 12 17:34:14 fisds0 named[5210]: client 192.168.2.7#10242: updating zone 'forsoft.com/IN': deleting an RR This would seem to indicate that the printer itself has issued the request to the DNS server but for the life of me I cannot see what might be doing it. Has anyone encountered something s...