Not supported by ZABBIX agent

[johnl]

hi,

i was wondering if anyone has a solution or come across this before. we are using a couple of perl scripts to monitor some services on our servers. i added them as user paramaters and they work fine but after a while (maybe 15mins or more) the zabbix status for these items switches to "Not supported". i can change them to 'monitored' and they will work for another 15mins or so before switching back to not supported.

i am currently using zabbix1.7alpha.

thanks
john

[eWebtricity]

check the zabbix_agentd.log or the zabbix_suckerd.log for any clues?

[johnl]

checked the log but it only shows the UserParameter switching to Unsupported. Alexei - could it be due to the cron job and zabbix accessing the output/result file at the same time that trips the agent to Unsupported.

thanks
john

[jack]

I am also experiencing the same problem with my UserParameter. Sometimes it stays up for minutes, sometimes hours, with luck it will stay for a day or two. But eventually it will go back to Unsupported.

My UserParameter does not produce any file, not is it in the crontab. It's just a simple tool that checks some udp services and writes the result to stdout. When I manually run the tool, it finishes in less than half a second and I have set my zabbix's timeout to 3 minutes so it is unlikely caused by performance reasons.

One possible reason I can think of is packet loss or any other types of lack of response from servers. In such case, my tool will exit with return code 1, with no output. Does anyone know of a better way to handle this? I could have print zero so Zabbix will not disable it after 3 failures, but zero is a very common valid value in my monitored item so I don't want to pollute the statistics.

[jack]

Correction: 30 seconds, not 3 minutes.