Upgrade Debian 9 and 4.x

I came here by looking for a solution to weakref.py error. I applied the fixes described below, but the web interface would throw a new error on anything I would do with it (for instance, I tried adding a scheduled job):

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkconf cron 2>&1' with exit code '1': Failed to import the site module
Error processing line 1 of /usr/lib/python3/dist-packages/zope.component-4.3.0-nspkg.pth:

Traceback (most recent call last):
File "/usr/lib/python3.5/site.py", line 173, in addpackage
exec(line)
File "<string>", line 1, in <module>
File "/usr/lib/python3.5/types.py", line 166, in <module>
import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in <module>
from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 109
def remove(wr, selfref=ref(self)), _atomic_removal=_remove_dead_weakref):
^
SyntaxError: invalid syntax

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3.5/site.py", line 580, in <module>
main()
File "/usr/lib/python3.5/site.py", line 567, in main
known_paths = addsitepackages(known_paths)
File "/usr/lib/python3.5/site.py", line 344, in addsitepackages
addsitedir(sitedir, known_paths)
File "/usr/lib/python3.5/site.py", line 212, in addsitedir
addpackage(sitedir, name, known_paths)
File "/usr/lib/python3.5/site.py", line 183, in addpackage
import traceback
File "/usr/lib/python3.5/traceback.py", line 5, in <module>
import linecache
File "/usr/lib/python3.5/linecache.py", line 8, in <module>
import functools
File "/usr/lib/python3.5/functools.py", line 23, in <module>
from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 109
def remove(wr, selfref=ref(self)), _atomic_removal=_remove_dead_weakref):
^
SyntaxError: invalid syntax in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/openmediavault/engined/module/cron.inc(51): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(168): OMVModuleCron->applyConfig()
#2 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus04...', '/tmp/bgoutputV2...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

I reverted weakref.py changes and now the web interface is working normally again.

When you change the lines to the described, it should work:

Upgrade Debian 9 and 4.x

Regards Hoppel

Quote from macom

I thought this is fixed in the meantime

By whom? Debian guys? They do not fix even serious issues since 'stable' so you need to 'fix' it yourself: https://github.com/armbian/bui…age.sh.template#L206-L210

Quote from tmihai20

def remove(wr, selfref=ref(self)), _atomic_removal=_remove_dead_weakref):

Ther's an error with the second parenthesis after "self", it should looks like:

def remove(wr, selfref=ref(self), _atomic_removal=_remove_dead_weakref):

Odd10: thank you for pointing that out. It seems that I did not pay enough attention to what I was doing and I copy pasted it wrong. This never happened on Linux (I was using KiTTY on Windows). My Python knowledge is close to zero

I updated everything there was to be updated, but it seems that OpenMediaVault 4 is a little behind than OpenMediaVault 3 was in regards to fixes and updates. There are also lots of plugins missing in OMV 3, even after this long period of time of being in Beta. It is still in Beta. Enough offtopic about OMV now.

I am sorry if I offended anyone, but I went from OMV 2 to 2 instances of OMV 3 and then to OMV 4. I has mostly everything in the latest version of OMV3, but my installation got messed up and I wanted to upgrade.

I may have been also tired when I modified that Python code. I want an error free installation. Is that such a bad thing? I miss the Deluge integration within the GUI. I am not using any other downloaders. I also updated Plex by hand with help from https://dev2day.de/. I honestly do not see the benefit of running downloaders in Docker.

You probably wanted to get rid of some packages because the components that we are discussing about were present there in the previous release of OMV. I know that you upgraded Debian. This situation happened for other when upgrading from OMV 2 to OMV 3. What would it mean to take over the plugins? Is there a github repo where the older plugin is present?

Quote from ryecoaaron

I didn't upgrade Debian. Volker is the OMV author and he did choose to Debian 9 for OMV 4.x but that has nothing to do with why the plugins are not maintained/ported to 4.x.

I thought some plugins were dropped because of being difficult to maintain them with the new Debian and/or new version of OMV.

Quote from ryecoaaron

I'm not sure what this statement means.

When I said "you", I meant "you guys/gals that are in charge of OMV or at least maintaing OMV".

Quote from ryecoaaron

You make them work although I don't know why you would. Most of the download plugins are just a start/stop. docker is still the best idea.

If you say it is not worth it, then I will not get involved anymore with the downloader plugins. I can live with installing and configuring Deluge by myself. Deluge plugin was the only one I needed.

Hi guys,

some days ago my server informed about new python packages, which I installed today.

Get:1 http://security.debian.org/debian-security stretch/updates/main amd64 python3.5 amd64 3.5.3-1+deb9u1 [229 kB]
Get:2 http://security.debian.org/debian-security stretch/updates/main amd64 libpython3.5-stdlib amd64 3.5.3-1+deb9u1 [2167 kB]
Get:3 http://security.debian.org/debian-security stretch/updates/main amd64 python3.5-minimal amd64 3.5.3-1+deb9u1 [1691 kB]
Get:4 http://security.debian.org/debian-security stretch/updates/main amd64 libpython3.5-minimal amd64 3.5.3-1+deb9u1 [573 kB]

After that I installed the new zfs packages and the weakref.py issue is back again:

