Pablo Iranzo Gómez wrote: > > Ola Marcelo > > > On Tue, 9 Sep 2008, Marcelo Giles wrote: > >> Hello, >> >> I'm running into a problem with cobbler on RHEL 5.2. and need help. >> >> I had my cobbler settings working with 3 distros and 3 profiles. >> Everything worked fine, PXE boot of the machines, customized kickstart >> files, etc. >> >> After I updated cobbler (via Epel) to latest version >> (cobbler-1.0.3-1.el5), my clients no longer PXE boot. >> >> I mean, they boot into PXE, but tftp times out without reaching the >> default cobbler Menu where yo can select the profile. >> >> After several tries I gave up, uninstalled cobbler and erased all config >> files. I reinstalled and started from scratch but no luck. >> >> I read the mailing list archives and googled a bit but found nothing >> useful. Any hints? TIA. > > Can you check any issues with firewall? ethereal may help ;) > > Check specially network settings, I have that setup with RHEL 5.2 > working ok. > > Regards > Pablo > Hi Pablo,
I've found the culprit: libvirtd. You see, this cobbler host is also a xen host. The dhcp server for cobbler was setup using dhcpd, thus the "next-server" and "filename" options are configured in /etc/dhcpd.conf. Being a xen host, it is running libvirtd, therefore this host was running the dnsmasq dhcp server as well. I suspected this when I run netstat on it and found two lines with port udp 67 listed. Two dhcp servers! After I run service libvirtd stop, the client could connect and got to the menu with no problems. Weird thing is that this configuration was running as is with an older version of cobbler. Oh well, who knows... Now I have a new problem that I'll post in a new message, so we don't mix things up. Thank you. Marcelo _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
