[ZBX-3267] Zabbix API trigger update Created: 2010 Dec 07  Updated: 2017 May 30  Resolved: 2010 Dec 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: API (A)
Affects Version/s: 1.8.4rc2
Fix Version/s: 1.8.4

Type: Incident report Priority: Major
Reporter: hamid sfandiari Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

freebsd 8 64bit mysql5.5 php5.2, http://andrewfarley.com/zabbix_php_api


 Description   

i wanna update a trigger via API but i get the "cannot update tirgger" . i have checked all of access permission , all is ok but i am still getting cannot update by the error code 32602

Login OK!
Tue, 07 Dec 10 13:01:11 +0330
CURL URL: http://81.91.129.14/zabbix/api_jsonrpc.php
<br>CURL Options: Array
(
[19913] => 1
[13] => 30
[78] => 5
[81] =>
[64] =>
[52] => 1
[74] => 1
[10023] => Array
(
[0] => Content-Type: application/json-rpc
[1] => User-Agent: ZabbixAPI v1.0 - http://andrewfarley.com/zabbix_php_api
)

[10036] => POST
[10015] => {"auth":"1ca202fe363ad0033abea702f5e8bd9a","method":"trigger.update","id":1,"params":

{"status":0,"triggerid":"40601"}

,"jsonrpc":"2.0"}
[10102] => gzip
)
Got response from API: ({"jsonrpc":"2.0","error":

{"code":-32602,"message":"Invalid params.","data":"[ CTrigger::update ] Trigger [Port Status of 001 is now at UP mode ]: cannot update"}

,"id":1})
Response decoded: (Array
(
[jsonrpc] => 2.0
[error] => Array
(
[code] => -32602
[message] => Invalid params.
[data] => [ CTrigger::update ] Trigger [Port Status of 001 is now at UP mode ]: cannot update
)

 Comments   
Comment by Artem Suharev (Inactive) [ 2010 Dec 07 ]

Fixed trigger updating through API. But you still can't update trigger value, that is not something that should be updated by user.

Comment by hamid sfandiari [ 2010 Dec 07 ]

i didn't want to update trigger value. I wanna change trigger status like somthing which written in zabbix apu ducumetatio exampl of trigger.update

Comment by richlv [ 2010 Dec 14 ]

the original issue is supposed to be fixed - if it's still reproducible in 1.8 svn head, please reopen

Generated at Fri Apr 19 22:14:43 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.