"La operación está desactualizada y es posible que nunca se incluya en la cadena"

Question

"La operación está desactualizada y es posible que nunca se incluya en la cadena"

5

170 2019-04-03

Lanzomi nodo así:

 ./tezos-node run --rpc-addr 127.0.0.1

Todopareceestarbien. Luego hago:

 ./tezos-client account activate alice with FileFromFaucet.json --force

Peronofunciona,apareceel siguienteerror:

 Warning:

                 This is NOT the Tezos Mainnet.

     The node you are connecting to claims to be running on the
               Tezos Alphanet DEVELOPMENT NETWORK.
          Do NOT use your fundraiser keys on this network.
          Alphanet is a testing network, with free tokens.

Waiting for the node to be bootstrapped before injection...
Current head: BLAFhGoUfmnS (timestamp: 2018-12-06T06:17:48Z, validation: 2019-04-03T14:08:44Z)
Node is bootstrapped, ready for injecting operations.
Operation successfully injected in the node.
Operation hash is 'opFZEnsWYL3AJfEnBDkjGdQggEDRrs1rqVYmNpebHkBcPvWsg6T'
Waiting for the operation to be included...
Fatal error:
  The operation opFZEnsWYL3AJfEnBDkjGdQggEDRrs1rqVYmNpebHkBcPvWsg6T is outdated and may never be included in the chain.
  We recommand to use an external block explorer.

Sigo sinentenderpor qué. ¿Minodonoestá actualizado?

EDITAR:

De acuerdo,el ./tezos-client get timestamp && date -u -Isecme da dostiempos diferentes. Sinembargo,sigoesperando ynada cambia. ¿Cómopuedo asegurarme de quemi nodoesté completamente sincronizado?

I launch my node like this:

./tezos-node run --rpc-addr 127.0.0.1

Everything seems to be okay. I then do:

./tezos-client account activate alice with FileFromFaucet.json --force

But it doesn't work, I get the following error:

Warning:

                 This is NOT the Tezos Mainnet.

     The node you are connecting to claims to be running on the
               Tezos Alphanet DEVELOPMENT NETWORK.
          Do NOT use your fundraiser keys on this network.
          Alphanet is a testing network, with free tokens.

Waiting for the node to be bootstrapped before injection...
Current head: BLAFhGoUfmnS (timestamp: 2018-12-06T06:17:48Z, validation: 2019-04-03T14:08:44Z)
Node is bootstrapped, ready for injecting operations.
Operation successfully injected in the node.
Operation hash is 'opFZEnsWYL3AJfEnBDkjGdQggEDRrs1rqVYmNpebHkBcPvWsg6T'
Waiting for the operation to be included...
Fatal error:
  The operation opFZEnsWYL3AJfEnBDkjGdQggEDRrs1rqVYmNpebHkBcPvWsg6T is outdated and may never be included in the chain.
  We recommand to use an external block explorer.

I still don't understand why. Is my node not updated?

EDIT:

Okay the ./tezos-client get timestamp && date -u -Isec command gives me two differents times. However, I keep waiting and nothing change. How can I make sure my node is fully synchronized?

- ¿Estásintentandoejecutarmainnet o alphanet?
  
  Are you trying to run mainnet or alphanet ?
  - 0
  - 2019-04-05
  - Ezy

1 respuesta

votos

RoMarQ · Accepted Answer · 2019-04-05

3

2019-04-05

Tu cadena aúnnoestá sincronizada.

(marca detiempo: 2018-12-06T06: 17: 48Z ,validación: 2019-04-03T14: 08: 44Z)

Comopuede ver,la cadenaestá actualmenteen 2018-12-06T06: 17: 48Z.

Para comprobar si la cadenaestá sincronizada,puede utilizar los siguientes comandos:

 ./tezos-client bootstrapped

o

 ./tezos-client get timestamp

Acerca de la sincronización denodos: enlace

Your Chain is not synced yet.

(timestamp: 2018-12-06T06:17:48Z, validation: 2019-04-03T14:08:44Z)

As you can see, the chain is currently in 2018-12-06T06:17:48Z.

To check if the chain is synced you can use the following commands:

./tezos-client bootstrapped

or

./tezos-client get timestamp

About node synchronization: link

Gracias.Lamarca detiempo actuales ahora 2018-12-15,pero llevamuchotiempo.Probablementepormi disco.Sinembargo,a vecesel comando de arranque se detiene y dice queel cliente se arranca con unamarca detiempo de 2018 ... Debería continuar HASTA queesté realmente hecho :(

Thank you. Current timestamp is now 2018-12-15 but it takes tons of time. Probably because of my disk. However, sometimes the bootstrapped command stop and says client is bootstrapped with a 2018 timestamp.... It should keep going UNTIL it's really done :(
- 0
- 2019-04-05
- iNukeLaPeste
Sí,el discoes ungranproblema.Conmi disco durotardaba semanasen sincronizarse. Solo verifique si lamarca detiempo siguemoviéndose a una velocidad relativamentebuena; de lo contrario,sumejor opción será usar unainstanciaen lanubepara sincronizar.

Yeah, disk is a big deal. With my hdd it was taking weeks to sync. Just check if the timestamp keeps moving at a relatively good speed, if not, your best option will be using a cloud instance to sync.
- 2
- 2019-04-05
- RoMarQ
Biengracias.Probaré con otro discoel lunes.Graciasportu respuesta,la acepto :)

Okay thanks. Will try with another disk on monday. Thanks for your answer, accepted it :)
- 1
- 2019-04-05
- iNukeLaPeste