DHCP don't acknowledges more than 80 users? (Mail with smaller dhcpd.leases)

Martin Hochreiter linuxbox at wavenet.at
Thu Dec 4 07:51:05 UTC 2008


> --On Wednesday, December 03, 2008 08:30:29 AM +0100 Martin Hochreiter 
> <linuxbox at wavenet.at> wrote:
>
>> Hi!
>>
>> I am still playing around with the problem that an  3.0.5 Dhcpd (that is
>> now failover),
>> isn't working correctly if I make it to a primary.
>>
>> I checked the logfiles of the last tests and disovered that it does not
>> work any more
>> after serving exactly 80 machines.
>> After that no new DHCPACK is recorded and the machines are not 
>> getting an
>> address
>>
>> can somebody tell me why please
>
> Well, let's see...
>
>
> - no logs
> - no configuration
> - no lease database
> ...
Hi Jeffrey!

Sorry - I didn't include more information, because the same 
configuration was working before
switching to Cent OS 5.2 so I do not expect that it is wrong - I thought 
somebody can give me
a hint like "check the ulimits for this or for that ..." - Sorry my 
fault here are the informations:

*System: *
Cent OS 5.2, ISC Dhcpd 3.0.5 with paranoia and ldap patch. Started with:
 /usr/sbin/dhcpd -f /etc/dhcpd.conf -chroot /var/lib/dhcp/ -lf 
/db/dhcpd.leases -user dhcpd -group nobody bond0

*Configuration:*
[root at xdaten ~]# cat /etc/dhcpd.conf
ddns-update-style none;
authoritative;
ignore declines;
ldap-server "xdaten";
ldap-dhcp-server-cn "xdaten";
ldap-port 389;
ldap-username "uid=Admin,ou=Users,dc=base,dc=at";
ldap-password "XXXXXXX";
ldap-base-dn "ou=DHCP,dc=base,dc=at";
ldap-method dynamic;
ldap-debug-file "/var/log/dhcp-ldap.log";
failover peer "dhcp-failover" {
 # secondary;
  primary;
  address 10.0.0.2;
  port 648;
  peer address 10.0.0.1;
  peer port 647;
  max-response-delay 30;
  max-unacked-updates 10;
  load balance max seconds 3;
  mclt 1800;
  split 128;
}



Logs (from the last test):
The Dhcpd serves all clients until the count of the leases reaches 80
(counted with: grep "hardware" dhcpd.leases | cut -d" " -f5 | sort -u| 
wc -l)
(Dec  3 08:04:48) then you get only DHCPACK for Dhcp Refreshes or
when you leases

