Installing OVM 4.x on Rasbian 9 Stretch Raspberry Pi Model B Rev 2

    • OMV 4.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Installing OVM 4.x on Rasbian 9 Stretch Raspberry Pi Model B Rev 2

      sudo lshw


      Code:

      Source Code

      1. Setting up php7.0-fpm (7.0.33-0+deb9u1) ...
      2. NOTICE: Not enabling PHP 7.0 FPM by default.
      3. NOTICE: To enable PHP 7.0 FPM in Apache2 do:
      4. NOTICE: a2enmod proxy_fcgi setenvif
      5. NOTICE: a2enconf php7.0-fpm
      6. NOTICE: You are seeing this message because you have apache2 package installed.
      7. Job for php7.0-fpm.service failed because a fatal signal was delivered to the control process.
      8. See "systemctl status php7.0-fpm.service" and "journalctl -xe" for details.
      9. invoke-rc.d: initscript php7.0-fpm, action "start" failed.
      10. * php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
      11. Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
      12. Active: failed (Result: signal) since Tue 2019-01-29 19:39:30 CET; 204ms ago
      13. Docs: man:php-fpm7.0(8)
      14. Process: 5637 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=killed, signal=ILL)
      15. Main PID: 5637 (code=killed, signal=ILL)
      16. Jan 29 19:39:30 raspberrypi systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
      17. Jan 29 19:39:30 raspberrypi systemd[1]: php7.0-fpm.service: Main process exited, code=killed, status=4/ILL
      18. Jan 29 19:39:30 raspberrypi systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
      19. Jan 29 19:39:30 raspberrypi systemd[1]: php7.0-fpm.service: Unit entered failed state.
      20. Jan 29 19:39:30 raspberrypi systemd[1]: php7.0-fpm.service: Failed with result 'signal'.
      21. dpkg: error processing package php7.0-fpm (--configure):
      22. subprocess installed post-installation script returned error exit status 1
      23. Setting up acpid (1:2.0.28-1) ...
      24. Job for acpid.service failed because of unavailable resources or another system error.
      25. See "systemctl status acpid.service" and "journalctl -xe" for details.
      26. invoke-rc.d: initscript acpid, action "start" failed.
      27. * acpid.service - ACPI event daemon
      28. Loaded: loaded (/lib/systemd/system/acpid.service; disabled; vendor preset: enabled)
      29. Active: failed (Result: resources)
      30. Jan 29 19:39:48 raspberrypi systemd[1]: Failed to start ACPI event daemon.
      31. Jan 29 19:39:48 raspberrypi systemd[1]: acpid.service: Failed with result 'resources'.
      32. Jan 29 19:39:52 raspberrypi systemd[1]: acpid.service: Got more than one socket.
      33. Jan 29 19:39:52 raspberrypi systemd[1]: acpid.service: Failed to run 'start' task: Invalid argument
      34. Jan 29 19:39:52 raspberrypi systemd[1]: Failed to start ACPI event daemon.
      35. Jan 29 19:39:52 raspberrypi systemd[1]: acpid.service: Failed with result 'resources'.
      36. Jan 29 19:39:53 raspberrypi systemd[1]: acpid.service: Got more than one socket.
      37. Jan 29 19:39:53 raspberrypi systemd[1]: acpid.service: Failed to run 'start' task: Invalid argument
      38. Jan 29 19:39:53 raspberrypi systemd[1]: Failed to start ACPI event daemon.
      39. Jan 29 19:39:53 raspberrypi systemd[1]: acpid.service: Failed with result 'resources'.
      Display All



      TEXT
    • This version of the RPi hasn't been supported since the early OMV 2.x days. It doesn't matter if you install Debian first since php-pam is compiled for newer cpus. omv-extras doesn't support armel at all. That RPi is way too slow for anything anyway.
      omv 4.1.22 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!
    • Users Online 1

      1 Guest