Recent content by aFrI

I just tested to give a sigterm, but none of the two running processes are considering it.. short strace on the one process which seems to still iterate over a log file: Update: And I am stupid, and just did find the other similar topic (GoAccess taking huge RAM allocations & running long...

TITLE GoAccess taking huge RAM allocations & running long times PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.79 Update #4 (on Debian Linux 12.15) PROBLEM DESCRIPTION Good day, As GoAccess was introduced as the new stats tool, I was switching from the former...

Thanks for taking a look - I will watchout for the EXTPLESK-4469 to be rolled out. But yes, in Grafana / Monitoring component of Plesk the /dev/sdX devices are showing up as graphs, the /dev/nvme* devices are not shown as graphs at all, nor do I see them anywhere in the Monitoring. But as this...

Forgot to add: Also gave the collectd service a restart already - but did not help the situation. Also did the hardware detect in the Plesk UI of the monitoring component - but it reported no changes.

Update from our installation: We updated to Obsidian 18.0.68 #2 (including the fix for this reported bug), but the NVMe disks did not appear in the Monitoring extension - even after some days. Uninstalling the Monitoring extension and re-install from the Plesk UI was not giving any success...

Thanks for taking a look and already having a future solution available - looking forward to have it rolled out in the future. Thanks for the great direct support, appreciated! Best regards

Also they seem to be created right away as Plesk was set up on the server by creation time and the modified also tells metrics should go in - question is why they are not showing up anyhow in the Plesk UI monitoring.. stat /opt/psa/var/health/data/localhost/disk-nvme1n1/disk_io_time.rrd File...

Here you go, the directories by devnames seem to be existing: # ls -la /opt/psa/var/health/data/localhost/ total 320 drwxr-xr-x 80 root root 4096 Jan 23 06:28 . drwxr-xr-x 3 root root 4096 Jan 16 23:08 .. drwxr-xr-x 2 root root 4096 Jan 16 23:17 cpu drwxr-xr-x 2 root root 4096 Jan 16 23:57...

to add, the structure of the Disks/RAIDs/Partitions: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 894.3G 0 disk └─md126 9:126 0 894.1G 0 raid1 /backup-raid sdb 8:16 0 894.3G 0 disk └─md126 9:126 0 894.1G 0 raid1 /backup-raid...

Obsidians still seems to watch just for /dev/sd[x] drives for having metrics gathered in Grafana. Example from one of my hosts where NVMe drives are totally ignored, while the metrics are delivered by the kernel for the drives: # cat /proc/diskstats 259 0 nvme0n1 11244539 41601...