I think this means the server returned no active checks for the host in question. I cannot think of any other reason besides the fact that the name of the host in zabbix server frontend does not match the hostname property in the agent config (I think they may be case sensitive).
Ad Widget
Collapse
Complete HP server hardware monitoring
Collapse
X
-
I think this means the server returned no active checks for the host in question. I cannot think of any other reason besides the fact that the name of the host in zabbix server frontend does not match the hostname property in the agent config (I think they may be case sensitive). -
no, zabbix_sender is for sending custom data to the server and it lives on the monitored machine. zabbix_get is on your zabbix server and should be located in /usr/local/bin/Comment
-
Edited.
This is an error returned by the monitoring script. Sorry but the script is not fail proof, if there is a problem it fails miserably (either because WBEM providers is not installed or because there is another problem).Code:zabbix_get -s 192.168.11.21 -k hp.query[1,1] C:\Program Files (x86)\Zabbix Agent\zabbix_hp_query.vbs(43, 1) Laufzeitfehler in Microsoft VBScript: Index außerhalb des gültigen Bereichs
The code in the script that returns the error is:
This means zabbix is sending the command to the agent without the arguments [1,1]. Check if the zabbix_agentd.config file you have has a UserParameter with value hp.query[*]....zabbix_hp_query.vbs //nologo $1 $2 $3.... The asterix and the $1 $2.... are the important bits.Code:If (WScript.Arguments(0) = "1") Then
If the UserParameter is ok, try a newer version of the zabbix agent (I read that older windows versions like 1.6 could not handle arguments in UserParameters, only the linux version could).
If you are any good with vbscript you could run the script directly on the server to test using "cscript zabbix_hp_query.vbs 1 1" from a cmd window (and in the zabbix folder, obviously). If this returns a numeric result, it's the problem above. If not.. just post the result and we'll see.Last edited by mmarkwitzz; 25-05-2011, 11:06.Comment
-
This is a problem with the monitoring script. Sorry again, but the script has no error handling whatsoever. It just spits out an error if there is a problem.
Line 44 and 45 of the script is
As far as I can tell there is a problem with the WBEM providers/WMI and the WMI query does not return any valid objects to work with.Code:Set colQuery = objWMI.ExecQuery("Select * from HP_WinComputerSystem") For Each objQuery in colQuery
Try running "Test WBEM Events" on the server (runas administrator for Windows 2008) and see if you get an error.
You could run the script directly on the server to test using "cscript C:\zabbix\zabbix_hp_query.vbs 1 1" and post back the results.Comment
-
Try running the script directly on the monitored computer from cmd.exe as described in the reply I gave to gizmo15 a couple of posts higher. Depending on the message you get it could be a zabbix config problem, a wmi problem or a script issue. My money is on the config.Comment
-
It works for me, thanks a lot.
I have some questions:
- Is it possible to install WBEM on a Windows 2000 server? And if it is, where is the link to download it because I didn't find it.
- I can see the status of my trigger in the overview page: Why don't some servers have all the trigger? There are unsupported. Do they depend upon the hardware? And I have a trigger in the Problem status, but I don't know what's wrong, how can I interprate the value (2 2OK3DEG4ER for example) in order to deal with the problem.
Thanks for advanceComment
-
-I think you cannot install on win2000. Wbem/wmi was introduced on win xp. However, i think you can install an update from microsoft to enable wmi for win 2000, in which case you could try to install the hp wbem providers for 2003 server.It works for me, thanks a lot.
I have some questions:
- Is it possible to install WBEM on a Windows 2000 server? And if it is, where is the link to download it because I didn't find it.
- I can see the status of my trigger in the overview page: Why don't some servers have all the trigger? There are unsupported. Do they depend upon the hardware? And I have a trigger in the Problem status, but I don't know what's wrong, how can I interprate the value (2 2OK3DEG4ER for example) in order to deal with the problem.
Thanks for advance
-The triggers available depend on the hardware and what hp gives us access to via the drivers. I have not tested but i believe all info available in hp system insight manager are also be available as triggers in zabbix.
Some others simply dont work via wbem providers. An example is the power source wattage - ilo reports ok, wmi returns nothing. You should always have all the important ones available in zabbix, though, and you will always have the 'hp system status' trigger to warn you even if no specific trigger is available.
-If you have a problem you will either get 'degraded' or 'error/failed' triggers. The actual value will not help you.
You could view the values for log/text keys which log the error description returned by wbem, but they are rarely useful. You can use ilo webpage or hp insight homepage to get further details.Comment
Comment