Recent content by psycho160

The systemd-journald-audit.socket error was fixed with following commands in my debian 11 lcx container: systemctl stop systemd-journald-audit.socket systemctl disable systemd-journald-audit.socket systemctl mask systemd-journald-audit.socket

Lösung: https://checkmk.com/werk/12307 Ist anscheinend ein neues Feature von LXC das noch nicht in den Agent von cmk eingabut ist. Also einfach abwarten.

Danke, kling plausibel. Werde ich checken

Hallo, habe soeben erfolgreich auf 7.0-8 aktualisiert. Soweit so gut. Checkmk meint nun bei allen meinen lxc Containern "CPU utilization-Item not found in monitoring data". Hab jetzt schon bisschen herumgespielt aber irgendwie komm ich an den Wert nicht mehr ran. Liegt das am neuen LXC 4.0...

thx, for the info. i found an amazon product comment where this error is described with especially toshiba disks. maybe a firmware issue Amazon comment i will try to rebuild my tank

only for correction, my disk is not an SSD as you said, it´s an HDD I´m afraid if i rebuild the tank, that then the other disk would alert that i use a ashift with 4K and the disk reports only 512B.. o_Oo_O

Hello, i have a zfs pool (ashift=9) and two different disks, one Seagate 4K (512e) and a Toshiba 4K (512e) My zfs setup was running about 5 months with 6.3 and after the latest proxmox update yesterday my check_mk put a warning about my zfs pool. So i looked into pve and zfs status says...