[ZBX-7516] [Z3005] query failed: [1054] Unknown column 'impi_disable_until' in 'field list' Created: 2013 Dec 10  Updated: 2017 May 30  Resolved: 2013 Dec 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.2.1
Fix Version/s: 2.2.2rc1, 2.3.0

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

Ubuntu 12.04


Issue Links:
Duplicate
is duplicated by ZBX-7514 PostgreSQL fatal error after upgrade ... Closed
is duplicated by ZBX-7584 Unknown column 'impi_errors_from' in ... Closed

 Description   

Since the upgrade from Zabbix 2.2.0 to 2.2.1 we get the log entries like this:

20808:20131210:132514.061 [Z3005] query failed: [1054] Unknown column 'impi_disable_until' in 'field list' [update hosts set impi_disable_until=1386678374,impi_error='cannot connect to IPMI host: [16777411] Unknown error 16777411' where hostid=10086]
20808:20131210:132520.070 [Z3005] query failed: [1054] Unknown column 'impi_disable_until' in 'field list' [update hosts set impi_disable_until=1386678335,impi_error='cannot connect to IPMI host: [16777345] Unknown error 16777345' where hostid=10109]

Obviously there is a typo, because usually there are filed with name "ipmi_disable_until" but not "impi_disable_until" (m and p swapped).

Searching trough the source code, I found the problematic place:
src\zabbix_server\poller\poller.c line 236

<< sqlset_prefix = "impi_";
>> sqlset_prefix = "ipmi_";

Changing this and recompiling made the error go away



 Comments   
Comment by Aleksandrs Saveljevs [ 2013 Dec 10 ]

Introduced in r40376 while fixing ZBX-7184.

Comment by Aleksandrs Saveljevs [ 2013 Dec 10 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7516 .

Comment by Andris Zeila [ 2013 Dec 10 ]

Successfully tested

Comment by Aleksandrs Saveljevs [ 2013 Dec 10 ]

Fixed in pre-2.2.2rc1 r40889 and pre-2.3.0 (trunk) r40890.

Comment by AndreaConsadori [ 2013 Dec 12 ]

same issue in centos 6 and mysql db

Generated at Fri Apr 26 06:14:32 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.