Very Wierd issue...

G

Gad

New Member
Feb 28, 2019
27
0
1
38
every week on Friday night sometime at late night hours my proxmox will get offline and i am not sure of the reason

its a headless server , and i cannot access GUI only reboot the system by hand , what logs can i check?

/var/log/syslog
/var/log/
/var/log/syslog.1,
/var/log/syslog.2.gz etc.

maybe someone can point me to what i am looking for?

maybe someone knows of a config that will restart my Proxmox every week (i did not setup this...)

thanks!
 
Gad said:
every week on Friday night sometime at late night hours my proxmox will get offline and i am not sure of the reason
Click to expand...
Backups maybe?

Gad said:
its a headless server , and i cannot access GUI only reboot the system by hand , what logs can i check?
Click to expand...
It's a web interface on port 8006.
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_gui

Gad said:
maybe someone knows of a config that will restart my Proxmox every week (i did not setup this...)
Click to expand...
None by default.
 
Hi thanks for the reply , soory has i said it happens once a week
so i was prepared this time :)

it seems it related to SMART Disk scan?
is that a BIOS thing or a Proxmox thing?

so the Proxmox GUI is NA , also the VMs are NA
is there a way to start the GUI?

Code: 
Apr 10 23:34:00 GadServer systemd[1]: Starting Proxmox VE replication runner...
Apr 10 23:34:01 GadServer systemd[1]: pvesr.service: Succeeded.
Apr 10 23:34:01 GadServer systemd[1]: Started Proxmox VE replication runner.
Apr 10 23:34:10 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550088 in /proc/stat, 556750 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:10 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550089 in /proc/stat, 556751 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:10 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550089 in /proc/stat, 556751 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:20 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550098 in /proc/stat, 556759 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:20 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550099 in /proc/stat, 556759 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:20 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550099 in /proc/stat, 556759 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:30 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550107 in /proc/stat, 556767 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:30 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550108 in /proc/stat, 556768 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:30 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550108 in /proc/stat, 556768 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:40 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550120 in /proc/stat, 556775 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:40 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550121 in /proc/stat, 556776 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:40 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550121 in /proc/stat, 556776 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:50 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550130 in /proc/stat, 556785 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:50 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550131 in /proc/stat, 556786 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:34:50 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550131 in /proc/stat, 556786 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:00 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550140 in /proc/stat, 556792 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:00 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550141 in /proc/stat, 556793 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:00 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550141 in /proc/stat, 556793 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:00 GadServer systemd[1]: Starting Proxmox VE replication runner...
Apr 10 23:35:01 GadServer systemd[1]: pvesr.service: Succeeded.
Apr 10 23:35:01 GadServer systemd[1]: Started Proxmox VE replication runner.
Apr 10 23:35:10 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550151 in /proc/stat, 556803 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:10 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550152 in /proc/stat, 556804 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:10 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550152 in /proc/stat, 556804 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:20 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550159 in /proc/stat, 556811 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:20 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550159 in /proc/stat, 556811 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:20 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550160 in /proc/stat, 556811 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:30 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550168 in /proc/stat, 556820 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:30 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550168 in /proc/stat, 556821 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:30 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550169 in /proc/stat, 556821 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:40 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550176 in /proc/stat, 556829 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:40 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550177 in /proc/stat, 556830 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:40 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550177 in /proc/stat, 556830 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:50 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550602 in /proc/stat, 556845 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:50 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550603 in /proc/stat, 556846 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:35:50 GadServer lxcfs[688]: bindings.c: 4526: cpuview_proc_stat: cpu3 from /lxc/101/ns has unexpected cpu time: 550603 in /proc/stat, 556846 in cpuacct.usage_all; unable to determine idle time
Apr 10 23:36:00 GadServer systemd[1]: Starting Proxmox VE replication runner...
Apr 10 23:36:45 GadServer smartd[687]: Device: /dev/sda [SAT], Read SMART Self Test Log Failed
Apr 10 23:36:45 GadServer smartd[687]: Sending warning via /usr/share/smartmontools/smartd-runner to root ...
Apr 10 23:36:45 GadServer kernel: [567074.105470] ata1.00: configured for UDMA/133 (device error ignored)
Apr 10 23:36:45 GadServer kernel: [567074.146848] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:45 GadServer kernel: [567074.265838] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:45 GadServer kernel: [567074.293892] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:46 GadServer kernel: [567075.173922] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:46 GadServer kernel: [567075.178708] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:46 GadServer kernel: [567075.201913] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:46 GadServer kernel: [567075.258021] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:46 GadServer kernel: [567075.265395] sd 0:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current]
Apr 10 23:36:46 GadServer kernel: [567075.265403] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 01 00 00
Apr 10 23:36:46 GadServer kernel: [567075.298026] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:46 GadServer kernel: [567075.302960] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:47 GadServer kernel: [567076.127439] ata1.01: SATA link down (SStatus 4 SControl 300)
Apr 10 23:36:53 GadServer kernel: [567081.999456] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 10 23:36:53 GadServer kernel: [567081.999467] ata1.01: SATA link down (SStatus 4 SControl 300)
Apr 10 23:36:53 GadServer kernel: [567082.002099] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:53 GadServer kernel: [567082.009322] ata1.00: failed to set xfermode (err_mask=0x1)
Apr 10 23:36:59 GadServer kernel: [567087.887440] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 10 23:36:59 GadServer kernel: [567087.890107] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:59 GadServer kernel: [567087.895199] ata1.00: supports DRM functions and may not be fully accessible
 
Gad said:
so the Proxmox GUI is NA , also the VMs are NA
is there a way to start the GUI?
Click to expand...
Yes, if you have IPMI , iLO or iDRAC.

But you should figure out why it's shutting down in the first place. SMART shouldn't turn off any PC, let alone a server. How did you determine that it was SMART that was shutting down the server? Are there errors that cause a shutdown?
 
last thing log has to say is

Apr 10 23:36:53 GadServer kernel: [567082.009322] ata1.00: failed to set xfermode (err_mask=0x1)
Apr 10 23:36:59 GadServer kernel: [567087.887440] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 10 23:36:59 GadServer kernel: [567087.890107] ata1.00: supports DRM functions and may not be fully accessible
Apr 10 23:36:59 GadServer kernel: [567087.895199] ata1.00: supports DRM functions and may not be fully accessible

i can wait another week and comapre hhh
 
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