1.1beta5 - user-defined item disables unexpectedly

[disparo]

Hello!

Since beta3 i had these string in zabbix-agentd.conf:

UserParameter=pm_exec.cpu_load,pm_exec.cpu_load.sh | sed s/,/./

it worked till i made update to beta5.

Now! In 'Status' column i saw "Not supported". Well, i checked script availability - it works! When i disables and enables item back, 'Status' column changes to "Active", but when i'm opening 'Monitoring -> Latest data', there's no data from this item

After 5 minutes i looked into "Items" configuration. Status of item became "Not Supported" again...

Wazzup???

[KarmaPolice]

Hello!

Since beta3 i had these string in zabbix-agentd.conf:

UserParameter=pm_exec.cpu_load,pm_exec.cpu_load.sh | sed s/,/./

it worked till i made update to beta5.

Now! In 'Status' column i saw "Not supported". Well, i checked script availability - it works! When i disables and enables item back, 'Status' column changes to "Active", but when i'm opening 'Monitoring -> Latest data', there's no data from this item

After 5 minutes i looked into "Items" configuration. Status of item became "Not Supported" again...

Wazzup???

Without seeing inside pm_exec.cpu_load.sh i can't tell you for sure what's going wrong with the parameter itself (it does appear to be formatted fine)...

The bit about the item going to "Not Supported" is exactly what it should do if it is not receiving a value for that item from the agent.

When you set it back to active manually you are overiding that status and so it sits in an active state until the agent responds again without any data (at which point it sets itself to "Not Supported" again)....

have you tried just running "pm_exec.cpu_load.sh | sed s/,/./" and see if it returns a single value? Are you sure you have your item defined properly in the zabbix server setup? Those are the two places i would check first, however nothing you've explained above is "abnormal behavior" for Zabbix

[cameronsto]

To further what KarmaPolice said, I think this can also happen when the script returns an invalid value, not just an empty value.

-cameron

[elvis]

I have almost the same problem. script which works fine with 1.1beta 2 stops working, (output become NOT SUPPORTED) in 1.1beta3 (Solaris).

After I tried every combination that I can think of with no success, I stoped Beta3 agent, started Beata2 and all works with script from begining.

something is changed (or broken) with agent 1.1beta3 (at least for Solaris)

BTW script in question is:

#!/usr/bin/perl
$vmstat = `vmstat 1 2`;
# Parse vmstat data
@temp1 = split /^/m, $vmstat;
$temp2 = @temp1[3];
@line = split /\s+/, $temp2;
$user = $line[20];
$system = $line[21];
print $user+$system;