1.1beta9: UserParameter keeps saying "unsupported" though zabbix_get sees value

[dcrandall]

Hi,

zabbix-1.1beta9, server running on FreeBSD 5.4 STABLE

Ok, I have UserParameters defined in my client's zabbix_agentd.conf that run scripts to get various peices of data, and Items defined for them.

For some reason the zabbix server keeps marking them "unsupported" even though I can use zabbix_get and see the live data retrieved by the zabbix_agentd on the clients!

I can disable, then activate the unsupported parameters, they become active and return values again, then after a short time they become unsupported again.

I'm having this problem with just about all of my client side UserParameters.

This is driving me nuts.
HELP!

Daniel

[erisan500]

I've had the exact same behavior with plain vanila snmp items running on Centos, but the problem dissapeared when i installed beta9.

I know it doesn't help you, maybe others can jump in here.

EriSan

[dcrandall]

At what point it is necessary to increase the number of preforked trappers and agents in the agentd and server configs?

Daniel

[dcrandall]

So I'm noticing that zabbix_agentd built in parameters are also randomly going "unsupported".

It's weird because on one box, all the parameters will be supported, while on an identical machine some builtin parameters and UserParameters are shown as
"unsupported."
Again the zabbix_get does return valid values for the parameters in question. It's just the zabbix server that seems to be having the problem.

Daniel

[dcrandall]

Ok, I think I've figured it out.

The time out in the zabbix client .confs and server .confs was still set to 3.
I set them to 30 and all of the the items magically stopped falling in to unsupported.

I'm guessing that and alternative fix, probably preferable, would be to increase the number of preforked agents on the clients and trappers on the server.
I need to find information on this in order to determine what number is apropriate for each.

Daniel