Node disqualified on all satellites right after suspension email

Hi,

Node : 12Rn4LsxqgmjyxJzwCQGuZVwG4TzbuRhUD54gXtDtDxDPDQzH5f
Yesterday, i received emails saying my node is suspended on all satellites, checked my node.

I read the whole topic, but did not see a solution to this problem. what to do? maybe this is due to the fact that almost all of the specified space is occupied? out of 7 Tb, 120 Gb remained free and problems started.

If the node is suspended and you have checked the node and its online just Keep it online.

Find out from your log what went wrong. Check for download failed and GET_AUDIT errors in the log. You have to start from scratch since you are disqualified from all satellites

I looked at the last log, there is no such error.
After updating to the latest version of the docker, at times I began to receive such a message, maybe the reason is this?
storj message

This error can be result of other errors in your logs.
Please, check your log

docker logs --tail 20 storagenode

Please, try to figure out, why your node lost data (or access to it) to do not repeat this error again with a new node.

C:\Users\Peter>docker logs --tail 20 storagenode
2020-05-17T05:36:04.083Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-05-17T05:36:05.204Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-05-17T05:36:05.204Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T05:36:05.204Z INFO Node 12Rn4LsxqgmjyxJzwCQGuZVwG4TzbuRhUD54gXtDtDxDPDQzH5f started
2020-05-17T05:36:05.204Z INFO Public server started on [::]:28967
2020-05-17T05:36:05.204Z INFO Private server started on 127.0.0.1:7778
2020-05-17T05:36:05.204Z INFO trust Scheduling next refresh {“after”: “4h35m6.742056386s”}
2020-05-17T05:36:05.210Z WARN piecestore:monitor Used more space than allocated. Allocating space {“bytes”: 7000000000000}
2020-05-17T05:40:00.825Z ERROR nodestats:cache Get held amount query failed {“error”: “heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment””, “errorVerbose”: “group:\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313”}
2020-05-17T06:36:05.205Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T07:36:05.205Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T08:36:05.205Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T09:36:05.205Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T10:11:13.517Z INFO trust Scheduling next refresh {“after”: “3h13m17.524903606s”}
2020-05-17T10:36:05.204Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T11:36:05.205Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T12:36:05.204Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T13:24:32.419Z INFO trust Scheduling next refresh {“after”: “4h12m20.916027222s”}
2020-05-17T13:36:05.204Z INFO bandwidth Performing bandwidth usage rollups
2020-05-17T14:36:05.204Z INFO bandwidth Performing bandwidth usage rollups

There is no errors anymore… Every time when you re-create the container, your old logs are gone.
Do you know the reason of losing data?
Have you tried to migrate node from the one device/location to the other?
Is it an external disk?

the node did not tolerate. The disk is not portable. touched nothing. just updated docker and that’s it. last log for May 9th, the node always shows online

The only way to be disqualified on any satellite is failing too much audits.
To fail audit your node should be online and responding on audit requests and did not provide the requested piece three times. If it fail too many audits and audit score is fall below the 0.6 (60% on current dashboard) the node will be disqualified.
So, your data is lost or inaccessible to the node for some reason.
Can you show your docker run command (you can remove the personal info)?

docker run -d --restart unless-stopped -p 28967:28967 -p 127.0.0.1:14002:14002 -e WALLET="" -e EMAIL="" -e ADDRESS=“storj.mykeenetic.com:28967” -e BANDWIDTH=“20TB” -e STORAGE=“7TB” --mount type=bind,source=“c:\Users\Peter\AppData\Roaming\Storj\Identity\storagenode”,destination=/app/identity --mount type=bind,source=“f:\DATA”,destination=/app/config --name storagenode storjlabs/storagenode:beta

what is wrong with my node, have any ideas?

Make sure you are not using curly quotes in your docker command.Use notepad++ to edit command.

startup commands are saved in notepad, I did not change them for several months. everything worked fine, there is no error.

Please, check your disk for errors and take attention to the report - Is there any problem with the disk?

Has the disk worked 73 hours?
And up to 2.56TB bandwidth in May?

Did you check it with scandisk (system tool)?

file system checked, no problem

C:\Users\Peter>docker logs --tail 20 storagenode
2020-05-19T00:50:04.419Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-05-19T00:50:04.421Z INFO tracing disabled
2020-05-19T00:50:04.435Z INFO Operator email {“Address”: “------------@gmail.com”}
2020-05-19T00:50:04.435Z INFO Operator wallet {“Address”: “------------552b62D7b8D”}
2020-05-19T00:50:05.926Z INFO db.migration Database Version {“version”: 36}
2020-05-19T00:50:07.271Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-05-19T00:50:08.417Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-05-19T00:50:08.417Z INFO bandwidth Performing bandwidth usage rollups
2020-05-19T00:50:08.417Z INFO Node 12Rn4LsxqgmjyxJzwCQGuZVwG4TzbuRhUD54gXtDtDxDPDQzH5f started
2020-05-19T00:50:08.417Z INFO Public server started on [::]:28967
2020-05-19T00:50:08.417Z INFO Private server started on 127.0.0.1:7778
2020-05-19T00:50:08.417Z INFO trust Scheduling next refresh {“after”: “4h37m5.361290773s”}
2020-05-19T00:52:33.388Z ERROR nodestats:cache Get held amount query failed {“error”: “heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment””, “errorVerbose”: "group:\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetPayment”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313\n— heldamount service error: protocol error: unknown rpc: "/heldamount.HeldAmount/GetPayme