-
Notifications
You must be signed in to change notification settings - Fork 28
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
Auto upgrade failed, interx doesn't start and host got jailed #69
Comments
I've reinstalled and issue persists, thanks in advance |
10.1.0.2 registry.local Adding those entries to the interx container, fixes the issue |
It only had:
|
I've just updated to latest version and same problem.... adding the ips' back moved state from 'configuring' to 'healthy' |
After full node (OS included) reinstallation issue still persists, node has both ipv4 and ipv6 connectivity and works fine once the hosts entries are added |
Node was running testnet-8, did vote and expected to get it upgraded.
The upgrade apparently failed reporting issues in "interx" container, several partial reinstall, full reinstall even VPS reinstall resulted in errors and double signing (dunno how) and node not starting.
I was able to manually start it when inspecting interx container and adding entries for the validator host in /etc/hosts, from that point, interx was able to start, but a container restart wiped it and reproduced the issue.
After clean reinstall the behavior was the same.
Any hint?
kira.zip
The text was updated successfully, but these errors were encountered: