ZBX_NotSupported in 2.2 but working in 2.0.8

[Vapochilled]

Hello everyone,

I'm having a very weird issue.
Im using Zabbix 2.0.8 ofr the production lab

In parallel I have installed a 2.2 to monitor a test lab and check the new features, performance, etc.



Here is my problem:
- I have one Discovery rule that will run a script I have (agent_active) and find some specific services in that host.
- When I run the 1st time the zabbix_get from zabbix_server
[root@PTPET ~]# zabbix_get -s 10.91.76.10 -k "OSSServices"

{"data":[
{"{#OSSSERVICE}":"netfs-sprintlab357vm4"},
{"{#OSSSERVICE}":"cpfnx2s-sprintlab357vm4"},
{"{#OSSSERVICE}":"OMAgentAF-sprintlab357vm4"},
{"{#OSSSERVICE}":"db"}]}


It works!!

Few seconds after...
[root@PTPET ~]# zabbix_get -s 10.91.76.10 -k "OSSServices"
ZBX_NOTSUPPORTED


:\


If I connect this host to my production system...
The script and the rule works.
Also.. as you can see the JSON seems to be ok.

Is this a bug from 2.2?

[Vapochilled]

Hi guys,

I've discovered my problem and this might be usefull to other guys.
The problem here was the timeout flag.

By default 2.2 is bringing a timeout = 3 secs
This discovery that I run just once (because I don't need to discover all the services on that host more than once) takes around 3 or 4 secs.

Because the Zabbix default in 2.2 is 3secs in the agents, I had ZBX not supported.
I believe this should be changed to timeout message in the GUI.
It was really difficult to see why it was failing..... in fact it is not ZBX_notsupported.. but should be timed-out.