I really don’t know why,but suddenly this mont one of my nodes have started to lose point in suspension and online parameters in almost all the satelites. [Captura] so I performed this script ( Script: Calculate Success Rates for Audit, Download, Upload, Repair ) and here are the results: [Captur…

[image] camulodunum: ordersfile corrupt entry: proto: pb.Order: illegal tag 0 (wire type 0) [image] One of my nodes getting suspension warnings troubleshooting Assuming that your node is a 32 bits architecture, the issue should be fixed on the next release v1.17.4 w…

[image] camulodunum: what can be making that much of downloads to fail Search your log for download failed and post the results. You can search failed audits by looking for 2 keywords in the same log line GET_AUDIT and failed

You might want to check your hard drive - it may be failing: sudo badblocks -v /dev/(whatever-your-device-is) This will take quite long, probably several hours.

run some diagnostics and don’t forget to check your cables… i would start by shutting the node down… to not create more damage while you figure out whats wrong… i would start by checking the smart stats of the hdd, if those says it’s going bad, then try to copy the data to a good drive and hope for…

[image] SGC: i would start by shutting the node down @camulodunum : If you shut down your node, be careful not to remove your docker container while shutting it down if you’re using the default docker logs though, otherwise they will be lost and you will not be able to analyse them. Just shut…

here I have he logs. seems to e some type of problems that is making the node to restart al time 2020-11-26T05:29:24.085Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”} 2020-11-26T05:29:24.088Z INFO Operator email {“Address”: “"} 2020-11-26T05:29:24.089…

mmmmm. weird since my node is running in 64 bits arm system Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-1022-raspi aarch64)

:thinking: Following the source files reported in the log that you have attached, I don’t find the same path that I found in my response to the other thread nor I cannot see why it’s panicking because it’s returning an error. I assumed that you are running v1.16.1 is that a right assumption?

[image] camulodunum: db.migration Database Version {“version”: 46} I think he does run v1.16.1 unless I am misreading this relation between database version with node version. As v1.15.3 had version 45

yeah 1.16.1 with watchtower working. at least for now moving the files seems to have solved the problems (the node is now 2h 36 min without restars) but can’t be sure tillsome days have passed. the weird thing about this is that I have 2 nodes runing on the same raspberry,and only 1 of them have h…

yeah 1.16.1 with watchtower working My apologies, I was wrong, the source path is the same, I was confused because the panic doesn’t come from the make function and I thought that it was when I investigated the case in the other post and I didn’t compare both log files line by line. On the other…

One of my nodes are starting to fail

Node Operators troubleshooting

nerdatwork November 26, 2020, 5:38am 7