OMV Inexplicably Shuts Down Daily @ 02:00

1st Official Post

    My OMV 6.9.16-1 running as a VM on proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve) has shutdown inexplicably at about 02:00 two days in a row. Historically OMV (and Promox, and all the other VMs & CTs) run forever without issue. I've gone up to a year without a restart.


    Several days ago I applied all available outstanding OMV updates. It had been a while since I updated OMV. I beleive there were MANY updates. Dozens? I didnt really comit it to memory. I YOLOd it. I feel very confident in my daily backups SnapRAID, etc so... Maybe an update did something.


    Anyway, I'm very fresh to linux & homelabbing. I did search and search, but this is one of those once per 5 years where I need help.


    I did check the OMV Diagnostics > System Logs > Logs, but dont see anything.


    It doesnt appear that Promox commanded the shutdown either.


    Can someone please point me in the right direct for where & which logs to check? Any ideas? I looked at every log in /var/log and they all just end by 02:00 and start back up at 16:00 when I started the VM after noticing it off again.


    Syslog:


    Messages:


    Kern.log

  • crashtest

    Approved the thread.
    Quote from fbeye

    Are you in an Apartment Complex?

    No, but I am super curious what being in one can do? If you're thinking power issues, my network is on a 1500VA UPS @ 15% load with 4 hours of battery runtime, and there have not been any power interuptions (according to the APC log) for weeks.


    Im in a house. All other 3 VMs and 3 CTs remain up. Just the OMV VM shuts down. Twice now 2 days in a row.

    I ask this both to help, but share a story.


    We had a customer who called in every day about her internet dropping same day for several weeks. We replaced the modem, wiring, changed the computer card etc, nothing. One day I happened to be downstairs and my co-worker was in the house and he calls me, "it just went down on the dot". It just so happened that their apartment was right next to the pool and so it was that whenever the soda machine cooler would turn on it would drain enough power it dropped her modem.

    Just, made me remember that.

    Oh boy, it shut down again, but at 20:00. It didnt even wait 'till 02:00. It shutdown 6hrs eariler than i thought it might.


    Kern.log & others have no interesting (I beleive) action in the hours before shutdown.


    Here is the syslog from the last 2.5hrs before shutdown:


    Perhaps a Cron job is doing bad stuff? These Crons didn't like up with the last shutdown. Hmmm

    • Official Post

    Check the output of


    journalctl -b -1 -e


    It will output the logs in the journal of the boot before the current one. You can read here about the command:

    journalctl

    If the last boot was not ended by the unwanted shutdown, try another boot, e.g. with


    journalctl -b -2 -e

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login