13-01:01:17 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n') 13-02:57:51 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 13-02:57:52 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 13-07:22:24 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 13-07:22:25 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 13-07:22:29 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 13-07:22:30 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 13-07:22:35 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 13-07:22:36 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 13-11:20:57 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 13-11:20:58 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 14-01:00:31 piBeaconUtils doReboot L:353 Lv:50 master rebooting / shutdown sudo killall -9 python; sleep 2;sudo reboot regular_reboot_at_1_hours_requested 14-01:00:58 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n') 14-03:20:33 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 14-03:20:34 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 14-07:38:17 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 14-07:38:18 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 14-12:24:45 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 14-12:24:46 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 14-14:25:42 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 14-14:25:43 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 14-18:17:38 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n') 14-21:22:03 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 14-21:22:04 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-01:00:32 piBeaconUtils doReboot L:353 Lv:50 master rebooting / shutdown sudo killall -9 python; sleep 2;sudo reboot regular_reboot_at_1_hours_requested 15-01:00:58 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n') 15-05:48:00 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-05:48:01 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-05:48:05 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-05:48:06 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-09:35:33 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-09:35:34 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-09:52:48 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-09:52:49 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-11:50:18 beaconloop execbeaconloop L:892 Lv:50 in Line 884 has error=timed out.. sock.recv error, likely time out 15-11:50:19 piBeaconUtils restartMyself L:101 Lv:50 beaconloop --- restarting --- sock.recv error 15-11:50:33 beaconloop startBlueTooth L:209 Lv:50 in Line 206 has error=(100, 'Network is down') 15-11:51:27 piBeaconUtils doReboot L:353 Lv:50 master rebooting / shutdown sudo killall -9 python; sleep 2;sudo reboot bluetooth_startup.ERROR:Network_is_down...need_to_reboot 15-11:51:54 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n') 15-12:30:56 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-12:30:57 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-12:31:02 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-12:31:03 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-13:37:44 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-13:37:45 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-15:48:20 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n') 15-17:10:44 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-17:10:45 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-17:10:50 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-17:10:51 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-18:42:26 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-18:42:27 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-19:23:29 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-19:23:30 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-22:40:15 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-22:40:16 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-22:40:20 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-22:40:21 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-22:43:13 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-22:43:14 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 15-23:03:40 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 15-23:03:41 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-01:00:50 piBeaconUtils doReboot L:353 Lv:50 master rebooting / shutdown sudo killall -9 python; sleep 2;sudo reboot regular_reboot_at_1_hours_requested 16-01:01:17 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n') 16-02:02:24 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-02:02:25 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-04:28:49 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-04:28:50 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-04:28:54 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-04:28:55 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-04:35:17 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-04:35:18 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-09:04:12 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-09:04:13 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-09:32:22 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-09:32:23 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-09:34:34 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-09:34:35 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-09:35:33 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-09:35:34 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-09:38:20 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-09:38:21 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-11:29:40 BLEconnect tryToConnect L:139 Lv:50 in Line 112 has error ... sock.recv error, likely time out 16-11:29:41 piBeaconUtils restartMyself L:101 Lv:50 BLEconnect --- restarting --- sock.recv error 16-13:04:05 master execMaster L:1672 Lv:50 hw clock info: ('', 'hwclock: Cannot access the Hardware Clock via any known method.\nhwclock: Use the --debug option to see the details of our search for an access method.\n')