I get this OMV error when trying to run sudo apt full-upgrade on my Raspberry Pi 4 (see attachment). I am thinking there is a python dependency issue here. I have a lot of other things installed on here too.
Failing to update to 6.9.14-1 from
-
- OMV 6.x
- litex2x
-
KM0201
Hat das Thema freigeschaltet. -
I get this OMV error when trying to run sudo apt full-upgrade on my Raspberry Pi 4 (see attachment). I am thinking there is a python dependency issue here. I have a lot of other things installed on here too.
Post the output inside CODE boxes of:
sudo omv-upgrade
dpkg -l | grep pip
If you installed pip on the host, you probably borked your install.
-
If you want to update from CLI you must use the omv-upgrade command. https://docs.openmediavault.or…arious/apt.html#using-cli
-
votdev
Hat das Label OMV 6.x hinzugefügt. -
Zitat
[ERROR ] Failed to import module glusterfs, this is due most likely to a syntax error:
Glusterfs??? This is not part of OMV. What have you installed in addition to OMV?
-
Alles anzeigen
Post the output inside CODE boxes of:
sudo omv-upgrade
dpkg -l | grep pip
If you installed pip on the host, you probably borked your install.
Glusterfs??? This is not part of OMV. What have you installed in addition to OMV?
I have Homebridge, Pihole, PiVPN, and also Plex Media Server installed here too. I also notice the version already says 6.9.14-1 in the dash. The instance seems to be operating fine despite the incomplete upgrade. I only use SMB.
I used the install script for the initial install -- https://github.com/OpenMediaVa…-Developers/installScript. -
I have Homebridge, Pihole, and also Plex Media Server installed here too.
And how are you running them?
On docker or you installed it on the host?
From the looks of your pip output, you installed things that messed with OMV.
Your installation is borked.
-
And how are you running them?
On docker or you installed it on the host?
From the looks of your pip output, you installed things that messed with OMV.
Your installation is borked.
Unfortunately it is all directly installed on the host. I will consider using docker if there is an opportunity. Should I try getting rid of pip?
-
Should I try getting rid of pip?
It's your call.
Just consider that you might do more damage than good.
The apps you installed (maybe Homebridge) are probably depending of it.
And by removing, you will (almost sure) break OMV or even uninstall it.
If you want to see what the command will remove, just run:
sudo apt remove python3-pip python-pip-whl --dry-run
This will simulate what apt would do when removing those packages.
If you really decide to go on, make a CLONE of the running OS (if on SDcard, just make it on another PC and flash the image to a new SDcard).
Boot up the Pi with the new card and try whatever you want.
If you don't like the outcome, just put back the old card and your system is still as it was.
Good luck
-
Alles anzeigen
It's your call.
Just consider that you might do more damage than good.
The apps you installed (maybe Homebridge) are probably depending of it.
And by removing, you will (almost sure) break OMV or even uninstall it.
If you want to see what the command will remove, just run:
sudo apt remove python3-pip python-pip-whl --dry-run
This will simulate what apt would do when removing those packages.
If you really decide to go on, make a CLONE of the running OS (if on SDcard, just make it on another PC and flash the image to a new SDcard).
Boot up the Pi with the new card and try whatever you want.
If you don't like the outcome, just put back the old card and your system is still as it was.
Good luck
Actually I think I see why this started happening now. A plugin I recently installed on homebridge installed python dependencies. This is probably a stupid question but is there a way to force OMV to use the version of Python it needs?
I guess the easy thing today is get Homebridge into docker since it is easier to export and import my configuration. -
is there a way to force OMV to use the version of Python it needs?
The issue isn't with python but with the modules that pip installs that messes with salt on OMV.
And you see it on the ERRORs you have.
I recall several old posts where users just found easier to just start fresh because it was a rabbit hole, trying to clean the system.
I guess the easy thing today is get Homebridge into docker since it is easier to export and import my configuration.
Not only Homebridge but also all other apps.
The idea is to keep the OS system as vanilla as possible by running all else on docker.
This is the way in almost all NAS systems nowadays: UnRAID, CasaOS, OMV, Synology, etc
Again, if you start fresh, it will be a breeze.
Trying to salvage the way you are now, will be a nightmare.
-
Alles anzeigen
The issue isn't with python but with the modules that pip installs that messes with salt on OMV.
And you see it on the ERRORs you have.
I recall several old posts where users just found easier to just start fresh because it was a rabbit hole, trying to clean the system.
Not only Homebridge but also all other apps.
The idea is to keep the OS system as vanilla as possible by running all else on docker.
This is the way in almost all NAS systems nowadays: UnRAID, CasaOS, OMV, Synology, etc
Again, if you start fresh, it will be a breeze.
Trying to salvage the way you are now, will be a nightmare.
I took your advice and started fresh. I installed omv on my raspberry pi host and have pihole, plexmediaserver, and homebridge running in docker containers. I switched from using pivpn to the omv wireguard plugin. I am up and running now.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
