You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the disk.py library there is a direct shell call to /sbin/udevadm.
I have found on some systems e.g. ubuntu server 20.04 the binary is located at /bin/udevadm, which results in no DEVNAME returned by the udevadm function.
This is the corresponsing snipped from the code: success, result = shell.shell_exec('/sbin/udevadm info --query=property --name={}'.format( device, ))
Would it be possible to first find out the correct path via e.g. which udevadm or call it directly via just udevadm?
In my usecase thr newly released disk-io plugin from the linuxfabrik-monitoring-plugins collection is missing the most important disks due to this bug.
In the disk.py library there is a direct shell call to
/sbin/udevadm
.I have found on some systems e.g. ubuntu server 20.04 the binary is located at
/bin/udevadm
, which results in no DEVNAME returned by the udevadm function.This is the corresponsing snipped from the code:
success, result = shell.shell_exec('/sbin/udevadm info --query=property --name={}'.format( device, ))
Would it be possible to first find out the correct path via e.g.
which udevadm
or call it directly via justudevadm
?In my usecase thr newly released disk-io plugin from the linuxfabrik-monitoring-plugins collection is missing the most important disks due to this bug.
The text was updated successfully, but these errors were encountered: