Open IaroslavTitov opened 2 years ago
Can you try to increase the power of the server
What do you mean by power, @DDeAlmeida?
I checked my CPU usage, 53% is idle:
12:04:26 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
12:04:26 PM all 43.61 0.00 2.20 0.07 0.00 0.58 0.00 0.00 0.00 53.55
There's also plenty of memory avaliable:
[ec2-user@ip-172-31-18-80 ~]$ free -m
total used free shared buff/cache available
Mem: 7643 4377 1021 0 2244 3091
Still have 236GB of disk space.
The machine is EC2 a1.xlarge - 4 CPUs, 8 GB of RAM
What else can I check/increase? I'm always getting stuck at 99%, not any other point in the sync.
4CPU is not enough from my pov
Well, I got the specs recommended in the challenge... Maybe I'll try a better machine later.
However, I doubt that is the issue, since a lot of participants seem to be running on minimum requirement machines, some just run on home PCs.
Try to upgrade your node to 8CPU and 16RAM, imo you are having a performance issue
Retried with analogous server, but on ubuntu - same result. I will try a stronger machine next.
I am having the same, once I lost sync while trying something out I can never get back, deleting data, neard init, config.json, different sw commits... nothing helps. And I am not running on Intel 386sx.
Mine worked after restarting on a different machine with 8 CPUs and 16GB RAM + made sure CPU had AVX support. Still having issues producing chunks, but at least sync seems to have succeeded.
The issue
The neard service runs and syncs successfully, but never finishes syncing. (See attached logs, gets stuck at 99%+) My contract is up and pinging successfully. It has enough delegated near to be picked at validator, but I'm getting 0 uptime because node won't sync. When I grab
curl -s http://127.0.0.1:3030/status
- status issyncing
Staking contract -
tias.factory.shardnet.near
Troubleshooting
I've tried the following list of suggestions from @NodeRunner in discord:
I've also tried stopping and starting the service, rebooting the machine, deleting
data
folder and resyncing, none of it helped.I am running on EC2 in Amazon Linux 2, the machine meets minimum requirements.
Please let me know if I can provide more information.