Working item turns not supported

[Keitamax]

Hi,
There is a behaviour i don't understand about the items status. I have an item the used to work fine. This morning, I don't know why, it has turned unsupported. When I turn it back to Active, it sends me good data for 1 or 2 minutes, and then self turns back again to Not supported! So frustrating....
Do you know where this behaviour could come from?

[toksick]

I have the exact same problem!

Hello,

I have the exact same problem as above. It seems it only happens with active agent (in use with User Parameter).

I don't find any error message in the logs (zabbix_agentd.log, zabbix_server.log, /var/log/message or /var/log/secure)

It works fine for some time, then after a few minutes it turns <not_supported>, and then after a while it comes back to <active>, and so on...

I have zabbix_server version 1.8.1 and I upgraded the zabbix_agentd to 1.8.10...

It works fine on some other hosts... I have this problem on 2 hosts (all the hosts is set to monitor the same things).

Does anyone has a clue? I've been searching for a fix for hours with no luck at all

Any tip would be greatly appreciated!

[eversor]

Same Problem

I'm having this exact problem. I have a number of user defined tests (UserParameter) set up on 2 machines. One machine is rock solid, the items never bounce to "Not Supported", the other machine bounces back and forth ("Not Supported", then "Supported") every 5 minutes or so. I have been unable to find any reason for this. The server doesn't really state it's reasoning for setting the status of Not Supported to an item anywhere.
I have tried changing the checking time on the item as well as in the agent, thinking the server may not be getting a response in an appropriate amount of time, but that did not help at all.
If anyone knows what causes this, it would be very helpful.

[nail]

[1060]:  Active check [ACH1_PS[localhost:80,test1,test2]] is not supported. Disabled.

got this on monitored host.
Using Zabbix 2.0, timeouts increased to 30 sec.
Getting this error only on single host, 2 others work fine.

Is there a way to disable the auto switch to "not supported" ?

[HullZabbix]

Possibly worth noting I get this with active system.cpu.util[,,avg1] check. It'll be fine for <5 mins then switch to not supported at seemingly random intervals. Then it'll re-enable it's self and start working again for a short period of time.

This is only on 4 servers out of around 20!