OMV won't start after doing updates

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

    • OMV won't start after doing updates

      -- Logs begin at Thu 2019-08-15 14:37:22 EDT, end at Thu 2019-08-15 14:49:22 EDT
      . --
      Aug 15 14:48:51 nas monit[1072]: 'omv-engined' trying to restart
      Aug 15 14:48:51 nas monit[1072]: 'omv-engined' start: '/bin/systemctl start open
      mediavault-engined'
      Aug 15 14:48:51 nas systemd[1]: Starting The OpenMediaVault engine daemon that p
      rocesses the RPC request...
      -- Subject: Unit openmediavault-engined.service has begun start-up
      -- Defined-By: systemd
      -- Support: debian.org/support
      --
      -- Unit openmediavault-engined.service has begun starting up.
      Aug 15 14:48:51 nas systemd[1]: openmediavault-engined.service: Supervis
      ing process 5588 which is not our child. We'll most likely not notice when it ex
      its.
      Aug 15 14:48:51 nas systemd[1]: Started The OpenMediaVault engine daemon that pr
      ocesses the RPC request.
      -- Subject: Unit openmediavault-engined.service has finished start-up
      -- Defined-By: systemd
      -- Support: debian.org/support
      --
      -- Unit openmediavault-engined.service has finished starting up.
      --
      -- The start-up result is done.
      Aug 15 14:48:51 nas omv-engined[5588]: PHP Fatal error: Uncaught Error:
      Class 'DOMDocument' not found in /usr/share/php/openmediavault/config/databaseba
      ckend.inc:110
      Stack trace:
      #0 /usr/share/php/openmediavault/
      config/database.inc(34): OMV\Config\DatabaseBackend->load()
      #1 /usr/share/php/openmediavault/
      config/database.inc(44): OMV\Config\Database->__construct()
      #2 /usr/share/openmediavault/engi
      ned/rpc/docker.inc(66): OMV\Config\Database::getInstance()
      #3 /usr/share/php/openmediavault/
      rpc/servicemanager.inc(40): OMVRpcServiceDocker->__construct()
      #4 /usr/share/php/openmediavault/
      rpc/servicemanager.inc(51): OMV\Rpc\ServiceManager->__construct()
      #5 /usr/sbin/omv-engined(377): OM
      V\Rpc\ServiceManager::getInstance()
      #6 {main}
      thrown in /usr/share/php/openme
      diavault/config/databasebackend.inc on line 110
      Aug 15 14:48:51 nas systemd[1]: openmediavauAug 15 14:48:51 nas systemd[1]: openmediavault-engined.service: Unit ent
      ered failed state.
      Aug 15 14:48:51 nas systemd[1]: openmediavault-engined.service: Failed w
      ith result 'exit-code'.


      Aug 15 14:49:22 nas monit[1072]: 'omv-engined' failed to start (exit sta
      tus 0) -- no outputlt-engined.service: Main pro[/b]
      cess exited, code=exited, status=255/n/a


      Any ideas? My dockers all started and are working... just the OMV website is throwing the 500 error.

      Thanks for any help!
    • It seems the php-xml package is missing.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit