[1.1 beta 8] problem with some UserParameters

[ProTON]

Hello,

I have some user defined parameters at one of my servers:

UserParameter=mrtgext.cpu1,/opt/zabbix/perl/nwstat.pl 10.1.1.11 UTIL1
UserParameter=mrtgext.connect,/opt/zabbix/perl/nwstat.pl 10.1.1.11 CONNECT
UserParameter=mrtgext.connmax,/opt/zabbix/perl/nwstat.pl 10.1.1.11 CONNMAX
UserParameter=mrtgext.connpeak,/opt/zabbix/perl/nwstat.pl 10.1.1.11 CONNPEAK
UserParameter=mrtgext.vmuapp,/opt/zabbix/perl/nwstat.pl 10.1.1.11 VMUAPP

As you see they are almost identical.

Now the problem. After upgrading from beta2 to beta8 one of the parameters (mrtgext.connmax) is not working. I see status "Unsupported" in item configuration page. When I try to active it, I get:

028140:20060330:164001 Parameter [mrtgext.connmax] is not supported by agent on host [<myhostname>] Old status [0]
] is not sutable for [mrtgext.connmax@<myhostname>]
028140:20060330:164001 Returning NOTSUPPORTED

I enabled debug level 4 in zabbix_agentd and it seems that it is working properly. Agent recieves request for the value and sends it back. The value sent back in my case is 255 or 256.

So I think it is something with zabbix_server. It doesn't understand a value returned or something.

I tried clearing history for that item, but it didn't help. Any ideas, thoughts?

[cameronsto]

Do the values have any leading/trailing spaces or newline characters? These have been known to cause issues in the past.

-cameron

[ProTON]

No values doesn't have any newlines or trailing spaces. As I said everything worked fine with beta2.

[ProTON]

Any more ideas? I'm a little bit desperate :|

[Alexei]

What exactly the script returns? Also check for value type of the item. Perhaps it is set to integer while you're sendinf a float, or something like this.

[ProTON]

The scripts returns "256" (without a quotes).

[root@backup perl]# ./nwstat.pl 10.1.1.11 CONNMAX
256

The value is set to "Numeric (float)" in item properties.

[ProTON]

I dumped the script into the pipe and after some investigation with HEX editor I found the problem. It was newline character indeed. Thanks to all who replied.