Loading...

XML

Word

Printable

Type: Incident report
Resolution: Duplicate
Priority: Critical
Fix Version/s: None
Affects Version/s: 3.0.1
Component/s: Server (S)
Labels:
None
Environment:

Hide
Server VM:
Zabbix server: 3.0.1 Revision 58734 26 February 2016, compilation time: Feb 28 2016 07:18:05
DB: Ver 15.1 Distrib 5.5.47-MariaDB, for Linux (x86_64) using readline 5.1

Proxy VM:
Zabbix proxy: 3.0.1 Revision 58734 26 February 2016, compilation time: Feb 28 2016 07:22:30
DB: sqlite

Agents: Windows Server 2008R2, Windows Server 2012R2
Zabbix agent 3.0.0.58455

Show
Server VM: Zabbix server: 3.0.1 Revision 58734 26 February 2016, compilation time: Feb 28 2016 07:18:05 DB: Ver 15.1 Distrib 5.5.47-MariaDB, for Linux (x86_64) using readline 5.1 Proxy VM: Zabbix proxy: 3.0.1 Revision 58734 26 February 2016, compilation time: Feb 28 2016 07:22:30 DB: sqlite Agents: Windows Server 2008R2, Windows Server 2012R2 Zabbix agent 3.0.0.58455

Pereodicaly all cyrillic characters in items and triggers created by LLD replaced with question marks.
All LLDs is active agent checks with vfs.file.contents key (no encoding specified). Files for LLD are generated by our scripts and written in UTF-8 w/o BOM.

We tried setting encoding in mysql config like in forum thread below, but now cyrillic items in several hosts are complitely replaced by question marks (even normal items not from LLD).

See also: https://www.zabbix.com/forum/showpost.php?p=181016&postcount=1