search

spacemeshos / bug-reports

Issue tracking for community-generated bug reports
Creative Commons Zero v1.0 Universal
0 stars 0 forks source link

App displays 'Offline' message repeatedly #3

Open yaelmhoffman opened 3 years ago

yaelmhoffman commented 3 years ago

User may start syncing, but repeatedly gets offline message in the status bar without any apparent solution.

Logs: https://drive.google.com/drive/u/1/folders/1OumPhrdnSYb3-mj_wFYE4pmDu2X7y7Et

lrettig commented 3 years ago

@yaelmhoffman I see three logs behind that link, which one should I be looking at?

yaelmhoffman commented 3 years ago

@lrettig Whichever one you like. They're all for the same issue.

lrettig commented 3 years ago

12_04_2021_connection_error.zip: looks like an NTP error. Is this user in China? Are they running the ntpfix version? Other network or firewall issues could prevent communication with NTP servers:

2021-04-12T13:42:25.522+0300    ERROR   00000.defaultLogger     Failed to initialize node.      {"errmsg": "NTP server errors [failed to read server response: read udp 109.234.39.127:48803->119.28.230.190:123: i/o timeout failed to read server response: read udp 109.234.39.127:53468->119.28.229.79:123: i/o timeout failed to read server response: read udp 109.234.39.127:45883->119.28.229.70:123: i/o timeout failed to read server response: read udp 109.234.39.127:35791->119.28.183.184:123: i/o timeout]"}
2021-04-12T15:19:47.286+0300    ERROR   164b8.app               system time couldn't synchronize        {"node_id": "164b82e76b7cc9a163846aab50a61a1471a87266c82f6e35ad7b11336ba29b7f", "errmsg": "NTP server errors [failed to read server response: read udp 109.234.39.127:57985->203.107.6.88:123: i/o timeout failed to read server response: read udp 109.234.39.127:42770->119.28.229.79:123: i/o timeout failed to read server response: read udp 109.234.39.127:55620->119.28.229.70:123: i/o timeout failed to read server response: read udp 109.234.39.127:53278->119.28.230.190:123: i/o timeout]"}

spacemesh-log_Layer1439Error: I don't see any errors in this log. I just see the node suddenly dying and restarting several times. Impossible to tell what's going on without more info. Could be that the process is running out of resources and is being killed by the OS. Could be user error.

spacemesh_offline_plap: same as previous one

lrettig commented 3 years ago

I noticed this in the app log for the last one. Not sure what this means. @avive any idea?

[2021-04-17 21:28:40.672] [error] In nodeManager, in startNode, error is: Error: Command failed: "/opt/Spacemesh/node/go-spacemesh" --grpc-server --grpc-port-new 9092 --json-server --tcp-port 7153 --config "/opt/Spacemesh/config/config.json" --coinbase 0x5c459965a3352bb6ac307de340e99abc846f6de255b7d528eb1c0e919da3d3af --start-mining --post-datadir "/home/username/Documents/spacemesh" -d "/home/username/.config/Spacemesh/no
de-data" >> "/home/username/.config/Spacemesh/spacemesh-log.txt"
Killed