Proxmox decided to make a shutdown... no interaction from outside.

M

mholux

Member
Aug 26, 2020
11
0
6
63
Luxembourg
Proxmox by itself performed a shutdown, closing correctly running VM's, stoping all services and shutding down the server.
I had to start it up using the power button of the server.
No clue why Proxmox performed the shutdown.
'
Sep 08 17:28:01 pve1 systemd[1]: Finished Proxmox VE replication runner. Sep 08 17:29:01 pve1 systemd[1]: Starting Proxmox VE replication runner... Sep 08 17:29:01 pve1 systemd[1]: pvesr.service: Succeeded. Sep 08 17:29:01 pve1 systemd[1]: Finished Proxmox VE replication runner. Sep 08 17:30:01 pve1 systemd[1]: Starting Proxmox VE replication runner... Sep 08 17:30:01 pve1 systemd[1]: pvesr.service: Succeeded. Sep 08 17:30:01 pve1 systemd[1]: Finished Proxmox VE replication runner. Sep 08 17:31:01 pve1 systemd[1]: Starting Proxmox VE replication runner... Sep 08 17:31:01 pve1 systemd[1]: pvesr.service: Succeeded. Sep 08 17:31:01 pve1 systemd[1]: Finished Proxmox VE replication runner. Sep 08 17:32:01 pve1 systemd[1]: Starting Proxmox VE replication runner... Sep 08 17:32:01 pve1 systemd[1]: pvesr.service: Succeeded. Sep 08 17:32:01 pve1 systemd[1]: Finished Proxmox VE replication runner. Sep 08 17:32:43 pve1 pvedaemon[3580933]: <root@pam> successful auth for user 'root@pam' Sep 08 17:32:49 pve1 systemd[1]: 100.scope: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped 100.scope. Sep 08 17:32:49 pve1 systemd[1]: 100.scope: Consumed 1d 11h 28min 10.987s CPU time. Sep 08 17:32:49 pve1 systemd[1]: 102.scope: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped 102.scope. Sep 08 17:32:49 pve1 systemd[1]: 102.scope: Consumed 2d 23h 25min 53.259s CPU time. Sep 08 17:32:49 pve1 systemd[1]: Removed slice qemu.slice. Sep 08 17:32:49 pve1 systemd[1]: qemu.slice: Consumed 1month 4d 10h 31min 16.073s CPU time. Sep 08 17:32:49 pve1 systemd[1]: Removed slice system-modprobe.slice. Sep 08 17:32:49 pve1 systemd[1]: Stopped target Graphical Interface. Sep 08 17:32:49 pve1 systemd[1]: Stopped target Multi-User System. Sep 08 17:32:49 pve1 systemd[1]: Stopped target Login Prompts. Sep 08 17:32:49 pve1 systemd[1]: Stopped target RPC Port Mapper. Sep 08 17:32:49 pve1 systemd[1]: Stopped target Timers. Sep 08 17:32:49 pve1 systemd[1]: apt-daily-upgrade.timer: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped Daily apt upgrade and clean activities. Sep 08 17:32:49 pve1 systemd[1]: apt-daily.timer: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped Daily apt download activities. Sep 08 17:32:49 pve1 systemd[1]: e2scrub_all.timer: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems. Sep 08 17:32:49 pve1 systemd[1]: fstrim.timer: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped Discard unused blocks once a week. Sep 08 17:32:49 pve1 systemd[1]: logrotate.timer: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped Daily rotation of log files. Sep 08 17:32:49 pve1 systemd[1]: man-db.timer: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped Daily man-db regeneration. Sep 08 17:32:49 pve1 systemd[1]: pve-daily-update.timer: Succeeded. Sep 08 17:32:49 pve1 systemd[1]: Stopped Daily PVE download activities.
 
Just before, someone logged in to the Proxmox web GUI with the root account. If it was an automated script, I would expect it to login via SSH, not the web GUI. Without any other information, I assume that someone clicked the wrong button and did a shutdown of the host instead of a shutdown of a VM. If you don't remember logging in at 17:32:43 (I don't know if the system was set to the right timezone), then maybe someone else did.
 
Hi, the system is more a Q&A system to see if Proxmox could also be used for Production. I am the only one who has access to the system.
So there is no one else who has the password to access.
 
mholux said:
Hi, the system is more a Q&A system to see if Proxmox could also be used for Production. I am the only one who has access to the system.
So there is no one else who has the password to access.
Click to expand...
If it was not you and nobody else could have guessed the password, then I cannot explain this log message: Sep 08 17:32:43 pve1 pvedaemon[3580933]: <root@pam> successful auth for user 'root@pam'. However, if someone has root acccess, they could also have changed the logs and could have hidden this message. Maybe someone else here has an alternative explanation?
 
Hi,
I just had the same experience.
Proxmox suddenly decided to shut down.
the only thing I see in logs is:
Code: 
Oct 19 10:57:01 pvenas systemd[1]: Finished Proxmox VE replication runner.
Oct 19 10:58:01 pvenas systemd[1]: Starting Proxmox VE replication runner...
Oct 19 10:58:01 pvenas systemd[1]: pvesr.service: Succeeded.
Oct 19 10:58:01 pvenas systemd[1]: Finished Proxmox VE replication runner.
Oct 19 10:58:58 pvenas systemd[1]: 100.scope: Succeeded.
Oct 19 10:58:58 pvenas systemd[1]: Stopped 100.scope.
Oct 19 10:58:58 pvenas systemd[1]: 100.scope: Consumed 9h 31min 21.768s CPU time.
Oct 19 10:58:58 pvenas systemd[1]: 102.scope: Succeeded.
Oct 19 10:58:58 pvenas systemd[1]: Stopped 102.scope.
Oct 19 10:58:58 pvenas systemd[1]: 102.scope: Consumed 1d 21h 32min 5.038s CPU time.
Oct 19 10:58:58 pvenas systemd[1]: Removed slice qemu.slice.
Oct 19 10:58:58 pvenas systemd[1]: qemu.slice: Consumed 2d 7h 3min 26.807s CPU time.
Oct 19 10:58:58 pvenas systemd[1]: Removed slice system-modprobe.slice.
Oct 19 10:58:58 pvenas systemd[1]: Stopped target Graphical Interface.
Oct 19 10:58:58 pvenas systemd[1]: Stopped target Multi-User System.
the shutdown started with this line:

Code: 
Oct 19 10:58:58 pvenas systemd[1]: 100.scope: Succeeded.

This is a home system, nobody could/did access it.
What could it be?

Thanks
 
You must log in or register to reply here.
Top Bottom