When setting up a new server i am facing one annoying issue. At a certain time the delay queues are filled wit a lot of items. This happens when I activate a new host which is connected to several templates. Activating it leads (at once) to ~1500 delayed items in the queue. All these items are zabbix agent checks (jmx checks for Zapcat). I cannot figure out why. It can't be a load or network related problem, this looks ok. The queue is not decreasing.
Before activating the new host (no item in the queue):
Required server performance, new values per second 38.1006
After activating:
Required server performance, new values per second 56.645
I also have another server which has a value of ~88 and no problems.
Looking at the "details" a lot of queues items have a "next check" of "01.01.1970 01:00:00". Is that correct? This leads to false alerts: triggers which rely on nodata(t) fail because they seem to be initialized with "01.01.1970 01:00:00" and evaluate to "true" at once...this is ugly.
Is there any way to track down why the items are queued?
Thanks,
Marek
Before activating the new host (no item in the queue):
Required server performance, new values per second 38.1006
After activating:
Required server performance, new values per second 56.645
I also have another server which has a value of ~88 and no problems.
Looking at the "details" a lot of queues items have a "next check" of "01.01.1970 01:00:00". Is that correct? This leads to false alerts: triggers which rely on nodata(t) fail because they seem to be initialized with "01.01.1970 01:00:00" and evaluate to "true" at once...this is ugly.
Is there any way to track down why the items are queued?
Thanks,
Marek
Comment