Proxmox does not respond after a few hours

sert

New Member
Jan 25, 2024
3
0
1
HI,

I am having the following problem. When a few hours pass (each time it is a different time), proxmos does not respond and hangs. The last thing written in the system logs is:
Jan 24 19:17:01 percom CRON[218872]: pam_unix(cron:session): session closed for user root Jan 24 19:19:56 percom pvedaemon[219454]: starting lxc termproxy UPID:percom:0003593E:008EDD0C:65B154CC:vncproxy:101:root@pam: Jan 24 19:19:56 percom pvedaemon[202534]: <root@pam> starting task UPID:percom:0003593E:008EDD0C:65B154CC:vncproxy:101:root@pam: Jan 24 19:19:56 percom pvedaemon[211125]: <root@pam> successful auth for user 'root@pam' Jan 24 19:19:59 percom pvedaemon[202534]: <root@pam> end task UPID:percom:0003593E:008EDD0C:65B154CC:vncproxy:101:root@pam: OK Jan 24 19:20:11 percom smartd[1137]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 66 Jan 24 19:20:11 percom smartd[1137]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 34 Jan 24 19:20:45 percom pveproxy[206163]: worker exit Jan 24 19:20:45 percom pveproxy[1486]: worker 206163 finished Jan 24 19:20:45 percom pveproxy[1486]: starting 1 worker(s) Jan 24 19:20:45 percom pveproxy[1486]: worker 219656 started Jan 24 19:28:32 percom pvedaemon[211125]: <root@pam> successful auth for user 'root@pam' Jan 24 19:43:32 percom pvedaemon[202534]: <root@pam> successful auth for user 'root@pam' Jan 24 19:46:11 percom pveproxy[1486]: worker 209826 finished Jan 24 19:46:11 percom pveproxy[1486]: starting 1 worker(s) Jan 24 19:46:11 percom pveproxy[1486]: worker 224040 started Jan 24 19:46:11 percom pveproxy[224039]: got inotify poll request in wrong process - disabling inotify Jan 24 19:50:12 percom smartd[1137]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 67 Jan 24 19:50:12 percom smartd[1137]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 33 Jan 24 20:17:01 percom CRON[229107]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jan 24 20:17:01 percom CRON[229109]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jan 24 20:17:01 percom CRON[229107]: pam_unix(cron:session): session closed for user root Jan 24 20:43:00 percom pvedaemon[211125]: <root@pam> successful auth for user 'root@pam' Jan 24 20:50:32 percom smartd[1137]: Device: /dev/sdh [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 68 Jan 24 20:50:32 percom smartd[1137]: Device: /dev/sdh [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 32 Jan 24 21:17:01 percom CRON[238979]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jan 24 21:17:01 percom CRON[238980]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jan 24 21:17:01 percom CRON[238979]: pam_unix(cron:session): session closed for user root Jan 24 21:41:34 percom pvedaemon[202534]: <root@pam> successful auth for user 'root@pam' Jan 24 22:17:01 percom CRON[248852]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jan 24 22:17:01 percom CRON[248853]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jan 24 22:17:01 percom CRON[248852]: pam_unix(cron:session): session closed for user root Jan 24 22:20:22 percom smartd[1137]: Device: /dev/sde [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 68 to 69 Jan 24 22:20:22 percom smartd[1137]: Device: /dev/sde [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 32 to 31 Jan 24 22:20:27 percom smartd[1137]: Device: /dev/sdf [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 68 Jan 24 22:20:27 percom smartd[1137]: Device: /dev/sdf [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 32 Jan 24 22:41:33 percom kernel: perf: interrupt took too long (2517 > 2500), lowering kernel.perf_event_max_sample_rate to 79250 Jan 24 22:42:59 percom pvedaemon[211125]: <root@pam> successful auth for user 'root@pam' -- Boot 2513b627e67e458d8e034016cab2d3d6 --
Almost 4 hours after inactivity, the proxmos does not respond.

Regards
 
Last edited: