Rockon service wont load

1

HI all.

Hope this is something with a quick fix, as I dont have the time here before Christmas for deep troubleshooting :slight_smile:

Yesterday we had a few power outages, and as a result the Rock on service wont load. And therefore Plex (which is the only Rockon I use) doesnt work…

I dont get much in the way off error messages.

When trying to start the Rock-On service i get this.

image
image808×533 13.8 KB

And each time I try to start the service I get this in dmesg output:

audit: type=1400 audit(1766218373.747:10): apparmor=“STATUS” operation=“profile_replace” info=“same as current profile, skipping” profile=“unconfined” name=“docker-default” pid=6839 comm=“apparmor_parser”

What could be wrong, and is there an easy way to get the rockon service up and running again?

I guess some config file has been corrupted or has gone missing.

A scrub of the system drive gave no errors.

2

Hi @KarstenV !

My first thought is to check the docker service…

systemctl status docker.service

… and look for errors at relevant timestamps:

journalctl -xeu docker.service

What I usually do is having 2 SSH sessions:

  • one monitoring the service: journalctl -f -u docker.service
  • the other starting the service: systemctl start docker.service

You should see a bit more about what is happening that way.

Hope that helps,

1 Like
3

Hi Flox.

Thanks for trying to help.

I ran the commands.

systemctl status docker.service:

× docker.service - Docker Application Container Engine

Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2025-12-20 18:32:28 CET; 6min ago
TriggeredBy: × docker.socket
Docs: http://docs.docker.com
Process: 30210 ExecStart=/usr/bin/dockerd --add-runtime oci=/usr/sbin/docker-runc $DOCKER_NETWORK_OPTIONS $DOCKER_OPTS --config-file /opt/rockstor/conf/docker-daemon.json (code=exited, status=1/FAILURE)
Main PID: 30210 (code=exited, status=1/FAILURE)

Dec 20 18:32:28 RockstorNAS systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Dec 20 18:32:28 RockstorNAS systemd[1]: Stopped Docker Application Container Engine.
Dec 20 18:32:28 RockstorNAS systemd[1]: docker.service: Start request repeated too quickly.
Dec 20 18:32:28 RockstorNAS systemd[1]: docker.service: Failed with result ‘exit-code’.
Dec 20 18:32:28 RockstorNAS systemd[1]: Failed to start Docker Application Container Engine.
Dec 20 18:32:49 RockstorNAS systemd[1]: docker.service: Start request repeated too quickly.
Dec 20 18:32:49 RockstorNAS systemd[1]: docker.service: Failed with result ‘exit-code’.
Dec 20 18:32:49 RockstorNAS systemd[1]: Failed to start Docker Application Container Engine.

journalctl -xeu docker.service:

Dec 20 18:32:28 RockstorNAS systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 9924 and the job result is failed.

journalctl -f -u docker.service, gave this output (While running “systemctl start docker.service"):

Dec 20 18:32:24 RockstorNAS systemd[1]: Starting Docker Application Container Engine…
Dec 20 18:32:24 RockstorNAS dockerd[30022]: time=“2025-12-20T18:32:24+01:00” level=info msg=“SUSE:secrets :: enabled”
Dec 20 18:32:24 RockstorNAS dockerd[30037]: time=“2025-12-20T18:32:24.939294647+01:00” level=warning msg=“failed to load plugin io.containerd.snapshotter.v1.devmapper” error=“devmapper not configured”
Dec 20 18:32:24 RockstorNAS dockerd[30037]: time=“2025-12-20T18:32:24.939846817+01:00” level=warning msg=“could not use snapshotter devmapper in metadata plugin” error=“devmapper not configured”
Dec 20 18:32:25 RockstorNAS dockerd[30022]: failed to start daemon: Devices cgroup isn’t mounted
Dec 20 18:32:25 RockstorNAS systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Dec 20 18:32:25 RockstorNAS systemd[1]: docker.service: Failed with result ‘exit-code’.
Dec 20 18:32:25 RockstorNAS systemd[1]: Failed to start Docker Application Container Engine.
Dec 20 18:32:26 RockstorNAS systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Dec 20 18:32:26 RockstorNAS systemd[1]: Stopped Docker Application Container Engine.

It tries 3 times, but the output is the same.

Sadly I’m none the wiser with these outputs :slight_smile:

4

@KarstenV I assume, a normal shutdown/clean reboot did not fix it either.

You are on Rockstor version 5.x right?

can you check whether your Rock-on Root is still correctly mounted/specified in the Rock-on configration?

Finally, since it complains about the cgroup not mounted, can you check whether that’s truly the case (I think it’s a follow-on error due to something else, but still):

mount | grep cgroup

I would expect an output like this:

cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)

systemctl restart network and starting the docker service doesn’t work either? I’ve had the case in the past where a network interface issue prevented the service from starting (though I never figured out what the root cause was for that).

Incidentally I had a power outage today … and while my box comes back on automatically, it usually requires me to restart it manually again to have everything back in working order, but that might just be my system’s personality disorder :slight_smile:

2 Likes
5

Rockstor version is 5.0.15-0

The Rock-on root is still shown in the configuration, and I believe it is mounted. Showing in the shares overview anyway.

“Mount | grep cgroup” gives this:

tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/dmem type cgroup (rw,nosuid,nodev,noexec,relatime,dmem)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
RockstorNAS:~ #

