Never ending check_reload_status:

[priller]

After taking a couple of weeks off from pfs, I thought I would try the latest build  ( 2.1-RC1 built on Wed Aug 14 02:38:23 EDT 2013) and the first thing I see are never ending "check_reload_status:" messages.  What going on here? I don't see anything changing that would trigger this.

Aug 14 16:03:58 check_reload_status: Reloading filter
Aug 14 16:03:49 check_reload_status: Restarting ipsec tunnels
Aug 14 16:00:57 check_reload_status: Restarting ipsec tunnels
Aug 14 16:00:57 check_reload_status: Reloading filter
Aug 14 15:53:15 check_reload_status: Reloading filter
Aug 14 15:53:05 check_reload_status: Reloading filter
Aug 14 15:51:03 check_reload_status: Restarting ipsec tunnels
Aug 14 15:50:54 check_reload_status: Reloading filter
Aug 14 15:48:55 check_reload_status: Restarting ipsec tunnels
Aug 14 15:48:45 check_reload_status: Reloading filter
Aug 14 15:45:29 check_reload_status: Reloading filter
Aug 14 15:42:22 check_reload_status: Restarting ipsec tunnels
Aug 14 15:42:13 check_reload_status: Reloading filter
Aug 14 15:37:28 check_reload_status: Restarting ipsec tunnels
Aug 14 15:37:15 check_reload_status: Reloading filter
Aug 14 15:37:05 check_reload_status: Reloading filter
Aug 14 15:37:00 check_reload_status: Restarting ipsec tunnels
Aug 14 15:36:51 check_reload_status: Restarting OpenVPN tunnels/interfaces
Aug 14 15:36:49 check_reload_status: Restarting ipsec tunnels
Aug 14 15:36:41 check_reload_status: Reloading filter
Aug 14 15:35:24 check_reload_status: Reloading filter
Aug 14 15:35:24 check_reload_status: Restarting OpenVPN tunnels/interfaces
Aug 14 15:35:24 check_reload_status: Restarting ipsec tunnels
Aug 14 15:34:49 check_reload_status: Restarting ipsec tunnels
Aug 14 15:34:40 check_reload_status: Reloading filter
Aug 14 15:33:35 check_reload_status: Reloading filter
Aug 14 15:33:24 check_reload_status: Reloading filter
Aug 14 15:33:03 check_reload_status: Restarting ipsec tunnels
Aug 14 15:32:54 check_reload_status: Reloading filter
Aug 14 15:32:04 check_reload_status: Restarting ipsec tunnels
Aug 14 15:32:04 check_reload_status: Reloading filter
Aug 14 15:31:48 check_reload_status: Restarting ipsec tunnels
Aug 14 15:31:48 check_reload_status: Reloading filter
Aug 14 15:31:38 check_reload_status: Restarting ipsec tunnels
Aug 14 15:31:35 check_reload_status: Reloading filter
Aug 14 15:31:23 check_reload_status: Restarting ipsec tunnels
Aug 14 15:31:18 check_reload_status: Reloading filter
Aug 14 15:30:15 check_reload_status: Restarting ipsec tunnels
Aug 14 15:30:14 check_reload_status: Reloading filter
Aug 14 15:29:50 check_reload_status: Reloading filter

[mystique]

Did you ever get anywhere with this?

257 root        1 136  20  6908K  1384K RUN      57:20 93.07% check_reload_status

I just had to wipe my old config and rebuild..

So far, that seems to have taken care of it..

[miles267]

@mystique:

Did you ever get anywhere with this?

257 root        1 136  20  6908K  1384K RUN      57:20 93.07% check_reload_status

I just had to wipe my old config and rebuild..

So far, that seems to have taken care of it..

I too am facing a similar issues.  check_reload_status is pegging my CPU up around 99%.  At first I thought it might be squid, but I've since removed all packages and the problem persists.  I'd prefer not to do a complete rebuild if possible.

[mystique]

Again updating from 2.1-RC2 (fresh install) to 2.1-Release..

never ending check_reload_status..

I restored a config from 2.0.3 AND 2.1-RC2 both did the same thing..

I wiped the config and did an install again..

Are you you using 'Aliases'?  I was..

In this 2.1 I have not used aliases.. see where this goes..

[miles267]

Yesterday I decided to do a clean install of 2.1-RELEASE on the same machine and restore a current config with all same settings.  I then reinstalled all same packages with same settings and the issue appears to have gone away for the time being.  Yes, I am using Aliases on a limited basis.