LBRYCommunity/lbrycrd
1
0
Fork 0
Code Issues 29 Pull requests 1 Projects Releases 32 Packages Wiki Activity

lbrycrdd crashes on after update new release package #278

New issue
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)
Copy link

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)
Copy link

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)
Copy link

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)
Copy link

@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)
Copy link

@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)
Copy link

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)
Copy link

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)
Copy link

@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)
Copy link

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)
Copy link

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)
Copy link

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)
Copy link

@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)
Copy link

@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 Branch/Tag specified
Branches Tags
master
mergemine_hf
block_info_fix
block_info_fix_try2
v19_master
hash_bit_seq
v17_master
finance
static_link
small_takeover_experiment
dont_force_segwit
add_signature_test
cache_nth_trie_children
v12_master
experimental_use_basho_leveldb
experimental_separate_dbs
experimental_use_bdb_for_claimtrie
experimental_prefix_node_pool
experimental_sqlite_kvps
move_to_gitlab_ci
get_activations_in_block
add_claim_import_scripts
v0.17.3.3
v0.19.1.3
v0.17.4.6
v0.19.1.2
v0.17.4.5
v0.19.1.1
v0.17.4.4
v0.17.4.3
v0.17.4.2
v0.17.4.1
v0.17.3.2
v0.17.3.1
v0.17.3.0rc1
v0.17.2.1
v0.17.2.0
v0.17.1.0
v0.12.4.1
v0.12.4.0
v0.12.3.1
v0.12.3.0
v0.12.2.3
v0.12.2.2
v0.12.2.1
v0.12.2.0
v0.12.1.2
v0.12.1.1
v0.12.1.0
v0.12.0.6
v0.12.0.5
getclaimbyid_1
v0.12.0.4
v0.12.0.3
v0.12.0.2
v0.3.16
v0.3.15
0.13.0
test-win-release
v0.12.99
v0.3-osx
v0.2-alpha
v0.1-alpha-os-x
v0.1-alpha
Labels
Clear labels   
area: devops

   
area: discovery

   
area: docs

   
area: livestream

   
area: proposal

Work is part of a proposal

  
consider soon

Discuss this issue at the next planning meeting, then remove this label

  
Epic

   
good first issue

   
hacktoberfest

Welcome to Hacktoberfest

  
hard fork

   
help wanted

   
icebox

Long-term storage

  
Invalid

   
level: 0

   
level: 1

No knowledge of the existing code required

  
level: 2

Some knowledge of the existing code is recommended

  
level: 3

Significant knowledge of the existing code is recommended

  
level: 4

Intimate knowledge of the existing code is recommended

  
needs: exploration

Solution unclear, needs research

  
needs: grooming

Issue needs to be groomed before work can start

  
needs: priority

Priority level needs to be defined

  
needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

  
needs: tech design

Needs technical design signoff before implementation can begin

  
on hold

Temporarily paused

  
priority: blocker

Issue is blocking release, do ASAP

  
priority: high

Work needs to be moved into sprint ASAP

  
priority: low

Work should be done but can stay in the backlog for now

  
priority: medium

Work needs to be done within 2-3 sprints

  
resilience

   
soft fork

   
Tom's Wishlist

   
type: bug

Existing functionality is wrong or broken

  
type: discussion

A conversation. No specific changes requested

  
type: improvement

Existing (or partially existing) functionality needs to be changed

  
type: new feature

New functionality that does not exist yet

  
type: refactor

Minimal user-visible changes, but significant internal work

  
type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

  
type: testing

Solution needs additional user testing

  
unplanned

Work that was not planned into the spirnt, took priority over planned work

  
work in progress

The proposed solution is still incomplete.

No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?