El nodo no comienza a sincronizarse

Question

El nodo no comienza a sincronizarse

4

144 2019-02-21

Tuveelnodo completamente sincronizado hace solo unpar de días ytuve que reiniciar varias vecesmientrastrabajabaen cosas. Ahorano comenzará a sincronizarse y seguirá arrojando losmismoserrores: ¿algunaidea sobre cómo solucionarlo?

¡Por supuesto queno quieroborrarmás de 80 Gb de contexto + cadena de datos! Ejecutandoen el contenedor dockerinstalado desdetezosmainnet.sh. La cajatiene 20gb de RAM,CPU y suficiente disco. Seejecutaen el últimoprotocolo 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)

- Cualestuplataforma?¿Cuálesel hash de confirmación detu compilación?¿Movió la carpeta de contexto?¿Está llenotu disco?¿Estás usando una ventana acoplable?Damás contexto,de lo contrario,es difícil ayudarte
  
  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
- seestáejecutandoen la ventana acoplableen alipine ...no construí usémainent.shen el sitio de documentacióntécnica detezos como dije queestaba sincronizado yfuncionandobien.Instaletodo con docker-compose ...no,nomoví la carpeta de contexto ...el discotiene muchoespacioejecutándoseen el últimoprotocolo 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
- Actualice supreguntapara dar contextoporfavoren lugar de responderen los comentarios.Esmejormejorar supreguntapara que quede lomás claroposibleporfavor.
  
  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 respuesta

votos

lefessan · Answer 1 · 2019-02-21

4

2019-02-21

Parece unainconsistenciaen labase de datos.Una vez que unbloque ha sido validadoporelnodo y almacenadoen labase de datos store,se supone que su contexto debe almacenarseen labase de datos context.Parece que losmensajes deerror dicen queelnodonopuedeencontrarel contexto de unbloque.Probablemente se deba a que las dosbases de datos yanoestán sincronizadas,probablemente labase de datos storetiene bloques queel contextnotiene.

Debeeliminar labase de datos store,se reiniciará la sincronización desdeelprincipio.Paramayor seguridad,tambiénpuedeeliminar labase de datos context,en caso de que hayamáserroresen suinterior.