Check_reload_status: Something wrong happened while sending request

[phil.davis]

This has happened a couple of times on different snapshots, but I had been updating snapshots so frequently that it hadn't been an issue that I had got around to reporting until now.

2.2-ALPHA (i386)
built on Mon Apr 21 13:01:11 CDT 2014
FreeBSD 10.0-STABLE
on Alix 2D13, nanoBSD, 2G image

I think it happens after the system has been running for "some time" (= at least a day?). I noticed again this morning because one of my WANs was down, but the policy-routing rules had not failed over. Looking in /tmp/rules.debug gateway groups that should have failed away from the down WAN were still being outed to the down WAN.

System log is spammed with loads of:

Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable
Apr 25 06:58:02 	check_reload_status: Something wrong happened while sending request: Resource temporarily unavailable

I tried restarting apinger, editing firewall rules to force a rule rebuild, no success. I guess I could have found a way to restart check_reload_status (would be nice if this process was listed in Status->Services, or would that cause more trouble with people felling the urge to restart it?) - in the end I rebooted to get internet back.

[darkytoo]

i've had the same issue here, 100% CPU:

262 root    122  20 16588K  2092K RUN    405:42 100.00% /usr/local/sbin/check_reload_status
  11 root    155 ki31    0K    16K RUN    741:56  0.00% [idle]