On a system with more than one storage partition used by EXAStorage, check_db_diskspace.py returns wrong output like this:
OK - Disk space usage of db = -140.9%, Usage in GiB = 7276.0GiB, Free space = -12441.0GiB|usage_percent=-140.9%;80.0;90.0 usage=7276.0GiB free=-12441.0GiB temp=12.0GiB temp_usage_ratio=0.3%;60.0;80.0
This seems to be cause by this line https://github.com/exasol/nagios-monitoring/blob/master/opt/exasol/monitoring/check_db_diskspace.py#L127, where it is assumed that the storage partition used by the database's volume is the only storage partition.
In our case, there is an additional storage partition that is used for an archive volume.
Apparently, the storage volume sizes are enumerated correctly, and then subtracted from the (wrong) storage partition size.
I tried, but I don't know enough Python to fix this.
On a system with more than one storage partition used by EXAStorage, check_db_diskspace.py returns wrong output like this:
OK - Disk space usage of db = -140.9%, Usage in GiB = 7276.0GiB, Free space = -12441.0GiB|usage_percent=-140.9%;80.0;90.0 usage=7276.0GiB free=-12441.0GiB temp=12.0GiB temp_usage_ratio=0.3%;60.0;80.0This seems to be cause by this line https://github.com/exasol/nagios-monitoring/blob/master/opt/exasol/monitoring/check_db_diskspace.py#L127, where it is assumed that the storage partition used by the database's volume is the only storage partition.In our case, there is an additional storage partition that is used for an archive volume. Apparently, the storage volume sizes are enumerated correctly, and then subtracted from the (wrong) storage partition size.
I tried, but I don't know enough Python to fix this.