Error response from daemon: driver failed programming external connectivity on endpoint storage node

[Screechingcrow]

Hey All,
I received the message, upon a quick restart of my PC, when trying to start my node, “Error response from daemon: driver failed programming external connectivity on endpoint storage node … : Error starting userland proxy … failed to start containers: storagenode”.

I looked at my log and the last two thing I saw were “ERROR piecestore protocol: rpc error: code = canceled desc = context canceled.”

Got a signal from the OS: terminated

I guess this means that my node was terminated? Since I don’t have much statistics I can’t troubleshoot/optimize the situation. It would be nice to be able to improve things on my end rather than be disqualified.
Cheers!
Kind Regards,
Adam

[donald.m.motsinger]

The “context canceled” is not really an error

Error Codes: What they mean and Severity Level [READ FIRST]

Hey all! I wanted to take the opportunity to compile a list of error codes, what they mean, and if you need to worry about the error. I will be updating this as I am able to get information, but wanted to create a central place that people can check. Find the error you are looking for in the list and click the Summary section below it. This will open up with a description of what the error means and its severity. 11/30/2020-A quick note since I have discovered threads that reference errors in t…

The …terminated" is most likely from when you stopped the node and rebooted.

Stop and remove the container

docker stop -t 300 storagenode
docker rm storagenode

and run the complete start command docker run ...

[BrightSilence]

Restart docker from the task tray. That should fix this issue.

[Screechingcrow]

Thank you BrightSilence. This worked. However, now since my node has been offline for 10 hours I’m pretty sure i’ll be disqualified! Ow well.

[BrightSilence]

You won’t be. Right now disqualification for downtime is suspended, so your node should be just fine.