Skip to content
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

Failed to load freeze state from levelDB. It is unsafe to continue. #922

Closed
Saul75 opened this issue Apr 24, 2019 · 26 comments
Closed

Failed to load freeze state from levelDB. It is unsafe to continue. #922

Saul75 opened this issue Apr 24, 2019 · 26 comments
Labels

Comments

@Saul75
Copy link

Saul75 commented Apr 24, 2019

Hello.

After synchronizing omnicore-qt 0.4.0 today I've got the message "Unknown block versions being mined! It's possible unknown rules are in effect." (due to ASICBoost?)

I closed the application. It has been closed normally, with the message "Do not shut down the computer until this window disappears".

And after that it won't start again with the message "Failed to load freeze state from levelDB. It is unsafe to continue."

Is it a bug or data corruption? What should I do?

@Saul75
Copy link
Author

Saul75 commented Apr 24, 2019

From omnicore.log:

2019-04-25 00:12:00 Loading freeze state from levelDB
2019-04-25 00:12:08 ------------------------------
2019-04-25 00:12:08 version: 0, class C
2019-04-25 00:12:08 type: 71 (Enable Freezing)
2019-04-25 00:12:08 property: 31 (SP token: 31)
2019-04-25 00:12:08 logicMath_EnableFreezing(): rejected: sender 3MbYQMMmSkC3AgWkj9FMo5LsPTW1zBTwXL is not issuer of property 31 [issuer=32TLn1WLcu8LtfvweLzYUYU6ubc2YV9eZs]
2019-04-25 00:12:08 ERROR: While loading freeze transaction f8d31b28c8f83d2cde19a8d78fb16f26746a4b234808b859418d62bfcfc9df0c: non-zero return from interpretPacket
2019-04-25 00:12:08 Failed to load freeze state from levelDB. It is unsafe to continue.

@Starry9
Copy link

Starry9 commented Apr 25, 2019

Same as this.
log:
2019-04-25 03:46:16 init message: Parsing Omni Layer transactions...
2019-04-25 03:46:24 RestoreInMemoryState(): file: /data1/omnicore/MP_persist/balances-000000000000000000001f3402fdba495e3eb9557e2ca9209a44563959afb996.dat , loaded lines= 331961, res= 0
2019-04-25 03:46:24 RestoreInMemoryState(): file: /data1/omnicore/MP_persist/offers-000000000000000000001f3402fdba495e3eb9557e2ca9209a44563959afb996.dat , loaded lines= 79, res= 0
2019-04-25 03:46:24 RestoreInMemoryState(): file: /data1/omnicore/MP_persist/accepts-000000000000000000001f3402fdba495e3eb9557e2ca9209a44563959afb996.dat , loaded lines= 0, res= 0
2019-04-25 03:46:24 RestoreInMemoryState(): file: /data1/omnicore/MP_persist/globals-000000000000000000001f3402fdba495e3eb9557e2ca9209a44563959afb996.dat , loaded lines= 1, res= 0
2019-04-25 03:46:24 RestoreInMemoryState(): file: /data1/omnicore/MP_persist/crowdsales-000000000000000000001f3402fdba495e3eb9557e2ca9209a44563959afb996.dat , loaded lines= 17, res= 0
2019-04-25 03:46:24 RestoreInMemoryState(): file: /data1/omnicore/MP_persist/mdexorders-000000000000000000001f3402fdba495e3eb9557e2ca9209a44563959afb996.dat , loaded lines= 217, res= 0
2019-04-25 03:46:53 *** Failed to load freeze state from levelDB. It is unsafe to continue.

2019-04-25 03:46:53 Error: Failed to load freeze state from levelDB. It is unsafe to continue.

@15915826040
Copy link

image
How can I solve this problem?

@15915826040
Copy link

@dexX7

@LibraHan
Copy link

I've met the same problem today. When restart the wallet ,got the message "Failed to load freeze state from levelDB. It is unsafe to continue. " Tried many times, also the same result... @dexX7

@trybye
Copy link

trybye commented Apr 25, 2019

My version is 0.3.1.0,the same result after I restart the client

@xuefengyang
Copy link

I also encountered the same problem

