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

bug: node exits abnormally #12358

Closed
4 tasks
Tracked by #13327
dreamer-zq opened this issue Jun 27, 2022 · 5 comments
Closed
4 tasks
Tracked by #13327

bug: node exits abnormally #12358

dreamer-zq opened this issue Jun 27, 2022 · 5 comments
Assignees
Labels
C:Rosetta Issues and PR related to Rosetta

Comments

@dreamer-zq
Copy link
Collaborator

dreamer-zq commented Jun 27, 2022

Summary of Bug

tendermint version

v0.35.4

cosmos-sdk

v0.46.0-rc1

environment

macos

Steps to Reproduce

  1. Initialize two nodes (the code I used when testing is demo), modify the port number of the response,
  2. Both nodes open the rosetta service (enable = true)
  3. Start two nodes, about less than a minute, one of the nodes will be down, error message: Error: maximum number of retries exceeded, last error: rpc error: code = Unavailable desc = connection closed before server preface received
  4. Shut down the rosetta service (enable = fasle), start two nodes, and the nodes are running normally

image


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@dreamer-zq dreamer-zq changed the title bug: Node exits abnormally bug: node exits abnormally Jun 27, 2022
@alexanderbez
Copy link
Contributor

Seems like a Rosetta issue, which unfortunately, no one is maintaining at the moment. Maybe it has something to do with your config? What do you mean by "modify the port number of the response"?

@tac0turtle tac0turtle added the C:Rosetta Issues and PR related to Rosetta label Jun 27, 2022
@dreamer-zq
Copy link
Collaborator Author

Seems like a Rosetta issue, which unfortunately, no one is maintaining at the moment. Maybe it has something to do with your config? What do you mean by "modify the port number of the response"?

Sorry, the word is wrong, it is to modify the port to prevent the port conflict of the two nodes

@alexanderbez
Copy link
Contributor

The rosetta port?

@dreamer-zq
Copy link
Collaborator Author

dreamer-zq commented Jun 29, 2022

The rosetta port?

What I mean is that if you start two nodes on the same machine, and both open the rosetta service, one of the nodes will probably exit automatically. The specific reproduction steps can use this script, close lines 84 and 97 in the script, 83 and line 96 opens. Then execute the script in the project root path:

./network/init.sh 
./network/start.sh

@alexanderbez
Copy link
Contributor

I see. Yeah, I have zero familiarity with Rosetta and no one is really maintaining it atm, so it's hard for me to say what could be the issue. I did take a look at where the error stems from and it seems it cannot establish a connection, so it might be an environment thing. Someone with Rosetta exp should chime in here.

cc @fdymylja

mergify bot pushed a commit that referenced this issue Nov 4, 2022
### Description

Closes:
#13083
#11402
#10678
#12358
#10776
#12934

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [x] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [x] added `!` to the type prefix if API or client breaking change
- [x] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting))
- [x] provided a link to the relevant issue or specification
- [x] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules)
- [x] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing)
- [x] added a changelog entry to `CHANGELOG.md`
- [x] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [x] updated the relevant documentation or specification
- [x] reviewed "Files changed" and left comments if necessary
- [ ] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:Rosetta Issues and PR related to Rosetta
Projects
None yet
Development

No branches or pull requests

5 participants