Project

General

Profile

Actions

Bug #4622

closed

/var/dhcpd/var/db/dhcpd6.leases grows to enormous size, cpu usage high

Added by Ivars Strazdins about 10 years ago. Updated about 10 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv6)
Target version:
-
Start date:
04/15/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

This pfsense installation is configured with IPv6 tunnel (hurricane electric) and DHCP for ipv6.
The issue is that file /var/dhcpd/var/db/dhcpd6.leases grows to enormous size and as a result CPU usage is unusually high.
This started with v2.1 and continues after upgrade to v2.2.1
Please note this issue was not happening initially, but begin to happen later.
Attaching leases file and screenshot from RRD performance graph.
CPU is busy with command php processsing prefixes.


Files

dhcpd6.leases.gz (25.1 KB) dhcpd6.leases.gz Ivars Strazdins, 04/15/2015 05:08 AM
Screenshot 2015-04-15 13.03.08.png (49 KB) Screenshot 2015-04-15 13.03.08.png Ivars Strazdins, 04/15/2015 05:08 AM
Screenshot 2015-04-15 18.03.16.png (248 KB) Screenshot 2015-04-15 18.03.16.png screenshot of top command showing php process running Ivars Strazdins, 04/15/2015 10:01 AM
Actions #2

Updated by Ivars Strazdins about 10 years ago

Looks like it has got worse after upgrade to 2.2.2. leases file is now 43Mb.

Actions #3

Updated by Chris Buechler about 10 years ago

  • Category set to DHCP (IPv6)
  • Affected Version set to All

the upgrade didn't change anything in that regard, in that circumstance it just grows over time. What's the device that has 2001:470:dd85::9d51 assigned on your network?

Actions #4

Updated by Ivars Strazdins about 10 years ago

I've got your point.
Turns out it was a rogue HP printer. I disabled IPv6 for it and voĆ­la, /var/dhcpd/var/db/dhcpd6.leases is 19k in size.
Don't know if there is a problem with DHCPv6 server, but the printer was behaving strange anyway, I could hardly connect to it. Upgraded f/w, too, although that's irrelevant.
As far as I am concerned, the case is over. Thanks for hints!

Actions #5

Updated by Chris Buechler about 10 years ago

  • Status changed from New to Not a Bug

seriously broken DHCPv4 or v6 clients like this will cause issues along these lines

Actions

Also available in: Atom PDF