Invalid drive and
Posted: Thu Nov 17, 2016 10:52 am
Hi
I am hoping someone can help a newbie please.
We have an installation of Nagios in a sensitive clients closed network to monitor 4 servers and 3 PCs on 6 sites which all connect back to a central Nagios server.
I have only just added 1 server and 3 machines on 3 of the sites using the existing config which works fine. So for all the checks drive space, memory check, CPU it works fine except on some but not all of the machines I have just added.
On some of them for C:\ Drive Space I am getting invalid drive, but that is the only drive on the machine, and on the same machines Memory Usage reports Return code of 139 is out of bounds.
As these checks work on all the other machines I am thinking that it must be something on the actual machine that is the issue. Would someone please be able to point me in the direction it could be?
One other problem I have is getting access to the machines, as I said it is a sensitive client and we have to have someone physically at the machine while we remote on as it causes an issue with one of their bespoke software packages (which is installed on all the machines working or not)
I am hoping someone can help a newbie please.
We have an installation of Nagios in a sensitive clients closed network to monitor 4 servers and 3 PCs on 6 sites which all connect back to a central Nagios server.
I have only just added 1 server and 3 machines on 3 of the sites using the existing config which works fine. So for all the checks drive space, memory check, CPU it works fine except on some but not all of the machines I have just added.
On some of them for C:\ Drive Space I am getting invalid drive, but that is the only drive on the machine, and on the same machines Memory Usage reports Return code of 139 is out of bounds.
As these checks work on all the other machines I am thinking that it must be something on the actual machine that is the issue. Would someone please be able to point me in the direction it could be?
One other problem I have is getting access to the machines, as I said it is a sensitive client and we have to have someone physically at the machine while we remote on as it causes an issue with one of their bespoke software packages (which is installed on all the machines working or not)