Problem after upgrading - no omv installation found

Rayman · 15. März 2018

Hello folks,

I got an problem with OMV.
I updated from omv3 to omv4 with the usual upgrade command. After I upgraded I got the following error:

Code

Fehler traten auf beim Bearbeiten von:
xrdp
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f33a70e4730>
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 0x7f33a70e4730>
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)

Alles anzeigen

Apache is running. I can't access OMV throught the website. But the data is still there in www.
I also cant start the nginx server. It got an error:

Code

collectd[977]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)

Code

nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-03-15 14:39:10 CET; 12s ago
Docs: man:nginx(8)
Process: 15861 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)


Mär 15 14:39:10 NAS-Server systemd[1]: Starting A high performance web server and a reverse proxy server...
Mär 15 14:39:10 NAS-Server nginx[15861]: nginx: [emerg] invalid number of arguments in "listen" directive in /etc/nginx/sites-enabled/openmediavault-pxe:2
Mär 15 14:39:10 NAS-Server nginx[15861]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mär 15 14:39:10 NAS-Server systemd[1]: nginx.service: Control process exited, code=exited status=1
Mär 15 14:39:10 NAS-Server systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Mär 15 14:39:10 NAS-Server systemd[1]: nginx.service: Unit entered failed state.
Mär 15 14:39:10 NAS-Server systemd[1]: nginx.service: Failed with result 'exit-code'.

Alles anzeigen

Anything I can do? My OMV backup is pretty old and when I try to run any OMV command I get:

Code

root@NAS-Server:~# omv-release-upgrade
-bash: omv-release-upgrade: Command not found.

Can anybody help me? I dont know any further.

Good day,
Rayman

ryecoaaron · 15. März 2018

Zitat von Rayman

After I upgraded I got the following error:

Most of that is a python bug and nothing to worry about. I would remove xrdp since the plugin isn't available in omv 4.x.

Zitat von Rayman

Apache is running

That is a problem since OMV uses nginx. I would remove apache.

Zitat von Rayman

Anything I can do?

I would try:
omv-mkconf nginx
omv-mkconf php-fpm
systemctl restart nginx
systemctl restart php7.0-fpm

omv-release-upgrade shouldn't exist on OMV 4.x since there is no OMV 5.x. So, your system must be running OMV 4.x. What is the output of:
dpkg -l | grep openm

Rayman · 15. März 2018

Zitat von ryecoaaron

Most of that is a python bug and nothing to worry about. I would remove xrdp since the plugin isn't available in omv 4.x.
That is a problem since OMV uses nginx. I would remove apache.
I would try:omv-mkconf nginx
omv-mkconf php-fpm
systemctl restart nginx
systemctl restart php7.0-fpm

omv-release-upgrade shouldn't exist on OMV 4.x since there is no OMV 5.x. So, your system must be running OMV 4.x. What is the output of:
dpkg -l | grep openm

Alles anzeigen

Thank you!!!! This did indeed help. I needed to remove apache and nginx did worked again

The only thing which does not yet work is my RAID. Somehow I can't mount it anymore?

This is the blkid output:

Code

root@NAS-Server:~# blkid
/dev/sdc: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="01cdd2a3-b86b-691b-a213-b5ca3cbd878c" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sdb: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="48c7850e-4c34-6651-7bb2-8224c4062565" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sda1: UUID="0a228258-4d3a-4cfe-b87e-b837f4f19183" TYPE="ext4" PARTUUID="c66cdb84-01"
/dev/sda5: UUID="b3c59904-4ca4-49f1-80c1-ec4998c43471" TYPE="swap" PARTUUID="c66cdb84-05"
/dev/sdd: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="d939cc33-0157-cae7-2fa5-813087994cfe" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sde: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="2c0c01de-3547-50aa-d14c-b77b426ae2a7" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"

Should work, shouldn't it?

Rayman · 15. März 2018

No one?

Rayman · 17. März 2018

Still got the problem :s

macom · 17. März 2018

Have you searched the forum? There are some threads about RAIDs which are not auto-detected after an upgrade.
I think in most cases the RAID had to be assembled from the CLI for the first time.

Rayman · 17. März 2018

Zitat von macom

Have you searched the forum? There are some threads about RAIDs which are not auto-detected after an upgrade.
I think in most cases the RAID had to be assembled from the CLI for the first time.

Looks like my GPT ist damaged and I need to rebuild the whole RAID.

Jetzt mitmachen!