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`