Zabbix item on host works but goes unsupported on zabbix server

[snetadmin]

Hi guys,

We have a cronjob that outputs results to a file. Then we have a zabbix item that will call out to the python script to grab the result.

The test works when run manually on the zabbix server but when I leave it alone, the zabbix item just becomes unsupported by itself.

When we execute the zabbix item manually, it works but not automatically.

Anyone have any ideas here on what I can do to resolve this issue?

All the other zabbix items is setup the same way but it started doing this behavior with this new zabbix item.

[cyber]

If item becomes unsupported, there is a red "!" besides it... what does it say there, if you hover mouse over it or click on it?

[snetadmin]

At first, it works for a while but then after a while it goes and stays unsupported stating "Value of type "string" is not suitable for value type "Numeric (unsigned)". Value """.
It's weird because I setup other zabbix items that same way and this is the first for me that it's starting to behave this way.

[cyber]

Anything in agents log? It looks like in some reason an empty value is returned, which is considered as string and will invalidate item as it expects Number... This is something you need to debug locally.. Add some logging to script or something.

[snetadmin]

I checked the agent logs and all it says is that it's unsupported. I can manually execute the item and the value returns a normal value.
However, after a minute it goes unsupported.