Looks like you are using HostMonitor (not RMA) to check UNIX system. In such case you need samba client on UNIX system or NFS client on Windows system.It returns "Windows cannot find the network path, verify that the network path is correct ................"
So, why we are talking about RMA if you do not use RMA?In this case I use "Host Monitor"
In test method I use "UNC"
Thanks Max, you cleared it up for me.KS-Soft Europe wrote:Lets clarify what exactly are you going to check. As I understand, you want to check the free space on the ESX Linux, right? That's why you have installed the agent on the ESX servers, right? So, let the agent check the "Drive Space" for you!
Please note: Remote Monitoring Agent is small application that accepts requests from HostMonitor, performs test and provides information about test result back to HostMonitor.
For instance, you want to check "total free space" of /home filesystem on ESX server, where the agent is installed. To make it work, you have to setup the "UNC" test method, from the "Test By" dropdown (that is located in the top of "Test Properties window") you have to select the appropriate agent (agent that is running on the ESX server). If you do not see the necessary agent in dropdown, you can setup it using "Agents List": http://www.ks-soft.net/hostmon.eng/mfra ... #agentlist
Then you have to specify /home into "UNC" input box. That is all. The test will be performed by the agent. The agent is installed on the target machine, so you do not need to specify //servername/home/ or \servername\home\ - just /home
Could you try it once more?
Regards,
Max
You are welcome.k2teknik wrote:Thanks Max, you cleared it up for me.
Glad it works!k2teknik wrote:Now it is working, I did write "/home" in path, and bingo !
The trick is that you have to specify the "local" filesystem ("local" for the agent of course), because the test is performed by the agent, not HostMonitor.k2teknik wrote:I think that the instruction should have some sampels on how a path can look like, but if it had had so, I would not have been here
Quote from the manual:Please, let us know how it works on 2.54k2teknik wrote:So now I will try to make the agent run on vmware 2.54.
and build that test enviroment so this can be tested. Please continue with this comments - specialy regarding the installation on 3.0.1 - I'm a total geek on Linux Great! Thank you for your help.k2teknik wrote:Now I had been installing/testing on vmware ESX 2.5x.
When starting the RMA agent on the ESX it complains about share access or missing file "libstdc++.so.5".
I was searching about "libstdc++.so.5" AND Red Hat 7.x on http://rpm.pbone.net.
It returns 4 results and "libstdc++-3.2-1.i386.rpm" contains the smallest number of files inculded "libstdc++.so.5".
So I install that, and the agent runs fine.
Probably it would be better to put a start agent command into /etc/rc.d/rc.local file.k2teknik wrote:I chose to autostart the agent in /etc/inittab (it works too) with a line "rma::once:/etc/RMA/rma -d /etc/RMA/rma.ini"
Is this ok, or are there better ways ?
Normann, could you provide what more information about your Virtual configuration, please:mos-eisley wrote:but all my clients and HM server are virtual.
The only "problem" I have seen is when a "text log" test should pass/scan very large files, our backend (NFS) storage was loaded heavily, but these were files above 1 Gb.