OMV does not start anymore...

    • OMV 4.x
    • OMV does not start anymore...

      Had Openmediavault up and running, then installed docker and zoneminder, everything was fine. Played around with zoneminder yesterday and at some point the openmediavault web interface was gone. Looking at /var/www/openmediavault showed that the directory was empty - all the php files where gone 8|

      And even worse:

      Source Code

      1. root@Servomat:~# omv-firstaid
      2. -bash: omv-firstaid: command not found.

      So ist looks like path or binaries got messed up, too. I just don't have a clue what's going on here...

      Edit: Zoneminder is up and running, and as it is running as a docker image and docker is installed to OMV, this seems to be even more strange :S


      Thanks for reading...

      The post was edited 1 time, last by yo_eddie ().

    • yo_eddie wrote:

      There seem to be problems with new kernels and omvextras sometimes:
      The kernels and omv-extras have nothing to do with omv-firstaid. if omv-firstaid doesn't exist, that means the openmediavault package itself is not installed (or completely installed). What is the output of: dpkg -l | grep openm

      yo_eddie wrote:

      Even worse, what about the OMV config? RAID data?
      If the /etc/openmediavault/config.xml database is gone, your config is gone. You could restore from backup if you have one. Raid data will not be removed because of OMV being uninstalled. The data disks should be untouched. If you have to reinstall OMV, just mount the filesystems, recreate users and shared folders, and setup services again.
      omv 4.1.17 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • ryecoaaron wrote:

      yo_eddie wrote:

      There seem to be problems with new kernels and omvextras sometimes:
      The kernels and omv-extras have nothing to do with omv-firstaid. if omv-firstaid doesn't exist, that means the openmediavault package itself is not installed (or completely installed). What is the output of: dpkg -l | grep openm

      yo_eddie wrote:

      Even worse, what about the OMV config? RAID data?
      If the /etc/openmediavault/config.xml database is gone, your config is gone. You could restore from backup if you have one. Raid data will not be removed because of OMV being uninstalled. The data disks should be untouched. If you have to reinstall OMV, just mount the filesystems, recreate users and shared folders, and setup services again.
      Thank you for your help!

      The output looks like this (not good):

      Source Code

      1. root@Servomat:~# systemctl status openmediavault-engined
      2. ● openmediavault-engined.service
      3. Loaded: masked (/dev/null; bad)
      4. Active: inactive (dead)
    • Source Code

      1. root@Servomat:~# systemctl unmask openmediavault-engined
      2. Removed /etc/systemd/system/openmediavault-engined.service.
      3. root@Servomat:~# service openmediavault-engined start
      4. root@Servomat:~# systemctl status openmediavault-engined
      5. ● openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request
      6. Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled; vendor preset: enabled)
      7. Active: active (running) since Sat 2018-12-01 15:07:16 CET; 28s ago
      8. Process: 2655 ExecStart=/usr/sbin/omv-engined (code=exited, status=0/SUCCESS)
      9. Main PID: 2657 (omv-engined)
      10. Tasks: 1 (limit: 4915)
      11. CGroup: /system.slice/openmediavault-engined.service
      12. └─2657 omv-engined
      13. Dez 01 15:07:16 Servomat systemd[1]: Starting The OpenMediaVault engine daemon that processes the RPC request...
      14. Dez 01 15:07:16 Servomat systemd[1]: openmediavault-engined.service: Supervising process 2657 which is not our child. We'll most likely not notice when it exits.
      15. Dez 01 15:07:16 Servomat systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request.
      Display All
      8o

      Webinterface working now. :thumbsup:

      Now I have to workout how to get Docker back into the OMV interface. Docker is still running, as is Zoneminder.
      I really would like to know how all this trouble was caused. Until I installed Docker / ZM I never had any issues with OMV 4.

      The post was edited 1 time, last by yo_eddie ().

    • It's possible to have Docker installed on the command line, without the Docker plugin. How that happened or why the Docker plugin was installed but is not in the GUI now, may be next to impossible to to explain (especially from remote).

      When all is working well, it's best to clone your boot drive. If something like this happens in the future, having a known good/working fallback (the clone) is a lot easier than trying to figure out the "inexplicable".

      The first thing I'd do is backup the OS then:
      You might be able to reinstall the Docker plugin, where the image and the running container should reappear in the plugin. (And if something goes sideways you'd have your clone.)

      If you're running a RAID array without backup - losing your data is just a matter of time.
      Start thinking "Backup". Sooner is better than later. Later may be too late.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 1 time, last by flmaxey: edit ().

    • I think I have figured out what actually caused all the trouble - it started after generating / activating a "purge when full" filter, set to 70%. Though ZM had almost 2TB to write to, the filter seems to be dodgy:

      • Capturing events did not work properly, some events were not recorded
      • After viewing a event, it was deleted instantly
      • It looks like the filter did not only delete the clips, but ran amok on my system
      Maybe I have configured the filter the wrong way or maybe there were some other config effects - but without this filter everything seems to work just fine.
      As the ZM manual states - be careful with the "Purge when full" filter. Seems to be even more important if you run ZM with OMV...
    • yo_eddie wrote:

      it started after generating / activating a "purge when full" filter, set to 70%
      OK.. :) Since I'm not aware of a "purge when full - filter", in OMV, do tell me what it is.
      A script? Something to do with a Docker?

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk