Il nodo non inizia la sincronizzazione

Question

Il nodo non inizia la sincronizzazione

4

144 2019-02-21

Avevoilnodo completamente sincronizzato solo unpaio digiornifae ho dovuto riavviarepiù voltementre lavoravo. Oranoninizierà la sincronizzazionee continuerà agenerare questi stessierrori: qualcheidea su come risolverlo?

Ovviamentenon voglioeliminarepiù di 80 GB di contesto + catena di dati! Inesecuzionenel container dockerinstallato datezosmainnet.sh. Box ha 20 GB di RAM libera,CPUe disco sufficiente. Inesecuzione sull'ultimoprotocollo 003-PsddFKi3

 Feb 21 00:44:11 - validator.peer(276): Worker started for NetXdQprcVkpa:idsjspFRxYWD
Feb 21 00:44:11 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Feb 21 00:44:11 - node.validator.bootstrap_pipeline: Error, dumping error stack:
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:
Feb 21 00:44:11 - validator.peer(276): Worker crashed:
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:15 - validator.peer(277): Worker started for NetXdQprcVkpa:idsn9he7cC2z
Feb 21 00:44:15 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Feb 21 00:44:15 - node.validator.bootstrap_pipeline: Error, dumping error stack:
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:
Feb 21 00:44:15 - validator.peer(277): Worker crashed:
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:17 - node.main: Received the TERM signal, triggering shutdown.
Feb 21 00:44:17 - node.main: Shutting down the Tezos node...
Feb 21 00:44:17 - validator.chain(1): Worker terminated
Feb 21 00:44:17 - validator.block: Worker terminated
Feb 21 00:44:17 - prevalidator.NetXdQprcVkpa.PsddFKi32cMJ(1): Worker terminated
Feb 21 00:44:17 - node.main: Shutting down the RPC server...
Feb 21 00:44:17 - node.main: BYE (-11)

I had the node fully synced just a couple of days ago and had to restart several times while working on things. Now it wont start syncing and keeps throwing these same errors - any ideas on how to fix?

Of course I don't wanna delete 80+ Gb context + data chain! Running in docker container installed from tezos mainnet.sh. Box has 20gb free ram, cpu and enough disk. Running on latest protocol 003-PsddFKi3

Feb 21 00:44:11 - validator.peer(276): Worker started for NetXdQprcVkpa:idsjspFRxYWD
Feb 21 00:44:11 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Feb 21 00:44:11 - node.validator.bootstrap_pipeline: Error, dumping error stack:
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:11 - node.validator.bootstrap_pipeline:
Feb 21 00:44:11 - validator.peer(276): Worker crashed:
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:11 - validator.peer(276): Not_found
Feb 21 00:44:15 - validator.peer(277): Worker started for NetXdQprcVkpa:idsn9he7cC2z
Feb 21 00:44:15 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Feb 21 00:44:15 - node.validator.bootstrap_pipeline: Error, dumping error stack:
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:   Not_found
Feb 21 00:44:15 - node.validator.bootstrap_pipeline:
Feb 21 00:44:15 - validator.peer(277): Worker crashed:
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:15 - validator.peer(277): Not_found
Feb 21 00:44:17 - node.main: Received the TERM signal, triggering shutdown.
Feb 21 00:44:17 - node.main: Shutting down the Tezos node...
Feb 21 00:44:17 - validator.chain(1): Worker terminated
Feb 21 00:44:17 - validator.block: Worker terminated
Feb 21 00:44:17 - prevalidator.NetXdQprcVkpa.PsddFKi32cMJ(1): Worker terminated
Feb 21 00:44:17 - node.main: Shutting down the RPC server...
Feb 21 00:44:17 - node.main: BYE (-11)

fonte
kahmed

- Qual è latuapiattaforma?Qual è l'hash di commit dellatuabuild?Hai spostato la cartella contestuale?Iltuo disco èpieno?Stai usando unafinestramobile?Forniscipiù contesto,altrimenti è difficile aiutarti
  
  What is your platform ? Which is the commit hash of your build ? Did you move the context folder ? Is your disk full ? Are you using a docker ? Give more context pls otherwise it is hard to help you
  - 0
  - 2019-02-21
  - Ezy
- funzionanellafinestramobile su alipine ..non ho compilato usatomainent.sh sul sito ditezostech docperché ho detto cheera sincronizzatoe funzionavabene.Installatutto con docker-compose ..nonon ho spostato la cartella del contesto ..il disco hamolto spazioin esecuzione sull'ultimoprotocollo 003-PsddFKi3
  
  it running in docker on alipine .. i didnt build used the mainent.sh on tezos tech doc site as i said it was synced and running fine. Install everything with docker-compose ..no i didn't move context folder..disk has plenty of space running on latest protocol 003-PsddFKi3
  - 0
  - 2019-02-21
  - kahmed
- Aggiorna latua domandaperfornire un contestoinvece di risponderenei commenti.Megliomigliorare latua domandaper renderlailpiù chiarapossibile
  
  Update your question to give context pls instead of responding in the comments. Better to improve your question to make it as clear as possible pls
  - 0
  - 2019-02-21
  - Ezy

1 risposta

voti

lefessan · Answer 1 · 2019-02-21

4

2019-02-21

Sembra un'incongruenzanel database.Una volta che unblocco è stato convalidato dalnodoe memorizzatonel database store,il suo contesto dovrebbeesserememorizzatonel database context.Sembra chei messaggi dierrore dicano cheilnodonon riesce atrovareil contesto di unblocco.Probabilmente èperchéi due databasenon sonopiù sincronizzati,probabilmenteil database store hablocchi cheil contextnon ha.

Dovresti rimuovereil database store,verrà riavviata la sincronizzazione dall'inizio.Permaggiore sicurezza,potresti anche rimuovereil database context,nel caso ci sianopiùerrori all'interno.