PVE automatically reboots at 3 a.m. every day

R

Rick.Jiang

New Member
Oct 9, 2023
7
0
1
Hello everyone, I have encountered a problem. I have set a schedule to perform backup at three o'clock in the morning every day. However, in the past few days, I found that as long as the backup time comes, it will automatically reboot.... I looked at the log but I don't know. What is the reason? It has been normal for the past month, but this situation has only occurred in the past few days.

Code: 
Dec 04 02:58:41 pve03 corosync[5814]:   [MAIN  ] Completed service synchronization, ready to provide service.
Dec 04 03:00:04 pve03 pvescheduler[3304061]: <root@pam> starting task UPID:pve03:00326A7E:00814213:656CDE44:vzdump::root@pam:
Dec 04 03:00:04 pve03 pvescheduler[3304062]: INFO: starting new backup job: vzdump --all 1 --mode snapshot --mailnotification always --storage pve_backup --mailto itd@tyxuan.com.vn --prune-backups 'keep-last=7' --compress zstd --node pve03 --notes-template '{{node}}-{{vmid}}-{{guestname}}' --quiet 1
Dec 04 03:00:04 pve03 pvescheduler[3304062]: INFO: Starting Backup of VM 101 (qemu)
Dec 04 03:00:04 pve03 pmxcfs[5746]: [status] notice: received log
Dec 04 03:00:04 pve03 systemd[1]: Started 101.scope.
Dec 04 03:00:06 pve03 kernel: device tap101i0 entered promiscuous mode
Dec 04 03:00:06 pve03 kernel: vmbr0: port 5(fwpr101p0) entered blocking state
Dec 04 03:00:06 pve03 kernel: vmbr0: port 5(fwpr101p0) entered disabled state
Dec 04 03:00:06 pve03 kernel: device fwpr101p0 entered promiscuous mode
Dec 04 03:00:06 pve03 kernel: vmbr0: port 5(fwpr101p0) entered blocking state
Dec 04 03:00:06 pve03 kernel: vmbr0: port 5(fwpr101p0) entered forwarding state
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Dec 04 03:00:06 pve03 kernel: device fwln101i0 entered promiscuous mode
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 1(fwln101i0) entered forwarding state
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 2(tap101i0) entered blocking state
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 2(tap101i0) entered disabled state
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 2(tap101i0) entered blocking state
Dec 04 03:00:06 pve03 kernel: fwbr101i0: port 2(tap101i0) entered forwarding state
Dec 04 03:00:44 pve03 corosync[5814]:   [TOTEM ] Token has not been received in 3225 ms
Dec 04 03:00:47 pve03 corosync[5814]:   [QUORUM] Sync members[4]: 1 2 3 4
Dec 04 03:00:47 pve03 corosync[5814]:   [TOTEM ] A new membership (1.fce) was formed. Members
Dec 04 03:00:47 pve03 corosync[5814]:   [QUORUM] Members[4]: 1 2 3 4
Dec 04 03:00:47 pve03 corosync[5814]:   [MAIN  ] Completed service synchronization, ready to provide service.
Dec 04 03:01:16 pve03 corosync[5814]:   [TOTEM ] Token has not been received in 3225 ms
Dec 04 03:02:07 pve03 corosync[5814]:   [TOTEM ] Retransmit List: 167
Dec 04 03:02:07 pve03 corosync[5814]:   [TOTEM ] Retransmit List: 168
Dec 04 03:02:07 pve03 corosync[5814]:   [TOTEM ] Retransmit List: 169
Dec 04 03:03:23 pve03 corosync[5814]:   [QUORUM] Sync members[4]: 1 2 3 4
Dec 04 03:03:23 pve03 corosync[5814]:   [TOTEM ] A new membership (1.fd2) was formed. Members
Dec 04 03:03:23 pve03 corosync[5814]:   [QUORUM] Members[4]: 1 2 3 4
Dec 04 03:03:23 pve03 corosync[5814]:   [MAIN  ] Completed service synchronization, ready to provide service.
Dec 04 03:03:47 pve03 pmxcfs[5746]: [status] notice: received log
Dec 04 03:03:53 pve03 corosync[5814]:   [TOTEM ] Token has not been received in 3225 ms
Dec 04 03:04:26 pve03 corosync[5814]:   [QUORUM] Sync members[4]: 1 2 3 4
Dec 04 03:04:26 pve03 corosync[5814]:   [TOTEM ] A new membership (1.fd6) was formed. Members
Dec 04 03:04:26 pve03 corosync[5814]:   [QUORUM] Members[4]: 1 2 3 4
Dec 04 03:04:26 pve03 corosync[5814]:   [MAIN  ] Completed service synchronization, ready to provide service.
Dec 04 03:05:10 pve03 pveproxy[3183782]: worker exit
Dec 04 03:05:10 pve03 pveproxy[5873]: worker 3183782 finished
Dec 04 03:05:10 pve03 pveproxy[5873]: starting 1 worker(s)
Dec 04 03:05:10 pve03 pveproxy[5873]: worker 3691420 started
Dec 04 03:06:47 pve03 pvedaemon[3187849]: worker exit
Dec 04 03:06:47 pve03 pvedaemon[5864]: worker 3187849 finished
Dec 04 03:06:47 pve03 pvedaemon[5864]: starting 1 worker(s)
Dec 04 03:06:47 pve03 pvedaemon[5864]: worker 3827508 started
Dec 04 03:06:59 pve03 corosync[5814]:   [TOTEM ] Token has not been received in 3225 ms
Dec 04 03:08:40 pve03 corosync[5814]:   [TOTEM ] Retransmit List: 418
Dec 04 03:08:40 pve03 corosync[5814]:   [TOTEM ] Retransmit List: 419
Dec 04 03:08:40 pve03 corosync[5814]:   [TOTEM ] Retransmit List: 41a
Dec 04 03:09:39 pve03 corosync[5814]:   [TOTEM ] Token has not been received in 3225 ms
Dec 04 03:10:01 pve03 CRON[4074320]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 04 03:10:01 pve03 CRON[4074321]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Dec 04 03:10:01 pve03 CRON[4074320]: pam_unix(cron:session): session closed for user root
Dec 04 03:10:43 pve03 corosync[5814]:   [QUORUM] Sync members[4]: 1 2 3 4
Dec 04 03:10:43 pve03 corosync[5814]:   [TOTEM ] A new membership (1.fda) was formed. Members
Dec 04 03:10:43 pve03 corosync[5814]:   [QUORUM] Members[4]: 1 2 3 4
Dec 04 03:10:43 pve03 corosync[5814]:   [MAIN  ] Completed service synchronization, ready to provide service.
Dec 04 03:11:03 pve03 corosync[5814]:   [KNET  ] link: host: 2 link: 0 is down
Dec 04 03:11:03 pve03 corosync[5814]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Dec 04 03:11:03 pve03 corosync[5814]:   [KNET  ] host: host: 2 has no active links
Dec 04 03:11:06 pve03 corosync[5814]:   [KNET  ] rx: host: 2 link: 0 is up
Dec 04 03:11:06 pve03 corosync[5814]:   [KNET  ] link: Resetting MTU for link 0 because host 2 joined
Dec 04 03:11:06 pve03 corosync[5814]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Dec 04 03:11:06 pve03 corosync[5814]:   [KNET  ] pmtud: Global data MTU changed to: 1397
Dec 04 03:15:04 pve03 pmxcfs[5746]: [status] notice: received log
Dec 04 03:15:41 pve03 pvedaemon[3178579]: worker exit
Dec 04 03:15:41 pve03 pvedaemon[5864]: worker 3178579 finished
Dec 04 03:15:41 pve03 pvedaemon[5864]: starting 1 worker(s)
Dec 04 03:15:41 pve03 pvedaemon[5864]: worker 246839 started
Dec 04 03:16:26 pve03 corosync[5814]:   [TOTEM ] Token has not been received in 3225 ms
Dec 04 03:16:27 pve03 corosync[5814]:   [QUORUM] Sync members[4]: 1 2 3 4
Dec 04 03:16:27 pve03 corosync[5814]:   [TOTEM ] A new membership (1.fde) was formed. Members
Dec 04 03:16:28 pve03 pmxcfs[5746]: [dcdb] notice: cpg_send_message retry 10
Dec 04 03:16:28 pve03 corosync[5814]:   [QUORUM] Members[4]: 1 2 3 4
Dec 04 03:16:28 pve03 corosync[5814]:   [MAIN  ] Completed service synchronization, ready to provide service.
Dec 04 03:16:28 pve03 pmxcfs[5746]: [dcdb] notice: cpg_send_message retried 11 times
Dec 04 03:17:01 pve03 CRON[361374]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 04 03:17:01 pve03 CRON[361375]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Dec 04 03:17:01 pve03 CRON[361374]: pam_unix(cron:session): session closed for user root
Dec 04 03:18:33 pve03 corosync[5814]:   [QUORUM] Sync members[4]: 1 2 3 4
Dec 04 03:18:33 pve03 corosync[5814]:   [TOTEM ] A new membership (1.fe2) was formed. Members
Dec 04 03:18:33 pve03 corosync[5814]:   [QUORUM] Members[4]: 1 2 3 4
Dec 04 03:18:33 pve03 corosync[5814]:   [MAIN  ] Completed service synchronization, ready to provide service.
Dec 04 03:18:47 pve03 pmxcfs[5746]: [status] notice: received log
Dec 04 03:30:04 pve03 pmxcfs[5746]: [status] notice: received log
-- Reboot --
 
