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.

Sign up for GitHub

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

Jump to bottom

Delayed node stuck when lost connection to trusted node #2034

Closed
17 tasks
abitmore opened this issue Oct 26, 2019 · 1 comment · Fixed by #2038
Closed
17 tasks

Delayed node stuck when lost connection to trusted node #2034

abitmore opened this issue Oct 26, 2019 · 1 comment · Fixed by #2038
Assignees
@pmconrad
Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design 6 Plugin Impact flag identifying at least one plugin
Milestone
5.0.0 - Protocol ...

Comments

@abitmore
Copy link
Member

Bug Description
Got this message when the trusted node was shut down:

2513518ms th_a delayed_node_plugin.cpp:162 connection_failed ] Connection to trusted node failed; retrying in 5 seconds...

then the delayed node got stuck there.

Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.

  • API (the application programming interface)
  • Build (the build process or something prior to compiled code)
  • CLI (the command line wallet)
  • Deployment (the deployment process after building such as Docker, Travis, etc.)
  • DEX (the Decentralized EXchange, market engine, etc.)
  • P2P (the peer-to-peer network for transaction/block propagation)
  • Performance (system or user efficiency, etc.)
  • Protocol (the blockchain logic, consensus, validation, etc.)
  • Security (the security of system or user data, etc.)
  • UX (the User Experience)
  • Other (please add below)

Host Environment
Please provide details about the host environment. Much of this information can be found running: witness_node --version.

  • Host OS: [e.g. Ubuntu 18.04 LTS]
  • Host Physical RAM [e.g. 4GB]
  • BitShares Version: [e.g. 2.0.180425]
  • OpenSSL Version: [e.g. 1.1.0g]
  • Boost Version: [e.g. 1.65.1]

Additional Context (optional)
Add any other context about the problem here.

CORE TEAM TASK LIST

  • Evaluate / Prioritize Bug Report
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
@pmconrad pmconrad added 3d Bug Classification indicating the existing implementation does not match the intention of the design 6 Plugin Impact flag identifying at least one plugin labels Nov 1, 2019
@pmconrad pmconrad added this to the 4.1.0 - Feature Release milestone Nov 1, 2019
@pmconrad pmconrad self-assigned this Nov 1, 2019
@pmconrad pmconrad mentioned this issue Nov 1, 2019
Merged
@abitmore abitmore linked a pull request Feb 8, 2020 that will close this issue
Fix reconnect of delayed node #2038
Merged
@abitmore
Copy link
Member Author

abitmore commented Feb 8, 2020

Closed by #2038.

@abitmore abitmore closed this as completed Feb 8, 2020
@abitmore abitmore mentioned this issue Sep 20, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pmconrad pmconrad

Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design 6 Plugin Impact flag identifying at least one plugin
Projects
None yet
Milestone
5.0.0 - Protocol Upgrade Release
Development

Successfully merging a pull request may close this issue.

Fix reconnect of delayed node bitshares/bitshares-core
2 participants
@pmconrad @abitmore