-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Comments
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 |
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 |
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 |
### 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)
Summary of Bug
tendermint version
v0.35.4
cosmos-sdk
v0.46.0-rc1
environment
macos
Steps to Reproduce
Error: maximum number of retries exceeded, last error: rpc error: code = Unavailable desc = connection closed before server preface received
For Admin Use
The text was updated successfully, but these errors were encountered: