Storj node app v1.3.15 bug

Apps and Virtualization
1

In case others run into the issue with the storj app that has been running fine for months suddenly not working correctly after the latest update.

I ran into the same issue as the bug report describes today when updating from 1.3.14 to 1.3.15 of the storj node app. I had to roll back from 1.3.15 to the earlier version of 1.3.14 to clear the QUIC misconfiguration. The app also kept flagging (terminating) constantly also as described.

The fix for now is to roll back to version 1.3.14.

2 Likes
2

Thanks for letting everyone know.

I’m still on v1.3.9. I was tired of updating what felt like every other day since the Storj Node app updates itself and I’m running on v1.137.5, without updating the TrueNAS App.

I got lucky here for actually not upgrading.

Remember the days when Windoze would send out an update and your system would break? Oh yes, that is still happening, but it is less frequent. :wink:

3

Yes my actual node is also on V1.137.5
I have found it is kind of a big risk to update apps, even the official ones (not just 3rd party/community ones) as they rarely have any notes about what changed and why it was changed so you go into the update blind with crossed fingers.

They closed the bug report I referenced as being a duplicate of an earlier similar one which is fine and referred to the previous bug report that contains a non-acceptable work around if you ask me. If a person is already running the app. and it broke they have to monkey with it and convert it to a custom app then remove a variable which is a not so acceptable (to me) way and for someone doing a “new” install installing a broken app would be a deal breaker and make me question the quality control of a “stable” branch app and thus the overall quality control of Truenas itself.

A simpler solution would be to instruct to user to do a roll back to the previous version. In the app catalogue remove the broken version from download or at least regress it to the previous version so others won’t install a broken app.

The current (v1.3.15) version of the Storj app in the official catalog is broken on new deployments.

The app template incorrectly adds an environment variable RUN_PARAMS: ‘–operator.wallet-features=’ to the container configuration.

This flag is obsolete and causes the storagenode-updater process to fail immediately with an “unknown flag” error. This puts the entire application into a restart loop.

Log Snippet:
Error: unknown flag: --operator.wallet-features

Workaround/Fix:
The issue is resolved by converting to a custom app, and manually deleting the RUN_PARAMS environment variable.

So the solution is to convert to a custom app and delete a flag?
That’s kind of an impracticable heavy handed solution.

I did see a post the other day somewhere I forget where now. There was a complaint about constant app updates being issued for apps in the app catalogue and most (according to the post) are without any comments of what is new or changed.

I feel this is fairly spot on. I find in most cases you must go to the github/truenas/apps site, find the app then go look at the bug reports and the commits if you wish to know what changed before updating. The app section on github for storj v1.3.15 simply said Uses newer image and simplifies template. then lists what files were touched.

That simple language could have been inserted as a whats new in this version or maybe better in a change log. There is a Notes section already that could be used or just add a change log module to the apps page. But the basic info would also need fleshing out somewhat; “newer image” of what? storj app or docker?

They did issue a new “major” update this morning I think, but it does not mention if the issue was actually fixed or if the docker container was the sole focus of the update.

4

The only sensible solution in the long term is to forget the apps store exists. This is now iX’ fourth attempt at providing apps for TrueNAS: they’ve abandoned three others after determining they were “too hard” (i.e., they were unable or unwilling to commit the resources needed) to maintain. I don’t see any reason to believe they’ll do any better this time around.

Learn enough Docker/Compose to build/edit your own YAML, and run that.

5

That’s true. I should learn enough to build my own containers and so should everyone else. However, Truenas does offer apps just like Synology and QNAP, etc. do and so many may take advantage of that and it is a selling point if I’m looking to get out from under a closed ecosystem.

As you say this the fourth go at apps. That the underlying base layer won’t change yet again making docker out the door and having to convert even custom apps to something different is a possibility. VM’s are at this moment in constant flux too so that is not a safe bet to create a VM to run containers of ones choice in either.

Regardless, it is what it is. Upkeep of apps is hard for the supplier/developer and I think Truenas has found it takes more resources than they would like at this time to devote to it. They did ask for community help in maintaining apps, but I think that requires more intimate knowledge of the apps and time than most people actually have.

I do think they could fairly easily incorporate some kind of changes log for each app that can be either expanded or a link to click on in the app that would show changes. Make it a requirement for apps listed in the catalogue/store to have a change log entry for the update so the maintainer will put something in there.

6

The TrueNAS app has been updated to v1.3.16 to fix the bug.

7

I built a docker for my RPI and it was surprisingly easy for my Storj Node.

Something happened and my node was not actually working for the past 31 days. It said it was online, all looked great. no real traffic. I removed my docker container and reloaded it. Less that 24 hours and I have had a lot of activity. I couldn’t tell you why it wasn’t working, I did everything exactly the same (wrote it down).

I suspect it would be just as easy in TrueNAS. Now I will give it a try, eventually.

8

@joeschmuck I just finished a few minutes ago installing the 1.3.16 app update. It seems to work fine.

Among other things like changing to hashstore, lots of activity is from they had the nodes adjust to do more repair because I think some were behind on getting the amount done they needed to do to keep the data on the nodes in good shape. If you look at the logs you will see more piecestore and repair operations going on.

1 Like