Another take on "Unknown internal error doing a POST to /api/rockons/update"

@greven Thanks for the report.

We’ve not had any other reports of this, however it could be that it’s simply taking too long to get all the rock-ons. We have seen this before due to the number of calls made on the server and have recently removed a redundant call in the code where every single Rockstor instance would update it’s Rock-ons list every time a dashboard was refreshed. This was an obvious waste of resources both on the client and the server.

The wget command to get the index file of root.json is a good test for access but is not the whole story. Once that file is retrieved each and every rock-on definition file is then individually downloaded and analyzed to incorporate/update the Rock-on definition in the local database.

Is your hardware particularly cpu slow for instance. In which case it could take more than 2 minutes to do this initial process. Or is the internet connection slow. This is the area I would look to first.

Also I’d stick to DIY installer installs myself as installing the rpm on a vanilla Leap 15.2 requires quite a few hoops to jump through, such as ipv6 kernel command line disable, that we detail here:

and shouldn’t be required unless you intend to setup a development environment.

Plus it’s easier to reproduce what you may have there from the installer than from the numerous dev env setup steps.

That’s a curios one and points again to something timing out. Look more to that log to see what has timed out in that case. We do have a new dependency on a Huey library and it may be it’s got a problem on your hardware.

If you could tell us more about the speed of the underlying system it may help to narrow this down as the Rock-on refresh is quite an intensive process, especially initially; and as our list grows of course. However we do have a Rock-on pruning process underway that is currently lead by forum member @Hooverdan under the following Rock-on repo issue:

Sorry not to be of more help on this one just yet.

Also take a look at the following excellent technical wiki entry by @Flox, lead dev on Rock-ons, for a background on what’s going on re the Rock-ons update process:

It should help to narrow down where the bottle neck is in your system or to identify a recent bug which is likely down to me I’m afraid.

Keep us posted and again, I’d persevire with the DIY installer variant as there are less variables on what you system config is. Plus is way smaller than any regular Leap 15.2 install derived Rockstor. We essentially started with a Leap JeOS variant and added only the critical dependencies for the Rockstor rpms from there on. Try taking a look at the comparative sizes of your installs to get an idea of the difference, assuming you got as far as the Leap 15.2 based attempt.

Hope that helps and do keep us posted.

2 Likes