DKMS: install completed.
Setting up libzpool2linux (0.7.11-1~bpo9+1) ...
Setting up libzfs2linux (0.7.11-1~bpo9+1) ...
Setting up zfsutils-linux (0.7.11-1~bpo9+1) ...
zfs-import-scan.service is a disabled or a static unit, not starting it.
Setting up zfs-zed (0.7.11-1~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb3031568c8>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fb3031568c8>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Done ...

So, I googled a bit around and found the following comment at github: https://github.com/OpenTechStr…85#issuecomment-324815526

Seemingly the issue is solved with python 3.6.1. So we have to wait until that version gets released officially. Until that happens I am using the workaround again.

Regards Hoppel

Quote from hoppel118

Seemingly the issue is solved with python 3.6.1. So we have to wait until that version gets released officially

No.

If you're interested in this absolutely harmless warning disappearing you need to take action since upstream Debian is not known to increase software versions in a release (the 'stable' mantra). So report issues upstream if you're interested in them getting resolved or live with it: crash omv-mkconf and omv-update

Hi everyone,

First of all i hope I'm not posting in the wrong thread as this mainly talked about the "weakref.py" error. I tried to fix it by changing the two lines explained in page 2 but no luck, and it does not even appear everytime I run apt-get update (about half the time). Anyway this is not my main issue with updating.

I have 2 NAS running Debian 9 and OMV 4. Have installed them pretty much the same way but I am now unable to update one of them for some reason (I suspect I have installed something different on this one but can't find out what...). When I try to apt-get upgrade it I run into the following error (sorry this is in french, I can translate if needed) :

root@NAS:/# apt-get upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Vous pouvez lancer « apt --fix-broken install » pour corriger ces problèmes.
Les paquets suivants contiennent des dépendances non satisfaites :
 python-samba : Dépend: libwbclient0 (= 2:4.5.12+dfsg-2+deb9u4) mais 2:4.5.16+dfsg-1 est installé
                Dépend: samba-libs (= 2:4.5.12+dfsg-2+deb9u4) mais 2:4.5.16+dfsg-1 est installé
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
   (ou indiquez une solution).

I then try to run "apt --fix-broken install" as suggested :

root@NAS:/# apt --fix-broken install
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Correction des dépendances... Fait
The following additional packages will be installed:
  python-dnspython python-samba
Paquets suggérés :
  python-gpgme
Les paquets suivants seront mis à jour :
  python-dnspython python-samba
2 mis à jour, 0 nouvellement installés, 0 à enlever et 22 non mis à jour.
4 partiellement installés ou enlevés.
Il est nécessaire de prendre 0 o/1 464 ko dans les archives.
Après cette opération, 4 096 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n]

I accept, and run into the following errors :

Lecture des fichiers de modifications (« changelog »)... Terminé
(Lecture de la base de données... 90096 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../python-dnspython_1.15.0-1+deb9u1_all.deb ...
  File "/usr/bin/pyclean", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: avertissement: le sous-processus ancien script pre-removal a retourné une erreur de sortie d'état 1
dpkg: tentative d'exécution du script du nouveau paquet à la place...
  File "/usr/bin/pyclean", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: erreur de traitement de l'archive /var/cache/apt/archives/python-dnspython_1.15.0-1+deb9u1_all.deb (--unpack) :
 le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 35, in <module>
    from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 24, in <module>
    from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'
dpkg: error while cleaning up:
 le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Préparation du dépaquetage de .../python-samba_2%3a4.5.16+dfsg-1_amd64.deb ...
  File "/usr/bin/pyclean", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: avertissement: le sous-processus ancien script pre-removal a retourné une erreur de sortie d'état 1
dpkg: tentative d'exécution du script du nouveau paquet à la place...
  File "/usr/bin/pyclean", line 63
    except (IOError, OSError), e:
                             ^
SyntaxError: invalid syntax
dpkg: erreur de traitement de l'archive /var/cache/apt/archives/python-samba_2%3a4.5.16+dfsg-1_amd64.deb (--unpack) :
 le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 35, in <module>
    from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 24, in <module>
    from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'
dpkg: error while cleaning up:
 le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Des erreurs ont été rencontrées pendant l'exécution :
 /var/cache/apt/archives/python-dnspython_1.15.0-1+deb9u1_all.deb
 /var/cache/apt/archives/python-samba_2%3a4.5.16+dfsg-1_amd64.deb
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fa48d9098c8>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fa48d9098c8>
Traceback (most recent call last):
  File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've been searching the web and trying stuff for 3 hours now but i am unable to make any progress, as everything lead me to the same exact error I have when I try to run apt-get upgrade. I can no longer remove any plugin from OMV web interface as well, it seems everything related to installing/updating/removing packages is stuck.

Is there something I missed when searching for a solution ?

Updating python to the Debian's testing branch seems to resolve the issue:

Add 'testing' to sources.list:

# sudo nano /etc/apt/sources.list
deb http://ftp.de.debian.org/debian testing main

Make the 'stable' repository default on your server:

# echo 'APT::Default-Release "stable";' | sudo tee -a /etc/apt/apt.conf.d/00local


# sudo nano /etc/apt/preferences
Package: *
Pin: release a=stable
Pin-Priority: 900
Package: *
Pin: release o=Debian
Pin-Priority: -10

Install updated python3 (this updated me to Python3.7.2+)
# sudo apt-get update
# sudo apt-get -t testing install python3

Based on: https://www.rosehosting.com/bl…python-3-6-4-on-debian-9/ and https://unix.stackexchange.com…to-set-default-apt-source