Hi fellow zabbix users,
right now I'm running a little test with the new beta version of 1.6 and run into some problems with remote command. Not that it is not working but zabbix_server complains like it seems about the returned value. Heres my setup:
Debian 4.0 updated running Zabbix Server and agentd in version 1.5.3 from the 4. June of 2008. Server and client can communicate with each other.
After that i installed an Action handler under "Configuration->Actions" with the name of "cmd_trigger" that does not considers any "Action conditions" (so works for every Trigger) and an "Action Operations" that runs a remote command on the zabbix_agentd.
So far so good. Script is called, it runs, my machine beeps and i'm happy. Just that little log line makes me nervous:
Also on the page under "Monitoring->Events" the Trigger shows up but the last coloum "Actions" reads "In progress" even though the script is long finished.
Is this a known bug? If not can anyone of you clearify how i can solve that log line?
Second but i guess this is solved when i return the expected value how do i get rid of "In Progress"?
Also i don't think the script is realy that bad, but who knows here you go
Hope that setuid'ing the script did not any bad.
Regards loophole
right now I'm running a little test with the new beta version of 1.6 and run into some problems with remote command. Not that it is not working but zabbix_server complains like it seems about the returned value. Heres my setup:
Debian 4.0 updated running Zabbix Server and agentd in version 1.5.3 from the 4. June of 2008. Server and client can communicate with each other.
After that i installed an Action handler under "Configuration->Actions" with the name of "cmd_trigger" that does not considers any "Action conditions" (so works for every Trigger) and an "Action Operations" that runs a remote command on the zabbix_agentd.
So far so good. Script is called, it runs, my machine beeps and i'm happy. Just that little log line makes me nervous:
Code:
9859:20080820:160734 Type of received value [1] is not sutable for [system.run[/usr/local/bin/zabbix_trigger Trigger Test: OFF,nowait]@Zabbix_Server_Agentd] having type [1219248454] 9859:20080820:160734 Returning NOTSUPPORTED
Is this a known bug? If not can anyone of you clearify how i can solve that log line?
Second but i guess this is solved when i return the expected value how do i get rid of "In Progress"?
Also i don't think the script is realy that bad, but who knows here you go
Code:
#!/bin/bash /usr/local/bin/beep -l 500 -d 100 -f 1000 -n -l 500 -d 100 -f 2000 -n -l 500 -d 100 -f 1000 2>&1 date >> /tmp/beeprun
Regards loophole
Comment