If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
I'm having the same issue as Phileppe, the host availability status does not update, for me I only monitor windows servers, so that's where I'm having problems. I don't know about linux agents. For me it seems to usually only update if there is a change to the availability, but not always.. i deleted the item and recreated it to see if that would get it going again, but it didn't... right now the only host that shows correct is the one for a server that was rebooted last night...
There is one server that the latest data shows a status of 2, but the server is up and running and so is the agent.. I'm collecting other data from it.. but it just shows a status of 2........ not sure why that is..?
If I stop the agent for 5-10 minutes and then turn it back on then the status updates once... but not every 60 seconds like I have configured in the item update interval setting.
Alexei.. can you let me know if this a bug with the agent, a configuration problem, or by design?
If I stop the agent for 5-10 minutes and then turn it back on then the status updates once... but not every 60 seconds like I have configured in the item update interval setting.
Alexei.. can you let me know if this a bug with the agent, a configuration problem, or by design?
It is by design. The update interval is ignored for the status item.
Alexei Vladishev
Creator of Zabbix, Product manager
New York | Tokyo | Riga My Twitter
Monitoring network interfaces (ppp) which temporary shutdown are put to "UNSUPPORTED" when using active agents and don't come back up in zabbix and so are not monitored anymore. Even the "refresh unsupported items" option doesn't help. The only workaround is to manually activate the items again.
Hi there,
I think there is a bug in zabbix agent for Windows.
It's about the vfs.fs.size key which returns a value in Byte instead of a value in KByte.
Hi,
I found another bug in the windows agent:
Under windows, net.tcp.port returns 1 when it can't etablish the connection, and 0 when it can etablish it.
the following line of network.cpp of the windows agent show the bug:
*value=1; // Port unreacheable
*value=0; // Connection successful
in the official documentation, is is written that:
net.tcp.port[<ip>, port]
Check, if it is possible to make TCP connection to port number port.
0 - cannot connect
1 - can connect
Hi,
i found a new bug:
when a host is added using his dns instead of his ip, the icmppingsec ( and icmpping i guess ) key are not working.
I prefer to use the domain name of my servers instead of their ip adresses.
Hi,
i found a new bug:
when a host is added using his dns instead of his ip, the icmppingsec ( and icmpping i guess ) key are not working.
I prefer to use the domain name of my servers instead of their ip adresses.
can you check that ?
It is not documented "feature" that has been discussed many times. Please do not post your bug reports in this thread! It is very hard to keep track of them. One post per bug report please!
Alexei Vladishev
Creator of Zabbix, Product manager
New York | Tokyo | Riga My Twitter
Comment