Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Automatically enable forging after rebuilding blockchain #141

Closed
jfernanz opened this issue May 20, 2016 · 6 comments
Closed

Automatically enable forging after rebuilding blockchain #141

jfernanz opened this issue May 20, 2016 · 6 comments

Comments

@jfernanz
Copy link

jfernanz commented May 20, 2016

I had to bash lisk.sh restart after the rebuild for the client to forge.

@mrv777
Copy link
Contributor

mrv777 commented May 20, 2016

I had the same experience. Except, I just did a reload after the rebuild to get it forging again

@Isabello
Copy link
Contributor

Isabello commented May 20, 2016

This is essentially expected behavior, since your delegate is not registered on the genesis block. Forging can't be enabled on a delegate that doesn't exist.

Not sure how it can be fixed since the API call is done upon startup of app.js.

@fix
Copy link
Contributor

fix commented May 26, 2016

Yes somehow the code can handle the end of rebuilding and trying again to enable forging on completion.

@fix
Copy link
Contributor

fix commented Aug 30, 2016

This is still pending i think. The very reason is that when the node start from scratch, it cannot find the account in the database that allow him to forge.

Mostly mitigated with db snapshot

@karmacoma karmacoma changed the title After rebuilding (bash lisk.sh rebuild), the client does not automatically enable forging Automatically enable forging after rebuilding blockchain Sep 30, 2016
@karmacoma karmacoma self-assigned this Sep 30, 2016
@karmacoma karmacoma added this to the Mainchain Stabilisation milestone Sep 30, 2016
@samsmith
Copy link

easier when #255 has been implemented ?

@karmacoma
Copy link
Contributor

@samsmith: No #255 is a separate issue, mainly related to swapping genesis block while connecting to the same database, which will cause conflict. We will fix, but not huge priority.

@karmacoma karmacoma added easy and removed medium labels Oct 14, 2016
shuse2 added a commit that referenced this issue Apr 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants