all cloudron apps not responding after reboot, most services down
-
I'm not sure what happened but after a reboot most of the services on my cloudron won't come up. Cloudron and Docket start fine but almost everything else has a red dot and all my apps show not responding:

I don't see anything incriminating in the logs but I'm happy to provide SSH access too, I'm baffled.
-
I'm not sure what happened but after a reboot most of the services on my cloudron won't come up. Cloudron and Docket start fine but almost everything else has a red dot and all my apps show not responding:

I don't see anything incriminating in the logs but I'm happy to provide SSH access too, I'm baffled.
-
@ianhyzy Could it be you are out of disk space (which is why logs are not showing up) ? If not, can you drop us a mail with ssh access?
-
It seems there is some strange docker issue.
# docker stop ceaf8163e71c Error response from daemon: cannot stop container: ceaf8163e71c: Cannot kill container ceaf8163e71c917ad9adf35a5308bed33f35135667a35f8d8fc9f3f3e83f9003: unknown error after kill: runc did not terminate sucessfully: container_linux.go:392: signaling init process caused "permission denied" : unknown -
@ianhyzy oh it seems you installed docker via snap. See also https://stackoverflow.com/questions/50482315/docker-compose-down-fails-due-to-permission-denied/51734756#51734756
root 970 0.3 0.5 1418616 96156 ? Ssl 04:00 0:09 dockerd --group docker --exec-root=/run/snap.docker --data-root=/var/snap/docker/common/var-lib-docker --pidfile=/run/snap.docker/docker.pid --config-file=/var/snap/docker/796/config/daemon.json root 2910 0.7 0.2 1207328 47688 ? Ssl 04:00 0:23 containerd --config /run/snap.docker/containerd/containerd.toml --log-level error root 5874 0.0 0.0 108728 7088 ? Sl 04:00 0:00 containerd-shim -namespace moby -workdir /var/snap/docker/common/var-lib-docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/ceaf8163e71c917ad9adf35a5308bed33f35135667a35f8d8fc9f3f3e83f9003 -address /run/snap.docker/containerd/containerd.sock -containerd-binary /snap/docker/796/bin/containerd -runtime-root /run/snap.docker/runtime-runc -
@ianhyzy oh it seems you installed docker via snap. See also https://stackoverflow.com/questions/50482315/docker-compose-down-fails-due-to-permission-denied/51734756#51734756
root 970 0.3 0.5 1418616 96156 ? Ssl 04:00 0:09 dockerd --group docker --exec-root=/run/snap.docker --data-root=/var/snap/docker/common/var-lib-docker --pidfile=/run/snap.docker/docker.pid --config-file=/var/snap/docker/796/config/daemon.json root 2910 0.7 0.2 1207328 47688 ? Ssl 04:00 0:23 containerd --config /run/snap.docker/containerd/containerd.toml --log-level error root 5874 0.0 0.0 108728 7088 ? Sl 04:00 0:00 containerd-shim -namespace moby -workdir /var/snap/docker/common/var-lib-docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/ceaf8163e71c917ad9adf35a5308bed33f35135667a35f8d8fc9f3f3e83f9003 -address /run/snap.docker/containerd/containerd.sock -containerd-binary /snap/docker/796/bin/containerd -runtime-root /run/snap.docker/runtime-runc -
@girish I realized my mistake - I installed docker when it asked on setup. I'm re-installing now and not doing, my mistake. Thanks for the help!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login