"작업이 오래되었으며 체인에 포함되지 않을 수 있습니다."

Question

"작업이 오래되었으며 체인에 포함되지 않을 수 있습니다."

5

170 2019-04-03

다음과 같이 노드를 시작합니다.

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

모든 것이 정상인 것 같습니다. 다음을 수행합니다.

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

하지만 작동하지 않습니다. 다음 오류가 발생합니다.

 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.

아직도 이유를 모르겠습니다. 내 노드가 업데이트되지 않습니까?

수정 :

알겠습니다. ./tezos-client get timestamp && date -u -Isec 명령은 나에게 두 가지 다른 시간을 제공합니다. 그러나 나는 계속 기다리며 아무것도 변하지 않습니다. 내 노드가 완전히 동기화되었는지 어떻게 확인할 수 있습니까?

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?

- 메인 넷 또는 알파넷을 실행하려고합니까?
  
  Are you trying to run mainnet or alphanet ?
  - 0
  - 2019-04-05
  - Ezy

1 대답

투표

RoMarQ · Accepted Answer · 2019-04-05

3

2019-04-05

체인이 아직 동기화되지 않았습니다.

( 타임 스탬프 : 2018-12-06T06 : 17 : 48Z ,유효성 검사 : 2019-04-03T14 : 08 : 44Z)

보시다시피 체인은 현재 2018-12-06T06 : 17 : 48Z에 있습니다.

체인이 동기화되었는지 확인하려면 다음 명령을 사용할 수 있습니다.

 ./tezos-client bootstrapped

또는

 ./tezos-client get timestamp

노드 동기화 정보 : 링크

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

감사합니다.현재 타임 스탬프는 이제 2018-12-15이지만 시간이 많이 걸립니다.아마도 내 디스크 때문일 것입니다.그러나 때때로 부트 스트랩 명령이 중지되고 클라이언트가 2018 타임 스탬프로 부트 스트랩되었다고 말합니다 .... 실제로 완료 될 때까지 계속 진행되어야합니다.

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
예,디스크는 큰 문제입니다.내 HDD로 동기화하는 데 몇 주가 걸렸습니다. 타임 스탬프가 비교적 좋은 속도로 계속 움직이는 지 확인하십시오. 그렇지 않은 경우 가장 좋은 방법은 클라우드 인스턴스를 사용하여 동기화하는 것입니다.

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
괜찮 감사.월요일에 다른 디스크로 시도합니다.답변 해 주셔서 감사합니다. 수락했습니다. :)

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