Node Getting Stuck


#1

Everything runs good, epoch check_config epoch.yaml turns OK.

I start it with ./epoch start

log file and all good

curl http://127.0.0.1:3013/v2/blocks/top

Check with this and see that I’m stuck at height 3116.

Here is the log/epoch_node.log file:

`2018-10-17 18:48:35.757 [debug] <0.13147.0>@aec_peers:async_add_peer:609 New IP address for host <<“MY IP”>> {54,212,16,13} -> {18,232,171,235}

2018-10-17 18:48:35.757 [info] <0.1313.0>@aec_peers:on_add_peer:1048 Peer “pp_2QWF3eQ…h32GE5H” - ignoring peer address changed from 113.89.239.100:3015 to 113.87.14.235:3015 by $

2018-10-17 18:49:06.207 [debug] <0.1313.0>@aec_peers:on_ping_timeout:1098 Peer “pp_zoq7ecY…7ikDnb9” - schedule ping

2018-10-17 18:49:11.209 [info] <0.7463.0>@aec_peer_connection:handle_request_timeout:423 ping request timeout, stopping peer_connection

2018-10-17 18:49:11.209 [debug] <0.13177.0>@aec_sync:ping_peer:526 Ping (“pp_zoq7ecY…7ikDnb9”): {error,request_timeout}

2018-10-17 18:49:11.210 [debug] <0.1313.0>@aec_peers:conn_schedule_ping:1494 Peer “pp_zoq7ecY…7ikDnb9” - wait 120000 ms for next ping

2018-10-17 18:49:11.210 [debug] <0.1313.0>@aec_peers:on_connection_failed:814 Peer “pp_zoq7ecY…7ikDnb9” - connection to 13.251.77.130:3015 failed by process <0.7463.0>

2018-10-17 18:49:11.211 [debug] <0.1313.0>@aec_peers:schedule_connect:723 Waiting 100 ms for the next connection

2018-10-17 18:49:11.312 [debug] <0.1313.0>@aec_peers:start_connection:753 Peer “pp_22UBkp9…RpSKWTr” - starting connection to 31.13.251.87:3015

2018-10-17 18:49:11.312 [debug] <0.1313.0>@aec_peer_connection:connect:68 New peer connection to #{host => <<“31.13.251.87”>>,port => 3015,pubkey => <<51,54,239,105,215,241,94,204$

2018-10-17 18:49:12.314 [debug] <0.13181.0>@aec_peer_connection:handle_info:271 Failed to connected to {<<“31.13.251.87”>>,3015}: {error,timeout}

2018-10-17 18:49:12.314 [debug] <0.1313.0>@aec_peers:on_connection_failed:814 Peer “pp_22UBkp9…RpSKWTr” - connection to 31.13.251.87:3015 failed by process <0.13181.0>

2018-10-17 18:49:12.314 [debug] <0.1313.0>@aec_peers:schedule_connect:723 Waiting 28999 ms for the next connection

2018-10-17 18:49:35.100 [debug] <0.1313.0>@aec_peers:on_ping_timeout:1098 Peer “pp_21Fj1Ez…MrtjJmM” - schedule ping

2018-10-17 18:49:40.102 [info] <0.12799.0>@aec_peer_connection:handle_request_timeout:423 ping request timeout, stopping peer_connection

2018-10-17 18:49:40.102 [debug] <0.13199.0>@aec_sync:ping_peer:526 Ping (“pp_21Fj1Ez…MrtjJmM”): {error,request_timeout}

2018-10-17 18:49:40.103 [debug] <0.1313.0>@aec_peers:on_connection_failed:814 Peer “pp_21Fj1Ez…MrtjJmM” - connection to 54.189.139.100:3015 failed by process <0.12799.0>

2018-10-17 18:49:40.103 [debug] <0.1313.0>@aec_peers:schedule_connect:723 Waiting 1210 ms for the next connection

2018-10-17 18:49:40.103 [debug] <0.1313.0>@aec_peers:on_log_ping:991 Peer “pp_21Fj1Ez…MrtjJmM” - got ping event error for unknown peer connection

2018-10-17 18:49:41.314 [debug] <0.1313.0>@aec_peers:start_connection:753 Peer “pp_2ZA2gge…eo8s18J” - starting connection to 13.251.129.130:3015

2018-10-17 18:49:41.314 [debug] <0.1313.0>@aec_peer_connection:connect:68 New peer connection to #{host => <<“13.251.129.130”>>,port => 3015,pubkey => <<51,54,239,105,215,241,94,2$

2018-10-17 18:49:41.315 [debug] <0.1313.0>@aec_peers:schedule_connect:723 Waiting 30000 ms for the next connection

2018-10-17 18:49:42.316 [debug] <0.13207.0>@aec_peer_connection:handle_info:271 Failed to connected to {<<“13.251.129.130”>>,3015}: {error,timeout}

2018-10-17 18:49:42.316 [debug] <0.1313.0>@aec_peers:on_connection_failed:814 Peer “pp_2ZA2gge…eo8s18J” - connection to 13.251.129.130:3015 failed by process <0.13207.0>

2018-10-17 18:49:42.316 [debug] <0.1313.0>@aec_peers:schedule_connect:723 Waiting 28999 ms for the next connection

2018-10-17 18:50:05.104 [debug] <0.1313.0>@aec_peers:on_ping_timeout:1098 Peer “pp_2ZyYhD9…jzXon1K” - schedule ping`


