Hi brand new user here so apologies if I have totally misunderstood something.
I was attracted to Rockstor because of the potential benefits of btrfs and the comprehensive feature set. One thing I liked was the Rock-Ons in particular lyrionmediaserver which I use a lot.
Lyrionmediaserver installed and ran perfectly until I came to reboot and found that the Rock-On service did not start after a boot. Later I realised that the bootstrap service also showed as disabled in the UI, and if I started it manually through the UI it would turn off again after a few seconds, I am guessing that bootstrap is responsible for starting the Rock-on service.
Here is the relevant part of the log during boot. During this boot I started the Rock-On service manually.
Apr 25 22:28:08 nas systemd[1]: rockstor-bootstrap.service: Consumed 37.924s CPU time.
Apr 25 22:28:08 nas systemd[1]: Failed to start Rockstor bootstrapping tasks.
Apr 25 22:28:08 nas systemd[1]: rockstor-bootstrap.service: Failed with result 'exit-code'.
Apr 25 22:28:08 nas systemd[1]: rockstor-bootstrap.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 22:28:08 nas poetry[16162]: Max attempts(10) reached. Connection errors persist. Failed to bootstrap. Error: Exception while setting acc>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:28:08 nas poetry[16162]: Oauth internal App client_secret updated.
Apr 25 22:28:08 nas poetry[16162]: Refreshing client_secret for oauth2_provider app from settings
Apr 25 22:28:08 nas poetry[16162]: BTRFS device scan complete
Apr 25 22:28:05 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:28:03 nas systemd[1]: Configuration file /etc/systemd/system/smb.service is marked world-inaccessible. This has no effect as configur>
Apr 25 22:27:55 nas systemd[1]: Reloading finished in 1414 ms.
Apr 25 22:27:55 nas systemd[1]: Configuration file /etc/systemd/system/smb.service is marked world-inaccessible. This has no effect as configur>
Apr 25 22:27:54 nas systemd[1]: Reloading...
Apr 25 22:27:54 nas systemd[1]: Reloading requested from client PID 16396 ('systemctl') (unit rockstor.service)...
Apr 25 22:27:46 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:27:28 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:27:09 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:26:51 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:26:37 nas systemd[1]: snapperd.service: Deactivated successfully.
Apr 25 22:26:32 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:26:30 nas systemd[1]: Configuration file /etc/systemd/system/smb.service is marked world-inaccessible. This has no effect as configur>
Apr 25 22:26:20 nas systemd[1]: Starting Rockstor bootstrapping tasks...
Apr 25 22:26:20 nas systemd[1]: Reloading finished in 1393 ms.
Apr 25 22:26:19 nas systemd[1]: Configuration file /etc/systemd/system/smb.service is marked world-inaccessible. This has no effect as configur>
Apr 25 22:26:18 nas systemd[1]: Reloading...
Apr 25 22:26:18 nas systemd[1]: Reloading requested from client PID 16127 ('systemctl') (unit rockstor.service)...
Apr 25 22:26:14 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:25:55 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:25:37 nas systemd[1]: snapper-cleanup.service: Deactivated successfully.
Apr 25 22:25:37 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:25:37 nas systemd-helper[16003]: running empty-pre-post cleanup for 'root'.
Apr 25 22:25:37 nas systemd-helper[16003]: running timeline cleanup for 'root'.
Apr 25 22:25:37 nas systemd-helper[16003]: running number cleanup for 'root'.
Apr 25 22:25:37 nas systemd-helper[16003]: running cleanup for 'root'.
Apr 25 22:25:37 nas systemd[1]: Started DBus interface for snapper.
Apr 25 22:25:37 nas dbus-daemon[623]: [system] Successfully activated service 'org.opensuse.Snapper'
Apr 25 22:25:37 nas systemd[1]: Starting DBus interface for snapper...
Apr 25 22:25:37 nas dbus-daemon[623]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by>
Apr 25 22:25:37 nas systemd[1]: Started Daily Cleanup of Snapper Snapshots.
Apr 25 22:25:34 nas kernel: perf: interrupt took too long (4982 > 4981), lowering kernel.perf_event_max_sample_rate to 40000
Apr 25 22:25:18 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:25:00 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:24:42 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:24:23 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:24:05 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:23:46 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:23:28 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:23:10 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:23:06 nas systemd[1]: ;;file://nas/usr/lib/systemd/system/nut-monitor.service/usr/lib/systemd/system/nut-monitor.service;;:7: PIDFile=
references a path below legacy directory /var/run/, upd;;>
Apr 25 22:23:04 nas systemd[1]: Configuration file /etc/systemd/system/smb.service is marked world-inaccessible. This has no effect as configur>
Apr 25 22:20:46 nas kernel: BTRFS info (device sda): using free space tree
Apr 25 22:20:46 nas kernel: BTRFS info (device sda): use no compression
Apr 25 22:20:46 nas kernel: BTRFS info (device sda): using crc32c (crc32c-generic) checksum algorithm
Apr 25 22:20:37 nas systemd[1]: Startup finished in 4.640s (kernel) + 16.508s (initrd) + 4min 40.623s (userspace) = 5min 1.772s.
Apr 25 22:20:37 nas systemd[1]: Finished Record Runlevel Change in UTMP.
Apr 25 22:20:37 nas systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Apr 25 22:20:37 nas systemd[1]: Starting Record Runlevel Change in UTMP...
Apr 25 22:20:37 nas systemd[1]: Reached target Multi-User System.
Apr 25 22:20:37 nas systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
Apr 25 22:20:37 nas systemd[1]: Failed to start Docker Application Container Engine.
Apr 25 22:20:37 nas systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 25 22:20:37 nas systemd[1]: docker.service: Start request repeated too quickly.
Apr 25 22:20:37 nas systemd[1]: Listening on Docker Socket for the API.
Apr 25 22:20:37 nas systemd[1]: Starting Docker Socket for the API...
Apr 25 22:20:37 nas systemd[1]: Stopping Docker Socket for the API...
Apr 25 22:20:37 nas systemd[1]: Closed Docker Socket for the API.
Apr 25 22:20:37 nas systemd[1]: docker.socket: Deactivated successfully.
Apr 25 22:20:37 nas systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 25 22:20:37 nas systemd[1]: Failed to start Docker Application Container Engine.
Apr 25 22:20:37 nas systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 25 22:20:37 nas systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 22:20:37 nas dockerd[15180]: chmod /mnt2/Rockon: operation not permitted
Apr 25 22:20:37 nas dockerd[15180]: time="2025-04-25T22:20:37+01:00" level=info msg="SUSE:secrets :: SUSEConnect support enabled (set /etc/dock>
Apr 25 22:20:37 nas systemd[1]: Starting Docker Application Container Engine...
Apr 25 22:20:37 nas systemd[1]: Listening on Docker Socket for the API.
Apr 25 22:20:37 nas systemd[1]: Starting Docker Socket for the API...
Apr 25 22:20:36 nas systemd[1]: Stopping Docker Socket for the API...
Apr 25 22:20:36 nas systemd[1]: Closed Docker Socket for the API.
Apr 25 22:20:36 nas systemd[1]: docker.socket: Deactivated successfully.
Apr 25 22:20:36 nas systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Apr 25 22:20:36 nas systemd[1]: Failed to start Docker Application Container Engine.
Apr 25 22:20:36 nas systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 25 22:20:36 nas systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 22:20:36 nas dockerd[15170]: chmod /mnt2/Rockon: operation not permitted
Apr 25 22:20:36 nas dockerd[15170]: time="2025-04-25T22:20:36+01:00" level=info msg="SUSE:secrets :: SUSEConnect support enabled (set /etc/dock>
Apr 25 22:20:36 nas systemd[1]: Started Samba SMB Daemon.
Apr 25 22:20:36 nas systemd[1]: Starting Docker Application Container Engine...
Apr 25 22:20:36 nas systemd[1]: Listening on Docker Socket for the API.
Apr 25 22:20:36 nas systemd[1]: Starting Docker Socket for the API...
Apr 25 22:20:36 nas smbd[15156]: Copyright Andrew Tridgell and the Samba Team 1992-2023
Apr 25 22:20:36 nas smbd[15156]: smbd version 4.19.9-git.404.38b26805d4150600.3.12.2SUSE-oS15.0-x86_64 started.
Apr 25 22:20:36 nas smbd[15156]: [2025/04/25 22:20:36.419280, 0] ../../source3/smbd/server.c:1748(main)
Apr 25 22:20:36 nas systemd[1]: Stopping Docker Socket for the API...
Apr 25 22:20:36 nas systemd[1]: Closed Docker Socket for the API.
Apr 25 22:20:36 nas systemd[1]: docker.socket: Deactivated successfully.
Apr 25 22:20:36 nas systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Apr 25 22:20:36 nas systemd[1]: Failed to start Docker Application Container Engine.
Apr 25 22:20:36 nas systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 25 22:20:36 nas systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 22:20:36 nas dockerd[15146]: chmod /mnt2/Rockon: operation not permitted
Apr 25 22:20:36 nas dockerd[15146]: time="2025-04-25T22:20:36+01:00" level=info msg="SUSE:secrets :: SUSEConnect support enabled (set /etc/dock>
Apr 25 22:20:35 nas update-apparmor-samba-profile[15153]: mv: cannot stat '/etc/apparmor.d/local/usr.sbin.smbd-shares.new': No such file or dir>
Apr 25 22:20:35 nas update-apparmor-samba-profile[15152]: diff: /etc/apparmor.d/local/usr.sbin.smbd-shares.new: No such file or directory
Apr 25 22:20:35 nas update-apparmor-samba-profile[15152]: diff: /etc/apparmor.d/local/usr.sbin.smbd-shares: No such file or directory
Apr 25 22:20:35 nas update-apparmor-samba-profile[15147]: /usr/share/samba/update-apparmor-samba-profile: line 62: /etc/apparmor.d/local/usr.sb>
Apr 25 22:20:35 nas update-apparmor-samba-profile[15151]: grep: /etc/apparmor.d/local/usr.sbin.smbd-shares: No such file or directory
Apr 25 22:20:35 nas update-apparmor-samba-profile[15150]: touch: cannot touch '/etc/apparmor.d/local/usr.sbin.smbd-shares': No such file or dir>
Apr 25 22:20:35 nas systemd[1]: Starting Samba SMB Daemon...
Apr 25 22:20:35 nas systemd[1]: Starting Docker Application Container Engine...
Apr 25 22:20:35 nas systemd[1]: rockstor-bootstrap.service: Consumed 45.241s CPU time.
Apr 25 22:20:35 nas systemd[1]: Failed to start Rockstor bootstrapping tasks.
Apr 25 22:20:35 nas systemd[1]: rockstor-bootstrap.service: Failed with result 'exit-code'.
Apr 25 22:20:35 nas systemd[1]: rockstor-bootstrap.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 22:20:34 nas poetry[14640]: Max attempts(10) reached. Connection errors persist. Failed to bootstrap. Error: Exception while setting acc>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:20:34 nas poetry[14640]: Oauth internal App client_secret updated.
Apr 25 22:20:34 nas poetry[14640]: Refreshing client_secret for oauth2_provider app from settings
Apr 25 22:20:34 nas poetry[14640]: BTRFS device scan complete
Apr 25 22:19:46 nas systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 25 22:19:32 nas kernel: perf: interrupt took too long (3985 > 3965), lowering kernel.perf_event_max_sample_rate to 50000
Apr 25 22:19:15 nas systemd[1]: Started Hostname Service.
Apr 25 22:19:15 nas dbus-daemon[623]: [system] Successfully activated service 'org.freedesktop.hostname1'
Apr 25 22:19:15 nas systemd[1]: Starting Hostname Service...
Apr 25 22:19:15 nas dbus-daemon[623]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.host>
Apr 25 22:18:54 nas poetry[14639]: 2025-04-25 22:18:54,396 INFO success: ztask-daemon entered RUNNING state, process has stayed up for > than 1>
Apr 25 22:18:49 nas poetry[14639]: 2025-04-25 22:18:49,387 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 5 sec>
Apr 25 22:18:46 nas poetry[14639]: 2025-04-25 22:18:46,380 INFO success: data-collector entered RUNNING state, process has stayed up for > than>
Apr 25 22:18:46 nas kernel: perf: interrupt took too long (3172 > 3138), lowering kernel.perf_event_max_sample_rate to 63000
Apr 25 22:18:44 nas poetry[14639]: 2025-04-25 22:18:44,368 INFO spawned: 'ztask-daemon' with pid 14654
Apr 25 22:18:44 nas poetry[14639]: 2025-04-25 22:18:44,354 INFO spawned: 'data-collector' with pid 14653
Apr 25 22:18:44 nas poetry[14639]: 2025-04-25 22:18:44,340 INFO spawned: 'gunicorn' with pid 14652
Apr 25 22:18:43 nas poetry[14639]: 2025-04-25 22:18:43,331 INFO supervisord started with pid 14639
Apr 25 22:18:43 nas poetry[14639]: 2025-04-25 22:18:43,330 INFO RPC interface 'supervisor' initialized
Apr 25 22:18:43 nas poetry[14639]: 2025-04-25 22:18:43,308 INFO Set uid to user 0 succeeded
Apr 25 22:18:39 nas systemd[1]: Starting Rockstor bootstrapping tasks...
Apr 25 22:18:39 nas systemd[1]: Started Rockstor startup script.
Apr 25 22:18:39 nas systemd[1]: Finished Tasks required prior to starting Rockstor.
Apr 25 22:18:38 nas systemd[1]: Started The nginx HTTP and reverse proxy server - 30-rockstor-nginx-override.conf.
Apr 25 22:18:38 nas nginx[14632]: nginx: configuration file /opt/rockstor/etc/nginx/nginx.conf test is successful
Apr 25 22:18:38 nas nginx[14632]: nginx: the configuration file /opt/rockstor/etc/nginx/nginx.conf syntax is ok
Apr 25 22:18:38 nas nginx[14630]: nginx: configuration file /etc/nginx/nginx.conf test is successful
Apr 25 22:18:38 nas nginx[14630]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
Apr 25 22:18:37 nas systemd[1]: Starting The nginx HTTP and reverse proxy server - 30-rockstor-nginx-override.conf...
Apr 25 22:18:37 nas systemd[1]: Reloading finished in 1369 ms.
Apr 25 22:18:36 nas systemd[1]: Configuration file /etc/systemd/system/smb.service is marked world-inaccessible. This has no effect as configur>
And here is the log messages if I start bootstrap manually
#journalctl -xeu rockstor-bootstrap.service
Apr 25 22:56:32 nas poetry[19949]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:56:32 nas poetry[19949]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:56:32 nas poetry[19949]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:56:32 nas poetry[19949]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:56:32 nas poetry[19949]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:56:32 nas poetry[19949]: Exception occurred while bootstrapping. This could be because rockstor.service is still starting up. will wa>
Apr 25 22:56:32 nas poetry[19949]: Max attempts(10) reached. Connection errors persist. Failed to bootstrap. Error: Exception while setting acc>
Apr 25 22:56:33 nas systemd[1]: rockstor-bootstrap.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit rockstor-bootstrap.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 25 22:56:33 nas systemd[1]: rockstor-bootstrap.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit rockstor-bootstrap.service has entered the 'failed' state with result 'exit-code'.
Apr 25 22:56:33 nas systemd[1]: Failed to start Rockstor bootstrapping tasks.
░░ Subject: A start job for unit rockstor-bootstrap.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit rockstor-bootstrap.service has finished with a failure.
░░
░░ The job identifier is 3410 and the job result is failed.
Apr 25 22:56:33 nas systemd[1]: rockstor-bootstrap.service: Consumed 44.829s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit rockstor-bootstrap.service completed and consumed the indicated resources.
I am using Rockstor version: 5.0.15-0 on an elderly Intel Atom mini-ITX
So far I have only one days experience with Rockstor, but so far I like it quite a bit. Good job developers,