You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In Skale Admin, there are two processes for each chain - one monitor is responsible for the status of contracts (creating chains, rotating ERC), and the second monitor checks the status of each Skaled container. Sometimes, the chain monitoring process hangs, ceases to initiate checks, and, in case of issues within the Skaled container, fails to perform the specified actions for recovery or restarting of such a Skaled.
Preconditions:
16 nodes
8 active chains
2 GETH nodes for 8 nodes each
Disabled auto_repair option in container config stream
Versions:
skalenetwork/admin:2.5.4-develop.1
To Reproduce
Clear steps for reproduction are missing.
To investigate, it is necessary for a failure to occur and to increase the log size for Skale-admin on QANet
Expected behavior
Skale admin should run 2 monitors after Geth nodes are synced
Actual state:
In some cases, skale admin initiates only contract monitoring, but does not restart the schain monitoring if it hangs.
Temporary workaround:
Restart the Skale admin container manually
The text was updated successfully, but these errors were encountered:
Describe the bug
In Skale Admin, there are two processes for each chain - one monitor is responsible for the status of contracts (creating chains, rotating ERC), and the second monitor checks the status of each Skaled container. Sometimes, the chain monitoring process hangs, ceases to initiate checks, and, in case of issues within the Skaled container, fails to perform the specified actions for recovery or restarting of such a Skaled.
Preconditions:
16 nodes
8 active chains
2 GETH nodes for 8 nodes each
Disabled auto_repair option in container config stream
Versions:
skalenetwork/admin:2.5.4-develop.1
To Reproduce
Clear steps for reproduction are missing.
To investigate, it is necessary for a failure to occur and to increase the log size for Skale-admin on QANet
Expected behavior
Skale admin should run 2 monitors after Geth nodes are synced
Actual state:
In some cases, skale admin initiates only contract monitoring, but does not restart the schain monitoring if it hangs.
Temporary workaround:
Restart the Skale admin container manually
The text was updated successfully, but these errors were encountered: