All my storagenodes are crashing because of updater. I have 8 storagenodes on my server - 1 for each hard drive. After updating to latest docker image (30 min ago), 7 out of 8 docker containers are crashing with following message: Error: Another program is already listening on a port that one of ou…

[storagenode] The multiple nodes with `--network host` after upgrade to 1.50.4 cannot work anymore opened 08:01AM - 25 Mar 22 UTC (UTC) [AlexeyALeonov] AlexeyALeonov …

i got 2 nodes running on the same proxmox container with docker inside, which both are updated to storagenode v1.50.4 they work fine… initially when i first installed the new version it exited because the updater wasn’t downloaded or something like that, but after a bit, it simply went away and ha…

Thanks for the suggestions. I reverted to image with ID f1a22a725dd5 and disabled auto update of my docker nodes. Once the github issue is fixed, I will switch to latest tag again.

It’s happen only if you use --network host, because all containers are listening on the host network, and thus must have an unique port. The supervisor is started on fixed port. This is the essential of the bug. You need either listen on random free port, or allow to configure the listening port or …

Any update when this will be fixed? I see there have been two more releases since the issue was introduced but github issue is still open. Right now I cannot update any of my servers because of this.

You can track this issue: [storagenode] The multiple nodes with `--network host` after upgrade to 1.50.4 cannot work anymore · Issue #4661 · storj/storj · GitHub At the moment I can suggest to remove the --network host and use port mapping, this resolves an issue. The other solution is to migrate …

I have 25 nodes over 5 servers and unfortunately I cannot do either of them due to complexity and time involved. Changing docker to not use host networking requires me to manually map all the ports used. It is already non-trivial to run the nodes and payout does not make it worth to keep spending t…

Yes, the non-standard configurations was not tested. In our documentation the docker nodes configured with port mapping. I would kindly ask you to update your docker run commands with port mappings instead of using of --network host. I’m running not so much nodes, but I used the docker-compose.yam…

you could just drop the –network host parameter, i don’t really see the point in using that, i only use one nic on my server for the lan and it has like 15 different vm’s with each their own ip addresses, even some of the nodes share containers which is single ip… so they all run on different port…

Storj Community Forum (official)

All docker nodes (except one) crashing because of updater

Node Operators