Unusable node after suspend

[MariusVanDerWijden]

I recently spent some time working on a little golang client to send and receive payments using Raiden during ethonline. @czepluch asked me to share some feedback here. I'll open seperate issues for them.

Suspending my machine produced the following exception and left the node in an unusable state. I think it should be possible to resume operation after un-suspending or otherwise it would be best if the node right out died. Leaving the node in an unusable state and neither recovering or fully shutting it down is pretty bad, especially if a user started the raiden node as a deamon.

requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='goerli.infura.io', port=443): Read timed out. (read timeout=10)
FATAL: An unexpected exception occurred. A traceback has been written to /tmp/raiden-exception-2020-10-11T19-27xcv5yb2q.txt
HTTPSConnectionPool(host='goerli.infura.io', port=443): Read timed out. (read timeout=10)
ReturnCode.FATAL