Service fail to start after Power outage

    • OMV 3.x
    • Resolved

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

    • Service fail to start after Power outage

      I had a brief power outage yesterday (No, I have no UPS yet...) and when the power was back on, Docker, Sabnzbd and Sickbeard services fails to start.
      I tried to uninstall and install them again, but that does not help.

      This is the exception I get when I try to start Sabnzbd:

      Source Code

      1. Error #0:
      2. exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start sabnzbd.service 2>&1' with exit code '1': Job for sabnzbd.service failed. See 'systemctl status sabnzbd.service' and 'journalctl -xn' for details.' in /usr/share/php/openmediavault/system/
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/system/ OMV\System\Process->execute(Array, 1)
      5. #1 /usr/share/php/openmediavault/system/ OMV\System\SystemCtl->exec('start', NULL, false)
      6. #2 /usr/share/openmediavault/engined/module/ OMV\System\SystemCtl->enable(true)
      7. #3 /usr/share/openmediavault/engined/rpc/ OMV\Engined\Module\Sabnzbd->startService()
      8. #4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      9. #5 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusa1...', '/tmp/bgoutputLR...')
      12. #8 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      13. #9 /usr/share/openmediavault/engined/rpc/ OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      14. #10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      15. #11 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
      16. #12 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      17. #13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      18. #14 {main}
      Display All

      And when I try io reinstall Docker I get this error:

      Source Code

      1. php5_invoke: Enable module imagick for cli SAPI
      2. php5_invoke: Enable module imagick for cgi SAPI
      3. php5_invoke: Enable module imagick for fpm SAPI
      4. dpkg: dependency problems prevent configuration of openmediavault-docker-gui:
      5. openmediavault-docker-gui depends on docker-engine (>= 1.10); however:
      6. Package docker-engine is not configured yet.
      7. dpkg: error processing package openmediavault-docker-gui (--configure):
      8. dependency problems - leaving unconfigured
      9. Processing triggers for libc-bin (2.19-18+deb8u9) ...
      10. Processing triggers for systemd (215-17+deb8u7) ...
      11. Processing triggers for openmediavault (3.0.79) ...
      12. Updating file permissions ...
      13. Purging internal cache ...
      14. Restarting engine daemon ...
      15. Errors were encountered while processing:
      16. docker-engine
      17. openmediavault-docker-gui
      Display All

      How can I do a cleanup so I can reinstall these plugins? I suspect that Sickrage have the same issue, so I start with these two.

      "Note:* A while back I installed some things to python, which means I have both Python 2.7 and 3.4 installed. I have not restarted OMV since that upgrade. Could that be an issue?
    • Completely different problem. When I posted the above, I got this message from OMV forum:

      Fatal error: An error occured. Sorry.

      ID: f98ccb67209bf0998708376facbcab0d6eaf71cd
      Please send the ID above to the site administrator.
      The error message can be looked up at “ACP » Logs » Errors”.

      But when I logged back in here from another browser, it had been posted OK.