NSClient++ Help (#1) - Checking for old Files (#443) - Message List

Hello,

Absolutely First I define the following aliases:

mime1=checkFile2 filter=in path=x:\nscp pattern=*.txt filter+written=<1d MaxWarn=1 MaxCrit=1 "syntax=%filename% %write%"
mime2=checkFile2 filter=in path=\\192.168.0.1\data\nscp pattern=*.txt filter+written=<1d MaxWarn=1 MaxCrit=1 "syntax=%filename% %write%"

Then I run in test mode and get the following:

mickem@gotrek:~/nsc$ $nrpe -c mime1
test.txt Tuesday, October 13, 2009 17:12:15, test.txt: 1 > critical|'test.txt'=1;1;1;
mickem@gotrek:~/nsc$ $nrpe -c mime2
test.txt Tuesday, October 13, 2009 17:12:15, test.txt: 1 > critical|'test.txt'=1;1;1;

So now we know "UNC" paths are working... lets move on...

Then I start the service and run the commands and I get:

mickem@gotrek:~/nsc$ $nrpe -c mime1
CheckFile ok|'no files found'=0;1;1;
mickem@gotrek:~/nsc$ $nrpe -c mime2
CheckFile ok|'no files found'=0;1;1;

Now this is might at first glancve seem like a bug but it is the correct results. The reason is that the service runs as "local system"(?) and "local system" does not have access to the shares above (if you check the nscp log you can see something fishy is going on).

Anyways, changing the user to "mickem" (the one I use which has access to the shares in question) gives the following: (since I don't have AD at home it is sort of hard to give fine grained access to the service user).

mickem@gotrek:~/nsc$ $nrpe -c mime1
CheckFile ok|'no files found'=0;1;1;
mickem@gotrek:~/nsc$ $nrpe -c mime2
test.txt Tuesday, October 13, 2009 17:12:15, test.txt: 1 > critical|'test.txt'=1;1;1;

Again this is expected the reason this time is that the mapped drives is mapped by me in my session where as the service is my user it does not share my session. But the second one works splendidly since it accesses thew remote share and not the mapped drive.

Presumably you can also add the "x:\" to the login script of the service but I have not tested that.

All of this is pretty much basic "Windows administrator 101" (or for that matter Unix administrator 101).

And I know that a lot of the problem people have is related to accounts and security and such but unfortunately it is outside the scope of this wiki to have windows configuration and administration tips.

Though I would like to add that perhaps I shall add a better error message since the only thing you get in the log is:

2009-10-13 19:33:58: debug:NSClient++.cpp:1073: Injecting: checkFile2: filter=in, path=x:\nscp, pattern=*.txt, filter+written=<1d, MaxWarn=1, MaxCrit=1, syntax=%filename% %write%
2009-10-13 19:33:58: debug:modules\CheckDisk\CheckDisk.cpp:116: Input is: x:\nscp / ffffffff
2009-10-13 19:33:58: debug:modules\CheckDisk\CheckDisk.cpp:119: Found a file dont do recursive scan: x:\nscp
2009-10-13 19:33:58: debug:modules\CheckDisk\CheckDisk.cpp:334: Looking for: path: x:, pattern: nscp
2009-10-13 19:33:58: debug:modules\CheckDisk\CheckDisk.cpp:122: Path is: x:

Which, unfortunately, does not really tell you what the problem is. I shall investigate this but unfortunately the "recursive model" used now is not really good for handling errors.

I hope this help! If not please send the debug log of NSClient++ running.

Michael Medin