Dec  3 08:04:23 xdaten dhcpd: DHCPDISCOVER from 00:1e:0b:23:ea:c1 via 
10.222.0.253
Dec  3 08:04:23 xdaten dhcpd: DHCPOFFER on 10.222.0.119 to 
00:1e:0b:23:ea:c1 via 10.222.0.253
Dec  3 08:04:24 xdaten dhcpd: DHCPREQUEST for 10.222.0.48 (10.0.0.2) 
from 00:17:a4:40:3b:a9 via 10.222.0.253
Dec  3 08:04:24 xdaten dhcpd: DHCPACK on 10.222.0.48 to 
00:17:a4:40:3b:a9 via 10.222.0.253
Dec  3 08:04:26 xdaten dhcpd: DHCPREQUEST for 10.222.0.48 (10.0.0.2) 
from 00:17:a4:40:3b:a9 via 10.222.0.254
Dec  3 08:04:26 xdaten dhcpd: DHCPACK on 10.222.0.48 to 
00:17:a4:40:3b:a9 via 10.222.0.254
Dec  3 08:04:28 xdaten dhcpd: DHCPDISCOVER from 00:0a:5e:43:b5:28 via 
10.1.0.254
Dec  3 08:04:28 xdaten dhcpd: DHCPOFFER on 10.1.12.108 to 
00:0a:5e:43:b5:28 via 10.1.0.254
Dec  3 08:04:29 xdaten dhcpd: DHCPDISCOVER from 00:0a:5e:43:b5:28 via 
10.1.0.253
Dec  3 08:04:29 xdaten dhcpd: DHCPOFFER on 10.1.12.108 to 
00:0a:5e:43:b5:28 via 10.1.0.253
Dec  3 08:04:31 xdaten dhcpd: BOOTREQUEST from 00:0d:93:64:34:50 via 
10.7.0.253
Dec  3 08:04:31 xdaten dhcpd: BOOTREPLY for 10.7.1.102 to mma102 
(00:0d:93:64:34:50) via 10.7.0.253
Dec  3 08:04:33 xdaten dhcpd: BOOTREQUEST from 00:0d:93:64:34:50 via 
10.7.0.254
Dec  3 08:04:33 xdaten dhcpd: BOOTREPLY for 10.7.1.102 to mma102 
(00:0d:93:64:34:50) via 10.7.0.254
Dec  3 08:04:34 xdaten dhcpd: DHCPREQUEST for 10.1.12.110 from 
00:0a:5e:43:af:22 via bond0
Dec  3 08:04:34 xdaten dhcpd: DHCPACK on 10.1.12.110 to 
00:0a:5e:43:af:22 via bond0
Dec  3 08:04:36 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:38:36 via 
10.7.0.254
Dec  3 08:04:36 xdaten dhcpd: DHCPOFFER on 10.7.1.104 to 
00:0d:93:64:38:36 via 10.7.0.254
Dec  3 08:04:37 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:34:50 via 
10.7.0.254
Dec  3 08:04:37 xdaten dhcpd: DHCPOFFER on 10.7.1.102 to 
00:0d:93:64:34:50 via 10.7.0.254
Dec  3 08:04:39 xdaten dhcpd: BOOTREQUEST from 00:17:a4:40:3b:a9 via 
10.222.0.254
Dec  3 08:04:39 xdaten dhcpd: BOOTREPLY for 10.222.0.48 to kpoelz1 
(00:17:a4:40:3b:a9) via 10.222.0.254
Dec  3 08:04:40 xdaten dhcpd: BOOTREQUEST from 00:17:a4:40:3b:a9 via 
10.222.0.253
Dec  3 08:04:40 xdaten dhcpd: BOOTREPLY for 10.222.0.48 to kpoelz1 
(00:17:a4:40:3b:a9) via 10.222.0.253
Dec  3 08:04:42 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:7a:53:98 via 
10.7.0.254
Dec  3 08:04:42 xdaten dhcpd: DHCPOFFER on 10.7.1.103 to 
00:0d:93:7a:53:98 via 10.7.0.254
Dec  3 08:04:43 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:34:50 via 
10.7.0.254
Dec  3 08:04:43 xdaten dhcpd: DHCPOFFER on 10.7.1.102 to 
00:0d:93:64:34:50 via 10.7.0.254
Dec  3 08:04:45 xdaten dhcpd: DHCPREQUEST for 10.7.1.103 (10.0.0.2) from 
00:0d:93:7a:53:98 via 10.7.0.254
Dec  3 08:04:45 xdaten dhcpd: DHCPACK on 10.7.1.103 to 00:0d:93:7a:53:98 
via 10.7.0.254
Dec  3 08:04:46 xdaten dhcpd: DHCPREQUEST for 10.7.1.103 (10.0.0.2) from 
00:0d:93:7a:53:98 via 10.7.0.254
Dec  3 08:04:46 xdaten dhcpd: DHCPACK on 10.7.1.103 to 00:0d:93:7a:53:98 
via 10.7.0.254
Dec  3 08:04:48 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:38:36 via 
10.7.0.254
Dec  3 08:04:48 xdaten dhcpd: DHCPOFFER on 10.7.1.104 to 
00:0d:93:64:38:36 via 10.7.0.254
Dec  3 08:04:52 xdaten dhcpd: BOOTREQUEST from 00:0d:93:7a:53:98 via 
10.7.0.253
Dec  3 08:04:52 xdaten dhcpd: BOOTREPLY for 10.7.1.103 to mma103 
(00:0d:93:7a:53:98) via 10.7.0.253
Dec  3 08:04:53 xdaten dhcpd: DHCPDISCOVER from 00:0a:5e:43:b5:28 via 
10.1.0.254
Dec  3 08:04:53 xdaten dhcpd: DHCPOFFER on 10.1.12.108 to 
00:0a:5e:43:b5:28 via 10.1.0.254
Dec  3 08:04:55 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:7a:53:98 via 
10.7.0.254
Dec  3 08:04:55 xdaten dhcpd: DHCPOFFER on 10.7.1.103 to 
00:0d:93:7a:53:98 via 10.7.0.254
Dec  3 08:04:57 xdaten dhcpd: DHCPDISCOVER from 00:1e:0b:23:ea:c1 via 
10.222.0.253
Dec  3 08:04:57 xdaten dhcpd: DHCPOFFER on 10.222.0.119 to 
00:1e:0b:23:ea:c1 via 10.222.0.253
Dec  3 08:04:58 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:34:50 via 
10.7.0.254
Dec  3 08:04:58 xdaten dhcpd: DHCPOFFER on 10.7.1.102 to 
00:0d:93:64:34:50 via 10.7.0.254
Dec  3 08:05:00 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:7a:53:98 via 
10.7.0.254
Dec  3 08:05:00 xdaten dhcpd: DHCPOFFER on 10.7.1.103 to 
00:0d:93:7a:53:98 via 10.7.0.254
Dec  3 08:05:01 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:34:50 via 
10.7.0.254
Dec  3 08:05:01 xdaten dhcpd: DHCPOFFER on 10.7.1.102 to 
00:0d:93:64:34:50 via 10.7.0.254
Dec  3 08:05:03 xdaten dhcpd: DHCPDISCOVER from 00:13:20:b7:76:b3 via 
10.222.0.253
Dec  3 08:05:03 xdaten dhcpd: DHCPOFFER on 10.222.0.75 to 
00:13:20:b7:76:b3 via 10.222.0.253
Dec  3 08:05:04 xdaten dhcpd: DHCPDISCOVER from 00:13:20:b7:76:b3 via 
10.222.0.254
Dec  3 08:05:04 xdaten dhcpd: DHCPOFFER on 10.222.0.75 to 
00:13:20:b7:76:b3 via 10.222.0.254
Dec  3 08:05:06 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:7a:53:98 via 
10.7.0.254
Dec  3 08:05:06 xdaten dhcpd: DHCPOFFER on 10.7.1.103 to 
00:0d:93:7a:53:98 via 10.7.0.254
Dec  3 08:05:07 xdaten dhcpd: DHCPDISCOVER from 00:0a:5e:43:b5:28 via 
10.1.0.253
Dec  3 08:05:07 xdaten dhcpd: DHCPOFFER on 10.1.12.108 to 
00:0a:5e:43:b5:28 via 10.1.0.253
Dec  3 08:05:09 xdaten dhcpd: DHCPDISCOVER from 00:0a:5e:43:b5:28 via 
10.1.0.254
Dec  3 08:05:09 xdaten dhcpd: DHCPOFFER on 10.1.12.108 to 
00:0a:5e:43:b5:28 via 10.1.0.254
Dec  3 08:05:11 xdaten dhcpd: DHCPDISCOVER from 08:bb:cc:04:a3:9d 
(XT-MICRO-04A39D) via 10.1.0.253: peer holds all free leases
Dec  3 08:05:12 xdaten dhcpd: DHCPDISCOVER from 08:bb:cc:04:a3:9d 
(XT-MICRO-04A39D) via 10.1.0.254: peer holds all free leases
Dec  3 08:05:14 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:34:50 via 
10.7.0.254
Dec  3 08:05:14 xdaten dhcpd: DHCPOFFER on 10.7.1.102 to 
00:0d:93:64:34:50 via 10.7.0.254
Dec  3 08:05:15 xdaten dhcpd: DHCPDISCOVER from 00:0a:5e:43:b5:28 via 
10.1.0.253
Dec  3 08:05:15 xdaten dhcpd: DHCPOFFER on 10.1.12.108 to 
00:0a:5e:43:b5:28 via 10.1.0.253
Dec  3 08:05:17 xdaten dhcpd: DHCPDISCOVER from 00:1e:0b:23:ea:c1 via 
10.222.0.253
Dec  3 08:05:17 xdaten dhcpd: DHCPOFFER on 10.222.0.119 to 
00:1e:0b:23:ea:c1 via 10.222.0.253
Dec  3 08:05:18 xdaten dhcpd: DHCPDISCOVER from 00:11:2f:f0:f0:da via 
10.1.0.253
Dec  3 08:05:18 xdaten dhcpd: DHCPOFFER on 10.1.20.100 to 
00:11:2f:f0:f0:da via 10.1.0.253
Dec  3 08:05:20 xdaten dhcpd: DHCPDISCOVER from 00:11:2f:f0:f0:da via 
10.1.0.254
Dec  3 08:05:20 xdaten dhcpd: DHCPOFFER on 10.1.20.100 to 
00:11:2f:f0:f0:da via 10.1.0.254
Dec  3 08:05:21 xdaten dhcpd: DHCPDISCOVER from 00:0d:93:64:34:50 via 
10.7.0.254
Dec  3 08:05:21 xdaten dhcpd: DHCPOFFER on 10.7.1.102 to 
00:0d:93:64:34:50 via 10.7.0.254
Dec  3 08:05:23 xdaten dhcpd: DHCPDISCOVER from 00:0a:5e:43:b5:28 via 
10.1.0.253
Dec  3 08:05:23 xdaten dhcpd: DHCPOFFER on 10.1.12.108 to 
00:0a:5e:43:b5:28 via 10.1.0.253
Dec  3 08:05:24 xdaten dhcpd: DHCPDISCOVER from 00:1e:0b:23:ea:c1 via 
10.222.0.254
Dec  3 08:05:24 xdaten dhcpd: DHCPOFFER on 10.222.0.119 to 
00:1e:0b:23:ea:c1 via 10.222.0.254
Dec  3 08:05:26 xdaten dhcpd: DHCPREQUEST for 10.6.0.131 from 
00:0e:0c:a4:0b:50 via bond0
Dec  3 08:05:26 xdaten dhcpd: DHCPACK on 10.6.0.131 to 00:0e:0c:a4:0b:50 
via bond0
Dec  3 08:05:28 xdaten dhcpd: DHCPDISCOVER from 00:11:2f:f0:f0:da via 
10.1.0.253

Lease database - I am including the last file itself as attachment

Maybe  you can help me now.

lg
Martin


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20081204/7e9a9b82/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dhcpd.leases.bz2
Type: application/x-bzip
Size: 26008 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20081204/7e9a9b82/attachment-0001.bin>


More information about the dhcp-users mailing list