Proxmox PVE 8.2-1 unresponsive after a few days

[islandtime]

Greetings. Proxmox PVE 8.2-1 host becomes unresponsive after a few days. It responds to ping, but no SSH or Web Interface. VMs are also unresponsive. The server needs to be power cycled in order to recover. In a few days again the same thing will happen.

Here are the errors that repeat from a remote syslog server:

/usr/sbin/ksmtuned: line 105: [: too many arguments
/usr/sbin/ksmtuned: line 79: /usr/bin/awk: Input/output error
/usr/sbin/ksmtuned: line 79: /usr/bin/ps: Input/output error
/usr/sbin/ksmtuned: line 83: /usr/bin/awk: Input/output error
/usr/sbin/ksmtuned: line 131: /usr/bin/sleep: Input/output error
/usr/sbin/ksmtuned: line 111: [: -lt: unary operator expected
/usr/sbin/ksmtuned: line 105: [: too many arguments
/usr/sbin/ksmtuned: line 79: /usr/bin/awk: Input/output error

Any help is greatly appreciated. I am a newbie but very excited about Proxmox.

 

[UdoB]

You gave us zero information about your setup. The more details you post here, the greater the chance for a helpful reply ;-)

Did you watch the RAM usage? Did you overcommit RAM? Is your storage set up with redundancy? Which filesystem does you host use?

Please start by giving us some information, like the copy-n-pasted output of some commands, run on a PVE host (either via SSH or via "Datacenter --> <one Node> --> Shell", both ways allow copy-n-paste):

Hardware information:

• lscpu # the CPU with its capabilities ("Flags")
• free -g # RAM availability including Swap. Units set to "GiB"

PVE System information:

• pveversion -v

PVE Storages/Disks:

• pvesm status #
• df -h | grep -v subvol- # disk usage without listing ZFS datasets used for containers

Those are examples. You may add/edit commands and options if you can enrich the information given. Oh, and please put each command in a separate [CODE]...[/CODE]-block for better readability.