[ZBX-11142] Zabbix server stops to send notifications after IBM DB2 SQL error (string escaping). Created: 2016 Aug 30  Updated: 2017 May 30  Resolved: 2016 Oct 11

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.0.4
Fix Version/s: None

Type: Incident report Priority: Blocker
Reporter: Oleg Ivanivskyi Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: actions, db2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 3.0.4
SLES12sp1
DB2 Express-C v10.5fp7

Issue Links:
Duplicate

 Description   

Zabbix server stops to send notifications after this error:

  6161:20160818:105058.988 [Z3005] query failed: [-10] 42603 [IBM][CLI Driver][DB2/LINUXX8664] SQL0010N  The string constant beginning with "'VMSSSSSTEST: New error message in Windows Application log  Zabbix tim" does not have an ending string delimiter.  SQLSTATE=42603 [insert into alerts (alertid,actionid,eventid,userid,clock,mediatypeid,sendto,subject,
message,status,error,esc_step,alerttype) values (9475994,74,4977300,56,1471506658,1,'[email protected]','VMSSSSSTEST: New error message in Windows Application log','VMSSSSSTEST: New error message in Windows Application log
Zabbix timestamp: 2016.08.17 15:29:21
Agent timestamp: 2016.08.17 15:29:09
Source="SSSSS" Severity=Error

Serious: Unexpected return code:
        Message catalog: 1, Message number: 1000
        Context: SOAP Message parsing failed : sss-complex-type.2.4.b: The content of element ''ns2:ReadExpandedCorresp
ondents'' is not complete. One of ''{"sss:sssss:sss:ssss":Identifier}'' is expected.
        Program: SS_appsrv, file: Logerrorssssss, line: 11, function:LogerrorOperation::E.',0,'',1,0);
]

Looks similar to ZBX-3255.

 Comments   
Comment by Glebs Ivanovskis (Inactive) [ 2016 Aug 30 ]

Isn't it related to ZBX-11072?

Comment by Oleg Ivanivskyi [ 2016 Aug 30 ]

This issue is actual for the patched version (Zabbix 3.0.4 with installed ZBX-11072 patch).

Comment by Aleksandrs Saveljevs [ 2016 Aug 30 ]

Rumor has it that the error message contains some interesting characters. oleg.ivanivskyi, could you please attach the relevant part of the log as a file instead of pasting it?

Comment by Oleksii Zagorskyi [ 2016 Aug 31 ]

Hexademical 0x0B is detected at the end of received and inserted to history_log table value.
The problem appear when escalator tries to expand {ITEM.VALUE} macro to make an insert then to alerts table.
The item is eventlog[].
Well, these specific characters are at end of the value: C3 88 C5 BE 45 0B but the very last 0B is supposedly the reason.

Comment by Sergejs Paskevics [ 2016 Aug 31 ]

Please provide the result of the following query:

select * from history_log where value like 'VMSSSSSTEST: New error message in Windows Application log%' and value like '%2016.08.17 15:29:21%';
Comment by Oleksii Zagorskyi [ 2016 Aug 31 ]

The value (with the hexademical chars) is already missing in the table, it was altered to let zabbix to recover.
Part from the SQL "VMSSSSSTEST: New error message in Windows Application" comes not from history_log, but from action settings.

Comment by Sergejs Paskevics [ 2016 Sep 01 ]

Could you please get info about database codepage?
command:

db2 get db cfg for <database_name>

params:

Database territory 
Database code page 
Database code set 
Database country/region code
Comment by Sergejs Paskevics [ 2016 Sep 14 ]

Combination of characters at the end of string - C3 88 C5 BE 45 0B, doesn't affect the processing. On our test systems it is working correctly.
The problem could be related to incorrectly configured codepages, that is described here - http://www.ibm.com/support/docview.wss?uid=swg21621640

Comment by Sergejs Paskevics [ 2016 Sep 21 ]

I propose to close this issue, as the problem not revealed.

Generated at Wed Apr 30 06:45:56 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.