As far as I can see, the node member is in a cluster?
I would suspect that your bandwidth is not enough for Corosync and the backup traffic or latency increases over time.

Tell us a little more about your entire cluster.
 
  • Like
Reactions: showiproute and esi_y
sb-jw said:
As far as I can see, the node member is in a cluster?
I would suspect that your bandwidth is not enough for Corosync and the backup traffic or latency increases over time.

Tell us a little more about your entire cluster.
Click to expand...
This :) Wild guess something like HA resources AND core router/switch rebooting at 3am.
 
I have turned off the backup schedule... It still reboots automatically in the early morning, but the time changes to around 12AM... Can anyone give me some advice? Thank you

Code: 
Dec 05 00:00:01 pve03 pmxcfs[4117]: [status] notice: received log
Dec 05 00:00:10 pve03 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Dec 05 00:00:10 pve03 systemd[1]: Starting logrotate.service - Rotate log files...
Dec 05 00:00:10 pve03 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Dec 05 00:00:10 pve03 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Dec 05 00:00:11 pve03 systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
Dec 05 00:00:12 pve03 pveproxy[216406]: send HUP to 4248
Dec 05 00:00:12 pve03 pveproxy[4248]: received signal HUP
Dec 05 00:00:12 pve03 pveproxy[4248]: server closing
Dec 05 00:00:12 pve03 pveproxy[4248]: server shutdown (restart)
Dec 05 00:00:12 pve03 systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
Dec 05 00:00:12 pve03 systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
Dec 05 00:00:13 pve03 spiceproxy[220180]: send HUP to 4255
Dec 05 00:00:13 pve03 spiceproxy[4255]: received signal HUP
Dec 05 00:00:13 pve03 spiceproxy[4255]: server closing
Dec 05 00:00:13 pve03 spiceproxy[4255]: server shutdown (restart)
Dec 05 00:00:13 pve03 systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
Dec 05 00:00:13 pve03 pvefw-logger[3567]: received terminate request (signal)
Dec 05 00:00:13 pve03 pvefw-logger[3567]: stopping pvefw logger
Dec 05 00:00:13 pve03 systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Dec 05 00:00:14 pve03 systemd[1]: pvefw-logger.service: Deactivated successfully.
Dec 05 00:00:14 pve03 systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Dec 05 00:00:14 pve03 systemd[1]: pvefw-logger.service: Consumed 9.577s CPU time.
Dec 05 00:00:14 pve03 systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Dec 05 00:00:14 pve03 systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Dec 05 00:00:14 pve03 pvefw-logger[220876]: starting pvefw logger
Dec 05 00:00:14 pve03 systemd[1]: logrotate.service: Deactivated successfully.
Dec 05 00:00:14 pve03 systemd[1]: Finished logrotate.service - Rotate log files.
Dec 05 00:00:14 pve03 spiceproxy[4255]: restarting server
Dec 05 00:00:14 pve03 spiceproxy[4255]: starting 1 worker(s)
Dec 05 00:00:14 pve03 spiceproxy[4255]: worker 220880 started
Dec 05 00:00:14 pve03 pveproxy[4248]: restarting server
Dec 05 00:00:14 pve03 pveproxy[4248]: starting 3 worker(s)
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220887 started
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220888 started
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220889 started
Dec 05 00:00:19 pve03 spiceproxy[4256]: worker exit
Dec 05 00:00:19 pve03 spiceproxy[4255]: worker 4256 finished
Dec 05 00:00:19 pve03 pveproxy[3583731]: worker exit
Dec 05 00:00:19 pve03 pveproxy[3623249]: worker exit
Dec 05 00:00:19 pve03 pveproxy[3263027]: worker exit
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3623249 finished
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3263027 finished
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3583731 finished
Dec 05 00:11:55 pve03 corosync[4188]:   [TOTEM ] Token has not been received in 3225 ms
Dec 05 00:17:01 pve03 CRON[1249434]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 05 00:17:01 pve03 CRON[1249435]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Dec 05 00:17:01 pve03 CRON[1249434]: pam_unix(cron:session): session closed for user root
Dec 05 00:17:27 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4d07f
Dec 05 00:24:01 pve03 CRON[1622952]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 05 00:24:01 pve03 CRON[1622953]: (root) CMD (if [ $(date +%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/trim ]; then /usr/lib/zfs-linux/trim; fi)
Dec 05 00:24:01 pve03 CRON[1622952]: pam_unix(cron:session): session closed for user root
Dec 05 00:36:54 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4e3a6
Dec 05 00:37:27 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4e43f
-- Reboot --
 
Last edited:
Rick.Jiang said:
I have turned off the backup schedule... It still reboots automatically in the early morning, but the time changes to around 12AM... Can anyone give me some advice? Thank you

Code: 
Dec 05 00:00:01 pve03 pmxcfs[4117]: [status] notice: received log
Dec 05 00:00:10 pve03 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Dec 05 00:00:10 pve03 systemd[1]: Starting logrotate.service - Rotate log files...
Dec 05 00:00:10 pve03 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Dec 05 00:00:10 pve03 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Dec 05 00:00:11 pve03 systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
Dec 05 00:00:12 pve03 pveproxy[216406]: send HUP to 4248
Dec 05 00:00:12 pve03 pveproxy[4248]: received signal HUP
Dec 05 00:00:12 pve03 pveproxy[4248]: server closing
Dec 05 00:00:12 pve03 pveproxy[4248]: server shutdown (restart)
Dec 05 00:00:12 pve03 systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
Dec 05 00:00:12 pve03 systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
Dec 05 00:00:13 pve03 spiceproxy[220180]: send HUP to 4255
Dec 05 00:00:13 pve03 spiceproxy[4255]: received signal HUP
Dec 05 00:00:13 pve03 spiceproxy[4255]: server closing
Dec 05 00:00:13 pve03 spiceproxy[4255]: server shutdown (restart)
Dec 05 00:00:13 pve03 systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
Dec 05 00:00:13 pve03 pvefw-logger[3567]: received terminate request (signal)
Dec 05 00:00:13 pve03 pvefw-logger[3567]: stopping pvefw logger
Dec 05 00:00:13 pve03 systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Dec 05 00:00:14 pve03 systemd[1]: pvefw-logger.service: Deactivated successfully.
Dec 05 00:00:14 pve03 systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Dec 05 00:00:14 pve03 systemd[1]: pvefw-logger.service: Consumed 9.577s CPU time.
Dec 05 00:00:14 pve03 systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Dec 05 00:00:14 pve03 systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Dec 05 00:00:14 pve03 pvefw-logger[220876]: starting pvefw logger
Dec 05 00:00:14 pve03 systemd[1]: logrotate.service: Deactivated successfully.
Dec 05 00:00:14 pve03 systemd[1]: Finished logrotate.service - Rotate log files.
Dec 05 00:00:14 pve03 spiceproxy[4255]: restarting server
Dec 05 00:00:14 pve03 spiceproxy[4255]: starting 1 worker(s)
Dec 05 00:00:14 pve03 spiceproxy[4255]: worker 220880 started
Dec 05 00:00:14 pve03 pveproxy[4248]: restarting server
Dec 05 00:00:14 pve03 pveproxy[4248]: starting 3 worker(s)
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220887 started
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220888 started
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220889 started
Dec 05 00:00:19 pve03 spiceproxy[4256]: worker exit
Dec 05 00:00:19 pve03 spiceproxy[4255]: worker 4256 finished
Dec 05 00:00:19 pve03 pveproxy[3583731]: worker exit
Dec 05 00:00:19 pve03 pveproxy[3623249]: worker exit
Dec 05 00:00:19 pve03 pveproxy[3263027]: worker exit
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3623249 finished
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3263027 finished
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3583731 finished
Dec 05 00:11:55 pve03 corosync[4188]:   [TOTEM ] Token has not been received in 3225 ms
Dec 05 00:17:01 pve03 CRON[1249434]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 05 00:17:01 pve03 CRON[1249435]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Dec 05 00:17:01 pve03 CRON[1249434]: pam_unix(cron:session): session closed for user root
Dec 05 00:17:27 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4d07f
Dec 05 00:24:01 pve03 CRON[1622952]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 05 00:24:01 pve03 CRON[1622953]: (root) CMD (if [ $(date +%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/trim ]; then /usr/lib/zfs-linux/trim; fi)
Dec 05 00:24:01 pve03 CRON[1622952]: pam_unix(cron:session): session closed for user root
Dec 05 00:36:54 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4e3a6
Dec 05 00:37:27 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4e43f
-- Reboot --
Click to expand...
As @sb-jw mentioned it would be good to know which hardware you use in your cluster and network.
 
You have to give us a little more information. We don't know your setup and can't look at it. Without knowledge of this, we cannot support you.
 
sb-jw said:
You have to give us a little more information. We don't know your setup and can't look at it. Without knowledge of this, we cannot support you.
Click to expand...
I'm sorry that I provided insufficient information. Can you tell me what information I need to provide that would be more helpful? Thank you
 
Rick.Jiang said:
I only joined the cluster and did not use HA or other cluster services. The other three nodes did not have this situation... I don't understand.
Click to expand...
Just joining an existing cluster already enables background services which rely on high speed & reliable network connections
 
Describe your entire cluster, what hardware the nodes have, where they are located, how they are connected, what your network hardware looks like, whether you use HA services, shared storage, etc. etc. Simply the basics of your setup.
 
sb-jw said:
Describe your entire cluster, what hardware the nodes have, where they are located, how they are connected, what your network hardware looks like, whether you use HA services, shared storage, etc. etc. Simply the basics of your setup.
Click to expand...
The composition structure of my cluster is as follows
1. Four nodes
2. Not using HA
3. Use SMB/CIFS to connect to NAS as VM backup
4. Four nodes are in the same data center and network segment (172.17.1.1-172.17.1.4) and a 1GB Switch and UP LINK to the core switch.

Two of the four nodes each have the same specifications. The node three and node four that have the same specifications, but except for the problem on node three, the other nodes do not have the problem. This makes me confused.
 
Last edited:
Since your access is more limited, so are the options for fixing it. Have you ever changed the cable, the port on the switch or on the server? There may be a defect.
Otherwise, you could ask the data center whether there were any abnormalities with the switch during the specified period.
 
showiproute said:
Just joining an existing cluster already enables background services which rely on high speed & reliable network connections
Click to expand...
He should not have anything rebooting without any HA resources (as was clarified later on).


Rick.Jiang said:
I have turned off the backup schedule... It still reboots automatically in the early morning, but the time changes to around 12AM... Can anyone give me some advice? Thank you

Code: 
Dec 05 00:00:01 pve03 pmxcfs[4117]: [status] notice: received log
Dec 05 00:00:10 pve03 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Dec 05 00:00:10 pve03 systemd[1]: Starting logrotate.service - Rotate log files...
Dec 05 00:00:10 pve03 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Dec 05 00:00:10 pve03 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Dec 05 00:00:11 pve03 systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
Dec 05 00:00:12 pve03 pveproxy[216406]: send HUP to 4248
Dec 05 00:00:12 pve03 pveproxy[4248]: received signal HUP
Dec 05 00:00:12 pve03 pveproxy[4248]: server closing
Dec 05 00:00:12 pve03 pveproxy[4248]: server shutdown (restart)
Dec 05 00:00:12 pve03 systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
Dec 05 00:00:12 pve03 systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
Dec 05 00:00:13 pve03 spiceproxy[220180]: send HUP to 4255
Dec 05 00:00:13 pve03 spiceproxy[4255]: received signal HUP
Dec 05 00:00:13 pve03 spiceproxy[4255]: server closing
Dec 05 00:00:13 pve03 spiceproxy[4255]: server shutdown (restart)
Dec 05 00:00:13 pve03 systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
Dec 05 00:00:13 pve03 pvefw-logger[3567]: received terminate request (signal)
Dec 05 00:00:13 pve03 pvefw-logger[3567]: stopping pvefw logger
Dec 05 00:00:13 pve03 systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Dec 05 00:00:14 pve03 systemd[1]: pvefw-logger.service: Deactivated successfully.
Dec 05 00:00:14 pve03 systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Dec 05 00:00:14 pve03 systemd[1]: pvefw-logger.service: Consumed 9.577s CPU time.
Dec 05 00:00:14 pve03 systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Dec 05 00:00:14 pve03 systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Dec 05 00:00:14 pve03 pvefw-logger[220876]: starting pvefw logger
Dec 05 00:00:14 pve03 systemd[1]: logrotate.service: Deactivated successfully.
Dec 05 00:00:14 pve03 systemd[1]: Finished logrotate.service - Rotate log files.
Dec 05 00:00:14 pve03 spiceproxy[4255]: restarting server
Dec 05 00:00:14 pve03 spiceproxy[4255]: starting 1 worker(s)
Dec 05 00:00:14 pve03 spiceproxy[4255]: worker 220880 started
Dec 05 00:00:14 pve03 pveproxy[4248]: restarting server
Dec 05 00:00:14 pve03 pveproxy[4248]: starting 3 worker(s)
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220887 started
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220888 started
Dec 05 00:00:14 pve03 pveproxy[4248]: worker 220889 started
Dec 05 00:00:19 pve03 spiceproxy[4256]: worker exit
Dec 05 00:00:19 pve03 spiceproxy[4255]: worker 4256 finished
Dec 05 00:00:19 pve03 pveproxy[3583731]: worker exit
Dec 05 00:00:19 pve03 pveproxy[3623249]: worker exit
Dec 05 00:00:19 pve03 pveproxy[3263027]: worker exit
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3623249 finished
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3263027 finished
Dec 05 00:00:19 pve03 pveproxy[4248]: worker 3583731 finished
Dec 05 00:11:55 pve03 corosync[4188]:   [TOTEM ] Token has not been received in 3225 ms
Dec 05 00:17:01 pve03 CRON[1249434]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 05 00:17:01 pve03 CRON[1249435]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Dec 05 00:17:01 pve03 CRON[1249434]: pam_unix(cron:session): session closed for user root
Dec 05 00:17:27 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4d07f
Dec 05 00:24:01 pve03 CRON[1622952]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 05 00:24:01 pve03 CRON[1622953]: (root) CMD (if [ $(date +%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/trim ]; then /usr/lib/zfs-linux/trim; fi)
Dec 05 00:24:01 pve03 CRON[1622952]: pam_unix(cron:session): session closed for user root
Dec 05 00:36:54 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4e3a6
Dec 05 00:37:27 pve03 corosync[4188]:   [TOTEM ] Retransmit List: 4e43f
-- Reboot --
Click to expand...

Is there anything before midnight there? This is now every day? No exceptions? Also, can you show more of these logs (multiple days around abrupt power cycle) for comparison? Your first one looked a bit different than this second one.
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back