[ZBX-4424] Handling of the log of long Japanese Created: 2011 Dec 08  Updated: 2017 May 30  Resolved: 2011 Dec 11

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Server (S)
Affects Version/s: 1.8.8, 1.8.9
Fix Version/s: 1.8.10, 1.9.9 (beta), 2.0.0

Type: Incident report Priority: Blocker
Reporter: suzuka Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: items, localization
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL CentOS 5.6, 6.0 Postgresql-8.4.7



 Description   

I am monitoring Windows EventLog.

When Zabbix Server receives the log of 255 or more Japanese characters(512 bytes or more ?), an error is outputted and data is not registered.

This problem occurs in zabbix1.8.8 and 1.8.9 and it does not coour in 1.8.7 and 1.8.6.

I guess that there is a problem in handling of the Japanese character after 255 character in 1.8.8 or later.

The following is a log when I test.

1) Zabbix v1.8.8
Japanese char 254 -> correct

[pg_log]

2011-12-08 11:06:03 JST: 4352: LOG: duration: 0.480 ms statement: insert into alerts (alertid,actionid,eventid,userid,clock,mediatypeid,sendto,subject,message,status,alerttype,esc_step) values (4703,4,40420,3,1323309963,4,'sasaki@localhost','[????] Error is output to ApplicationLog on Windows2008: PROBLEM','?????????????

Error is output to ApplicationLog on Windows2008: PROBLEM
Last value: ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

',0,0,0)

[zabbix_server.log]

none

2) Zabbix v1.8.8
Japanese char 255 -> Not correct

[pg_log]

2011-12-08 11:10:32 JST: 4354: ERROR: invalid byte sequence for encoding "UTF8": 0xe32720
2011-12-08 11:10:32 JST: 4354: HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding".
2011-12-08 11:10:32 JST: 4354: ERROR: current transaction is aborted, commands ignored until end of transaction block
2011-12-08 11:10:32 JST: 4354: STATEMENT: insert into history_log (id,itemid,clock,timestamp,source,severity,value,logeventid) values (8,25109,1323310227,1323310148,'EventCreate',4,'???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????',1000);

2011-12-08 11:10:32 JST: 4354: ERROR: current transaction is aborted, commands ignored until end of transaction block

[zabbix_server.log]

3688:20111208:111032.678 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: invalid byte sequence for encoding "UTF8": 0xe32720
HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encodi
ng".
[update items set lastclock=1323310227,lastlogsize=15486,mtime=0,prevvalue=lastvalue,lastvalue='??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<E3>' where itemid=25109;
]
3688:20111208:111032.679 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of tra
nsaction block
[insert into history_log (id,itemid,clock,timestamp,source,severity,value,logeventid) values (8,25109,1323310227,1323310148,'EventCreate',4,'?
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????',1000);
]
3688:20111208:111032.679 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of tra
nsaction block
[select distinct t.triggerid,t.type,t.value,t.error,t.expression,f.itemid from triggers t,functions f,items i where t.triggerid=f.triggerid and
f.itemid=i.itemid and t.status=0 and f.itemid in (25109) order by t.triggerid]

3) Zabbix v1.8.7
Japanese char 254 -> correct

[pg_log]

2011-12-08 11:34:34 JST: 5504: LOG: duration: 0.747 ms statement: insert into alerts (alertid,actionid,eventid,userid,clock,mediatypeid,sendto,subject,message,status,alerttype,esc_step) values (4705,4,40681,3,1323311674,4,'sasaki@localhost','[????] Error is output to ApplicationLog on Windows2008: PROBLEM','?????????????

Error is output to ApplicationLog on Windows2008: PROBLEM
Last value: ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

',0,0,0)

[zabbix_server.log]

none

4) Zabbix v1.8.7
Japanese char 255 -> correct

[pg_log]

2011-12-08 11:38:05 JST: 5504: LOG: duration: 0.764 ms statement: insert into alerts (alertid,actionid,eventid,userid,clock,mediatypeid,sendto,subject,message,status,alerttype,esc_step) values (4706,4,40682,3,1323311885,4,'sasaki@localhost','[????] Error is output to ApplicationLog on Windows2008: PROBLEM','?????????????

Error is output to ApplicationLog on Windows2008: PROBLEM
Last value: ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

',0,0,0)

[zabbix_server.log]

none



 Comments   
Comment by Alexander Vladishev [ 2011 Dec 11 ]

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

Comment by dimir [ 2011 Dec 12 ]

Please review my changes in r23928.

<Sasha> Great! CLOSED

Comment by Alexander Vladishev [ 2011 Dec 13 ]

Fixed in version pre-1.8.10, revision 23950.

Generated at Fri Mar 29 02:35:02 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.