[SOLVED] Rockon installations fail (Rockstor 3.9.2-57)

[Flox]

Hi @StephenBrown2,

Welcome to the forums! Before starting, I’d like to apologize for the too-long delay in getting to reviewing your Github PR… I personally have been completely taken by our effort on the openSUSE rebase that led me with not enough time to take care of all I’d like.

Now, the symptoms you are unfortunately experiencing are indeed rather curious and I can think of two things that might be related.

The first is:

@StephenBrown2

(It is currently rebalancing).

I know balancing is a rather intensive task for your system, and based on the amount of work to do, it will impact your system negatively while it is still running. For instance, have a look at one of @phillxnet’s recent posts and its included screenshot:

Error running a command. (Create a Share)

@b8two Hello again. Re: This simply means that btrfs had to wait for something for more than 120 seconds which is not expected on adequate hardware. This is normal. A drive removal is a form of balance that sets the target size of the to-be-removed drive as zero. Hence info is read from that drive but not, generally, written. And over time the read info is re-located on one of the other drives until no info is left where upon it is not longer part of the drive. Rockstor referes to this as a…

As a result, there may have been some timeouts happening while you were trying to install your Rock-ons, which ultimately resulted in some sync errors between what containers are running on your system and what was registered in Rockstor’s database. Pending experts’ opinions (@phillxnet?) I would recommend waiting for the balance to finish.

The other thing I can think of, would be some sync issues if you re-use the same rock-ons root share in your re-installed system (when compared to before the re-installation). In a Rockstor re-installation scenario, I generally prefer to delete this rockons_root share and re-create it, so that I’m sure there won’t be any kind of conflict with pre-existing docker container layers. As docker containers are designed to be nuked and rebuilt anyway, I’ve never hesitated to do that in a Rockstor reinstallation scenario.

@StephenBrown2

Since this is a fresh install, I wouldn’t expect there to be any info in the DB for any Rock-ons as of yet.

Correct. The related database models are blank upon Rockstor re-installation, and re-populated afresh by clicking on the “Update” button in the top right corner of the Rock-ons page. If interested, you will find more information in the wiki post below:

Rock-on framework implementation

Note: this document will be split in several posts in order to fit within characters’ limit. Make sure to browse the second post as well for more information . Preambule This is a wikified post documenting how Rockstor implements the rock-on framework, and should thus be considered a live document expected to be updated as necessary. As a user documentation already exists on how to use the framework (see link below), however, this write-up intends to first summarize the overall rock-on …

In this post, you will also see that when you click “Submit” at the end of a rock-on installation, Rockstor will run the docker pull image-name command for all containers listed in a given rock-on. Now, note that by default, this docker pull command will not run if it believes the image is already on the system. While this might be a possibility one can envision if you re-used a rock-ons_root share with pre-existing container layers, the fact that the images downloaded successfully when you triggered it manually goes against this hypothesis.

There still seems to be some out-of-sync issues going on, however, so it might be worth trying to reset it completely (and possibly waiting for your balance to finish):

1. Turn off rock-ons service
2. /opt/rockstor/bin/delete-rockon "Emby Server" (and any other rock-on for which you saw this error)
3. Go to Rock-ons > Click on “Update” in the top right
4. Go to Storage > Shares > <rock-ons_root> > Snapshots > delete all snapshots
5. Delete <rock-ons_root>
6. Create a new share to be used for rock-ons root
7. Configure the Rock-ons service using the share created in step 6 above as rock-ons_root
8. Turn on the Rock-ons service
9. Go to Rock-ons page and click on the “Update” button in the top right.

Everything should now be reset and ready to go.

Hope this helps,