[ZBX-7319] Critical error. Field [showdisabled] is not integer on clicking configuration-web button Created: 2013 Nov 07  Updated: 2017 May 30  Resolved: 2014 Jun 06

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.8.18
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Constantine Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 1
Labels: dm, trivial
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

[root@zabbix ~]# uname -a
Linux zabbix.srvlan.local 2.6.32-358.18.1.el6.x86_64 #1 SMP Fri Aug 2 17:04:38 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@zabbix ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)


 Description   

By coincidence i was able to do this:
If i go to web-configuration, then select some host that doesn't have scenarios assigned, press [ Show disabled scenarios ] and try to open web-configuration again I will get

ERROR: Zabbix has received an incorrect request
Critical error. Field [showdisabled] is not integer

Have to go to db and do

delete from profiles where userid=100100000000003;

to get back to webchecks config.

 Comments   
Comment by Wagz [ 2014 Jan 09 ]

The resolution did not work for me.

SELECT * FROM `profiles` WHERE `idx`='web.httpconf.showdisabled';
returns the row in question.

The value_str column is set to '1'. Changing that to a number one without the quotes corrects the issue.
Most likely, the update of that field is occurring on the value_str column and instead should be updating the value_int column, although I have not looked close enough to see if that is the case. It may just be that the value_str needs to be updated without the single quotes.

Comment by Oleksii Zagorskyi [ 2014 Jun 06 ]

Cannot reproduce it n 1.8.21.
This is a minor issue. And even if there is a bug but probably will not be fixed for 1.8
Especially that there are nodes, which support removed for 2.4

Closed.

Generated at Sat Apr 27 03:56:59 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.