Re: dhpd.conf creation failure
On Tue, Sep 16, 2008 at 5:22 PM, Greg Chavez <greg.chavez(a)gmail.com> wrote:
I'm working on an inherited cobbler server managing dhcp and dns.
My
first attempt to add a server to cobbler for PXE boot and kickstart
failed, however, due to the following dhcp.conf generated after a
cobbler sync:
### /etc/dhcpd.conf
# ******************************************************************
# Cobbler managed dhcpd.conf file
# generated from cobbler dhcp.conf template (Tue Sep 16 20:45:14 2008)
# ******************************************************************
ddns-update-style none;
authoritative;
#ddns-update-style interim;
allow booting;
allow bootp;
option domain-name "xyz.testlab";
option domain-name-servers 192.168.13.211;
ignore client-updates;
set vendorclass = option vendor-class-identifier;
subnet 192.168.110.0 netmask 255.255.254.0 {
option routers 192.168.110.240;
option subnet-mask 255.255.254.0;
# range dynamic-bootp 192.168.1.100 192.168.1.254;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 192.168.110.118;
option domain-name "xyz.testlab";
option domain-name-servers 192.168.13.211;
}
$insert_cobbler_system_definitions
###EOF
For some reason, the insert_cobbler_system_definitions variable is
being left as is. This prevents dhcpd from starting and even if I
remove it from the template, I am left without what I assume should be
my host definitions. Here also is our settings file:
Answering my own, otherwise unanswered question, the problem was that
I had updated Cobbler from the version running when I took over from
the previous admin, from 1.0.2 to 1.2.4. The newer versions ships a
new dhcp template as /etc/cobbler/dhcp.template.rpmnew which contains
new conditional statements and variables that create the proper host
definitions. The $insert_cobbler_system_definitions variables now
seems defunct in this context. Hooray.
<snip>
--
--Greg Chavez
--