Closed travisperson closed 2 years ago
I believe a similar issues
➜ filecoin-chain-archiver git:(master) ✗ kubectl logs butterfly-filecoin-chain-archiver-snapshots-1654620900-p25cp
{"level":"error","ts":"2022-06-07T16:55:47.850Z","logger":"filecoin-chain-archiver","caller":"filecoin-chain-archiver/main.go:44","msg":"exit","error":"cannot dial address ws://lotus-a-lotus-daemon:1234/rpc/v1 for dial tcp 172.20.42.198:1234: i/o timeout: dial tcp 172.20.42.198:1234: i/o timeout","errorVerbose":"cannot dial address ws://lotus-a-lotus-daemon:1234/rpc/v1 for dial tcp 172.20.42.198:1234: i/o timeout:\n github.com/filecoin-project/go-jsonrpc.websocketClient.func1\n /go/pkg/mod/github.com/filecoin-project/go-jsonrpc@v0.1.5/client.go:193\n - dial tcp 172.20.42.198:1234: i/o timeout"}
Similar issue but occured when dialing the second node
{"level":"error","ts":"2022-06-23T20:00:53.668Z","logger":"filecoin-chain-archiver","caller":"filecoin-chain-archiver/main.go:44","msg":"exit","error":"cannot dial address ws://lotus-b-lotus-daemon:1234/rpc/v1 for dial tcp 172.20.227.221:1234: i/o timeout: dial tcp 172.20.227.221:1234: i/o timeout","errorVerbose":"cannot dial address ws://lotus-b-lotus-daemon:1234/rpc/v1 for dial tcp 172.20.227.221:1234: i/o timeout:\n github.com/filecoin-project/go-jsonrpc.websocketClient.func1\n /go/pkg/mod/github.com/filecoin-project/go-jsonrpc@v0.1.5/client.go:193\n - dial tcp 172.20.227.221:1234: i/o timeout"}
Running two configured nodes. The first node ran into a connection timeout. When the job restarted, it failed immediately when trying to connect to the first node. This shouldn't of exited, instead it should of skipped over the first node and tried to the second.
Logging from first job failure