Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Chris Buechler wrote:
On Wed, Oct 14, 2009 at 2:28 PM, Roberto Greiner mrgrei...@gmail.com wrote:
At beginning of the file I have the following:
failover peer dhcp0 state {
my state normal at 3 2009/10/14 14:23:17;
partner state normal at 3 2009/10/14 14:13:17;
}
lease 172.16.89.254 {
starts 3 2009/10/14 17:04:35;
ends 3 2009/10/14 19:04:35;
tsfp 3 2009/10/14 20:04:35;
atsfp 3 2009/10/14 20:04:35;
cltt 3 2009/10/14 17:04:35;
binding state active;
next binding state expired;
hardware ethernet 00:0a:e4:5e:b5:a3;
}
That IP is for the notebook I'm using for setup.
After that, there are thousand of entries like the following:
lease 172.16.255.254 {
starts 3 2009/10/14 14:08:33;
binding state backup;
}
All those failover entries on that big of a scope exhaust PHP's memory
limit. No way around that for the time being, I opened a bug ticket
but you won't see that fixed in 1.2.x at least. Either use a smaller
scope, or use something else as your DHCP server. Or send patches to
fix the problem. :)
Ok,
as soon as possible I will try using a smaller scope.
Tks.
Roberto
--
-
Marcos Roberto Greiner
Os otimistas acham que estamos no melhor dos mundos
Os pessimistas tem medo de que isto seja verdade
James Branch Cabell
-
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
[pfSense Support] DHCP fatal error in services_dhcp.php line 48
Hi, I was configuring CARP, and as a final touch, I chose to enable, inside the DHCP server, the NTP servers option. When I activated it, pointing NTP to the LAN-CARP address (in this case 172.16.0.1. The physical LAN address is 172.16.0.2), I got a blank page with only the following line: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/local/www/services_dhcp.php on line 48 The DHCP server is no longer working. Did somebody else get something like that? Now, if I try to make any changes on the DHCP server, after clicking on save the pages dies on reload, it never refreshes. A reboot did not solve the problem. My server is a Xen virtual machine running with 512MB memory, 2 virtual processors, and a 10GB disk. The physical server is Core 2 Duo machine, with 4GB RAM. The pfsense version I'm running is 1.2.3-RC1, built Apr,22 15:36:34 2009. Thanks, Roberto -- - Marcos Roberto Greiner Os otimistas acham que estamos no melhor dos mundos Os pessimistas tem medo de que isto seja verdade James Branch Cabell - - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Roberto Greiner wrote: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/local/www/services_dhcp.php on line 48 That is during the DHCP lease cleanup routine. Your /var/dhcpd/var/db/dhcpd.leases file must be huge. It doesn't typically grow that large during normal operation. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Jim Pingle wrote: Roberto Greiner wrote: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/local/www/services_dhcp.php on line 48 That is during the DHCP lease cleanup routine. Your /var/dhcpd/var/db/dhcpd.leases file must be huge. It doesn't typically grow that large during normal operation. It's a new server. No user ever connected to it Roberto -- - Marcos Roberto Greiner Os otimistas acham que estamos no melhor dos mundos Os pessimistas tem medo de que isto seja verdade James Branch Cabell - - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Roberto Greiner wrote: Jim Pingle wrote: Roberto Greiner wrote: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/local/www/services_dhcp.php on line 48 That is during the DHCP lease cleanup routine. Your /var/dhcpd/var/db/dhcpd.leases file must be huge. It doesn't typically grow that large during normal operation. It's a new server. No user ever connected to it Can you check that file just to be sure? If nobody has connected to the server, you can probably safely remove the leases file anyhow. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Jim Pingle wrote: Roberto Greiner wrote: Jim Pingle wrote: Roberto Greiner wrote: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/local/www/services_dhcp.php on line 48 That is during the DHCP lease cleanup routine. Your /var/dhcpd/var/db/dhcpd.leases file must be huge. It doesn't typically grow that large during normal operation. It's a new server. No user ever connected to it Can you check that file just to be sure? If nobody has connected to the server, you can probably safely remove the leases file anyhow. $ ls -l /var/dhcpd/var/db total 17792 -rw-r--r-- 1 root _dhcp 4529052 Oct 14 09:42 dhcpd.leases -rw-r--r-- 1 dhcpd _dhcp 4528906 Oct 14 09:42 dhcpd.leases~ I removed both files and restarted the server (without the ntp configuration). The ntp server started properly. As a test, I tried to enable the ntp servers configuration again, and got the same error as before. Roberto -- - Marcos Roberto Greiner Os otimistas acham que estamos no melhor dos mundos Os pessimistas tem medo de que isto seja verdade James Branch Cabell - - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Roberto Greiner wrote: Jim Pingle wrote: Roberto Greiner wrote: Jim Pingle wrote: Roberto Greiner wrote: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/local/www/services_dhcp.php on line 48 That is during the DHCP lease cleanup routine. Your /var/dhcpd/var/db/dhcpd.leases file must be huge. It doesn't typically grow that large during normal operation. It's a new server. No user ever connected to it Can you check that file just to be sure? If nobody has connected to the server, you can probably safely remove the leases file anyhow. $ ls -l /var/dhcpd/var/db total 17792 -rw-r--r-- 1 root _dhcp 4529052 Oct 14 09:42 dhcpd.leases -rw-r--r-- 1 dhcpd _dhcp 4528906 Oct 14 09:42 dhcpd.leases~ I removed both files and restarted the server (without the ntp configuration). The ntp server started properly. As a test, I tried to enable the ntp servers configuration again, and got the same error as before. That is rather odd. Something weird must be going on with its network connection if it has a 4.5MB leases file. I can't reproduce this on my test box either. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Jim Pingle wrote: Roberto Greiner wrote: Jim Pingle wrote: Roberto Greiner wrote: Jim Pingle wrote: Roberto Greiner wrote: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /usr/local/www/services_dhcp.php on line 48 That is during the DHCP lease cleanup routine. Your /var/dhcpd/var/db/dhcpd.leases file must be huge. It doesn't typically grow that large during normal operation. It's a new server. No user ever connected to it Can you check that file just to be sure? If nobody has connected to the server, you can probably safely remove the leases file anyhow. $ ls -l /var/dhcpd/var/db total 17792 -rw-r--r-- 1 root _dhcp 4529052 Oct 14 09:42 dhcpd.leases -rw-r--r-- 1 dhcpd _dhcp 4528906 Oct 14 09:42 dhcpd.leases~ I removed both files and restarted the server (without the ntp configuration). The ntp server started properly. As a test, I tried to enable the ntp servers configuration again, and got the same error as before. That is rather odd. Something weird must be going on with its network connection if it has a 4.5MB leases file. I can't reproduce this on my test box either Could it be something mwith the fact that my box is a Xen virtual server? Roberto -- - Marcos Roberto Greiner Os otimistas acham que estamos no melhor dos mundos Os pessimistas tem medo de que isto seja verdade James Branch Cabell - - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] DHCP fatal error in services_dhcp.php line 48
Keenan Tims wrote:
Quoting Roberto Greiner mrgrei...@gmail.com:
Could it be something mwith the fact that my box is a Xen virtual
server?
Perhaps posting the generated leases file (or an excerpt of it) would
be helpful? I don't see how this would be directly related to your use
of Xen, though I suppose if your network configuration is badly broken
you might see this.
Keenan
At beginning of the file I have the following:
failover peer dhcp0 state {
my state normal at 3 2009/10/14 14:23:17;
partner state normal at 3 2009/10/14 14:13:17;
}
lease 172.16.89.254 {
starts 3 2009/10/14 17:04:35;
ends 3 2009/10/14 19:04:35;
tsfp 3 2009/10/14 20:04:35;
atsfp 3 2009/10/14 20:04:35;
cltt 3 2009/10/14 17:04:35;
binding state active;
next binding state expired;
hardware ethernet 00:0a:e4:5e:b5:a3;
}
That IP is for the notebook I'm using for setup.
After that, there are thousand of entries like the following:
lease 172.16.255.254 {
starts 3 2009/10/14 14:08:33;
binding state backup;
}
All with IPs ranging from 172.16.50.0 to 172.16.255.254 (The range I used when
setting DHCP).
At the very end of the file I got the following:
lease 172.16.89.254 {
starts 3 2009/10/14 17:56:52;
ends 3 2009/10/14 19:56:52;
tsfp 3 2009/10/14 20:56:52;
atsfp 3 2009/10/14 20:56:52;
cltt 3 2009/10/14 17:56:52;
binding state active;
next binding state expired;
hardware ethernet 00:0a:e4:5e:b5:a3;
}
It's the same IP as in the start of the file. Is that expected? An
effect of having two servers with DHCP due to CARP?
Roberto
--
-
Marcos Roberto Greiner
Os otimistas acham que estamos no melhor dos mundos
Os pessimistas tem medo de que isto seja verdade
James Branch Cabell
-
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
