Amahi Forums

Hello.

I'm having problems with my dhcp server. It is failing to start.

My symptoms seem exactly like Bug 412

In my log I see:

Feb 4 22:48:39 localhost dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Feb 4 22:48:39 localhost dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Feb 4 22:48:39 localhost dhcpd: All rights reserved.
Feb 4 22:48:39 localhost dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Feb 4 22:48:39 localhost dhcpd: /etc/dhcp/dhcpd.conf line 20: semicolon expected.
Feb 4 22:48:39 localhost dhcpd: #011max-lease-time
Feb 4 22:48:39 localhost dhcpd: ^
Feb 4 22:48:39 localhost dhcpd: /etc/dhcp/dhcpd.conf line 20: expecting a parameter or declaration
Feb 4 22:48:39 localhost dhcpd: #011max-lease-time ;
Feb 4 22:48:39 localhost dhcpd: ^
Feb 4 22:48:39 localhost dhcpd: Configuration file errors encountered -- exiting
Feb 4 22:48:39 localhost dhcpd:
Feb 4 22:48:39 localhost dhcpd: This version of ISC DHCP is based on the release available
Feb 4 22:48:39 localhost dhcpd: on ftp.isc.org. Features have been added and other changes
Feb 4 22:48:39 localhost dhcpd: have been made to the base software release in order to make
Feb 4 22:48:39 localhost dhcpd: it work better with this distribution.
Feb 4 22:48:39 localhost dhcpd:
Feb 4 22:48:39 localhost dhcpd: Please report for this software via the Red Hat Bugzilla site:
Feb 4 22:48:39 localhost dhcpd: http://bugzilla.redhat.com
Feb 4 22:48:39 localhost dhcpd:
Feb 4 22:48:39 localhost dhcpd: exiting.


and my dhcpd.conf reads:

ddns-update-style interim;
do-forward-updates on;
allow unknown-clients;
ddns-updates on;
ddns-domainname "emjake.local";
ddns-rev-domainname "in-addr.arpa";
ignore client-updates;
allow bootp;
allow booting;

subnet 192.168.1.0 netmask 255.255.255.0 {
authoritative;
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option domain-name "emjake.local";
option domain-name-servers 192.168.1.10, 192.168.1.10;
option time-offset -18000;
range 192.168.1.100 192.168.1.254;
default-lease-time ;
max-lease-time ;
filename "pxelinux.0";
next-server 192.168.1.10;
}

key "ddnskey" {
algorithm hmac-md5;
secret "8zaPJsiw9tOh2JFv4xiArw==";
};

zone emjake.local. {
primary 127.0.0.1;
key ddnskey;
}

zone 1.168.192.in-addr.arpa. {
primary 127.0.0.1;
key ddnskey;
}



I am a complete newb to linux. I've tried to do my own research.. but I'm just kind of lost. Have I provided enough information?

Any help would be appreciated.

Thanks

You seem to be missing parameters on the following two lines in your dhcpd.conf file:
Here are the same two lines from my file:
I suggest you edit your file and add those values. They should be the same for everybody.

You seem to be missing parameters on the following two lines in your dhcpd.conf file:

Code: Select all

default-lease-time ; max-lease-time ;

Here are the same two lines from my file:

Code: Select all

default-lease-time 14400; max-lease-time 14400;

Advanced settings allow you to change this value. Perhaps the OP set it to zero?

Advanced settings allow you to change this value. Perhaps the OP set it to zero?

Yes, thanks for that. I has forgotten about advanced settings! (it has been a while since I modified my configuration).

thank you all for the help.

yes, editing the config file fixed my issue.

I'm pretty sure I didn't set them to 0 with the advanced features.

However I am pretty sure I have a bug or some program is misbehaving.

After I fixed the issue, my server ran for 2 days with no issue. Then, sometime on Saturday, the two values in question got written to 0 again and my DHCP server shut down again. The machine was not rebooted, and nobody messed with it (I was actually at work at the time and the wife called me and said "I can't get on the internet".) So I have no idea what is going on. As of this post, it is still running fine.

Are there any steps I can take, or logs I could turn on to try to figure out what is editing this file? It has happened twice so far, so most likely it will happen again in the near future

The HDACTL service rebuilds the dhcp.conf file. Editing it only fixes things temporarily. You have to look at your MYSQL settings table as to what the values are so that when the conf file gets rebuilt, it does not get hosed.

Look at the advance setting options for dhcp. And/or install phpMyAdmin and use that to look at the setting table.

I'm having problems finding the offending settings in phpMyAdmin. I've located hda_production and found the settings. However I do not see any entry for the two entries that keep getting overwritten.

Could you dumb down your advice or point me in the right direction to learn what I need to.

Thanks again for your time.

I upgraded to Fedora 14 and Amahi 6 today. My problem still persists. Everytime I reboot, the DHCP server config file gets written with errors.

Any thoughts on the fix?

Thanks.

If possible, please come by the IRC for live troubleshooting help. Also, we may need to file a bug or tag on the existing one.

It easier to help resolve live than in the forums.

I got it fixed.

Thanks to bk and Solar__ in the chat room that helped me out.

Through doing a few query's that SolaR__ wrote for me and bk tested and verified, it seems that line 19 in my HDA db was missing. This line held the default lease time setting. A quick insert into the db, thanks again to SolaR__ for the code, and I was all set. We did not have to do anything to the max lease time. It just worked.

I rebooted several times and my dhcp server starts up every time as it should. Thanks guys.

now no more calls at work from the boss saying the internet is down and she can't get on her internet shopping sites....

wait a minute... damn it... maybe I should of left it broken...