Standalone server with pve-ha-lrm reboot for 3 times

[Gilberto Ferreira]

Has anyone had this problem?

grep reboot / var / log / syslog
Nov 25 09:59:13 proxmox01 pve-ha-lrm [1384]: reboot LRM, stop and freeze all services
Nov 25 10:04:45 proxmox01 cron [1398]: (CRON) INFO (Running @reboot jobs)
Nov 25 10:12:00 proxmox01 pve-ha-lrm [1485]: reboot LRM, stop and freeze all services
Nov 25 10:16:38 proxmox01 cron [1432]: (CRON) INFO (Running @reboot jobs)
Nov 25 10:24:48 proxmox01 pve-ha-lrm [1510]: reboot LRM, stop and freeze all services
Nov 25 10:30:08 proxmox01 cron [1303]: (CRON) INFO (Running @reboot jobs)

Server restarted 3 times.
First I assumed that could be hardware problem.
But consulting the log now I saw that this pve-ha-lrm really had nothing!
The only suspicious thing would be to install the phoronix-test-suite, but I doubt that it would cause the server to restart ....

 

[fiona]

Hi,
were you able to figure out the problem in the meantime? Otherwise, please check your cron jobs:

cd /etc/
grep -R "@reboot" cron*

 

[Gilberto Ferreira]

Hi,
were you able to figure out the problem in the meantime? Otherwise, please check your cron jobs:

cd /etc/
grep -R "@reboot" cron*

Hi

It's seems the issue was some problem with the DC, power outage or something like that. I do not have another issues since.
Here's the output of the command
cd /etc/
proxmox01:/etc# grep -R "@reboot" cron*
proxmox01:/etc#

Thanks anyway.

 

[fiona]

Ah, I was confusing the order when reading the log and didn't see that the cron message came after the reboot.

In any case, glad to hear that the problem was solved!

 

[Tsvyatko Kriviradev]

Hello, I am heaving exactly the same problem.
Only one of my servers has it.

root@pves01:/etc# grep reboot /var/log/syslog
Apr 24 23:15:47 pves01 kernel: [   17.319110] softdog:              soft_reboot_cmd=<not set> soft_active_on_boot=0
Apr 24 23:15:57 pves01 cron[1891]: (CRON) INFO (Running @reboot jobs)
Apr 25 02:54:46 pves01 kernel: [   17.777139] softdog:              soft_reboot_cmd=<not set> soft_active_on_boot=0
Apr 25 02:54:56 pves01 cron[1893]: (CRON) INFO (Running @reboot jobs)

In the syslog of the pve server I can see following lines.

Apr 25 02:34:27 pves01 pmxcfs[1819]: [status] notice: received log
Apr 25 02:34:32 pves01 pmxcfs[1819]: [status] notice: received log
Apr 25 02:35:01 pves01 CRON[66824]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 25 02:35:01 pves01 CRON[66826]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 25 02:35:01 pves01 CRON[66824]: pam_unix(cron:session): session closed for user root
Apr 25 02:41:19 pves01 kernel: perf: interrupt took too long (4316 > 2500), lowering kernel.perf_event_max_sample_rate to 46250
Apr 25 02:45:01 pves01 CRON[77470]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 25 02:45:01 pves01 CRON[77471]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 25 02:45:01 pves01 CRON[77470]: pam_unix(cron:session): session closed for user root
-- Reboot --

root@pves01:/etc# grep -R "@reboot" cron*
root@pves01:/etc#

According this --> https://serverfault.com/questions/883370/cron-running-reboot-jobs

it is related to the power supply units. Or is there any other way we can identify unexpected reboots?