Node V1.3.3 - Offline: ERROR nodestats:cache Get pricing-model/join date failed

Updated to v1.3.3 via window GUI wizard, dashboard showing node offline, Windows service running and node running in dashboard, uptime increasing, logs show error below,
held amount can be seen in the dashboard

Any help would be much appreciated, thank you

2020-04-24T22:26:29.422+0100 INFO Public server started on [::]:28967
2020-04-24T22:26:29.422+0100 INFO Private server started on 127.0.0.1:7778
2020-04-24T22:26:33.307+0100 ERROR nodestats:cache Get pricing-model/join date failed {“error”: “heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetAllPaystubs”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetAllPaystubs””, “errorVerbose”: “group:\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetAllPaystubs”\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/GetAllPaystubs”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313”}

Thanks for reporting the issue. We are slowly rolling out the v1.3.3 storage node release to operators. The slow release is done intentionally to catch unexpected issues just like this one. The team has been notified and I’ll keep you posted as we find out more.

1 Like

It appears we have a satellite out there that hasn’t been updated yet. The error happens because the storage node tries to reach out to an endpoint this satellite doesn’t know about yet. The error isn’t fatal and shouldn’t cause any harm (other than being noisy in the logs).

We are updating the offending satellite tomorrow. Once the satellite is updated you shouldn’t see this error in the logs anymore. Will touch base again tomorrow.

That error has nothing to do with your offline status. My node is printing that in the logs as well but is running fine on v1.3.3

Thanks for the feedback, but all I seem to be getting in the logs is usage rollups, any ideas on why the node is offline, no other errors in the node startup log?

2020-04-24T22:26:33.307+0100 ERROR nodestats:cache Get pricing-model/join date failed {“error”: “heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetAllPaystubs”; heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetAllPaystubs””, “errorVerbose”: “group:\n— heldamount service error: protocol error: unknown rpc: “/heldamount.HeldAmount/GetAllPaystubs”\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/GetAllPaystubs”\n\tstorj.io/drpc/drpcwire.UnmarshalError:26\n\tstorj.io/drpc/drpcstream.(*Stream).HandlePacket:156\n\tstorj.io/drpc/drpcmanager.(*Manager).manageStreamPackets:313”}
2020-04-24T23:26:29.422+0100 INFO bandwidth Performing bandwidth usage rollups
2020-04-25T00:26:29.422+0100 INFO bandwidth Performing bandwidth usage rollups
2020-04-25T01:21:23.782+0100 INFO trust Scheduling next refresh {“after”: “4h31m33.144994404s”}
2020-04-25T01:26:29.422+0100 INFO bandwidth Performing bandwidth usage rollups

Just the usual stuff like for example a wrong port forwarding.

Port forwarding issue, few network changes here, thanks for the support.

2 Likes