Constant Reboots After Latest Upgrade

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

    • Constant Reboots After Latest Upgrade

      I did an update through the GUI about 10 hours ago and then added a cron job to reboot my BMC since it sucks and crashes about every 24 hours so I set it to reboot it every 12 hours, the only option in the GUI was Reboot, shutdown or something else which I can't remember. About two minutes after I hit save, my server rebooted....and continued to do so for the next half hour or so. It would boot up successfully with no issues, start up everything OMV related, then proceed to reboot about 1.5 to 2 minutes later. I managed to shell in and remove the command from root's crontab...which didn't stop it. Just to make sure I checked the GUI as well as quickly as I could and it didn't...and then it rebooted. I booted into recovery mode and it was stable, so I removed root's cron, admin's cron (the user I was logged into the GUI as) and my own user just for good measure... and that seemed to fix it...until about 10 hours later when it rebooted again.

      I'm currently at work, so I can't really look anything up relating to versions since I shutdown my server since it kept rebooting again and my roommate told me my computer was making noise, and it's currently 1 AM.

      The only info I could grab is that I'm running 4.18.0-0.bpo.3-amd64 and that my server was stable for weeks (new to OMV) before I updated today, previous uptime was 8 days prior to upgrading the kernel. I'll be able to grab more info when I get home in about 8 hours.
    • Installed OMV packages:

      Source Code

      1. openmediavault/arrakis,arrakis,now 4.1.16-2 all [installed]
      2. openmediavault-diskstats/arrakis,arrakis,now 4.0.2-1 all [installed]
      3. openmediavault-docker-gui/stretch,now 4.1.1 all [installed]
      4. openmediavault-downloader/stretch,now 3.6.2 all [installed]
      5. openmediavault-keyring/arrakis,arrakis,now 1.0 all [installed]
      6. openmediavault-omvextrasorg/stretch,now 4.1.13 all [installed]
      7. openmediavault-plexmediaserver/stretch,now 3.8.2 all [installed]
      8. openmediavault-resetperms/stretch,now 3.3 all [installed]
      9. openmediavault-shellinabox/stretch,now 3.4 all [installed]
      10. openmediavault-transmissionbt/stretch,now 4.0 all [installed]
      11. openmediavault-zfs/stretch,now 4.0.4 amd64 [installed]
      Display All
      I also enabled persistent journal logging, but that didn't really provide anything useful

      Source Code

      1. Dec 29 17:07:49 mediavault sudo[5251]: [b] bran : TTY=pts/0 ; PWD=/home/bran ; USER=root ; COMMAND=/bin/journalctl -b 1[/b]
      2. Dec 29 17:07:49 mediavault sudo[5251]: pam_unix(sudo:session): session opened for user root by bran(uid=0)
      3. Dec 29 17:07:49 mediavault sudo[5251]: pam_unix(sudo:session): session closed for user root
      4. Dec 29 17:08:06 mediavault sudo[26293]: [b] bran : TTY=pts/0 ; PWD=/home/bran ; USER=root ; COMMAND=/bin/journalctl -b 2[/b]
      5. Dec 29 17:08:06 mediavault sudo[26293]: pam_unix(sudo:session): session opened for user root by bran(uid=0)
      6. Dec 29 17:09:01 mediavault CRON[11660]: pam_unix(cron:session): session opened for user root by (uid=0)
      7. Dec 29 17:09:01 mediavault CRON[11677]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
      8. Dec 29 17:09:01 mediavault CRON[11660]: pam_unix(cron:session): session closed for user root
      9. Dec 29 17:09:01 mediavault systemd[1]: Starting Clean php session files...
      10. Dec 29 17:09:01 mediavault systemd[1]: Started Clean php session files.
      11. [bran@mediavault ~]$ sudo journalctl -b 1
      12. -- Logs begin at Sat 2018-12-29 00:44:42 EST, end at Sat 2018-12-29 17:11:38 EST. --
      13. Dec 29 00:44:42 mediavault systemd[3505]: pam_unix(systemd-user:session): session closed for user bran
      14. Dec 29 00:44:42 mediavault systemd[3503]: Starting Exit the Session...
      15. Dec 29 00:44:42 mediavault systemd[3503]: Stopped target Timers.
      16. Dec 29 00:44:42 mediavault systemd[3503]: Received SIGRTMIN+24 from PID 9781 (kill).
      17. [bran@mediavault ~]$ sudo journalctl -b
      18. -- Logs begin at Sat 2018-12-29 00:44:42 EST, end at Sat 2018-12-29 17:11:48 EST. --
      19. Dec 29 16:59:23 mediavault kernel: mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x5000000080000000), phys(16)
      20. Dec 29 16:59:23 mediavault kernel: [b]random: fast init done[/b]
      21. Dec 29 16:59:23 mediavault kernel: [b]scsi 0:0:0:0: Direct-Access ATA WDC WD60EFRX-68L 0A82 PQ: 0 ANSI: 6[/b]
      22. Dec 29 16:59:23 mediavault kernel: scsi 0:0:0:0: SATA: handle(0x0011), sas_addr(0x4433221100000000), phy(0), device_name(0x0000000000000000)
      23. Dec 29 16:59:23 mediavault kernel: scsi 0:0:0:0: enclosure logical id (0x5000000080000000), slot(3)
      24. Dec 29 16:59:23 mediavault kernel: scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
      25. Dec 29 16:59:23 mediavault kernel: [b]scsi 0:0:1:0: Direct-Access ATA WDC WD60EFRX-68L 0A82 PQ: 0 ANSI: 6[/b]
      Display All

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

    • Well it's not an issue with latest kernel or the watchdog service, because I booted up bpo.1 instead of bpo.3 and disabled the watchdog service and it was up about 7 hours and rebooted. Then just rebooted again once it came back up!

      This is getting ridiculous....I'm about to switch back to Arch because I had zero issues with it, a GUI isn't this important....