On 09/18/2009 10:36 AM, Chris O'Regan wrote: > Cobbler version 1.6.5 > > I was building a system with Cobbler yesterday when kickstart failed. > While investigating, I noticed that the Cobbler daemon was down and > would not re-start. Since this had happened once before, I was able to > narrow it down quickly. The configuration file of the system being built > was zero bytes. I deleted it and was able to restart Cobbler. >
As I recall from before you are using a non-RPM installed version of Cobbler so that you could put /var/lib/cobbler on some other partion? What are the details regarding that again? The most likely cause is that cobblerd somehow crashed while updating the state file. There are various checks in place to make sure invalid contents don't cause problems, so I'm not sure what might be causing this. Is /var/lib/cobbler on NFS or something, or could the system have run out of memory? And yes, reporting items with the latest dot release is pretty much requirement a reproducibility as problems of various sorts may have already been resolved -- 2.0 is still in testing for the next week or so. > I stepped through my kickstart and compared it with the newly built > system. The fault occurred near the very end of the %post section where > I call $kickstart_done which translates into: > > wget "http://XXX.encs.concordia.ca/cblr/svc/op/nopxe/system/YYY"; -O /dev/null > wget "http://XXX.encs.concordia.ca/cblr/svc/op/ks/system/YYY"; -O > /root/cobbler.ks > wget "http://XXX.encs.concordia.ca/cblr/svc/op/trig/mode/post/system/YYY"; -O > /dev/null > > I don't know which of these failed, but I suspect it's the "nopxe" > trigger since it would be writing to this system's configuration file. > > I've been using this setup quite a bit and I have run into this problem > only once before. It's not a problem with disk space -- there's about > 100G free. I wasn't accessing cobbler at the time either. There isn't > much in the cobbler logs, either, just a message in install.log stating > the start time for this system. Nothing in either cobbler.log or > cobblerd.log. > > I'm planning to upgrade to the latest 1.6.X release soon; not sure if I > am ready to switch to just 2.0.X yet. > > > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
