|
POLARIS
London Hub Naqs Log Summary for 2022-03-03
|
||||||
| # | Flag | Date | Time UT | Node | Process | Comments |
| 1 | W | 2022-03-03 | 00:00:00 | POL-1 | NaqsLog.........(1) | New log file: Naqs_20070303.log |
| 2 | I | 2022-03-03 | 00:00:00 | POL-1 | NaqsServer......(0) | NaqsServer version 1.90.00 |
| 3 | I | 2022-03-03 | 00:00:26 | POL-1 | DSSubscriber....(5) | starting with priority 4 |
| 4 | W | 2022-03-03 | 00:00:26 | POL-1 | DSSubscriber....(2) | Queue full, data being discarded |
| 5 | W | 2022-03-03 | 00:00:27 | POL-1 | DSSubscriber....(3) | Discarded 709 packets since Queue full |
| 6 | W | 2022-03-03 | 01:12:46 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 7 | W | 2022-03-03 | 01:17:17 | POL-1 | RingBuffer......(1) | PEMO.SHH: no data received for 600 seconds |
| 8 | I | 2022-03-03 | 01:17:21 | POL-1 | RingBuffer......(1) | PEMO.SHH is now receiving from TRI122 |
| 9 | I | 2022-03-03 | 01:17:21 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 10 | W | 2022-03-03 | 01:27:56 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 11 | I | 2022-03-03 | 01:29:21 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 12 | W | 2022-03-03 | 01:39:51 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 13 | W | 2022-03-03 | 01:45:21 | POL-1 | RingBuffer......(1) | PEMO.SHH: no data received for 600 seconds |
| 14 | I | 2022-03-03 | 01:45:21 | POL-1 | RingBuffer......(1) | PEMO.SHH is now receiving from TRI122 |
| 15 | I | 2022-03-03 | 01:45:21 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 16 | W | 2022-03-03 | 02:10:47 | POL-1 | RingBuffer......(1) | PEMO.SHH: no data received for 600 seconds |
| 17 | W | 2022-03-03 | 02:12:16 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 18 | I | 2022-03-03 | 02:14:21 | POL-1 | RingBuffer......(1) | PEMO.SHH is now receiving from TRI122 |
| 19 | I | 2022-03-03 | 02:16:21 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 20 | W | 2022-03-03 | 02:37:21 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 21 | I | 2022-03-03 | 02:50:21 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 22 | W | 2022-03-03 | 03:01:22 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 23 | I | 2022-03-03 | 03:16:21 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 24 | W | 2022-03-03 | 03:34:46 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| # | Flag | Date | Time UT | Node | Process | Comments |
| 25 | I | 2022-03-03 | 03:36:21 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 26 | W | 2022-03-03 | 03:57:11 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 27 | I | 2022-03-03 | 04:02:17 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 28 | W | 2022-03-03 | 04:12:17 | POL-1 | RingBuffer......(1) | PEMO.SHH: no data received for 600 seconds |
| 29 | W | 2022-03-03 | 04:13:11 | POL-1 | RingBuffer......(1) | PEMO.SOH: no data received for 600 seconds |
| 30 | I | 2022-03-03 | 04:13:21 | POL-1 | RingBuffer......(1) | PEMO.SHH is now receiving from TRI122 |
| 31 | I | 2022-03-03 | 04:23:17 | POL-1 | RingBuffer......(1) | PEMO.SOH is now receiving from CYG184 |
| 32 | I | 2022-03-03 | 07:56:41 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR030 |
| 33 | I | 2022-03-03 | 07:59:41 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR030 |
| 34 | W | 2022-03-03 | 08:02:07 | POL-1 | RingBuffer......(1) | COWN.SHH: no data received for 600 seconds |
| 35 | W | 2022-03-03 | 08:02:07 | POL-1 | RingBuffer......(1) | COWN.SOH: no data received for 600 seconds |
| 36 | W | 2022-03-03 | 08:02:57 | POL-1 | RingBuffer......(1) | COWN.BHE: no data received for 600 seconds |
| 37 | W | 2022-03-03 | 08:02:57 | POL-1 | RingBuffer......(1) | COWN.BHN: no data received for 600 seconds |
| 38 | W | 2022-03-03 | 08:02:57 | POL-1 | RingBuffer......(1) | COWN.BHZ: no data received for 600 seconds |
| 39 | I | 2022-03-03 | 08:14:41 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR030 |
| 40 | I | 2022-03-03 | 12:01:24 | POL-1 | DSSubscriber....(5) | starting with priority 4 |
| 41 | W | 2022-03-03 | 12:01:24 | POL-1 | DSSubscriber....(2) | Queue full, data being discarded |
| 42 | W | 2022-03-03 | 12:01:25 | POL-1 | DSSubscriber....(3) | Discarded 681 packets since Queue full |
| 43 | I | 2022-03-03 | 16:21:37 | POL-1 | RingBuffer......(1) | COWN.SHH is now receiving from TRI241 |
| 44 | I | 2022-03-03 | 16:21:37 | POL-1 | RingBuffer......(1) | COWN.SOH is now receiving from CYG250 |
| 45 | I | 2022-03-03 | 16:17:33 | TIM234 | TimingSubSystem.(5) | 'Raw Time' changed to 'No Lock': COWN |
| 46 | I | 2022-03-03 | 16:21:41 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR030 |
| 47 | I | 2022-03-03 | 16:17:34 | TIM234 | OncoreController(7) | New GPS hardware time fix.: COWN |
| 48 | I | 2022-03-03 | 16:18:00 | TIM234 | TimingSubSystem.(2) | Time has been aligned on a 100 us grid by 1688600 us: COWN |
| # | Flag | Date | Time UT | Node | Process | Comments |
| 49 | I | 2022-03-03 | 16:18:03 | TIM234 | TimingSubSystem.(5) | 'No Lock' changed to 'Coarse Lock': COWN |
| 50 | I | 2022-03-03 | 16:21:52 | POL-1 | RingBuffer......(1) | COWN.BHZ is now receiving from TRI241 |
| 51 | I | 2022-03-03 | 16:21:52 | POL-1 | RingBuffer......(1) | COWN.BHE is now receiving from TRI241 |
| 52 | I | 2022-03-03 | 16:21:52 | POL-1 | RingBuffer......(1) | COWN.BHN is now receiving from TRI241 |
| 53 | I | 2022-03-03 | 16:19:46 | TIM234 | TimingSubSystem.(5) | 'Coarse Lock' changed to 'Fine Lock': COWN |
| 54 | I | 2022-03-03 | 16:23:54 | TIM234 | TimingSubSystem.(5) | 'Fine Lock' changed to 'Coarse Lock': COWN |
| 55 | I | 2022-03-03 | 16:24:27 | TIM234 | TimingSubSystem.(5) | 'Coarse Lock' changed to 'Fine Lock': COWN |
| 56 | I | 2022-03-03 | 17:27:28 | POL-1 | DSSubscriber....(5) | starting with priority 4 |
| 57 | I | 2022-03-03 | 17:27:41 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR030 |
| 58 | I | 2022-03-03 | 17:28:01 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR030 |
| 59 | I | 2022-03-03 | 17:28:01 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR030 |
| 60 | I | 2022-03-03 | 17:28:01 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR031 |
| 61 | I | 2022-03-03 | 17:28:01 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR031 |
| 62 | I | 2022-03-03 | 17:28:11 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR030 |
| 63 | I | 2022-03-03 | 17:28:11 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR031 |
| 64 | I | 2022-03-03 | 17:28:11 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR031 |
| 65 | I | 2022-03-03 | 17:28:21 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR030 |
| 66 | I | 2022-03-03 | 17:28:22 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR031 |
| 67 | I | 2022-03-03 | 17:28:22 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR031 |
| 68 | I | 2022-03-03 | 17:28:32 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR031 |
| 69 | I | 2022-03-03 | 17:28:41 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR030 |
| 70 | I | 2022-03-03 | 17:28:41 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR030 |
| 71 | I | 2022-03-03 | 17:28:42 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR031 |
| 72 | I | 2022-03-03 | 17:29:01 | CAR030 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR030 |
| # | Flag | Date | Time UT | Node | Process | Comments |
| 73 | I | 2022-03-03 | 17:29:02 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR031 |
| 74 | I | 2022-03-03 | 17:29:02 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR031 |
| 75 | I | 2022-03-03 | 17:29:02 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR031 |
| 76 | I | 2022-03-03 | 17:30:12 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOk from CAR031 |
| 77 | W | 2022-03-03 | 19:15:55 | CAR030 | TenMhzRefChecker(1) | 10 MHz drifting quickly |
| 78 | I | 2022-03-03 | 23:58:02 | CAR031 | AlertSender.....(0) | enqueuing alert VSatRxOutage from CAR031 |
| 79 | I | 2022-03-04 | 00:00:00 | POL-1 | NaqsServer......(0) | NaqsServer version 1.90.00 |
| 80 | I | 2022-03-04 | 00:00:00 | POL-1 | NaqsServer......(0) | Uptime: 1 days 02:11:26 |
| 81 | I | 2022-03-04 | 00:00:00 | POL-1 | PacketReceiver..(0) | Packets recd since 2007/03/03_00:00:00: 3275565 |
| 82 | I | 2022-03-04 | 00:00:00 | POL-1 | PacketSender....(0) | Packets sent since 2007/03/03_00:00:00: 38711 |
| 83 | I | 2022-03-04 | 00:00:00 | POL-1 | EventStatus.....(0) | Events detected since 2007/03/03_00:00:00: 0 |
| 84 | I | 2022-03-04 | 00:00:00 | POL-1 | DSServer........(0) | New connections since 2007/03/03_00:00:00: 3 |
| 85 | I | 2022-03-04 | 00:00:00 | POL-1 | DSServer........(0) | Current number of connections: 6 |
| 86 | I | 2022-03-04 | 00:00:00 | POL-1 | SubscriberList..(0) | Subscriber 1: 130.179.65.45:1891 |
| 87 | I | 2022-03-04 | 00:00:00 | POL-1 | SubscriberList..(0) | Subscriber 2: 206.191.47.130:48683 |
| 88 | I | 2022-03-04 | 00:00:00 | POL-1 | SubscriberList..(0) | Subscriber 3: 134.117.204.97:1810 |