Proxmox Root session down, OS is down but hardware is still running

francabicon

New Member
Jan 11, 2024
2
1
1
Hi there,
I have encountered this issue eversince the PVE 8.0.3 update and it has freeze the entire server EVERYDAY at a certain time but the hardware isn't down and still running
do check out this error for this log file:
Code:
Jan 10 03:17:01 pve CRON[2182601]: pam_unix(cron:session): session closed for user root
Jan 10 04:01:15 pve systemd[1]: Starting apt-daily.service - Daily apt download activities...
Jan 10 04:01:15 pve systemd[1]: apt-daily.service: Deactivated successfully.
Jan 10 04:01:15 pve systemd[1]: Finished apt-daily.service - Daily apt download activities.
Jan 10 04:17:01 pve CRON[2253132]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 04:17:01 pve CRON[2253133]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 04:17:01 pve CRON[2253132]: pam_unix(cron:session): session closed for user root
Jan 10 05:17:01 pve CRON[2322604]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 05:17:01 pve CRON[2322605]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 05:17:01 pve CRON[2322604]: pam_unix(cron:session): session closed for user root
Jan 10 05:46:15 pve systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Jan 10 05:46:15 pve systemd[1]: Starting man-db.service - Daily man-db regeneration...
Jan 10 05:46:15 pve systemd[1]: man-db.service: Deactivated successfully.
Jan 10 05:46:15 pve systemd[1]: Finished man-db.service - Daily man-db regeneration.
Jan 10 05:46:22 pve pveupdate[2356464]: <root@pam> starting task UPID:pve:0023F5F2:00C00D4D:659DBEAE:aptupdate::root@pam:
Jan 10 05:46:23 pve pveupdate[2356722]: update new package list: /var/lib/pve-manager/pkgupdates
Jan 10 05:46:26 pve pveupdate[2356464]: <root@pam> end task UPID:pve:0023F5F2:00C00D4D:659DBEAE:aptupdate::root@pam: OK
Jan 10 05:46:26 pve systemd[1]: pve-daily-update.service: Deactivated successfully.
Jan 10 05:46:26 pve systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Jan 10 05:46:26 pve systemd[1]: pve-daily-update.service: Consumed 5.230s CPU time.
Jan 10 06:07:36 pve systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Jan 10 06:07:36 pve systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Jan 10 06:07:36 pve systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Jan 10 06:17:01 pve CRON[2392895]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 06:17:01 pve CRON[2392916]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 06:17:01 pve CRON[2392895]: pam_unix(cron:session): session closed for user root
Jan 10 06:25:01 pve CRON[2402557]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 06:25:01 pve CRON[2402558]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Jan 10 06:25:01 pve CRON[2402557]: pam_unix(cron:session): session closed for user root
Jan 10 07:17:01 pve CRON[2464015]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 07:17:01 pve CRON[2464016]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 07:17:01 pve CRON[2464015]: pam_unix(cron:session): session closed for user root
Jan 10 07:17:15 pve systemd[1]: Starting apt-daily.service - Daily apt download activities...
Jan 10 07:17:15 pve systemd[1]: apt-daily.service: Deactivated successfully.
Jan 10 07:17:15 pve systemd[1]: Finished apt-daily.service - Daily apt download activities.
Jan 10 07:49:03 pve smartd[3409]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 62 to 63
Jan 10 07:49:03 pve smartd[3409]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 38 to 37
Jan 10 08:17:01 pve CRON[2535227]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 08:17:01 pve CRON[2535228]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 08:17:01 pve CRON[2535227]: pam_unix(cron:session): session closed for user root
Jan 10 08:49:02 pve smartd[3409]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 63 to 62
Jan 10 08:49:02 pve smartd[3409]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 37 to 38
Jan 10 09:17:01 pve CRON[2606823]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 09:17:01 pve CRON[2606824]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 09:17:01 pve CRON[2606823]: pam_unix(cron:session): session closed for user root
Jan 10 10:17:01 pve CRON[2679605]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 10:17:01 pve CRON[2679606]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 10:17:01 pve CRON[2679605]: pam_unix(cron:session): session closed for user root
Jan 10 11:17:01 pve CRON[2752657]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 10 11:17:01 pve CRON[2752658]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 10 11:17:01 pve CRON[2752657]: pam_unix(cron:session): session closed for user root
-- Reboot --
Jan 11 17:48:41 pve kernel: Linux version 6.2.16-3-pve (tom@sbuild) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-3 (2023-06-17T05:58Z) ()
Jan 11 17:48:41 pve kernel: Command line: initrd=\EFI\proxmox\6.2.16-3-pve\initrd.img-6.2.16-3-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs
Jan 11 17:48:41 pve kernel: KERNEL supported cpus:
Jan 11 17:48:41 pve kernel:   Intel GenuineIntel
Jan 11 17:48:41 pve kernel:   AMD AuthenticAMD
Jan 11 17:48:41 pve kernel:   Hygon HygonGenuine
Jan 11 17:48:41 pve kernel:   Centaur CentaurHauls
Jan 11 17:48:41 pve kernel:   zhaoxin   Shanghai

Any help is highly appreciated. Thanks in advance.
 
Last edited:
  • Like
Reactions: tanman0217
Bumping this. I am experiencing a pretty identical issue. It is interesting that the minute of our issue is the same. Not sure if the local timezone is used, but I think it is. I am in EST, and it matches up with my local time. So, depending on @francabicon TZ, it may be the same time for both of us. I am going to continue looking into it and if I find something, I will respond again. If someone else with better knowledge than I do has some insight, that would be great.

Thanks.
 

Attachments

  • Like
Reactions: tanman0217

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!

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!