Storagenode could not start because it is marked as removal container

Node Operators troubleshooting
1

This is the Error i get when i Type in “docker start storagenode”:
Error response from daemon: container is marked for removal and cannot be started
Error: failed to start containers: storagenode

You must know that the Node runs more than 3 Month in a row and no error etc. happend.
Watchover (or Auto-Update) - Image is also enabled.

My DynDns is Up-to-date and Ports are also opend

I gave the Storagenode 3TB of storage on my NAS.
Please help me because i dont know what happend i did nothing i only noticted because one day i could not enter the Webinterface on Port 14002 and also could not open the Dashboard via Command “docker exec -it storagenode /app/dashboard.sh”

2

Can you show last 20 lines of the log?

3

How? I can not access anything on or to storagenode because it dont shows up when i type docker ps or somthing like that it only shows another container with a random name and nothing running on

4

Error response from daemon: can not get logs from container which is dead or marked for removal

In addition this (above) is the error if i try to get the logs

5

Now i tried to catch the logs of the “unnamed” and “random” container:

time=“2020-01-30T23:01:25Z” level=info msg=“Stopping /storagenode (a45ada8878c08021022961c96c5c68f73e58aa0f2b54d47b8a95f8f0d8d46806) with SIGTERM”
time=“2020-01-30T23:01:33Z” level=info msg=“Creating /storagenode”
time=“2020-02-19T17:01:36Z” level=info msg=“Found new storjlabs/storagenode:beta image (sha256:927cebfc3923c4e34f95a79530d5806d8246eadf2fef59f09d10c735a5c183c5)”
time=“2020-02-19T17:01:43Z” level=info msg=“Found new storjlabs/watchtower:latest image (sha256:6af6621e20c1aeba8c90eb20bd439609d1a4c3d350815292c4ac8fba8202af5a)”
time=“2020-02-19T17:01:43Z” level=info msg=“Stopping /storagenode (171f54a62d8a968a97658b737dd87433a2765ab7119450dda72d9ec39b95c4bd) with SIGTERM”
time=“2020-02-19T17:03:18Z” level=info msg=“Creating /storagenode”
time=“2020-02-19T17:03:27Z” level=info msg=“Creating /watchtower”
time=“2020-03-10T23:01:30Z” level=info msg=“Found new storjlabs/storagenode:beta image (sha256:a409accd7f0c9a1320c6ef28a1ba0fe2db026eb535ffacf8c87c3a20ba93ed3c)”
time=“2020-03-10T23:01:30Z” level=info msg=“Stopping /storagenode (f1fad8772c3624ca6130f1de9e5433e01f4fb3af416d2a4f8b9db30d09502834) with SIGTERM”
time=“2020-03-10T23:01:51Z” level=info msg=“Creating /storagenode”
time=“2020-03-15T10:55:19Z” level=info msg=“Waiting for running update to be finished…”
time=“2020-03-15T12:04:31Z” level=info msg=“Waiting for running update to be finished…”
time=“2020-03-15T14:21:47Z” level=info msg=“Waiting for running update to be finished…”
time=“2020-03-15T16:57:33Z” level=info msg=“Waiting for running update to be finished…”
time=“2020-03-27T12:53:38Z” level=info msg=“Waiting for running update to be finished…”
time=“2020-03-27T19:04:48Z” level=info msg=“Found new storjlabs/storagenode:beta image (sha256:154eebec441e681262ab11c44f6f3bde09efca08a149a2e16e0d131e9c2e6895)”
time=“2020-03-27T19:04:50Z” level=info msg=“Stopping /storagenode (a572971c1cec4b2bec2902737108bd1746d14d77f7bdcfafd2bd05eebf8dedba) with SIGTERM”
time=“2020-03-28T19:42:51Z” level=info msg=“Waiting for running update to be finished…”
time=“2020-03-28T22:16:19Z” level=info msg=“Waiting for running update to be finished…”
time=“2020-03-28T22:36:35Z” level=info msg=“Waiting for running update to be finished…”

Thats the last twenty lines so i think the old “storagenode” container is markt as removeal and the “random” container is the new storagenode container but update failed for some reason?
So how do i fix that?

6

So i fixed it by myself by removeing the old “storagenode” with docker rm storagenode and also removed the “random” container with docker rm [container_id]

After that i runed my old “docker create”-Command and taaaddaa everything worked just fine.
But now i see that this error is since 3 days and so i do not have any Traffic or Disk Space Usage for this 3 days