Step 1: Am I affected? If you see something like this in your logfile you should worry. orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S sending {"count": 1582} orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW sending {"count": 7666} orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz…

How do you check for still not settled orders?

Restart your node and look at the logs. It should send unsettled orders right away.

Thanks, but it’s sometimes very hard to find the right lines in the log. grep -E "sending|finished" /mnt/storagenode/node/node.log is what I was looking for.

The lines for order sending happen right after the restart. I usually use tail to follow what’s happening. In your case. tail -f /mnt/storagenode/node/node.log

I know the tail command. The problem is, that the “finished” doesn’t always come immediately after the “sending”. With all the other logs in-between it’s easy to miss these messages. For this the output of grep is much easier to read.

What do you get when you grep for "order_expiration" ?

With v0.19.7 we also increase the dial timeout (v0.19.6 was the request timeout only) and we reduce the batch size on the satellite side to stop the deadlock errors.

[image] littleskunk: What do you get when you grep for "order_expiration" ? 2019-09-03T09:41:30.719Z ERROR orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW gRPC client when sending new orders settlements {"error": "order: sending settlement agreements returned an error: EOF", "errorV…

Looks like a good reason to panic. Meanwhile you submitted all orders?

Yes, the amount of lines containing “sending” is followed by the same amount of “finished” lines.

Storj Community Forum (official)

Workaround for order sender errors (execute this before they expire)

Node Operators