On Thu, Apr 16, 2009 at 3:22 PM, Michael DeHaan mdehaan@redhat.com wrote:
Rodrique Heron wrote:
On Thu, Apr 16, 2009 at 3:04 PM, Rodrique Heron <swygue@rodhouse.org mailto:swygue@rodhouse.org> wrote:
On Thu, Apr 16, 2009 at 2:55 PM, Rodrique Heron <swygue@rodhouse.org <mailto:swygue@rodhouse.org>> wrote: My installation of cobbler 1.6.2-1 fails to start when you issue "service cobblerd start" command, when you check the status "service cobblerd status", I get this output: cobblerd dead but snippets. Any ideas? the logs for cobbler does has no errors. Sorry, the error message I included was wrong, its : [root@w-inf-cob-01 snippets]# service cobblerd status cobblerd dead but subsys locked I am on centos 5.2 Thanks
I removed the lock and tried starting cobbler again, but got the same error. So it appears cobbler stating then immediately crashing. There's nothing in the logs.
[root@w-inf-cob-01 subsys]# rm /var/lock/subsys/cobblerd rm: remove regular empty file `/var/lock/subsys/cobblerd'? y [root@w-inf-cob-01 subsys]# service cobblerd status cobblerd is stopped [root@w-inf-cob-01 subsys]# service cobblerd start Starting cobbler daemon: [ OK ] [root@w-inf-cob-01 subsys]# service cobblerd status cobblerd dead but subsys locked
This came up on IRC yesterday. In this case, starting cobblerd with "--no-daemonize" showed that the address was already in use.
In which case you are probably using cobbler with manage_dhcp on, and dhcpd has restarted (from cobbler) and claimed cobbler's port (and lsof claims that dhcpd also owns cobblerd.log, which is nonsensical)
As a fit for this, cobbler 1.6.3 has replaced all "os.system" calls with usage of the subprocess module with close_fds=True, which, should, in theory, keep things a bit better behaved.
I'm not positive that resolves the problem, but we're testing that now. Previously cobblerd daemonized itself with os.system.
Thanks for the explanation, I am using cobbler with manage_dhcp on. This isn't the first I time I ran experienced this issue, the last time, I backed up my cobbler install and reinstalled. That's what I am doing now, especially since I just noticed 1.6.2 is available in EPEL and I was using your SRPM.