Re: ypbind init script fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Aaron Konstam wrote:
> On Mon, 2007-07-16 at 19:06 -0400, Andrew Robinson wrote:
>> I'm running FC6 on an eMachines laptop. I'm trying to configure NIS for 
>> my growing home network. I seem to be having peculiar problems with the 
>> ypbind init script. When I try to start the init script, it fails:
>>
>> [root@proteus ~]# /etc/rc.d/init.d/ypbind start
>> Starting NIS service:                                      [  OK  ]
>> Binding  NIS service: .........                            [FAILED]
>> Shutting down NIS service:                                 [  OK  ]
>>
>> However, I find that if I run the init script with the restart option, 
>> it will often, but not always, succeed:
>>
>> [root@proteus run]# /etc/rc.d/init.d/ypbind restart
>> Shutting down NIS service:                                 [FAILED]
>> Starting NIS service:                                      [  OK  ]
>> Binding  NIS service: ...                                  [  OK  ]
>>
>> If I start ypbind by itself from a command line, it always succeeds. I 
>> verify the successes and failures with ps, ypwhich and ypcat commands.
>>
>> Anyone have a clue as to what is going on here? I've been looking for 
>> some indication in some log, but haven't found any. The goal is to get 
>> the init script to succeed on boot up. (The init script gives the same 
>> messages at bootup as it does when run with "start" from the command
>> line.)
>>
>> Thanks!
>>
>> Andrew Robinson
> Looks to me that ypbind is not being shut down properly when things shut
> down. Look at the logs. Is there a complaint on starting ypbind thar a
> lock file has been lying around when it shouldn't.
> 
> I would start with executing chkconfig ypbind off
> Then execute: chkconfig --level 35 ypbind on
> 
From the response to a restart, it looks more like ypbind is
shutting down by itself. When you get the [FAILED] on shutdown, it
is usually because there is a PID file for the service, but the
program died. Because the PID files are cleaned up at boot, it is
not caused by the service not being shut down when the system shuts
down. When using "service restart <service>" or
"/etc/init.d/<service> restart", the links created by chkconfig ar
not used. The service file in /etc/init.d is run directly, and will
work even if the service in turned off by chkconfig.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux