SUMMARY: System startup hung on 'named' startup; won't continue bootup
Tim Evans <[email protected]>
| Newsgroups | gmane.linux.redhat.release.taroon.general |
|---|---|
| Message-ID | <[email protected]> |
Earlier I wrote: >I have an RHEL 3 Academic Server that is hung during boot-up at 'named' >startup. It's complaining about missing/malformed named.conf file. > >Boot will not proceed further, so other services aren't starting either. Can't >log in remotely because sshd hasn't started; can't get to NFS exports since >nfsd hasn't started. >I'm dealing with this remotely, and don't have console access. Is there a >keystroke combination I can dictate to someone onsite to break out of the >'named' startup and continue the bootup? Or is single-user boot the only >option here? Thanks to Anthony J Placilla <[email protected]> for suggesting booting in interactive mode. I was able to hand-hold an onsite user through this. We skipped over the BIND startup and got the system running. Explanation for the problem was that up2date installed the latest chrooted BIND, and the startup script was unable to find the data directory. (This system hadn't been updated in a good while.) Once I copied the named data files over into the chroot /etc directory, BIND started up with no trouble. -- Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court [email protected] | Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | -- Taroon-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/taroon-list