lbrycrdd crashes on after update new release package #278

Closed
opened 2019-05-21 16:56:24 +02:00 by osiztechnologies · 12 comments
osiztechnologies commented 2019-05-21 16:56:24 +02:00 (Migrated from github.com)

We got below error message from terminal after update the v0.12.4.1 package.

lbrycrdd: main.cpp:2124: bool DisconnectBlock(const CBlock&, CValidationState&, const CBlockIndex*, CCoinsViewCache&, CClaimTrieCache&, bool*): Assertion `pindex->GetBlockHash() == trieCache.getBestBlock()' failed.
Aborted (core dumped)

we have tried -reindex. but not working properly.

Kindly guide how to resolve this issue.

We got below error message from terminal after update the v0.12.4.1 package. lbrycrdd: main.cpp:2124: bool DisconnectBlock(const CBlock&, CValidationState&, const CBlockIndex*, CCoinsViewCache&, CClaimTrieCache&, bool*): Assertion `pindex->GetBlockHash() == trieCache.getBestBlock()' failed. Aborted (core dumped) we have tried -reindex. but not working properly. Kindly guide how to resolve this issue.
BrannonKing commented 2019-05-21 17:50:36 +02:00 (Migrated from github.com)

What version were you running before?
What OS are you on?
You're using an official build or you compiled it yourself?
Do you have anything in the wallet associated with that instance (or would it be okay to lose that wallet)?
What block number failed?
Does it fail on restart now?
Can you get the output of the getchaintips RPC call?
Or can you find that error in the ~/.lbrycrd/debug.log file? Such that you could trim it down to a few KB of context and post that here?

What version were you running before? What OS are you on? You're using an official build or you compiled it yourself? Do you have anything in the wallet associated with that instance (or would it be okay to lose that wallet)? What block number failed? Does it fail on restart now? Can you get the output of the getchaintips RPC call? Or can you find that error in the ~/.lbrycrd/debug.log file? Such that you could trim it down to a few KB of context and post that here?
tzarebczan commented 2019-05-22 03:30:12 +02:00 (Migrated from github.com)

Also, how much memory is available on the server? LBRYcrd requires around 4GB to run currently.

Also, if you upgraded from a pre-hardfork version, you'll need to clear out the data/banned list (excluding the wallet) and re-sync. See https://lbry.com/news/hf1903

Also, how much memory is available on the server? LBRYcrd requires around 4GB to run currently. Also, if you upgraded from a pre-hardfork version, you'll need to clear out the data/banned list (excluding the wallet) and re-sync. See https://lbry.com/news/hf1903
osiztechnologies commented 2019-05-22 07:45:51 +02:00 (Migrated from github.com)

@BrannonKing
What version were you running before? - 12.2.0
What OS are you on? - ubuntu 16.04
You're using an official build or you compiled it yourself? - lbrycrd-linux.zip - v0.12.4.1
What block number failed? - after 450000

@BrannonKing What version were you running before? - 12.2.0 What OS are you on? - ubuntu 16.04 You're using an official build or you compiled it yourself? - lbrycrd-linux.zip - v0.12.4.1 What block number failed? - after 450000
osiztechnologies commented 2019-05-22 08:07:49 +02:00 (Migrated from github.com)

@tzarebczan

we have used 16GB of memory in instance.
Kindly share how to clear the data/banned list from the wallet.

@tzarebczan we have used 16GB of memory in instance. Kindly share how to clear the data/banned list from the wallet.
tzarebczan commented 2019-05-22 16:53:07 +02:00 (Migrated from github.com)

Yes, sounds like you were on the old chain and need to clear out. The link I shared before has this information. You pretty much want to clear out everything in the lbrycrd folder except for your wallet, and configuration file.

Yes, sounds like you were on the old chain and need to clear out. The link I shared before has this information. You pretty much want to clear out everything in the lbrycrd folder **except for your wallet, and configuration file**.
BrannonKing commented 2019-05-22 17:14:21 +02:00 (Migrated from github.com)

0.12.4.0 contained a hard-fork that went live at the end of March. That means you've been on the wrong chain for two months. Sure it was failing on 450000 rather than 540000 ?

0.12.4.0 contained a hard-fork that went live at the end of March. That means you've been on the wrong chain for two months. Sure it was failing on 450000 rather than 540000 ?
osiztechnologies commented 2019-05-23 10:36:38 +02:00 (Migrated from github.com)

@tzarebczan we have tried. but same issue occurred again.

How to resolve this issue.

@tzarebczan we have tried. but same issue occurred again. How to resolve this issue.
BrannonKing commented 2019-05-23 21:53:30 +02:00 (Migrated from github.com)

We don't have enough information to solve this at the moment. I need some log files. Can you upload them somewhere and put a link here?

We don't have enough information to solve this at the moment. I need some log files. Can you upload them somewhere and put a link here?
osiztechnologies commented 2019-05-24 10:18:12 +02:00 (Migrated from github.com)

Hereby i have attached debug.log file for your reference.
debug.log

Hereby i have attached debug.log file for your reference. [debug.log](https://github.com/lbryio/lbrycrd/files/3215811/debug.log)
BrannonKing commented 2019-05-24 15:29:50 +02:00 (Migrated from github.com)

Thanks for the log file. Here's what I get from the log file: the last time that your older version was ran it wasn't clean killed. I.e. it was killed with SIGKILL rather than SIGTERM or SIGINT. Hence, the database was not in a clean state, it was probably corrupted. After that, I see many attempts to run that all crash in a similar manner. It's possible that they are crashing on corrupt data in the database. However, it's more likely that the OS is terminating them for too much RAM usage or you're out of disk space.

Thanks for the log file. Here's what I get from the log file: the last time that your older version was ran it wasn't clean killed. I.e. it was killed with SIGKILL rather than SIGTERM or SIGINT. Hence, the database was not in a clean state, it was probably corrupted. After that, I see many attempts to run that all crash in a similar manner. It's possible that they are crashing on corrupt data in the database. However, it's more likely that the OS is terminating them for too much RAM usage or you're out of disk space.
osiztechnologies commented 2019-05-27 10:30:34 +02:00 (Migrated from github.com)

@BrannonKing Kindly share how to overcome this issue.

@BrannonKing Kindly share how to overcome this issue.
tzarebczan commented 2019-05-28 20:02:17 +02:00 (Migrated from github.com)

@osiztechnologies have you followed the directions above (https://github.com/lbryio/lbrycrd/issues/278#issuecomment-494837854) or on https://lbry.com/news/hf1903 ?

Shoot me a DM on chat.lbry.com (@jiggytom) if you need help with this process. Closing the issue for now as it seems to be upgrade related.

@osiztechnologies have you followed the directions above (https://github.com/lbryio/lbrycrd/issues/278#issuecomment-494837854) or on https://lbry.com/news/hf1903 ? Shoot me a DM on chat.lbry.com (@jiggytom) if you need help with this process. Closing the issue for now as it seems to be upgrade related.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#278
No description provided.