-
Notifications
You must be signed in to change notification settings - Fork 36
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
After Mainnet spork is complete, system doesn't connect to it automatically. #274
Comments
We didn't find this behavior on Testnet. It automatically connected to testnet nodes after testnet spork around 8th February 2022. |
Hi @Ronak-59! There have been some connectivity issues on mainnet. Have you been able to get over a testnet spork without issues? |
Hey @latenssi, apologies for the delay in response. Yes this wallet-api automatically connects to testnet nodes once the testnet spork is complete. But not for Mainnet spork. Considering that on restarting this service, it successfully connected to Mainnet nodes immediately, I don't think it was connectivity issues on Mainnet nodes. It seemed more like this wallet service was stuck in an endless loop to log the error every minute until it was restarted. |
I had the same problem after 6th April 2022 Mainnet Spork completion. Even after restarting it was not able to connect to Chain and the service was continuously throwing |
This happened a while back around 9th February 2022 Flow Mainnet Spork. It was fine until then but as soon as spork started, it started giving following error (which is okay and intentional I believe) :
level=warning msg="Unable to connect to chain, pausing system" function=Listener.Start.goroutine package=chain_events
But long after the spork was complete, the errors were still coming till 11th February 2022 when we checked and decided to restart the service on AWS ECS which started normally and was able to connect to Mainnet nodes. But every now and then, we are seeing the above error in logs randomly at a frequency of like around 5 times a day.
Do we need to restart the service after each Mainnet spork?
The text was updated successfully, but these errors were encountered: