Environment
Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
Situation
dhcpService object for a given cluster was "accidentally" deleted. To
recover, an ldif file was created to recreate the many missing object.
Upon starting up, the following was observed in the dhcpd.log file:
dhcpd: LDAP line 5440: semicolon expected.
dhcpd: option routers 10.20.104.1.
dhcpd: ^
dhcpd: LDAP line 5450: semicolon expected.
dhcpd: option routers 10.20.105.1.
dhcpd: ^
dhcpd: LDAP: cannot parse dhcpService entry 'cn=DHCP_server01,ou=SERVERS,ou=CHI,ou=IL,o=Novell'
dhcpd: Configuration file errors encountered -- exiting
dhcpd: LDAP line 5440: semicolon expected.
dhcpd: option routers 10.20.104.1.
dhcpd: ^
dhcpd: LDAP line 5450: semicolon expected.
dhcpd: option routers 10.20.105.1.
dhcpd: ^
dhcpd: LDAP: cannot parse dhcpService entry 'cn=DHCP_server01,ou=SERVERS,ou=CHI,ou=IL,o=Novell'
dhcpd: Configuration file errors encountered -- exiting
Resolution
Modify the subnet definition that had 5 octets in the "gateway" or router definition.
Cause
There were two subnets (CIDR/25) that contained an extra octet on the gateway/router definition in dhcp. While it was not 10.20.104.1 nor 10.20.105.1; it was on their counterparts 10.20.104.128 & 10.20.105.128. This caused the service not to load.
Additional Information
Since all of the subnets were created via LDIF file, all of the information was available so those subnets could be recreated. Removing those 2 subnets from the tree, and letting eDirectory sync, yielded the issue moved to different subnet definitions. So this can be a quick way to rule out the subnets listed in the error message. It was in reviewing the gateway/router option for all subnets, that the extra octet was found on 2 subnets. Once these were remediated, the service loaded as expected.