Trigger Events.jpg
[ZBX-5731] No data trigger going off even though data received sooner. Created: 2012 Oct 24 Updated: 2017 May 30 Resolved: 2013 Jul 23 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Major |
| Reporter: | Mikhail Dobrinin | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | event, proxy, server, trigger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Server appliance, proxy running on Ubuntu 12.04 |
||
| Attachments: |
Trigger Events.jpg
|
| Description |
|
Host monitored by JMX through active proxy. Active proxy forwards data to server every 30s: 28446:20121023:132855.568 In send_data_to_server ... 28446:20121023:132925.833 In send_data_to_server ... Server is receiving data every 30s. A view of the Latest Data page: 2012.Oct.23 15:44:39 30077 2012.Oct.23 15:44:09 30150 2012.Oct.23 15:43:39 30034 2012.Oct.23 15:43:09 30078 2012.Oct.23 15:42:39 29926 2012.Oct.23 15:42:10 29225 2012.Oct.23 15:41:40 30082 2012.Oct.23 15:41:10 30082 2012.Oct.23 15:40:40 30089 2012.Oct.23 15:40:10 30190 2012.Oct.23 15:39:40 30018 The trigger:
{HOSTNAME} is not reachable - {JMX Generic:jmx["java.lang:type=Runtime","Uptime"].nodata(45)}=1
Trigger is going off: 23 Oct 2012 15:44:09 ProxyJMXTest is not reachable OK High 51s No 23 Oct 2012 15:43:00 ProxyJMXTest is not reachable PROBLEM High 1m 9s No 23 Oct 2012 15:42:10 ProxyJMXTest is not reachable OK High 50s No 23 Oct 2012 15:42:31 ProxyJMXTest is not reachable PROBLEM High 21s No 23 Oct 2012 15:41:40 ProxyJMXTest is not reachable OK High 51s No 23 Oct 2012 15:42:00 ProxyJMXTest is not reachable PROBLEM High 20s No 23 Oct 2012 15:41:10 ProxyJMXTest is not reachable OK High 50s No 23 Oct 2012 15:41:30 ProxyJMXTest is not reachable PROBLEM High 20s No 23 Oct 2012 15:40:40 ProxyJMXTest is not reachable OK High 50s No 23 Oct 2012 15:41:00 ProxyJMXTest is not reachable PROBLEM High 20s No 23 Oct 2012 15:40:10 ProxyJMXTest is not reachable OK High 50s No 23 Oct 2012 15:40:30 ProxyJMXTest is not reachable PROBLEM High 20s No 23 Oct 2012 15:39:40 ProxyJMXTest is not reachable OK High 50s No 23 Oct 2012 15:40:00 ProxyJMXTest is not reachable PROBLEM High 20s No 23 Oct 2012 15:39:09 ProxyJMXTest is not reachable OK High 51s No 23 Oct 2012 15:39:30 ProxyJMXTest is not reachable PROBLEM High 21s No Trigger appears to be unstable. Sometimes it is in OK state for a while: 24 Oct 2012 11:29:41 ProxyJMXTest is not reachable High 10m 38s No -4 Oct 2012 10:29:00 ProxyJMXTest is not reachable PROBLEM High 1h 41s No 24 Oct 2012 10:28:11 ProxyJMXTest is not reachable OK High 49s No 24 Oct 2012 10:28:30 ProxyJMXTest is not reachable PROBLEM High 19s No 24 Oct 2012 10:27:41 ProxyJMXTest is not reachable OK High 49s No |
| Comments |
| Comment by Mikhail Dobrinin [ 2012 Oct 24 ] |
|
The last part should be: 24 Oct 2012 12:50:30 ProxyJMXTest is not reachable High 19s No 24 Oct 2012 12:49:41 ProxyJMXTest is not reachable High 49s No 24 Oct 2012 12:50:00 ProxyJMXTest is not reachable High 19s No 24 Oct 2012 12:49:11 ProxyJMXTest is not reachable High 49s No 24 Oct 2012 12:49:30 ProxyJMXTest is not reachable High 19s No 24 Oct 2012 12:48:41 ProxyJMXTest is not reachable High 49s No 24 Oct 2012 12:49:00 ProxyJMXTest is not reachable High 19s No 24 Oct 2012 11:29:41 ProxyJMXTest is not reachable OK High 1h 19m 19s No 24 Oct 2012 10:29:00 ProxyJMXTest is not reachable PROBLEM High 1h 41s No<<<<<Machine went off the network |
| Comment by Mikhail Dobrinin [ 2012 Oct 24 ] |
|
The number of items does not affect the problem from arising. I originally included that information because before further investigation I thought that may have contributed to the problem. With one item polled every 30 seconds there is still the trigger event going off: 24 Oct 2012 13:36:30 ProxyJMXTest is not reachable High 20s No 24 Oct 2012 13:35:40 ProxyJMXTest is not reachable High 50s No 24 Oct 2012 13:36:00 ProxyJMXTest is not reachable High 20s No 24 Oct 2012 13:35:10 ProxyJMXTest is not reachable High 50s No 24 Oct 2012 13:35:30 ProxyJMXTest is not reachable High 20s No 24 Oct 2012 13:34:40 ProxyJMXTest is not reachable High 50s No |
| Comment by richlv [ 2012 Oct 25 ] |
|
why send data every 30 seconds only ? default is one second... most likely proxy is unable to transmit all collected data quickly/timely enough, and it arrives in server with a delay. the timestamps you see for item values are assigned on the proxy, they are not indicating when server received the values. i'd suggest reducing the data sending interval to 1, 5 or even 10 seconds and seeing whether the problem goes away. |
| Comment by Mikhail Dobrinin [ 2012 Oct 25 ] |
|
Indeed that solves the problem. However, even when the rate is 30 seconds, it appears that the proxy transmits the data just fine. I've tested it with a single host monitored with a single item and the problem exists. |
| Comment by richlv [ 2012 Oct 25 ] |
|
is that a single host with single item on a single proxy, and the only thing monitored by a server ? |
| Comment by Alexei Vladishev [ 2013 Jul 23 ] |
|
I am closing it for now, feel free to reopen in case of any news. |