OMV 3 to 4 upgrade issues

    • OMV 3.x
    • Upgrade 3.x -> 4.x
    • OMV 3 to 4 upgrade issues

      I have done the jump from OMV3 to OMV4 today. I am encountering some issues in OMV4 after the upgrade:

      - Remote desktop to the OMV server does not work anymore (no response when trying to connect)
      - My nextcloud installation does not work anymore ("The server encountered an internal error and was unable to complete your request.")
      - My Let's encrypt SSL certificate does not seem to work anymore
      - The virtualbox plugin has disappeared from the installed plugins list (seems not to be installed anymore. So i guess the fix is to reinstall it)

      That is what i could find so far. Are these known issues? How would i proceed to find the root causes and fix them?

      The post was edited 1 time, last by monsen ().

    • UPDATE:

      I could solve the nextcloud issue by following these directions: disable memache


      Some additional info for the remote desktop problem that i have retrieved from the CLI:

      Source Code

      1. xrdp (0.9.8-2~bpo9+1) wird eingerichtet ...
      2. Job for xrdp.service failed because the control process exited with error code.
      3. See "systemctl status xrdp.service" and "journalctl -xe" for details.
      4. invoke-rc.d: initscript xrdp, action "restart" failed.
      5. ● xrdp.service - xrdp daemon
      6. Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled)
      7. Active: failed (Result: exit-code) since Mon 2018-11-26 14:08:18 CET; 22ms ago
      8. Docs: man:xrdp(8)
      9. man:xrdp.ini(5)
      10. Process: 12385 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited, status=1/FAILURE)
      11. Process: 12376 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, status=0/SUCCESS)
      12. CPU: 45ms
      13. Nov 26 14:08:18 debNAS systemd[1]: Starting xrdp daemon...
      14. Nov 26 14:08:18 debNAS systemd[1]: xrdp.service: Control process exited, code=exited status=1
      15. Nov 26 14:08:18 debNAS systemd[1]: Failed to start xrdp daemon.
      16. Nov 26 14:08:18 debNAS systemd[1]: xrdp.service: Unit entered failed state.
      17. Nov 26 14:08:18 debNAS systemd[1]: xrdp.service: Failed with result 'exit-code'.
      18. dpkg: Fehler beim Bearbeiten des Paketes xrdp (--configure):
      19. Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
      20. dpkg: Abhängigkeitsprobleme verhindern Konfiguration von openmediavault-remotedesktop:
      21. openmediavault-remotedesktop hängt ab von xrdp (>= 0.9.4); aber:
      22. Paket xrdp ist noch nicht konfiguriert.
      Display All
    • monsen wrote:

      Remote desktop to the OMV server does not work anymore (no response when trying to connect)
      Remove the plugin and re-install it.

      monsen wrote:

      The virtualbox plugin has disappeared from the installed plugins list (seems not to be installed anymore. So i guess the fix is to reinstall it)
      Do you have backports enabled?

      monsen wrote:

      Are these known issues? How would i proceed to find the root causes and fix them?
      Nope. What is the output of: dpkg -l | grep openm
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Remove the plugin and re-install it.

      I did but no joy:

      Source Code

      1. Job for xrdp.service failed because the control process exited with error code.
      2. See "systemctl status xrdp.service" and "journalctl -xe" for details.
      3. invoke-rc.d: initscript xrdp, action "restart" failed.
      4. * xrdp.service - xrdp daemon
      5. Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled)
      6. Active: failed (Result: exit-code) since Mon 2018-11-26 16:52:59 CET; 23ms ago
      7. Docs: man:xrdp(8)
      8. man:xrdp.ini(5)
      9. Process: 10464 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited, status=1/FAILURE)
      10. Process: 10454 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, status=0/SUCCESS)
      11. CPU: 42ms
      12. Nov 26 16:52:59 debNAS systemd[1]: Starting xrdp daemon...
      13. Nov 26 16:52:59 debNAS systemd[1]: xrdp.service: Control process exited, co…us=1
      14. Nov 26 16:52:59 debNAS systemd[1]: Failed to start xrdp daemon.
      15. Nov 26 16:52:59 debNAS systemd[1]: xrdp.service: Unit entered failed state.
      16. Nov 26 16:52:59 debNAS systemd[1]: xrdp.service: Failed with result 'exit-code'.
      17. Hint: Some lines were ellipsized, use -l to show in full.
      18. dpkg: error processing package xrdp (--configure):
      19. subprocess installed post-installation script returned error exit status 1
      20. Processing triggers for man-db (2.7.6.1-2) ...
      21. Processing triggers for openmediavault (4.1.14-1) ...
      22. Restarting engine daemon ...
      23. Processing triggers for hicolor-icon-theme (0.15-1) ...
      24. dpkg: dependency problems prevent configuration of openmediavault-remotedesktop:
      25. openmediavault-remotedesktop depends on xrdp (>= 0.9.4); however:
      26. Package xrdp is not configured yet.
      27. dpkg: error processing package openmediavault-remotedesktop (--configure):
      28. dependency problems - leaving unconfigured
      29. Setting up xterm (327-2) ...
      30. Processing triggers for libc-bin (2.24-11+deb9u3) ...
      31. Errors were encountered while processing:
      32. xrdp
      33. openmediavault-remotedesktop
      Display All




      monsen wrote:

      The virtualbox plugin has disappeared from the installed plugins list (seems not to be installed anymore. So i guess the fix is to reinstall it)
      Do you have backports enabled?

      I think so yes. How do i find out?

      monsen wrote:

      Are these known issues? How would i proceed to find the root causes and fix them?
      Nope. What is the output of: dpkg -l | grep openm


      Source Code

      1. ii libopenmpt-modplug1:amd64 0.2.7386~beta20.3-3+deb9u3 amd64 module music library based on OpenMPT -- modplug compat library
      2. ii libopenmpt0:amd64 0.2.7386~beta20.3-3+deb9u3 amd64 module music library based on OpenMPT -- shared library
      3. ii openmediavault 4.1.14-1 all openmediavault - The open network attached storage solution
      4. ii openmediavault-apttool 3.5 all apt tool plugin for OpenMediaVault.
      5. ii openmediavault-backup 4.0.4 all backup plugin for OpenMediaVault.
      6. ii openmediavault-docker-gui 4.1 all OpenMediaVault plugin for Docker
      7. ii openmediavault-downloader 3.6.2 all OpenMediaVault downloader plugin
      8. rc openmediavault-fail2ban 1.3.1 all OpenMediaVault Fail2ban plugin
      9. ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
      10. ii openmediavault-letsencrypt 3.4.5 all Generate free and valid SSL certificates for OMV
      11. ii openmediavault-locate 3.4 all locate plugin for OpenMediaVault.
      12. ii openmediavault-mysql 4.1.2 all MySQL plugin for OpenMediaVault.
      13. ii openmediavault-nginx 4.0.3 all Nginx plugin for OpenMediaVault.
      14. pc openmediavault-nzbget 3.2 all command-line based binary newsgrabber for nzb files
      15. ii openmediavault-omvextrasorg 4.1.13 all OMV-Extras.org Package Repositories for OpenMediaVault
      16. ii openmediavault-plexmediaserver 3.8.2 all OpenMediaVault Plex Media Server plugin
      17. iU openmediavault-remotedesktop 4.0.1 all Remote desktop plugin for OpenMediaVault.
      18. ii openmediavault-rsnapshot 4.2.1 all OpenMediaVault rsnapshot backup plugin.
      19. ii openmediavault-shellinabox 3.4 all Web-based SSH client.
      20. ii openmediavault-symlinks 3.1.4 all OpenMediaVault symlinks plugin
      21. ii openmediavault-urbackup-server 3.1 all OpenMediaVault urbackup-server plugin
      22. rc openmediavault-virtualbox 3.0.8 all VirtualBox plugin for OpenMediaVault.
      23. ii openmediavault-wol 3.4.1 all OpenMediaVault WOL plugin
      Display All
    • monsen wrote:

      How do i find out?
      Click the enable backports button in omv-extras. What is the output of dpkg -l | grep xrdp

      jollyrogr wrote:

      are the backports supposed to be enabled for VB in omv 4?
      Yes. That is where Debian puts the virtualbox package. It is not available in the regular repo.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      monsen wrote:

      How do i find out?
      Click the enable backports button in omv-extras. What is the output of dpkg -l | grep xrdp

      Sorry I don't see any option to enable backports kernel in omv-extras. There is an option to install the Proxmox kernel...

      Source Code

      1. root@debNAS:~# dpkg -l | grep xrdp
      2. ii xorgxrdp 0.9.1-9+deb9u3 amd64 Remote Desktop Protocol (RDP) modules for X.org
      3. iF xrdp 0.9.8-2~bpo9+1 amd64 Remote Desktop Protocol (RDP) server
    • monsen wrote:

      I clicked on "enable" and did a reboot. Nothing changed.
      It just enables a repo. No reboot required.

      monsen wrote:

      What now, reinstall virtualbox?
      Sure.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Ok virtualbox is installed again. Now i wonder where my VM's did go. Did they get deleted when plugin was uninstalled by the release-upgrade procedure?
      Can't find anything that fits with "locate .vbox" or .vdi

      In that case i could probably extract them out of the backup i did with clonezilla before the upgrade?

      The post was edited 1 time, last by monsen ().

    • monsen wrote:

      Did they get deleted when plugin was uninstalled by the release-upgrade procedure?
      No but the user id probably changed for the vbox user. You will need to change the permissions on the files.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • jollyrogr wrote:

      Maybe I'm crazy, but I have put plans to migrate from 3 to 4 on hold. OMV 3 works flawlessly and I'm not looking for problems to fix. When the time comes, I'll probably migrate using a fresh install. Maybe wait until 5 is ready and go from 3 to 5.
      From what little I have read about OMV 5, there will be no upgrade path from any prior version. A fresh install will be the only way.
      --
      Google is your friend and Bob's your uncle!

      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • jollyrogr wrote:

      Maybe wait until 5 is ready and go from 3 to 5.

      gderf wrote:

      From what little I have read about OMV 5, there will be no upgrade path from any prior version. A fresh install will be the only way.
      And you have never been able to skip versions. These problems aren't happening to everyone. I have tested upgrades many, many times and upgraded my own systems without these issues.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • another thing i have remarked is that the Mysql plugin is marked as non running in the dashboard.
      Although it reports it is not running, I did not remark anything that is not working due to that.
      As soon as i do a "systemctl status mysql" in the CLI it gets green in the OMV web frontend. The output on the CLI is:

      Source Code

      1. systemctl status mysql ● mariadb.service - MariaDB 10.1.37 database server
      2. Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
      3. Active: active (running) since Tue 2018-11-27 09:40:30 CET; 1 day 10h ago
      4. Docs: man:mysqld(8)
      5. https://mariadb.com/kb/en/library/systemd/
      6. Main PID: 1411 (mysqld)
      7. Status: "Taking your SQL requests now..."
      8. Tasks: 31 (limit: 4915)
      9. Memory: 151.0M
      10. CPU: 4min 33.962s
      11. CGroup: /system.slice/mariadb.service
      12. └─1411 /usr/sbin/mysqld
      13. Nov 27 09:40:28 debNAS systemd[1]: Starting MariaDB 10.1.37 database server...
      14. Nov 27 09:40:29 debNAS mysqld[1411]: 2018-11-27 9:40:29 140249766937024 [Note] /usr/sbin/mysqld (mysqld 10.1.37-MariaDB-0+deb9u1) starting as process 1411 .
      15. Nov 27 09:40:30 debNAS systemd[1]: Started MariaDB 10.1.37 database server.
      Display All
      Images
      • mysql1.png

        24.93 kB, 838×282, viewed 145 times
      • mysql2.png

        30.79 kB, 1,262×289, viewed 149 times
      • mysql3.png

        38.02 kB, 882×361, viewed 160 times
      • mysql4.png

        20.5 kB, 836×256, viewed 184 times
    • monsen wrote:

      As soon as i do a "systemctl status mysql" in the CLI it gets green in the OMV web frontend. The output on the CLI is:
      That is strange. Almost seems like a browser cache issue. The indicator works fine on all of my systems using the mysql plugin.
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      monsen wrote:

      As soon as i do a "systemctl status mysql" in the CLI it gets green in the OMV web frontend. The output on the CLI is:
      That is strange. Almost seems like a browser cache issue. The indicator works fine on all of my systems using the mysql plugin.
      It is not a browser cache issue. I have just cleared the browser and the issue remains.
      Also: as soon as i check the status via CLI

      Source Code

      1. systemctl status mysql
      The light turns green in the Web GUI
    • monsen wrote:

      It is not a browser cache issue. I have just cleared the browser and the issue remains.
      Also: as soon as i check the status via CLI
      I don't know what to tell you then. It works on all of my systems and the code is identical to OMV core plugins.
      github.com/OpenMediaVault-Plug…ined/module/mysql.inc#L80
      github.com/openmediavault/open…/module/shairport.inc#L95
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      monsen wrote:

      It is not a browser cache issue. I have just cleared the browser and the issue remains.
      Also: as soon as i check the status via CLI
      I don't know what to tell you then. It works on all of my systems and the code is identical to OMV core plugins.github.com/OpenMediaVault-Plug…ined/module/mysql.inc#L80
      github.com/openmediavault/open…/module/shairport.inc#L95

      Hmm ok. It seems as it does not affect anything, so I will just ignore it.