Houston we have a problem

Immediately after upgrading to V 5.0.15_0 tried to access jellyfin rockon ( installed
Rockons were showing ) a message to switch rockons ON popped up which were then showing as switched off.
The Houston message popped up when trying to switch them on.

I wasnt really paying attention so missed a couple of other screens that appeared whhen the initial jellyfin page was showing.

Detailed step by step instructions to reproduce the problem

[write here]

Web-UI screenshot

[Drag and drop the image

Did you reboot after the upgrade? I sometimes found in the past that it works (and don’t ask me why) if you turn on the Rockon service from the Systems menu, as opposed to within the Rockon screen itself. But I didn’t encounter your symptom when I upgraded from RC 14 to 15 recently


1 Like

Thanks @Hooverdan
I did reboot (a couple of times) no dice unfortunately.

Have also tried to start Rockons fron the system/services page but no luck, it didn’t achieve anything, the page flickered and remained the same.
Also have a strange looking caterpillar crossing the Ave cpu chart on the dashboard page.

Any ideas?

strange, that caterpillar
 no clue why that would happen.

take a look at
command line:
journalctl -xe maybe it tries to start the docker service, but can’t at boot time.

and then
tail -n 200 /opt/rockstor/var/log/rockstor.log to see whether anything obvious pops up w.r.t. dockerd/docker not starting.

The caterpillar is also present on the other charts and the top shares chart is continually buffering.
Have shutdown gracefully just in case and considering a revert to an earlier version.

Thanks again @Hooverdan
Will restart the system and add the lines suggested tomorrow.

1 Like

Managed to find a slot in my busy schedule (life just gets in the way sometimes) to boot up the box and let things settle down for 15 minuits or so, during which there is no repeat of the caterpillar on any of the Dashboard screens.
Rockons are switched off
Starting Rockons via the sustem/services
Rockons immedially switch off and caterpillars appear on Dasboard screens.
Entered the commands suggested
The first (journalct1 -xe) produced an

Blockquote

unknown command

Blockquote

reply
The second (tail
) produced numerous screens of data which didn’t want to be copied or saved or repeoduced in any way, however I did photograph the listing generating 11 photos.
I have no idea what the data is telling me, however after the listing the page continued to beffer as did all pages on the WUI. There were numerous errors being listed or the use of the word error was being used on many lines.
Any ideas, the photos can be sent just let me know an address to send to.
System now shutdown
Thanks in advance

actually, the first command contains an “L” (lower case) instead of a “one” (1). Like an abbreviation of “control” to “ctl”, so it should be:

journalctl -xe - sorry these fonts are often not conducive to reading them off (since you couldn’t copy it from the browser to your command window).

before you send the pictures, let’s check these two commands (see above for it to be a lower case “L” at the end):

systemctl status docker

this will likely show that the Rockon service cannot start, but to be sure, you can also try to start it from the command line:

systemctl start docker

The tail command I mentioned above 
 you can actually just download the log using the WebUI (under the systems menu towards the bottom is the Logs Manager, and it essentially executes the command I described, listing the last 200 lines of the log) open that file in an external editor and then post the error messages that seem the most relevant.

1 Like

Thanks @Hooverdan
Will try again tomorrow

1 Like

before Rockons started
systemctl
shows three failures

  1. Activation of DM Raid sets
  2. Docker App;ication ontainer Engine
  3. Docker Socket for the API

Log for systemctl start docker
File “/opt/rockstor/src/rockstor/system/osi.py”, line 289, in run_command
raise CommandException(cmd, out, err, rc)
system.exceptions.CommandException: Error running a command. cmd = /usr/bin/systemctl start docker. rc = 1. stdout = [‘’]. stderr = [‘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.’, ‘’]

[21/Dec/2024 20:17:05] ERROR [smart_manager.data_collector:1017] Failed to update disk state
 exception: Exception while setting access_token for url(http://127.0.0.1:8000): HTTPConnectionPool(host=‘127.0.0.1’, port=8000): Read timed out. (read timeout=2). content: None
[21/Dec/2024 20:17:07] ERROR [smart_manager.data_collector:1017] Failed to update pool state
 exception: Exception

Hope this helps

away from my machine today, unfortunately, but the first message on DM RAID sets is not really an error, since running on btrfs.

might be another command to try to see whether you can see more details about the docker failure.

I’m wondering whether the Rockon Root has been corrupted, and that’s why you can’t start the docker service, but at this moment that’s just a guess. I’ve only seen docker issues when it ran into problems to start up Rockstor entirely (due to Network Manager not liking some of the hardware links), but that doesn’t seem to be the case with you, since you’re able to access the WebUI.

Thanks @Hooverdan
Happy Christmass

Did try this command which returned this

System now shut down till after the Hols
Thanks again

Same to you!

Sorry, should have pointed out that you should run these commands as root, e.g.:

elevate your command prompt from Mike to root by

su - which will then ask for the root password. Then you can execute:

journalctl -xeu docker.service

this will likely produce a few pages of output, you can page up/down, and quit the display of that list by typing q.

The status command does not require the elevated command prompt (but of course works there as well).
systemctl status docker

But, if you want to start the docker the service at the command line, it does require the elevated comman prompt:
systemctl start docker

If you want to leave the elevated command prompt, just type exit and you will drop down to user Mike.

2 Likes

Thanks @Hooverdan
It is me that should be sorry, had I had an inkling of knowledge related to the use of the system commands we would all be better of in terms of time.
Thanks again.
I do have some data for you (Glad I wrote down the su password, but then couldn’t remember where I stored it :thinking:)

Must get some practice in the use of system commands, its quite empowering (and quite dangerous, I am beginning to feel)

Happy New Year to all.

2 Likes

Below is the only item in the log that has the appearance of a problem, couldn’t see anything else that stands out.
[27/Dec/2024 07:03:51] INFO [scripts.initrock:458] The replication_crontab (/etc/cron.d/replicationtab) could not be found.
could it be an error in the update process (something not quite right with my cobbled together rig) as all worked fine prior to the latest change, would it be an idea to re-initiate the update (if that’s even possinble)?

Browsing aroiund the Wb UI I noticed the disc screen had a possible indication as to a possible resource issue with the hard drives.


The power status of two drives is listed as unknown.
Could this be the problem?
Although the dashboard screen disc activity thingabejig shows both drives active???

I’m on the road again today, but could you reboot and post the output of

tail -n 200 /opt/rockstor/var/log/rockstor.log
(you should be able to select and copy/paste from the WebUI screen if I’m not mistaken)? I don’t think you need the elevated command prompt for that, but it won’t hurt if you use it.

I have the same problem with 6 Seagate drives. I think it’s a timing or sequence issue. If you click the “SMART” switch off/on it will update the status correctly. It only does this on my Seagate drives, not on my HGST or WD drives.

:sunglasses:

Thanks again @Hooverdan
I have two log files (MS notebook format) but it seems the upload system will only allow a limited number of file formats, mainly images.
The last screen from the sys log converted to JPG (Pre Rockon initialisation)


Second to last screen as I am unsure where the latest log starts.

The post rockon initialisation log (last screen)


Second to last Post Rockon Iniitialisation screen

Hope this is this data is relevant and sufficient.