With previous Ubuntu versions, I used to get an output similar to this:
DISK OK - free space: / 43754 MB (80% inode=86%):
On Ubuntu 18.04.1, instead, I get:
DISK OK - free space: /var/tmp 43754 MB (80% inode=86%):
I am shown an incorrect mount point
/var/tmp for the root
I tracked this behaviour to be dependent on having
- I went to look into
/var/tmpand found a directory named
- then examined the service definition and noticed
PrivateTmp=true(which isn't there e.g. for NRPE2 on Ubuntu 16.04)
- finally, tried deleting the line and the root mountpoint was then detected as
I feel like I'm facing three options:
Live with it.
Find a reasonable workaround.
I'm inclined to just live with it, but if I were more aware of the implications of not having a private
/tmp for the service, I could make an informed choice about option 2.
The optimal solution could be to find a workaround, instructing
check_disk to return the correct mount point information even in this case. Not being able to access the system
/tmp should not represent an obstacle.
Question: Please illustrate the implications of
PrivateTmp=true, explaining why it would be recommended and in what cases and with what caveats it can be removed.
Secondary question: Is there a sensible workaround to make
check_disk or an equivalent tool display the correct root mountpoint even when run by a service with
The complete command is:
/usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /dev/mapper/vg-root. When run locally, even with the
nagios user, the output correctly shows
/. When run remotely from the Nagios server with:
/usr/local/libexec/nagios/check_nrpe2 -H 192.168.1.2 -c check_root, the output shows
/var/tmp instead of the expected