Closed daniel1302 closed 1 year ago
The same issue is happening for a last few days:
failed to create and publish segment: failed to create snapshot: failed to get data dump metadata: failed to get database version: FATAL: terminating connection due to administrator command (SQLSTATE 57P01)
failed to initialise network history:failed to create networkHistory service:failed to create network history store:failed to create index:failed to open level db file:resource temporarily unavailable
Error: maximum number of possible restarts has been reached: failed to execute binary /jenkins/workspace/common/system-tests-lnl-mainnet/networkdata/testnet/visor/visor13/current/vega [datanode node --hom
https://jenkins.ops.vega.xyz/job/common/job/system-tests-lnl-mainnet/308/
Problem encountered
After the protocol upgrade we are not able to open go level DB in the data node. We are getting this error:
We saw this error, but there was a fix to close the go-level db properly, and we haven't seen it for 2 weeks.
You can see the pipeline that failed here: https://jenkins.ops.vega.xyz/job/common/job/system-tests-lnl-mainnet/291
Observed behaviour
Data node is failing after protocol upgrade.
Expected behaviour
Data node should not fail
System response
Data-node stderr:
Data node STD OUT:
Steps to reproduce
Manual
Steps to reproduce the behaviour manually:
Automation
Link to automation and explanation on how to run it to reproduce the problem/bug
Evidence
Logs
If applicable, add logs and/or screenshots to help explain your problem.
Additional context
Add any other context about the problem here including; system version numbers, components affected.
Definition of Done
Before Merging
After Merging
Done
if there is NO requirement for new system-tests