Error in parsing of filesystem usage when monitoring NFS mounts
Dear fellow xymon users,
I monitor filesystems on one of my xymon clients. This went really well until switching to NFS. I managed to list and monitor the NFS mount, but the parsing of the transmitted string for the disk usage seems to go wrong at some point:
Xymon says: /BACKUP (172% used) has reached the PANIC level (95%)
But in reality, some lines below, it shows the correct value of 64%: 172.X.X.X:/Backup 26T 17T 9.3T 64% /BACKUP
I guess xymon parses the IP address of the NFS and takes this as the disk usage. Any hints on how to edit the parsing or other help on how to solve this would be highly appreciated.
Kind Regards,
i. A. Marcus Mundt
forsa Gesellschaft für Sozialforschung und statistische Analysen mbH Schreiberhauer Straße 30 10317 Berlin Telefon: (0 30) 6 28 82-0 Telefax: (0 30) 6 28 82-4 00 E-Mail: Marcus.Mundt at forsa.de
AG Berlin-Charlottenburg HRB 80391 Geschäftsführer: Prof. Manfred Güllner
On Thu, March 26, 2015 3:37 am, Marcus Mundt wrote:
Dear fellow xymon users,
I monitor filesystems on one of my xymon clients. This went really well until switching to NFS. I managed to list and monitor the NFS mount, but the parsing of the transmitted string for the disk usage seems to go wrong at some point:
Xymon says: /BACKUP (172% used) has reached the PANIC level (95%)
But in reality, some lines below, it shows the correct value of 64%: 172.X.X.X:/Backup 26T 17T 9.3T 64% /BACKUP
I guess xymon parses the IP address of the NFS and takes this as the disk usage. Any hints on how to edit the parsing or other help on how to solve this would be highly appreciated.
Marcus,
Can you provide the OS type you're running on, along with a copy of the full '[df]' section that's coming back in the client report?
Also, which version are you running on the server?
Regards,
-jc
On 26 March 2015 at 21:37, Marcus Mundt <marcus.mundt at forsa.de> wrote:
I monitor filesystems on one of my xymon clients. This went really well until switching to NFS. I managed to list and monitor the NFS mount, but the parsing of the transmitted string for the disk usage seems to go wrong at some point
I would think that NFS-mounted filesystems would be monitored on the server that hosted them, rather than other servers that mount them.
#df -Pl -x iso9660 -x $EXCLUDES | sed -e '/^[^ ][^ ]*$/{
without "l" lists NAS_BACKUP_DAILY
df -hP -x iso9660 -x $EXCLUDES | sed -e '/^[^ ][^ ]*$/{
You've replaced "df -Pl" with "df -hP". The "-h" changes the headers. This is important because the [df] parser specifically looks for columns with the titles "Available", "Capacity" and "Mounted" to work out what each column is for. By adding "-h" you instead get "Avail", "Use%" and "Mounted". I think when the column headers can't be found, the parser will assume that the values are in position 1, hence the "172" being interpreted as disk space usage.
Try changing "df -hP" to "df -P" and see if that works better.
J
participants (3)
-
cleaver＠terabithia.org
-
jlaidman＠rebel-it.com.au
-
marcus.mundt＠forsa.de