”systemctl restart network” didn’t seem to do anything. “systemctl start docker.service” gives this:

Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xeu docker.service” for details.

”systemctl status docker.service” comes out with no info, and “journalctl -xeu docker.service” comes up with this:

Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 15828 and the job result is failed.
Dec 21 04:46:15 RockstorNAS systemd[1]: docker.service: Scheduled restart job, restart count>
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 21 04:46:15 RockstorNAS systemd[1]: Stopped Docker Application Container Engine.
░░ Subject: A stop job for unit docker.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit docker.service has finished.
░░
░░ The job identifier is 15947 and the job result is done.
Dec 21 04:46:15 RockstorNAS systemd[1]: Starting Docker Application Container Engine…
░░ Subject: A start job for unit docker.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has begun execution.
░░
░░ The job identifier is 15947.
Dec 21 04:46:15 RockstorNAS dockerd[32531]: time=“2025-12-21T04:46:15+01:00” level=info msg=>
Dec 21 04:46:15 RockstorNAS dockerd[32552]: time=“2025-12-21T04:46:15.285028036+01:00” level>
Dec 21 04:46:15 RockstorNAS dockerd[32552]: time=“2025-12-21T04:46:15.285653053+01:00” level>
Dec 21 04:46:16 RockstorNAS dockerd[32531]: failed to start daemon: Devices cgroup isn’t mou>
Dec 21 04:46:16 RockstorNAS systemd[1]: docker.service: Main process exited, code=exited, st>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit docker.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 1.
Dec 21 04:46:16 RockstorNAS systemd[1]: docker.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit docker.service has entered the ‘failed’ state with result ‘exit-code’.
Dec 21 04:46:16 RockstorNAS systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 15947 and the job result is failed.
Dec 21 04:46:16 RockstorNAS systemd[1]: docker.service: Scheduled restart job, restart count>
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 21 04:46:16 RockstorNAS systemd[1]: Stopped Docker Application Container Engine.
░░ Subject: A stop job for unit docker.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit docker.service has finished.
░░
░░ The job identifier is 16066 and the job result is done.
Dec 21 04:46:16 RockstorNAS systemd[1]: docker.service: Start request repeated too quickly.
Dec 21 04:46:16 RockstorNAS systemd[1]: docker.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit docker.service has entered the ‘failed’ state with result ‘exit-code’.
Dec 21 04:46:16 RockstorNAS systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 16066 and the job result is failed.

I have restartet the system several times with no results.

In other respects the system works fine, I can access the shares without porblems, there are no problems reported in the UI, besides Rock-On not being started and refusing to do so.

This system has recovered some times before from outages without incidents, so its weird that it went wrong this time.

It does not seem like something easy to fix.

Perhaps its time for a reinstall.

That’ll have to wait till after christmas.

6

see whether you can use a configuration backup to makes this less painful and have your services and plex Rock-on automatically re-installed.

2 Likes
7

I’ll definitely try that.

Let’s see how this goes — it’s been a few years since I last installed Rockstor.

Which, in a sense, is a testament to how reliable it has been.

4 Likes
8

I have now made a reinstall. That went very smoothly, about 10 minutes, then I had it isntalled and updated.

The auto import function worked well enough, it restored my scheduled tasks, but Plex wouldn’t reinstall.

I fixed that myself and Plex is now running again.

I have had a few problems though.

I have tried to change the IP adress to a static one, but that is not going well.

I edit the setting to the ones I used before, and get this:

CUT
Traceback (most recent call last):
File “/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py”, line 40, in _handle_exception
yield
File “/opt/rockstor/src/rockstor/storageadmin/views/network.py”, line 449, in put
device = nco.networkdevice_set.first().name
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: ‘NoneType’ object has no attribute ‘name’

CUT END

So that doesn’t work, and I cant find what I’m doing wrong.

I have to have this changed.

I cant get SSH working either, I get this error when trying to connect:

“Couldn’t agree a host key algorith” (and a key is then shown as available).

What could be wrong here?

9

@KarstenV glad to see that the reinstall worked at least somewhat. I am surprised that Plex did not re-install, though good that you were able to do this yourself again. Did you see any specific errors why that failed in the rockstor log?

As for the other items:

check out this discussion thread:

The mentioned issue in that thread is still open, as it’s still not entirely clear why it happens (my attempts at reproducing it were only marginally successful then). So I think your best bet is to use the nmcli or nmtui to set a static address, if you can’t/don’t want to force it via static IP address on the dhcp router.

As for the ssh issue. I have not ecountered that before, are you using PuTTY (and if so, SSH Protocol version 2 setting, found under the SSH section) to connect or some other ssh client?
It seems that older versions of PuTTY can run into that issue related to which HostKeyAlgorithms are allowed/used.

2 Likes
10

I didn’t see any errors, but I’m relatively certain it was due to some shares not being available. Some of the original Plex specific shares recided on my boot drive, and that was wiped when i reinstalled.

I just used the normal setup routine, I find it easy enough, took me perhaps 10 minutes.

Putty was due to an old version. Downloading the latest fixed it.

I setup network via nmtui, seemed straight forward enough, and worked in first try.

And shows the correct data in rockstor to :slight_smile:

I have a few other specific settings I need to fix, but its working as expected now :slight_smile:

3 Likes