#2

Hey, we have forwarded your question to the dev team. Expect a reply soon.


#3

Hey there,

Quick update;

This morning I have tried again with 0.24 and height went a little bit more say height 3400.

I have deleted everything and tested 0.22 and 0.23 versions as well. This time height didn’t move at all. It was height 0.

Right after seeing that, I have deleted and switched to 0.24 again. But this time height got stuck at 0 and didn’t move at all.

It’s not just me, another person on Telegram group had the same problem I’ve had as well.


#4

Hi @oldnovember,

you can’t sync 0.22 and 0.23 to testnet (0.24) because the version incompatibility.

In regards to 0.24 sync issue it’s known issue that should be addressed in the next release. As a workaround you can try restarting the node (it may need more than one try). The issue is performance related, so if you run on faster hardware you should not experience it.


#5

+10gbps network, $10K worth GPU card, Xeon Plat 8k and etc… I think my machine is good enough :slight_smile:

Will be looking forward to 0.25 release.


#6

@oldnovember That’s would be shame indeed :slight_smile:
I overlooked your logs. It’s not the same issue I’m talking about.

Could you please make sure you’re running v0.24 then share the output of
log/epoch.log and log/epoch_sync.log as well as the output of curl localhost:3013/v2/status


#7

I have the same problem. Ubuntu 18.04 epoch 0.24 repeatedly started the node by deleting the my_db first but the height is totally different from that of https://explorer.aepps.com/

Starting peers are:
<<“aenode://[email protected]0:3015”>>, %% us-west-2
<<“aenode://[email protected].60:3015”>>, %% eu-central-1
<<“aenode://[email protected].250:3015”>>,%% ap-southeast-1
<<“aenode://[email protected]7:3015”>> %% eu-west-2

The machine is fast enough 8cores and 16Gb of ram.

Status is:

curl localhost:3013/v2/status
{“difficulty”:267345229,“genesis_key_block_hash”:“kh_2FVh76cT3KogqaK7WLxY91SynARRCdK6tdevquatBspqFEZoUw”,“listening”:true,“node_revision”:“0204d168dd2ae992bc0b88e0b3a03cdbe4fcaba3”,“node_version”:“0.24.0”,“peer_count”:96,“pending_transactions_count”:0,“protocols”:[{“effective_at_height”:0,“version”:25}],“solutions”:0,“syncing”:true}

curl http://127.0.0.1:3013/v2/blocks/top
{“key_block”:{“beneficiary”:“ak_tjnw1KcmnwfqXvhtGa9GRjanbHM3t6PmEWEWtNMM3ouvNKRu5”,“hash”:“kh_25JLewuLFLZ3AXxRAni8mxknQ5NEu9vgmEpZvYFxCoQ9XLk1Df”,“height”:7642,“miner”:“ak_VbNY4UkVCwiXX1tDbotdLDVwU7z7ufXfyfQs4BCmJeN8undNY”,“nonce”:13188373383693018078,“pow”:[472903,17395154,22836516,25784869,44301924,58130233,82216259,86525387,116097203,125822841,126190491,126424827,131734416,140129987,146326214,149681496,169177838,171855320,177053492,179286382,194223028,206870600,235814877,245923568,329734706,347295433,347571925,349387004,369743966,392174048,397113768,399735791,408948347,411561424,417892874,433632081,449369134,450524245,457405439,514010146,525048267,529649568],“prev_hash”:“kh_2iN7XDACCG5hT9LgLCdFvznP46zryWNNsrwj3Fgz7WBa8PDa8e”,“prev_key_hash”:“kh_2iN7XDACCG5hT9LgLCdFvznP46zryWNNsrwj3Fgz7WBa8PDa8e”,“state_hash”:“bs_2quZ8JxUNtbouMHSP17dbPwNohzh1Eg8TxoAECX1u7SDA3ZczD”,“target”:537923748,“time”:1540656343014,“version”:25}}

Logs are quite big, where should i put them?


#8

Can anybody explain on what epoch version are these resources?
And how can we sync on the same chain?
The faucet and the explorer seem to be on different chains

https://faucet.aepps.com/

https://explorer.aepps.com/#/


#9

Hey @sirhashalot,

We’ve forwarded your questions to the dev team and they’ll get back to you as soon as possible.

Regards,
Albena


#10

Hey @sirhashalot,

You are perfectly in sync (or was at block 7642) with UAT/Testnet.

Please check this discussion for more information, seems like the problem is similar.

Regards,
Albena


Help on ubuntu mining