--- Original Message --- From: David Walser <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [Cooker] ypbind fails on boot
>Has anyone looked into this? I did a bit...looking at >messages after booting, I see: > >Sep 17 08:45:15 mccarthy ypbind: ypbind startup >succeeded >Sep 17 08:45:15 mccarthy ypbind[977]: Unable to >register (YPBINDPROG, YPBINDVERS >, udp). > >then later: > >Sep 17 08:45:07 mccarthy network: Setting network >parameters: succeeded >Sep 17 08:45:07 mccarthy network: Bringing up loopback >interface: succeeded >Sep 17 08:45:07 mccarthy ifup: Determining IP >information for eth0... > >and: > >Sep 17 08:45:13 mccarthy dhcpcd[890]: dhcpConfig: >ioctl SIOCADDRT: File exists >Sep 17 08:45:13 mccarthy ifup: done. >Sep 17 08:45:14 mccarthy network: Bringing up >interface eth0: succeeded > >I think you get the idea. rc5.d shows an S10network, >and an S17ypbind, but from the log, it looks like >ypbind is getting started before network. Possible >initscripts problem? > >Looking into it further, it *appears* that running >concurrently with rc.sysinit are some of the startup >scripts in rc5.d, like usb, gpm, and ypbind, but >network is going later than all of these. > >--- David Walser <[EMAIL PROTECTED]> wrote: >> Fresh installation. >> You get green OKs during the boot, but then it's not >> working, and service ypbind status shows: >> ypbind dead but pid file exists >> but if you just do service ypbind start >> it works from then on out. >> >> The only thing I can think is maybe it's trying to >> start too early in the boot, before something it >> needs. >> I answered your message asking a question: Do you have portmap service enabled? # chkconfig --list portmap should show it on. If you look at the time tags, you will see that the network is started at 08:45:14, and ypbind one second later. The fact that they show up in a different order in the syslog is a minor issue (buffering I would guess), but is not the cause of your problem. ypbind works fine here. One more thing I remember, check that NISDOMAIN is set in /etc/sysconfig/network. It is surely set since you can start the service later on. Good luck, =o= kk1 =-= kk1
