Huges troubles after updating from omv3 to 4

    • OMV 4.x
    • Upgrade 3.x -> 4.x
    • Huges troubles after updating from omv3 to 4

      Hello everybody,
      After my my update from omv3 to 4, It seems everything was working fine except a little samba issue I reported here.
      But trying to solve this I realized that I can't update anymore.
      1st I had this weird Python bug (with weakref.py) I can solve following instrction on this forum.

      Then I was stuck with a strange "collectd thing" cannot even remove it :

      Source Code

      1. Setting up collectd-core (5.7.1-1.1) ...
      2. Job for collectd.service failed because the control process exited with error code.
      3. See "systemctl status collectd.service" and "journalctl -xe" for details.
      4. invoke-rc.d: initscript collectd, action "start" failed.
      5. * collectd.service - Statistics collection and monitoring daemon
      6. Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
      7. Active: activating (auto-restart) (Result: exit-code) since Wed 2018-08-15 15:26:56 CEST; 6ms ago
      8. Docs: man:collectd(1)
      9. man:collectd.conf(5)
      10. https://collectd.org
      11. Process: 26351 ExecStartPre=/usr/sbin/collectd -t [0;1;31m(code=exited, status=1/FAILURE)[0m
      12. Aug 15 15:26:56 DebiOMV systemd[1]: [0;1;31mFailed to start Statistics collection a…mon.[0m
      13. Aug 15 15:26:56 DebiOMV systemd[1]: [0;1;39mcollectd.service: Unit entered failed state.[0m
      14. Aug 15 15:26:56 DebiOMV systemd[1]: [0;1;39mcollectd.service: Failed with result 'e…de'.[0m
      15. Hint: Some lines were ellipsized, use -l to show in full.
      16. dpkg: error processing package collectd-core (--configure):
      17. subprocess installed post-installation script returned error exit status 1
      18. dpkg: dependency problems prevent configuration of collectd:
      19. collectd depends on collectd-core (>= 5.7.1-1.1); however:
      20. Package collectd-core is not configured yet.
      21. collectd depends on collectd-core (<< 6~); however:
      22. Package collectd-core is not configured yet.
      23. dpkg: error processing package collectd (--configure):
      24. dependency problems - leaving unconfigured
      25. dpkg: dependency problems prevent configuration of openmediavault:
      26. openmediavault depends on collectd; however:
      27. Package collectd is not configured yet.
      28. dpkg: error processing package openmediavault (--configure):
      29. dependency problems - leaving unconfigured
      30. Errors were encountered while processing:
      31. collectd-core
      32. collectd
      33. openmediavault
      Display All


      I tried to uninstall and reinstall
      apt-get --purge remove openmediavault
      and then when I apt-get install openmediavault

      Source Code

      1. Lecture des listes de paquets... Fait
      2. Construction de l'arbre des dépendances
      3. Lecture des informations d'état... Fait
      4. openmediavault is already the newest version (4.1.9).
      5. 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
      6. 3 partiellement installés ou enlevés.
      7. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
      8. Souhaitez-vous continuer ? [O/n] O
      9. Paramétrage de collectd-core (5.7.1-1.1) ...
      10. Job for collectd.service failed because the control process exited with error code.
      11. See "systemctl status collectd.service" and "journalctl -xe" for details.
      12. invoke-rc.d: initscript collectd, action "start" failed.
      13. â collectd.service - Statistics collection and monitoring daemon
      14. Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
      15. Active: activating (auto-restart) (Result: exit-code) since Wed 2018-08-15 15:32:53 CEST; 8ms ago
      16. Docs: man:collectd(1)
      17. man:collectd.conf(5)
      18. https://collectd.org
      19. Process: 26969 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=1/FAILURE)
      20. août 15 15:32:53 DebiOMV systemd[1]: Failed to start Statistics collection and monitoring daemon.
      21. août 15 15:32:53 DebiOMV systemd[1]: collectd.service: Unit entered failed state.
      22. août 15 15:32:53 DebiOMV systemd[1]: collectd.service: Failed with result 'exit-code'.
      23. dpkg: erreur de traitement du paquet collectd-core (--configure)Â :
      24. le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
      25. dpkg: des problèmes de dépendances empêchent la configuration de collectd :
      26. collectd dépend de collectd-core (>= 5.7.1-1.1) ; cependant :
      27. Le paquet collectd-core n'est pas encore configuré.
      28. collectd dépend de collectd-core (<< 6~) ; cependant :
      29. Le paquet collectd-core n'est pas encore configuré.
      30. dpkg: erreur de traitement du paquet collectd (--configure)Â :
      31. problèmes de dépendances - laissé non configuré
      32. dpkg: des problèmes de dépendances empêchent la configuration de openmediavault :
      33. openmediavault dépend de collectd ; cependant :
      34. Le paquet collectd n'est pas encore configuré.
      35. dpkg: erreur de traitement du paquet openmediavault (--configure)Â :
      36. problèmes de dépendances - laissé non configuré
      37. Des erreurs ont été rencontrées pendant l'exécution :
      38. collectd-core
      39. collectd
      40. openmediavault
      41. E: Sub-process /usr/bin/dpkg returned an error code (1)
      Display All
      So now I don't know what to do.... ;(


      I also now have a "502 Bad Gateway nginx" error trying to access the GUI (before uninstalling)

      Here is the openmediavault-webgui_error.log:

      Source Code

      1. 2018/08/15 15:27:25 [crit] 25917#25917: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      2. 2018/08/15 15:28:26 [crit] 26395#26395: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      3. 2018/08/15 15:29:27 [crit] 26431#26431: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      4. 2018/08/15 15:30:28 [crit] 26486#26486: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      5. 2018/08/15 15:31:29 [crit] 26814#26814: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      6. 2018/08/15 15:32:30 [crit] 26852#26852: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      7. 2018/08/15 15:33:20 [crit] 26888#26888: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      8. 2018/08/15 15:34:21 [crit] 27015#27015: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      9. 2018/08/15 15:35:22 [crit] 27051#27051: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"
      10. 2018/08/15 15:36:23 [crit] 27087#27087: *1 connect() to unix:/var/run/php-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: openmediavault-webgui, request: "HEAD / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-openmediavault-webgui.sock:", host: "127.0.0.1:8081"

      Can you help?
    • I run into issues as well, i just did a fresh install of the latest iso available 4.13 and upgraded to 4.17 but.... yeah i still run into the same weakref.py issue solved by editing the file, now again i run into ZFS plugin install issues header missing i thought that was solved as well, grrrrr seems lately nothing works first go.
    • Hello ArmandH,
      Thanks for your reply.
      When you say you did a fresh install you mean format it all? :/ Do you know a way to restor config after that? Because I spend a lot of time (like everybody I think) to configure everything.
      Saving config.xml is enought? Plus I also have a MySql Database I need to restore...
    • the files or database you have on a RAID or ZFS has nothing to do with the OMV install, you can reinstall and mount again your data disks.
      If for example you have stored your config files from docker etc on the RAID you can install the image and point to that config again.
      Another option is making a full clone of your OMV disk and then restore that.
    • No if i was you i would start fresh install the omv 4.x, after install upgrade it, install OMV-extras, do your configurations, if you use docker there is a great guide which applies for all docker apps you want to have.

      OMV + Docker plugin media server (Plex, PlexPy, Ombi, Libresonic, NZBGet, ruTorrent, Sonarr, Radarr, Mylar, and more)

      Then when ready make a full backup, check under the plugins backup section which backup you want to install and use.