FIXED: Saillogger plugin fails to install on Venus OS v3.62
-
IMPORTANT NOTE: This issue has been resolved in Saillogger Signal K plugin version 4.2.1. In collaboration with Victron, we identified the root cause and fixed it by rebuilding the dependency. Please install Signal K Saillogger plugin version 4.2.1 or later.
The latest Victron Venus OS release (v3.62) misses a critical package that prevents the Saillogger plugin from installing in Signal K (see attached screenshot).
We’re working with Victron on a fix. In the meantime, please use one of these workarounds:
1. If you haven’t upgraded yet: hold off on updating to v3.62 until the issue is resolved. We’ll post an update as soon as a fix is available.
2. If you’re already on v3.62: downgrade to a previous version. On the Victron GX display go to Settings → Firmware → Stored Backup Firmware and choose an older release.
3. If downgrading isn’t possible: install the missing package via SSH:
3.1 Enable SSH access by following these instructions and ssh to your Victron GX device using a terminal.
3.2 Run/opt/victronenergy/swupdate-scripts/remount-rw.shto remount the filesystem read-write.
3.3 Executeopkg update, thenopkg install python3-pip
3.4 Exit the terminal and install the Saillogger plugin normally.We apologize for the inconvenience and thank @Gerler for identifying the workaround in step 3.
This post will be updated once the fix is released in Venus OS.
-
A admin pinned this topic
-
A admin referenced this topic
-
A admin referenced this topic
-
Hello to all saillogger friends, unfortunately I had not read this post before and I installed the 4.2.1 update which obviously did not install. However, there is a variant in my case that I would like to report, I still have version 3.55 and although this version is reported as the one on which 4.2.1 works, in my case it is not installed, could there be a solution in my case?
-
-
I am fairly new to Saillogger [~ 2weeks] and it performs very well. Nicely done!
I upgraded to Venus 3.62 on a Cerbo GX Mk2 after the initial Saillogger installation- before seeing this warning [which I found while researching reasons for consistent failed attempts to perform installs/upgrades from the venus.local SignalK app store.]
I discovered this issue when I tried to add true wind direction capability by installing the derived-data plug-in. [Likewise for Saillogger 4.21, etc.] Everything failed install from the venus.local SignalK app store.
After discovering this posting, I tried all of the above installs/updates via the venus.local app store after installing fresh copies of Venus 3.55, then 3.60, 3.62, and even the latest beta release candidates 3.70-6. [I tried iPadOS and MacOS-using both Safari and Chrome on each. All current.] Every attempt fails in every version of VenusOS- leading me to think either I have something drastically wrong with my set-up, or that Victron has fubared their SignalK instance- at least as pertains to installs/updates via the app store.
I offer all of this as feedback, and don’t believe it has anything to do with Saillogger [which continues to perform well through all of this…]
However, for me today, expanding/upgrading anything in the Venus.local SignalK environment is not possible, and this doesn’t bode well for my future reliance on your excellent Saillogger service. I hope this all changes in the near future.
Cordially, Bill on SV Denali Rose
PS: I should also mention I am no longer comfortable trying my skills using the command line interface to maintain Venus/SignalK app environment- and that isn’t really why I go cruising anyway… So for now I am content to wait a little longer to see if Victron tames their SignalK implementation [if my assumption is correct…]
-
@wrwakefield Hi Bill, so since you updated to VenusOs 3.62 on Venus SK have you managed to update to saillogger 4.21 or not?
-
Hi Andrea,
Thanks for your inquiry.
I’ve tried every version of VenusOS from 3.55 through to the latest beta release candidate [3.70-7] with the same results. 3.62 was no different [and is where I started from with the first install failures.] Saillogger 4.21 fails installation [as does the derived-data plug-in…] in every attempt in every V OS tried so far…
I’ll be patient and see how things evolve on the Victron end…
Cheers, Bill
-
@wrwakefield Actually a case study. Since you have the Cerbo GX have you ever installed a plugin in SK? because it seems strange that in a native configuration like that of version 3.50 with Venus Large, Signal K can give problems, I have used numerous Cerbo even with versions prior to 3.50 and both Signal K and Node Red have always worked well. Of course in Signal K has it made your login and password and do you access with those correctly?
-
Hi Andrea,
The irony is Saillogger is working well since I installed it. [Although something went wrong on the Saillogger end and they sent an email indicating they took care of it so my new account could go live.]
RE: Logging into Venus.local SignalK: Yes. It won’t let me see the app store until I log in to SignalK. It shows all installed apps and plug-ins, and those with updates. It shows the ‘installing’ status when an update is selected, but to date all have ‘failed’.
It could be something is fubared in my local SignalK install, but since Saillogger continues to operate despite not being able to upgrade, I’ll just let it slide for a while to see if it is me or my instance, or a fix is introduced along the way…
Thanks again.
Cheers, Bill
-
@wrwakefield Sorry last suggestion, have you tried asking on the Victron website?
-
Nothing to be sorry about, Andrea.
We all try to assist each other on these forums, and I appreciate your feedback…
I have perused the Victron sites but not posted yet. Since Saillogger is working despite my ministrations, I figured I would hold out until the next Venus update is released [mentioned as impending in a Victron Professional update I received recently.]
Crossing fingers…
Cheers, Bill
-
@wrwakefield Good luck
-
@wrwakefield, sorry to hear the problems you encountered. v3.62 and Saillogger Plugin 4.2.1 should work alongside other plugins, we also use v3.62 ourselves and run many additional plugins beyond Saillogger. It’s possible that Signal K became corrupted in the process; have you tried restarting the Cerbo GX completely? If you did and it didn’t work, completely removing it and re-configuring may be the best thing to do.
This will require root access to Cerbo GX though. Instructions are here but please read the warnings carefully.
Please follow these steps after obtaining root access:
- Stop Signal K process (Toggle off Signal K in Venus OS menu) - This is important
- SSH into Venus OS
- Delete the Signal K directory by issuing the command rm -rf /data/conf/signalk
- Exit ssh by exit or closing the terminal
- Start Signal K process
This will give you a fresh, brand new Signal K instance. That also means all your previous configuration will be lost. You will need to download the Signal K plugin again and configure it. Make sure you wait long enough for installing the plugin and do not interrupt it. It can take longer than 30 minutes.
Let us know if this helps.
-
Thank you for your detailed response.
RE: rebooting the Cerbo: I have performed numerous cold and warm boots of the Cerbo during this process with the same end results.
Before seeing your response, I was pondering performing a ‘factory reset’ [and only that] on the Cerbo.
I am considering this in case other aspects of my Cerbo GX Mk2 Venus install also have issues I haven’t noticed yet… [All seems to perform normally sans the app store install/upgrade issue in SignalK…]
Your suggestion is a good one and more surgical in that it only resets SignalK. Do you know if Victron’s reset also deletes the SignalK directory [as per your SSH command?]
Since we are full time cruisers, and since we are on the cusp of shoving off again for a few months into very remote areas, I am being cautiously pragmatic in an effort to avoid bricking the Cerbo through my ineptitude. [It can take weeks to receive packages up here…]
Thanks again for your time.
Cheers, Bill
-
Hi @wrwakefield ,toggling Signal K on or off doesn't delete the Signal K configuration. We haven't explicitly tested the factory reset but pretty sure it would wipe out Signal K configuration as well.
We regularly delete the Signal K config to test out things from scratch, it has never caused an issue but of course operating on the CLI requires diligence. Just make sure "Signal K" toggle is off before you delete that directory. I don't think it is a showstopper if you don't but it is safer to do so.
