Configure NTFS mount points disk space monitoring

[keerthiprashanths]

Hi Team,
We would like to Configure NTFS mount points disk space monitoring when mount point paths have special characters in them.
Please provide us a document or solution for the same.

[tgriep]

When an option for a plugin has a special character in it, usually encapsulating the option in either single quotes or double quotes usually fixes the issue.
Try placing the mount name between the quotes and see if that works for you.
If not, can you post what the name of the mount is?

[keerthiprashanths]

There are 2 scenarios:-

1) -a Drive= 'F:\3PAR_Citrix_SystemDB' MinCritFree=15% MinWarnFree=20% :- The output is correct after running this command.

2) -a Drive= 'C:\#_Exc_Data_#\DB01_Log' MinCritFree=15% MinWarnFree=20% :- There is blank output. We tried this with double quotes and single quotes and without quotes also but no luck.

Please suggest what needs to be done.

[bolson]

Try running this from the command line of your nagios server escaping the special characters with the unix escape character "\"

-a Drive= 'C:\\#_Exc_Data_\#\DB01_Log' MinCritFree=15% MinWarnFree=20% And see if it returns correct data or a different error message.

[keerthiprashanths]

We tried as per the command that you have provided but still the same issue.

Screenshot attached.

Please suggest us on the same.

[dwhitfield]

That looks to me like you are running it from the run option in the XI UI, which is unreliable. Are you actually running that directly from the command line?

I assume you are using NSClient. Can you attach your nsclient.ini?

[keerthiprashanths]

We have tried to implement the command from CLI but we are getting the same error.

Please find the response from CLI and attached the nsclient.ini file of target server .

[scottwilkerson]

I'm not 100% sure, this will fix it but if we are escaping the # with a \ you should have 3 \\\ after C: because the standard in the check has 2 \\

I have a feeling that it may be because of the # special char and the best way around this would be to add the check directly to the nsclient.ini file as a custom check and yyou can put all of the directives right in the ini file and restart NSClient++, then just call the custom check name

[keerthiprashanths]

Hello Team,

We have tried that but its still the same issue.

[kyang]

I have a feeling that it may be because of the # special char and the best way around this would be to add the check directly to the nsclient.ini file as a custom check and you can put all of the directives right in the ini file and restart NSClient++, then just call the custom check name

Have you tried this?