-
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
System doesn't connected itself even after Mainnet spork is completed #288
Comments
This is a critical issue team, we need a fix as we are facing the same challenge. |
@arpit-systango @rpatidar-isystango Did you find any useful information to resolve this issue? |
Nope, no response till... but we have found a manual way to resolve it... First, you need to stop the service then there is a block_height column in system_settings table where you can set the value to 0, and after that restart the service. It will reconnect the chain without a problem. |
@rpatidar-isystango 🙌 Thanks man it worked. On a side note, my jobs are taking a lot of time from changing the state from |
Try Webhook and async calls, they are better than polling. |
We are already using async. How much time does it takes normally to complete an async transaction on your end? |
It's based on the method. Account creation takes 10-15 sec along with the account setup and minting takes 30-40 sec.. but varies on Tesnet and Mainnet. I personally feel, the TestNet is faster than the MainNet |
After the 6th April 2022 Mainnet Spork completion. Even after restarting it was not able to connect to Chain and the service was continuously throwing
level=warning msg="Unable to connect to chain, pausing system" function=Listener.Start.goroutine package=chain_events
. From the local system, the chain was getting connected but not from my production server. Then I created a new DB and connect the service to the newly created DB and there it was connected. not sure what status was being managed in DB. Only one configuration I found in the system_settings table where it was managing paused_since value with some date and time. but even setting it to null it was automatically reset to a DateTime.I have requested the wallet-api to create/setup some accounts but at that time mainnet was down(Sporked) so API failed and after failing it was continuously retied creating accounts until we went out of Flows
The text was updated successfully, but these errors were encountered: