2026-10-03 06:17:42,224 - distributed.scheduler - ERROR - broadcast to tcp://100.96.4.84:34743 failed: OSError: Timed out trying to connect to tcp://100.96.4.84:34743 after 30 s
2026-10-03 06:16:08,277 - distributed.scheduler - ERROR - broadcast to tcp://100.96.4.84:34743 failed: OSError: Timed out trying to connect to tcp://100.96.4.84:34743 after 30 s
2026-10-03 06:11:39,086 - distributed.scheduler - ERROR - broadcast to tcp://100.96.4.84:34743 failed: OSError: Timed out trying to connect to tcp://100.96.4.84:34743 after 30 s
2026-10-03 01:33:47,189 - distributed.scheduler - ERROR - broadcast to tcp://100.96.3.80:36325 failed: OSError: Timed out trying to connect to tcp://100.96.3.80:36325 after 30 s
2026-10-03 01:25:08,076 - distributed.scheduler - ERROR - broadcast to tcp://100.96.3.80:36325 failed: OSError: Timed out trying to connect to tcp://100.96.3.80:36325 after 30 s
2026-10-03 01:22:18,063 - distributed.scheduler - ERROR - broadcast to tcp://100.96.3.80:36325 failed: OSError: Timed out trying to connect to tcp://100.96.3.80:36325 after 30 s
2026-10-02 23:53:34,336 - distributed.scheduler - ERROR - broadcast to tcp://100.96.2.211:37257 failed: OSError: Timed out trying to connect to tcp://100.96.2.211:37257 after 30 s
2026-10-02 23:53:20,105 - distributed.scheduler - ERROR - broadcast to tcp://100.96.2.211:37257 failed: OSError: Timed out trying to connect to tcp://100.96.2.211:37257 after 30 s
2026-10-02 23:50:30,530 - distributed.scheduler - ERROR - broadcast to tcp://100.96.2.211:37257 failed: OSError: Timed out trying to connect to tcp://100.96.2.211:37257 after 30 s
2026-10-02 21:52:00,568 - distributed.scheduler - ERROR - broadcast to tcp://100.96.9.48:38145 failed: OSError: Timed out trying to connect to tcp://100.96.9.48:38145 after 30 s
2026-10-02 21:50:26,428 - distributed.scheduler - ERROR - broadcast to tcp://100.96.9.48:38145 failed: OSError: Timed out trying to connect to tcp://100.96.9.48:38145 after 30 s
2026-10-02 21:46:48,560 - distributed.scheduler - ERROR - broadcast to tcp://100.96.9.48:38145 failed: OSError: Timed out trying to connect to tcp://100.96.9.48:38145 after 30 s
2026-10-01 12:46:47,913 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.22.34:35589
2026-10-01 12:46:47,913 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.22.34:35589 name: tcp://100.96.22.34:35589
2026-10-01 12:41:23,799 - distributed.scheduler - INFO - Remove worker addr: tcp://100.96.20.5:38017 name: tcp://100.96.20.5:38017 (stimulus_id='handle-worker-cleanup-1790858483.79963')
2026-09-04 01:29:30,376 - distributed.scheduler - ERROR - broadcast to tcp:/100.96.11.9:33393 failed: ValueError: invalid address 'tcp:/100.96.11.9:33393'; maybe: ipv6 needs brackets like [::1]
2026-09-02 05:30:16,577 - distributed.scheduler - ERROR - broadcast to tcp:/100.96.14.7:45641 failed: ValueError: invalid address 'tcp:/100.96.14.7:45641'; maybe: ipv6 needs brackets like [::1]
2026-09-02 03:58:48,023 - distributed.scheduler - ERROR - broadcast to tcp:/100.96.12.29:34993 failed: ValueError: invalid address 'tcp:/100.96.12.29:34993'; maybe: ipv6 needs brackets like [::1]
2026-09-02 00:34:23,428 - distributed.scheduler - ERROR - broadcast to tcp:/100.96.20.5:38017 failed: ValueError: invalid address 'tcp:/100.96.20.5:38017'; maybe: ipv6 needs brackets like [::1]
2026-07-14 12:42:24,313 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.12.29:34993
2026-07-14 12:42:24,313 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.12.29:34993 name: tcp://100.96.12.29:34993
2026-07-14 12:39:53,539 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.20.5:38017
2026-07-14 12:39:53,539 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.20.5:38017 name: tcp://100.96.20.5:38017
2026-07-14 12:39:15,292 - distributed.scheduler - INFO - Remove worker addr: tcp://100.96.2.211:42117 name: tcp://100.96.2.211:42117 (stimulus_id='handle-worker-cleanup-1784032755.2921748')
2026-07-14 12:38:56,298 - distributed.scheduler - INFO - Remove worker addr: tcp://100.96.3.80:41489 name: tcp://100.96.3.80:41489 (stimulus_id='handle-worker-cleanup-1784032736.2983816')
2026-07-14 12:26:36,799 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.14.7:45641
2026-07-14 12:26:36,799 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.14.7:45641 name: tcp://100.96.14.7:45641
2026-07-14 12:24:37,603 - distributed.scheduler - INFO - Remove worker addr: tcp://100.96.1.220:39929 name: tcp://100.96.1.220:39929 (stimulus_id='handle-worker-cleanup-1784031877.6033745')
2026-07-14 12:08:06,294 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.11.9:33393
2026-07-14 12:08:06,294 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.11.9:33393 name: tcp://100.96.11.9:33393
2026-07-14 12:07:48,326 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.2.211:42117
2026-07-14 12:07:48,325 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.2.211:42117 name: tcp://100.96.2.211:42117
2026-07-14 12:07:34,044 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.3.80:41489
2026-07-14 12:07:34,043 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.3.80:41489 name: tcp://100.96.3.80:41489
2026-07-14 12:06:56,769 - distributed.scheduler - INFO - Starting worker compute stream, tcp://100.96.1.220:39929
2026-07-14 12:06:56,763 - distributed.scheduler - INFO - Register worker addr: tcp://100.96.1.220:39929 name: tcp://100.96.1.220:39929
2026-07-14 12:06:49,899 - distributed.scheduler - INFO - Registering Worker plugin shuffle
2026-07-14 12:06:49,899 - distributed.scheduler - INFO - dashboard at: http://100.96.11.5:8787/status
2026-07-14 12:06:49,899 - distributed.scheduler - INFO - Scheduler at: tcp://100.96.11.5:8786
2026-07-14 12:06:49,898 - distributed.scheduler - INFO - -----------------------------------------------
2026-07-14 12:06:49,895 - distributed.scheduler - INFO - State start