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
On web3 container startup when the DB is not empty (as it will be on an environment that is not local) the following exception occurs on state initialization:
Error creating bean with name 'mirrorNodeState': Invocation of init method failed
...
Caused by: java.lang.IllegalStateException: Total balance of all accounts does not match the total float: actual: 0 vs expected: 5000000000000000000
2025-03-06 14:10:21 at com.hedera.node.app.service.token.impl.schemas.V0490TokenSchema.createGenesisSchema(V0490TokenSchema.java:194)
2025-03-06 14:10:21 at com.hedera.node.app.service.token.impl.schemas.V0490TokenSchema.migrate(V0490TokenSchema.java:116)
2025-03-06 14:10:21 at com.hedera.mirror.web3.state.components.SchemaRegistryImpl.migrate(SchemaRegistryImpl.java:127)
2025-03-06 14:10:21 at com.hedera.mirror.web3.state.components.ServiceMigratorImpl.lambda$doMigrations$0(ServiceMigratorImpl.java:69)
...
The reason for that is that on startup all of the account balances are summed up and the value is expected to be equal to 50,000,000,000 HBARs (comes from config). Currently the account size is not returned correctly and no actual sum is performed.
Solution
Disable the account balance verification since it is not applicable for the mirror node.
Alternatives
No response
The text was updated successfully, but these errors were encountered:
Problem
On web3 container startup when the DB is not empty (as it will be on an environment that is not local) the following exception occurs on state initialization:
The reason for that is that on startup all of the account balances are summed up and the value is expected to be equal to 50,000,000,000 HBARs (comes from config). Currently the account size is not returned correctly and no actual sum is performed.
Solution
Disable the account balance verification since it is not applicable for the mirror node.
Alternatives
No response
The text was updated successfully, but these errors were encountered: