RunOnFlux/flux

[BUG]

Closed this issue · 0 comments

Describe the bug
after upgrading to fluxos 4.4.0 the node cannot connect to fluxOS

To Reproduce
Steps to reproduce the behavior:
upgrade node from fluxos 4.3 to 4.4

Expected behavior
node works

Environment(please complete the following information):

  • OS: [Ubuntu 20.04 LTS

fluxbenchmark debug.log

2023-07-18 16:10:50 Flux Benchmark version v3.8.0-01695bc (2023-03-09 08:21:34 +0100)
2023-07-18 16:10:50 Using OpenSSL version OpenSSL 1.1.1a 20 Nov 2018
2023-07-18 16:10:50 HTTP: creating work queue of depth 16
2023-07-18 16:10:50 HTTP: starting 4 worker threads
2023-07-18 16:10:50 Bound to [::]:16225
2023-07-18 16:10:50 Bound to 0.0.0.0:16225
2023-07-18 16:10:50 init message: Done loading
2023-07-18 16:10:50 Starting Fluxnode Benchmarking Thread
2023-07-18 16:10:50 ---Starting new bench verification
2023-07-18 16:10:50 ---Node tier not set waiting 3m. Possible reboot give time for flux start.
2023-07-18 16:13:50 ---Failed: Could not connect to FluxOS to get Node Tier. Check your networking configuration or FluxOs error log.
2023-07-18 16:14:25 ---Restarting benchmarks
2023-07-18 16:14:25 ---Starting new bench verification
2023-07-18 16:14:25 ---Node tier not set waiting 3m. Possible reboot give time for flux start.

========================
flux debug.log
2023-07-18 16:11:26 socket recv error Connection reset by peer (104)
2023-07-18 16:11:27 ProcessMessages: advertizing address 80.178.83.102:16125
2023-07-18 16:11:27 receive version message: /MagicBean:6.2.0/: version 170018, blocks=1427820, us=85.130.201.244:51324, peer=14
2023-07-18 16:11:27 Added time data, samples 11, offset +0 (+0 minutes)
2023-07-18 16:11:27 nTimeOffset = +0 (+0 minutes)
2023-07-18 16:11:28 ProcessMessages: advertizing address 80.178.83.102:16125
2023-07-18 16:11:28 receive version message: /MagicBean:6.2.0/: version 170018, blocks=1427820, us=85.130.201.244:60078, peer=15
2023-07-18 16:11:28 Added time data, samples 12, offset +0 (+0 minutes)
2023-07-18 16:11:29 ProcessMessages: advertizing address 80.178.83.102:16125
2023-07-18 16:11:29 receive version message: /MagicBean:6.2.0/: version 170018, blocks=1427820, us=85.130.201.244:50696, peer=16
2023-07-18 16:11:29 Added time data, samples 13, offset +0 (+0 minutes)
2023-07-18 16:11:29 nTimeOffset = +0 (+0 minutes)
2023-07-18 16:11:35 ProcessMessages: advertizing address 80.178.83.102:16125
2023-07-18 16:11:35 receive version message: /MagicBean:6.2.0/: version 170018, blocks=1427820, us=85.130.201.244:56902, peer=17
2023-07-18 16:11:35 Added time data, samples 14, offset +0 (+0 minutes)
2023-07-18 16:11:41 ProcessMessages: advertizing address 80.178.83.102:16125
2023-07-18 16:11:41 receive version message: /MagicBean:6.2.0/: version 170018, blocks=1427820, us=85.130.201.244:37372, peer=18
2023-07-18 16:11:41 Added time data, samples 15, offset +0 (+0 minutes)
2023-07-18 16:11:41 nTimeOffset = +0 (+0 minutes)
2023-07-18 16:11:41 connect() to 185.187.169.253:16125 failed after select(): Connection refused (111)
2023-07-18 16:11:42 ProcessMessages: advertizing address 80.178.83.102:16125
2023-07-18 16:11:42 receive version message: /MagicBean:6.2.0/: version 170018, blocks=1427820, us=85.130.201.244:41540, peer=19
2023-07-18 16:11:42 Added time data, samples 16, offset +0 (+0 minutes)
2023-07-18 16:11:59 connect() to 154.12.242.89:16125 failed after select(): Connection refused (111)
2023-07-18 16:12:00 socket recv error Connection reset by peer (104)
2023-07-18 16:12:00 ProcessMessages: advertizing address 80.178.83.102:16125
2023-07-18 16:12:00 receive version message: /MagicBean:6.2.0/: version 170018, blocks=1427820, us=85.130.201.244:36870, peer=21
2023-07-18 16:12:00 Added time data, samples 17, offset +0 (+0 minutes)
2023-07-18 16:12:00 nTimeOffset = +0 (+0 minutes)