Trouble installing OMV on pi4 : No access to GUI

    • OMV 5.x (beta)
    • Resolved
    • Yul wrote:

      I want to add the following.

      Yesterday during the day I could install and run everything, but because I want to start it from SSD I had to install it a lot of times.
      The problems started in the evening. That is when the troubles began and I couldn't start OMV5 again.
      So something happened during the day.

      Now I will go back to OMV4. I still have the image and this is working.
      Yes, it seems that something happened yesterday. We are all experiencing the exact same behavior: no access to the web gui and after setting a port in firstaid we get the 502 bad gateway nginx error. We used different raspbian busters lite images so the problem doesn't seem to be related to this.
      It happend yesterday during the day. Anyone knows of changes to omv 5 that were made yesterday maybe ?
    • Hey guys,

      i encountered the same problem with OMV 5.x on Armbian Buster (Kernel 4.14.y).

      It seems that during the installation process a file got missing or a service is not started correctly. I get the following error messages:

      Source Code: /var/log/nginx/openmediavault-webgui_error.log

      1. 2019/12/26 17:39:29 [crit] 1803#1803: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
      I hope this information is in some way useful.

      Greetings Slam
    • I also want to add something. Before I left home I checked the time of my server and it was an hour behind. I think the timezone is incorrect or summertime is active.

      Maybe that is the cause of this problem?

      I installed NTP to set a timeserver and didn’t check what it said before I confirmed installation and it actually removed openmediavault package along a few other packages like chrony before installing NTP so I completely screwed up my installation. I didn’t think that another time server application was installed. Tomorrow I will reinstall my server and OMV5 and set the date and time so it will be correct and check whether that makes a difference. Will post results.
    • Just a note... When posting no output from a failed install, it doesn't help anything. Testing now since I wasn't do anything OMV yesterday including installing on RPis or reading the forum.
      omv 5.3.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.4
      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!
    • Haven't tried the rpi yet but on a rock64, I had to do the following to fix the web interface (install script will do this as well).

      omv-salt deploy run nginx
      omv-salt deploy run phpfpm

      I will try the RPi4 in a little bit.
      omv 5.3.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.4
      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!
    • th0m_89 wrote:

      Maybe it should be added to the manual for the time being.
      Good to hear. I already put it in the install script. So, no need to adjust the manual :) Still need to figure out what changed in the openmediavault package itself.
      omv 5.3.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.4
      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!
    • ZotteI wrote:

      How do I apply the script? With wget -O? Or manually pasting it in the terminal
      Did you already follow the directions and are looking for a fix to the web interface issue? If so, just run the two commands I posted above. Otherwise, follow the directions in the guide again.
      omv 5.3.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.4
      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!
    • Trouble installing OMV on pi4 : No access to GUI

      ryecoaaron wrote:

      ZotteI wrote:

      How do I apply the script? With wget -O? Or manually pasting it in the terminal
      Did you already follow the directions and are looking for a fix to the web interface issue? If so, just run the two commands I posted above. Otherwise, follow the directions in the guide again.
      I'll try that!

      Gesendet von meinem CLT-L29 mit Tapatalk
    • Hallo,

      After re-installing OMV5 it worked! Thanks!

      Now I have the problem, if I want to save a setting in the web-gui, I always get this error!



      Shell-Script

      1. Fehler #0:
      2. OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run collectd 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
      3. if not isinstance(exes, collections.Iterable):
      4. raspberrypi:
      5. Data failed to compile:
      6. ----------
      7. Rendering SLS 'base:omv.deploy.collectd.plugins.disk' failed: Problem running salt function in Jinja template: A valid link was not specified.; line 54
      8. ---
      9. [...]
      10. {% if salt['mount.is_mounted'](mountpoint.dir) %}
      11. {% set parent_device_file = salt['omv_utils.get_fs_parent_device_file'](mountpoint.fsname) %}
      12. {% if parent_device_file %}
      13. # Get the canonical device file to extract the device name. The collectd disk
      14. # plugin wants this format: https://collectd.org/wiki/index.php/Plugin:Disk
      15. {% set canonical_parent_device_file = salt['file.readlink'](parent_device_file, True) %} <======================
      16. # Extract the device name from '/dev/xxx'.
      17. {% set _ = disks.append(canonical_parent_device_file[5:]) %}
      18. {% endif %}
      19. {% endif %}
      20. {% endfor %}
      21. [...]
      22. --- in /usr/share/php/openmediavault/system/process.inc:182
      23. Stack trace:
      24. #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
      25. #1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
      26. #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
      27. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      28. #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      29. #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusVA...', '/tmp/bgoutputvN...')
      30. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      31. #7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      32. #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
      33. #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      34. #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      35. #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      36. #12 {main}
      Display All
      Do you have an idea how to solve this?

      Best regards
      uwe from berlin/de
    • ryecoaaron wrote:

      Haven't tried the rpi yet but on a rock64, I had to do the following to fix the web interface (install script will do this as well).

      omv-salt deploy run nginx
      omv-salt deploy run phpfpm

      I will try the RPi4 in a little bit.
      Happy new year to everybody!

      I'm the one who got hit by github.com/openmediavault/openmediavault/issues/457: NGinx wasn't available after dist-upgrading and changing a parameter. Recently I found the reason for the issue. By changing this single parameter, not only that parameter is changed, but the whole OMV config is merely rewritten. Expecially this hunk is of interest:

      Source Code

      1. @@ -26,19 +29,19 @@
      2. location ~ \.php$ {
      3. try_files $uri =404;
      4. fastcgi_split_path_info ^(.+\.php)(/.+)$;
      5. - fastcgi_pass unix:/var/run/php-fpm-openmediavault-webgui.sock;
      6. + fastcgi_pass unix:/run/php/php7.3-fpm-openmediavault-webgui.sock;
      7. fastcgi_index index.php;
      8. fastcgi_read_timeout 60s;
      9. include fastcgi.conf;
      10. fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
      11. }
      Display All
      It is from file /etc/nginx/sites-available/openmediavault-webgui: the config now refers to a socket file, which does not exist and hence nginx fails to run correctly. Running your two commands solves the issue permantly, as the socket file does now exists.

      However I'd expect that the Debian package too creates all socket files it potentially needs. I did not test yet w/ 5.2.2, but it failed w/ 5.2.1 and I don't see an commit on git, which promises a fix in 5.2.2. Are there plan to introduce the fix into the Debian packages too?