Bridge dies when Parity is stopped #22
Comments
yrashk
added a commit
to yrashk/parity-bridge
that referenced
this issue
Feb 27, 2018
Steps to reproduce:
Run two Parity-based nodes responsible for Home and Foreign chains.
Run bridge: RUST_LOG=info bridge --config ... --database ....
Kill parity process responsible for Foreign chain.
Expected results:
The bridge handles gracefully death of Parity node: warns about the
connection lose, shutdowns all operations (deposit_relay,
withdraw_confirm and withdraw_relay) for a while, waits when the
connection appears and runs all operations after that.
Actual results:
After killing Parity process the following appear in the terminal where
the bridge is running:
WARN:<unknown>: Unexpected IO error: Error { repr: Os { code: 32,
message: "Broken pipe" } }
No messages appear from withdraw_confirm and withdraw_relay.
Then after some time (few seconds or few minutes) the following appear
on the terminal and the bridge dies:
Request eth_blockNumber timed out
Solution: once "Broken pipe" error is caught, attempt to
reconnect repeatedly with a pause of 1 second between attempts.
When other errors are caught, simply restart the bridge,
as there is no indication that the connection has been severed.
Fixes omni#22
|
Fixed by 9c375cc |
ghost
removed
the
This was referenced Mar 10, 2018
noot
pushed a commit
to noot/poa-bridge
that referenced
this issue
Jul 18, 2018
Steps to reproduce:
Run two Parity-based nodes responsible for Home and Foreign chains.
Run bridge: RUST_LOG=info bridge --config ... --database ....
Kill parity process responsible for Foreign chain.
Expected results:
The bridge handles gracefully death of Parity node: warns about the
connection lose, shutdowns all operations (deposit_relay,
withdraw_confirm and withdraw_relay) for a while, waits when the
connection appears and runs all operations after that.
Actual results:
After killing Parity process the following appear in the terminal where
the bridge is running:
WARN:<unknown>: Unexpected IO error: Error { repr: Os { code: 32,
message: "Broken pipe" } }
No messages appear from withdraw_confirm and withdraw_relay.
Then after some time (few seconds or few minutes) the following appear
on the terminal and the bridge dies:
Request eth_blockNumber timed out
Solution: once "Broken pipe" error is caught, attempt to
reconnect repeatedly with a pause of 1 second between attempts.
When other errors are caught, simply restart the bridge,
as there is no indication that the connection has been severed.
Fixes omni#22
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduced on the latest (3961987) POA master branch.
Steps to reproduce:
RUST_LOG=info bridge --config ... --database ....Expected results:
The bridge handles gracefully death of Parity node: warns about the connection lose, shutdowns all operations (
deposit_relay,withdraw_confirmandwithdraw_relay) for a while, waits when the connection appears and runs all operations after that.Actual results:
After killing Parity process the following appear in the terminal where the bridge is running:
No messages appear from
withdraw_confirmandwithdraw_relay.Then after some time (few seconds or few minutes) the following appear on the terminal and the bridge dies:
The text was updated successfully, but these errors were encountered: