Stop Xeoma from auto-updating

[Scottomated]

What's the best way to disable the hourly CRON job that updates Xeoma?

When you run this image specifying a specific version of Xeoma using environment variables, it starts up with the desired version. At some point, however, Xeoma gets updated to the latest version regardless of what is specified in the VERSION setting. This is undesirable because if the user's license doesn't cover the very latest version then Xeoma will stop working (switches to supporting 0 devices). The update occurs even if updating is disabled in the Xeoma GUI.

Ideally it wouldn't try to update if the user has specified anything other than "latest" for VERSION.

[neurocis]

I am not seeing this behavior, when VERSION set to 20.11.30 this actually now fixes version3.xml no longer being published to xeoma's site and does not update with cronjob:

root@3cc770915e5c:/etc/cron.hourly# ./update_xeoma 
[Dec 15 03:40:40 AM] Attempting to auto-update Xeoma
vvvvvvvvvvvvvvvvvvv
2020-12-15 03:40:40 Determining version of Xeoma to use
2020-12-15 03:40:40 Config version is "20.11.30"
2020-12-15 03:40:40 Using Xeoma version 20.11.30 (a user-specified version)
2020-12-15 03:40:40 Downloaded file /config/downloads/xeoma_20.11.30.tgz already exists. Skipping download
2020-12-15 03:40:40 Skipping installation because the currently installed version is the correct one
^^^^^^^^^^^^^^^^^^^
[Dec 15 03:40:40 AM] Xeoma has not been updated.
root@3cc770915e5c:/etc/cron.hourly#

[andrew-from-toronto]

I have this problem.. I'm currently trying to run version 20.7.31 and after some time running it seems to update it self to the latest version which several of my licenses are no longer eligible for. I believe passing -noautoupdate in the startup script should suffice. I will submit a PR

[andrew-from-toronto]

I've got a version of the container running with my proposed change, will submit a PR once I verify it resolves the issue.

[andrew-from-toronto]

-noautoupdate doesn't seem to be a switch on the CLI anymore. The help output lists a new option -disableDownloads [], which I've tried as stated however it does not seem to work either. I'm sure instead of the [] I am supposed to be passing in something, however there are no docs that I can find on this. I've engaged Xeoma support to find out more.

[andrew-from-toronto]

After a bit more investigation I think this is actually due to some bug in the update process built into the container when using environment variables instead of the configuration file.

[coppit]

AFAIK the container will only update the version (on startup) if you specify "latest" or "latest_beta" for the desired version. I'm highly skeptical that Xeoma itself will update to a newer version, as their licensing is tied to specific versions.

Can someone clarify?