Mount Point Monitoring

[s.diwakar1]

I am using the Nagios Core 4.4.3

We are monitoring the Mount Points using the Script: "./check_mount.sh"
https://exchange.nagios.org/directory/P ... is/details

One Mount Point is giving the Continuous Alerts: "WARNING - /backup is mounted several times! (2)"

There is no issue with the server.

Kindly suggest.

[Box293]

Same response as your other post:

You are going to need to run the command that the plugin runs manually when the issues is occurring. The command in the plugin is:

Code: Select all

MOUNTED=`mount | grep "$MOUNT" | grep -c "$FS "`            # execute the command to check the mount...

So as the nagios user run:

Code: Select all

mount

The output generated from this should help determine exactly what the issue is. Please paste the entire output here.

[s.diwakar1]

Here is the output of command that you shared:

XXX:/export/common/util on /util type nfs4 (rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp,addr=xxx,clientaddr=xxx)
XXX:/backup on /backup type nfs (ro,addr=xxx)
XXX:/export/common/backup on /zfstst type nfs4 (rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp,addr=xxx,clientaddr=xxx)

The issue is still going on.

There is no issue at the server end. Mount Point "/backup" is mounted only one time. But it is generating continuous alert "Mounted several times(2)."

[Box293]

So what is the output like 10 times in a row, or 20 times?. We need to nail down any sort of pattern.

[s.diwakar1]

can you please explain in detail the meaning of your last reply??

I can't understand "what is the output like 10 times in a row, or 20 times?"

[s.diwakar1]

can anyone help me out to resolve this issue?

[scottwilkerson]

The problem is, this plugin is written in such a way, that it is just greps the output of mount for what you are passing, and if you pass /backup it is finding multiple matches

XXX:/backup on /backup type nfs (ro,addr=xxx)
XXX:/export/common/backup on /zfstst type nfs4 (rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp,addr=xxx,clientaddr=xxx)

You probably could modify the plugin somehow to get around this, or contact the author