Search results

  1. Z

    Syslog is spammed with: unable to determine idle time

    Actually no. I can't see any spikes in CPU usage when this happens. When /lib/systemd/system/lxcfs.service was running with the -l flag, there was a problem with one tool. The CPU usage was always at 100%, and if I recall, correctly, it was htop when top, glances and monitoring solution showed...
  2. Z

    Syslog is spammed with: unable to determine idle time

    Some time ago I started to receive syslog errors like this every few seconds for all containers in a physical node: bindings.c: 4526: cpuview_proc_stat: cpuX from /lxc/CID/ns has unexpected cpu time: 9164403 in /proc/stat, 9393872 in cpuacct.usage_all; unable to determine idle time I added flag...

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!