Server not responding showing error

O

osopolar

Member
Nov 3, 2022
60
1
13
HI Guys

Server was not responding this morning and saw this on the screen
I have no idea what it means is this a 1 of glitch or do i need to fix something?
I rebooted it and it came back u with no errors
 
You can from check the syslog from both GUI/CLI in GUI you can go to Datacenter -> {Node} -> Syslog. From CLI you can use journalctl as the following command:

Bash: 
journalctl --since "2024-03-07 01:00" --until "2024-03-08 15:00"
You may change date/time in the above command.
 
Linux proxmox 6.5.13-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-1 (2024-02-05T13:50Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Dec 5 11:13:01 GMT 2023 on pts/0
root@proxmox:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-6-pve-signed: 6.5.11-6
proxmox-kernel-6.5.11-5-pve-signed: 6.5.11-5
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2.16-18-pve: 6.2.16-18
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.7-pve2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve2
root@proxmox:~# ^C
root@proxmox:~#
 
I Have shut down several apps to see if it was them but my server crashing several times a day.
Any ideas please
Latest sys log HERE
 
Last edited:
Not sure what's going on, also don't know what's your storage config, but what's up with /dev/sda & sdb? Their temps seem rather toasty.
 
osopolar said:
View attachment 64428
Click to expand...
Now choose the drive (click on /dev/sda) and then click on "Show S.M.A.R.T. values"
Do the same for the other drive (/dev/sdb).

I'm not sure I can be of much more help, but my wild guess is that you have a "cooling" problem in your server. Have you physically checked the server; ventilation, fans etc.
 
gfngfn256 said:
Now choose the drive (click on /dev/sda) and then click on "Show S.M.A.R.T. values"
Do the same for the other drive (/dev/sdb).

I'm not sure I can be of much more help, but my wild guess is that you have a "cooling" problem in your server. Have you physically checked the server; ventilation, fans etc.
Click to expand...
1710142996431.png
1710143026532.png
1710143059056.png
 
Nothing stands out. I don't know what HW you're on. As I said check cooling + ventilation.
As to your OP, google "i915 fifo underrun" you'll get plenty of results.
 
Moayad said:
Could you please post the output of pveversion -v?
Click to expand...
Hello
Still had random crashes with the following log

I read through the log just for the word error found see below.
Very weird my SSD are only 6 months old and have been rock solid

I also not a update to Proxmox would that have any fixes in or are my erros not related

15 02:52:16 proxmox smartd[675]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 110 to 112

Mar 15 11:20:07 proxmox kernel: RAS: Correctable Errors collector initialized.

Mar 15 11:20:08 proxmox kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

Mar 15 11:20:11 proxmox smartd[675]: Device: /dev/nvme0, number of Error Log entries increased from 100 to 101

Mar 15 11:20:11 proxmox smartd[675]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 112 to 120
Mar 15 11:20:11 proxmox smartd[675]: Device: /dev/sdb [SAT], SMART Usage Attribute: 195 ECC_Uncorr_Error_Count changed from 120 to 100

Mar 15 11:20:11 proxmox smartd[675]: Device: /dev/sdb [SAT], no SMART Error Log, ignoring -l error (override with -T permissive)


I also notice at shutdown the following "
Mar 15 09:17:01 proxmox CRON[1491793]: pam_unix(cron:session): session closed for user root
Mar 15 09:17:43 proxmox pvestatd[984]: auth key pair too old, rotating..
-- Reboot --"


Code: 
ar 15 04:17:01 proxmox CRON[1412593]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 04:17:01 proxmox CRON[1412594]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 15 04:17:01 proxmox CRON[1412593]: pam_unix(cron:session): session closed for user root
Mar 15 04:22:16 proxmox smartd[675]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 78 to 79
Mar 15 04:33:11 proxmox systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Mar 15 04:33:13 proxmox pveupdate[1416848]: <root@pam> starting task UPID:proxmox:00159E95:01ECA7E7:65F3CF89:aptupdate::root@pam:
Mar 15 04:33:14 proxmox pveupdate[1416853]: update new package list: /var/lib/pve-manager/pkgupdates
Mar 15 04:33:16 proxmox pveupdate[1416848]: <root@pam> end task UPID:proxmox:00159E95:01ECA7E7:65F3CF89:aptupdate::root@pam: OK
Mar 15 04:33:16 proxmox systemd[1]: pve-daily-update.service: Deactivated successfully.
Mar 15 04:33:16 proxmox systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Mar 15 04:33:16 proxmox systemd[1]: pve-daily-update.service: Consumed 4.552s CPU time.
Mar 15 05:17:01 proxmox CRON[1428808]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 05:17:01 proxmox CRON[1428809]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 15 05:17:01 proxmox CRON[1428808]: pam_unix(cron:session): session closed for user root
Mar 15 06:17:01 proxmox CRON[1444541]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 06:17:01 proxmox CRON[1444542]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 15 06:17:01 proxmox CRON[1444541]: pam_unix(cron:session): session closed for user root
Mar 15 06:22:16 proxmox smartd[675]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 79 to 78
Mar 15 06:25:01 proxmox CRON[1446629]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 06:25:01 proxmox CRON[1446630]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Mar 15 06:25:01 proxmox CRON[1446629]: pam_unix(cron:session): session closed for user root
Mar 15 06:47:11 proxmox systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Mar 15 06:47:11 proxmox systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Mar 15 06:47:11 proxmox systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Mar 15 07:17:01 proxmox CRON[1460297]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 07:17:01 proxmox CRON[1460298]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 15 07:17:01 proxmox CRON[1460297]: pam_unix(cron:session): session closed for user root
Mar 15 08:17:01 proxmox CRON[1476089]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 08:17:01 proxmox CRON[1476090]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 15 08:17:01 proxmox CRON[1476089]: pam_unix(cron:session): session closed for user root
Mar 15 09:17:01 proxmox CRON[1491793]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 15 09:17:01 proxmox CRON[1491794]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 15 09:17:01 proxmox CRON[1491793]: pam_unix(cron:session): session closed for user root
Mar 15 09:17:43 proxmox pvestatd[984]: auth key pair too old, rotating..
-- Reboot --
 
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