Stephan Huiser wrote:
Michael DeHaan wrote:
Stephan Huiser wrote:
fresh install of cobbler 1.6.3 on Fedora 10
'cobbler sync' fails on '/usr/sbin/dhcpd -t'
Error in /var/log/messages
Apr 17 23:01:52 hell dhcpd: Internet Systems Consortium DHCP Server 4.0.0 Apr 17 23:01:52 hell dhcpd: Copyright 2004-2007 Internet Systems Consortium. Apr 17 23:01:52 hell dhcpd: All rights reserved. Apr 17 23:01:52 hell dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Apr 17 23:01:52 hell dhcpd: /etc/dhcpd.conf line 32: expecting a parameter or declaration Apr 17 23:01:52 hell dhcpd: fixed-address 10.76.0.2; Apr 17 23:01:52 hell dhcpd: ^ Apr 17 23:01:52 hell dhcpd: Configuration file errors encountered -- exiting Apr 17 23:01:52 hell dhcpd: Apr 17 23:01:52 hell dhcpd: This version of ISC DHCP is based on the release available Apr 17 23:01:52 hell dhcpd: on ftp.isc.org. Features have been added and other changes Apr 17 23:01:52 hell dhcpd: have been made to the base software release in order to make Apr 17 23:01:52 hell dhcpd: it work better with this distribution. Apr 17 23:01:52 hell dhcpd: Apr 17 23:01:52 hell dhcpd: Please report for this software via the Red Hat Bugzilla site: Apr 17 23:01:52 hell dhcpd: http://bugzilla.redhat.com Apr 17 23:01:52 hell dhcpd: Apr 17 23:01:52 hell dhcpd: exiting.
I think this piece of dhcp.template causes the error:
#if $iface.hostname: hostname $iface.hostname; #end if
After removing these lines and running 'cobbler sync', DHCPD runs fine ...
- Stephan
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Can you share the output of "cobbler system report --name=foo" for the system in question and also the "/etc/dhcpd.conf" that cobbler creates?
It seems that the error you posted is about a IP address, which is not a hostname, and that confuses me a bit...
--Michael
system : xen profile : redhat-5.2-x86_64 comment : created : Sun Dec 21 14:26:48 2008 gateway : 10.76.0.1 hostname : xen.dmz.huiser.nl image : kernel options : {} kernel options post : {} kickstart : <<inherit>> ks metadata : {} mgmt classes : [] modified : Sat Feb 14 09:32:56 2009 name servers : [] name servers search : [] netboot enabled? : True owners : [u'admin'] redhat mgmt key : e97cc16ce9f08cc1 redhat mgmt server : <<inherit>> server : <<inherit>> template files : {} virt cpus : 1 virt file size : 0 virt path : <<inherit>> virt ram : <<inherit>> virt type : <<inherit>> power type : apc_snmp power address : power user : power password : power id : interface : dmz mac address : 00:1C:C0:35:3C:78 bonding : bonding_master : bonding_opts : is static? : True ip address : 10.76.0.2 subnet : 255.255.255.0 static routes : [] dns name : dhcp tag : virt bridge :
------8<-------------
# ****************************************************************** # Cobbler managed dhcpd.conf file # generated from cobbler dhcp.conf template (Fri Apr 17 22:15:55 2009) # Do NOT make changes to /etc/dhcpd.conf. Instead, make your changes # in /etc/cobbler/dhcp.template, as /etc/dhcpd.conf will be # overwritten. # ******************************************************************
ddns-update-style interim;
allow booting; allow bootp;
ignore client-updates; set vendorclass = option vendor-class-identifier;
subnet 192.168.1.0 netmask 255.255.255.0 { option routers 192.168.1.5; option domain-name-servers 192.168.1.1; option subnet-mask 255.255.255.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 10.76.1.2; }
# group for Cobbler DHCP tag: default group { host generic1 { hardware ethernet 00:1C:C0:35:3C:78; fixed-address 10.76.0.2; hostname xen.dmz.huiser.nl; option subnet-mask 255.255.255.0; option routers 10.76.0.1; filename "/pxelinux.0"; next-server 10.76.1.2; } }
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Using the above template and trying to replicate this scenario I'm *not* getting this restart error.
Except I'm using F-10.
Anyone have an idea as to /why/ this is invalid syntax? It looks valid to me.
Perhaps it's a variance in different versions of dhcpd, or I'm just missing something obvious?
--Michael