Periodically I'll have a system where everything is working fine and then one day the hub will stop being able to execute the _probeCheckin call. It tries a number of times and then terminates.
Sep 8 15:59:22:206 [16836] hub: Automatic restart will occur at 15:59 Wed 09 Sep 2015
Sep 8 15:59:22:206 [16836] hub: --------------------------------------------------------------------------------------------------------
Sep 8 15:59:22:206 [16836] hub: ----- Hub 7.72 [Build 7.72.3529, Jun 3 2015] initializing -----
Sep 8 15:59:22:206 [16836] hub: Tunnel has started in thread [ 0612 ]
Sep 8 15:59:22:252 [16836] hub: nimSessionNew - _probeCheckin failed - communication error
Sep 8 15:59:22:534 [16836] hub: ----- HUB started -----
Sep 8 15:59:22:534 [16836] hub: Name = ABC001007 IP = 192.168.10.17 port = 48002
Sep 8 15:59:22:534 [16836] hub: Domain = MergeHC-dom addr = /MergeHC-dom/ABC001007/******.ABC001007/hub
Sep 8 15:59:22:534 [16836] hub: log_level= 0 , log_file=hub.log
Sep 8 15:59:22:534 [16836] hub: license on * robots=13000 expire=Sat Oct 31 00:00:00 2015
Sep 8 15:59:22:534 [16836] hub: -----
Sep 8 15:59:22:534 [16768] hub: hubi main thread started
Sep 8 15:59:22:534 [16836] hub: nimSessionNew - _probeCheckin failed - communication error
Sep 8 15:59:22:534 [16836] hub: nimRegisterProbe failed
Sep 8 15:59:40:268 [17232] hub: nimSessionNew - _probeCheckin failed - communication error
Sep 8 15:59:40:268 [17232] hub: nimSessionNew - _probeCheckin failed - communication error
Sep 8 15:59:40:268 [17232] hub: nimSessionNew - _probeCheckin failed - communication error
Sep 8 15:59:40:268 [17232] hub: nimSessionNew - _probeCheckin failed - communication error
Sep 8 15:59:40:268 [17232] hub: hub ip changed 127.0.0.1 => 192.168.10.17
Sep 8 15:59:40:284 [17232] hub: Automatic restart will occur at 15:59 Wed 09 Sep 2015
Sep 8 15:59:40:284 [17232] hub: --------------------------------------------------------------------------------------------------------
Sep 8 15:59:40:284 [17232] hub: ----- Hub 7.72 [Build 7.72.3529, Jun 3 2015] initializing -----
Almost always it is necessary to restart the OS to make it start working again. CA support doesn't know why this is happening and is in the "need more logs when it happens again" mode with the issue.
I'm hoping that someone here might have a better bead on what is going in.
-Garin