Check_reload_status CPU usage

TGruber · Apr 16, 2013, 2:07 AM

Hi Everybody,

I also have high CPU Load for the check_reload_status process in Version:
2.1-BETA1 (amd64)
built on Sun Apr 14 16:35:09 EDT 2013
FreeBSD 8.3-RELEASE-p7

The above case was highly probably a link flap… but my case is more strange. I also got the High CPU Load for check_reload_status (reloading over and over again). But in my case the Problem first appeared when I added the IPv6 Gateway of my provider. After this pfsense reloads every 10 seconds.

I also:

deleted the v6 Gateway.
and Killed the check_reload_status process (gets restarted by WebUI)
and Rebooted the box
-> All this did not terminate the high load...

I fell back to 2.0.3 for now, but I will be able to set up a test box to provide more info if desired.

Here is a little excerpt from system.log:


Apr 15 09:11:19 kerberos php: /system_gateways.php: ROUTING: setting default route to <<gw ip="" removed="">>
Apr 15 09:11:19 kerberos php: /system_gateways.php: ROUTING: setting IPv6 default route to fe80::1%re0
Apr 15 09:11:19 kerberos check_reload_status: Reloading filter
Apr 15 09:11:58 kerberos check_reload_status: Syncing firewall
Apr 15 09:12:00 kerberos php: /system_gateways.php: ROUTING: setting default route to <<gw ip="" removed="">>
Apr 15 09:12:00 kerberos php: /system_gateways.php: ROUTING: setting IPv6 default route to fe80::1%re0
Apr 15 09:12:00 kerberos check_reload_status: Reloading filter
Apr 15 09:13:16 kerberos check_reload_status: Syncing firewall
Apr 15 09:14:28 kerberos check_reload_status: Syncing firewall
Apr 15 09:14:38 kerberos check_reload_status: Syncing firewall
Apr 15 09:14:40 kerberos php: /system_gateways.php: ROUTING: setting default route to <<gw ip="" removed="">>
Apr 15 09:14:40 kerberos php: /system_gateways.php: ROUTING: setting IPv6 default route to fe80::1%re0
Apr 15 09:14:40 kerberos check_reload_status: Reloading filter
Apr 15 09:15:01 kerberos check_reload_status: updating dyndns MyISP,MyISPV6
Apr 15 09:15:01 kerberos check_reload_status: Restarting ipsec tunnels
Apr 15 09:15:01 kerberos check_reload_status: Restarting OpenVPN tunnels/interfaces
Apr 15 09:15:01 kerberos check_reload_status: Reloading filter
Apr 15 09:15:01 kerberos check_reload_status: Updating all dyndns
Apr 15 09:15:01 kerberos check_reload_status: Restarting OpenVPN tunnels/interfaces
Apr 15 09:15:11 kerberos check_reload_status: Updating all dyndns
Apr 15 09:15:11 kerberos check_reload_status: Restarting ipsec tunnels
Apr 15 09:15:11 kerberos check_reload_status: Restarting OpenVPN tunnels/interfaces
Apr 15 09:15:11 kerberos check_reload_status: Reloading filter</gw></gw></gw>

Cheers

Thomas

cmb · Apr 16, 2013, 5:57 AM

Different issue so I split it, please don't hijack threads.

What type of IPv6 were you adding a gateway for (static, PPPoE, DHCPv6, …)? The fe80::1%re0 is actually the default route your provider assigned you? The looks of that makes me wonder if you're adding your own IP as your default gateway.