@DingGeng-GitHub
Copy link

我也遇到了同样的问题

@Laizhongsheng
Copy link

how to fix it?

@lizaifang
Copy link

same problem, i deleted MP_* and OMNI_*, now it is scaning now

@Saul75
Copy link
Author

Saul75 commented Apr 25, 2019

The official answer regarding this issue is here: https://twitter.com/Omni_Layer/status/1121412541136216064 .

@qizikd
Copy link

qizikd commented Apr 26, 2019

The official answer regarding this issue is here: https://twitter.com/Omni_Layer/status/1121412541136216064 .

thanks

@xuefengyang
Copy link

I solved the problem by restart client command —— ./omnicored -startclean , The total time spend is about five hours.

@thisdaydayde
Copy link

same problem

@xuehuizhang
Copy link

xuehuizhang commented Apr 28, 2019

I solved the problem by restart client command —— ./omnicored -startclean , The total time spend is about five hours.

How did you do it? so little time?

@v1nc3ntlaw
Copy link

holy crap!

@i3bitcoin
Copy link

Any ETA on when the new update will be added?
One and half day needed to recover the wallet on HDD, but it's working too slow after -startclean.

@dexX7
Copy link
Member

dexX7 commented Apr 29, 2019

Hello guys,

we are aware of the issue. For now, there is a workaround:

  1. Restart Omni Core with ´-startclean` flag
  2. Wait until in parses all Omni Layer transactions, which can take 30 minutes up to a few hours
  3. Don't shutdown Omni Core (otherwise you have to repeat the parsing)

A fix is provided via #925 and any testing would be appreciated!

@gituser
Copy link

gituser commented May 1, 2019

Just stumbled upon this issue. Any ETA on new release?

Thanks.

@dexX7
Copy link
Member

dexX7 commented May 3, 2019

Hey guys,

we released Omni Core v0.5.0, which fixes the problem. You can find the binaries here:

https://github.com/OmniLayer/omnicore/releases

Or build from source from here:

https://github.com/OmniLayer/omnicore/tree/develop

@Saul75, @Starry9, @15915826040, @LibraHan, @trybye, @xuefengyang, @dg707170913, @Laizhongsheng, @lizaifang, @qizikd, @qianzhihui, @xuehuizhang, @v1nc3ntlaw, @i3bitcoin, @gituser

@dexX7 dexX7 closed this as completed May 3, 2019
@gituser
Copy link

gituser commented May 6, 2019

@dexX7
Rescan seems to be super slow and I can see a lot of requests being passed to hdds..

Is there any way to speed up? It's going like 0.01% for about 5-6 minutes.

And also it seems showing incorrect progress time:

2019-05-06 02:38:39 Still scanning.. at block 543038 of 574640. Progress: 83.10 %, about 5:317:05 hours remaining..
2019-05-06 02:38:39 init message: Still scanning.. at block 543038 of 574640.
Progress: 83.10 % (about 5:317:05 hours remaining)
2019-05-06 02:39:47 Still scanning.. at block 543053 of 574640. Progress: 83.10 %, about 5:317:07 hours remaining..
2019-05-06 02:39:47 init message: Still scanning.. at block 543053 of 574640.
Progress: 83.10 % (about 5:317:07 hours remaining)

@dexX7
Copy link
Member

dexX7 commented May 7, 2019

Hi @gituser, can you post your bitcoin.conf? (without any credentials!)

@gituser
Copy link

gituser commented May 7, 2019

@dexX7
there you go:

txindex=1
limitancestorcount=100
limitdescendant=100
cache=1024
walletnotify=/home/omnicore/.omnicore/cryptonotify.sh %s

EDIT: now replay has finished, but the process took us more than 3 days!
And certainly there is an issue in correct display of the remaining time for the replay process based on the average block scan speed as mentioned above.

@jamesleeabc
Copy link

-overrideforcedshutdown=1

@knoxcard2
Copy link

This did it for me...

omnicored -reindex=1

@dexX7
Copy link
Member

dexX7 commented Apr 24, 2020

Hi all,

please upgrade to the latest version of Omni Core, which resolves this issue most likely:

https://github.com/OmniLayer/omnicore/releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests