Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken error handling for karura #64

Open
brson opened this issue Nov 1, 2022 · 1 comment
Open

Broken error handling for karura #64

brson opened this issue Nov 1, 2022 · 1 comment

Comments

@brson
Copy link
Collaborator

brson commented Nov 1, 2022

In the logs I see:

log/realtps-import.5.log:2022-10-31T11:49:48.719739180+00:00 INFO realtps_import::import - importing at least 3 blocks for chain karura
log/realtps-import.5.log:2022-10-31T11:49:48.719747368+00:00 DEBUG realtps_import::helpers - fetching block 2965699 for chain karura
log/realtps-import.5.log:2022-10-31T11:49:49.063628198+00:00 WARN realtps_import::delay - for chain karura received err connection error: Connection reset by peer (os error 104). retrying in 500 ms
log/realtps-import.5.log:2022-10-31T11:49:50.208977603+00:00 WARN realtps_import::delay - for chain karura received err error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1913: (self signed certificate). retrying in 1000 ms

And then "karura" is never mentioned again. I expect to see a third error printed by the top-level job runner, and then the job to be retried.

I see this error handling working for other chains, so I can't understand what is happening offhand.

@brson
Copy link
Collaborator Author

brson commented Nov 1, 2022

I wonder if this task panicked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant