I have previously erased three state-related files and replaced them with a third-party state.sql due to exhaustion of disk space.
Proof activation was not initiated after the replacement either.
And this time it will be the next Proof activation after that.
replace state.sql
leading up to the timing of the first proof activation after the replacement => proof activation was not performed
the next proof activation after that is today.
I have previously erased three state-related files and replaced them with a third-party state.sql due to exhaustion of disk space.
Proof activation was not initiated after the replacement either.
And this time it will be the next Proof activation after that.
replace state.sql
leading up to the timing of the first proof activation after the replacement => proof activation was not performed
the next proof activation after that is today.
Another thing I know is that this problem is occurring on more than one PC.
However, there are some PCs where the state.sql has been replaced, but this time the proof activation is running.
Please pursue the cause from the logs and correct the problem.
Environment
Describe the bug
Proof activation doesn't start.
Steps to reproduce
Expected behavior
Proof activation starts normally.
Actual behavior
Proof activation doesn't start.
Logs
spacemesh-log-7c8cef2b 2.txt.zip
Extra information
I have previously erased three state-related files and replaced them with a third-party state.sql due to exhaustion of disk space. Proof activation was not initiated after the replacement either. And this time it will be the next Proof activation after that.
I have previously erased three state-related files and replaced them with a third-party state.sql due to exhaustion of disk space. Proof activation was not initiated after the replacement either. And this time it will be the next Proof activation after that.
Another thing I know is that this problem is occurring on more than one PC. However, there are some PCs where the state.sql has been replaced, but this time the proof activation is running.
Please pursue the cause from the logs and correct the problem.