Server is Debian 10, Zabbix 5.0
Proxy is Ubuntu 20.04, Proxy 5.0, Agent2 5.0

Hi,

Thanks for reaching out to public bug tracker.

Can you please list all the templates that are assigned to this agent2 host? Are they stock templates from 5.0 without any modifications?

Can you please attach a screenshot of the error as seen on item? Is this custom item?

Also are there any other items which show single quote in the error message? You can check this in database with query: 

SELECT hosts.hostid,items.key_ FROM item_rtdata
JOIN items ON (items.itemid=item_rtdata.itemid)
JOIN hosts ON (hosts.hostid=items.hostid)
WHERE item_rtdata.error="'";

Hi Kristians,

there are 210 items returned from your sql query of which are >200 stock Zabbix templates. The hosts are Raspberry Pis with Ubuntu. The affected items come from all templates, and all items are affected. The Zabbix Agent2 and Proxy where compiled by me, as you don't have arm ubuntu builds in your repository, but I compiled them using the source packages available from the correct Ubuntu repository, and I did not apply any patches. Besides, it's working properly besides showing these "error". Interestingly, no other host is affected. I pretty sure I deleted the templates when upgrading Zabbix, and imported the 5.0 templates from git.

Template App Zabbix Proxy
Template Module ICMP Ping
Template OS Linux by Zabbix agent

Hi Max,

Can you please share some screenshots of the mentioned error? 

Which Ubuntu version are you using? I will see if I can replicate this 

Thanks,

Kristians

Hi Kristians,

I was positive I attached a screenshot...  They are running 20.04 arm64, respectively 20.04 armhf.

Thanks for the screenshot, quite a lot of those errors.

Where is your proxy installed? On the same Pi or somewhere else? What settings have you configured for the proxy?

These are the configuration files. The Agent2 is installed on the same device as the proxy.
 

# grep -vE "^#|^$" /etc/zabbix/zabbix_agent2.conf
PidFile=/var/run/zabbix/zabbix_agent2.pid
LogFile=/var/log/zabbix/zabbix_agent2.log
LogFileSize=0
Server=127.0.0.1
ListenIP=127.0.0.1
ServerActive=127.0.0.1
Include=/etc/zabbix/zabbix_agent2.d/*.conf
ControlSocket=/tmp/agent.sock
TLSConnect=psk
TLSAccept=psk
TLSPSKIdentity=psk
TLSPSKFile=/etc/zabbix/psk
DenyKey=system.run[*]
 
# grep -vE "^#|^$" /etc/zabbix/zabbix_proxy.conf
Server=<fqdn>
LogType=system
LogFile=/var/log/zabbix/zabbix_proxy.log
LogFileSize=0
PidFile=/var/run/zabbix/zabbix_proxy.pid
SocketDir=/var/run/zabbix
DBName=/var/lib/zabbix/zabbix_proxy
DBUser=zabbix
ProxyOfflineBuffer=14
SNMPTrapperFile=/var/log/snmptrap/snmptrap.log
Timeout=4
ExternalScripts=/usr/lib/zabbix/externalscripts
FpingLocation=/usr/bin/fping
Fping6Location=/usr/bin/fping6
LogSlowQueries=3000
StatsAllowedIP=127.0.0.1
TLSConnect=psk
TLSAccept=psk
TLSPSKIdentity=psk
TLSPSKFile=/etc/zabbix/psk

Hi Max,

I was unable to reproduce this issue and I don't see any errors like you do, everything seems to be working fine. With that said I don't think this is a bug with proxy or server but rather something Agent2 related. We have an arm build for Raspbian which works the same as other Zabbix installations that you can get from our repositories and as far as I know it doesn't have any issues.

I would suggest maybe to do a clean install of Zabbix from source. Run

make uninstall

from source code directory and after wards check and clear any remaining zabbix binaries in /usr/bin/ /usr/sbin/ /usr/local/etc /etc/zabbix/ or wherever you installed it. Also don't forget to clear the database also by dropping it or just deleting/ renaming db file. And after that do a fresh install again following the documentation https://www.zabbix.com/documentation/current/manual/installation/install

And in case you were upgrading existing installation you can check the docs here: https://www.zabbix.com/documentation/current/manual/installation/upgrade/sources

Also make sure that Zabbix Server and Zabbix Proxy are the same versions.

Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, I will be closing this ticket. Thank you for understanding. 

Hi Kristians,

Thank you for your answer.

Actually, I can't find Agent2 as an arm build in your repository at all. It doesn't seem as if it exists. Additionally, I'd like to install it from your tarball, but unfortunately it is outdated, and your git doesn't have a 5.0.1 tag or branch. As you requested, I should try with the same versions of zabbix-server and zabbix-proxy, but I won't downgrade my production zabbix-server just for this test.

Besides, how doesn't this qualify as a bug? It's at least a cosmetic one.

Regards,
Max

Hi Max,

Apologies, yes it seems that Zabbix Agent 2 is missing from Raspbian repository, it should be added soon. Also you can download source code for 5.0.1 from here: https://github.com/zabbix/zabbix/releases/tag/5.0.1 

As for why it doesn't qualify as a bug - this issue should be reproducible with the same results and that was not the case using Zabbix Agent 2 5.0.0 and Zabbix proxy 5.0.0 compiled from source  (https://cdn.zabbix.com/zabbix/sources/stable/5.0/zabbix-5.0.0.tar.gz) on Ubuntu 20.04 arm64 with Zabbix Server 5.0.1 running elsewhere. If it were a problem with source code, then this issue should affect more than just arm platform builds. This seems to be something more specific to your environment which would fall under commercial support and services and not a public bug.

Regards,
Kristians

I'm using Zabbix 5.0 server and agent compiled from source without a proxy.  I have two custom templates for monitoring ZoL (ZFS on Linux) and MySQL.  All of the discovered items showed a single quote in the 'info' column as seen in the attached screenshot.  Some items were Zabbix Trapper and some were Zabbix Agent. 

This occurred after upgrading from 4.4 to 5.0  A database query that removes the single quote from item_rtdata.error clears the appearance of error in the UI.

I can also confirm that it is reproduce-able though.  If I unlink and clear the template, then link again as new, the issue returns.  Perhaps this is template related?  Let me know if I can provide any further detail.

Hi don

Can you please confirm what flags are you using when compiling from sources? On what OS is this happening?

Thanks,
Kristiāns

Zabbix was installed from sources on Gentoo with the following configuration options:

$ ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/zabbix-5.0.1 --htmldir=/usr/share/doc/zabbix-5.0.1/html --libdir=/usr/lib64 --enable-agent --enable-ipv6 --disable-java --enable-proxy --enable-server --disable-static --with-libcurl --without-ldap --without-libxml2 --with-mysql --without-unixodbc --with-openipmi --without-oracle --without-postgresql --with-net-snmp --without-sqlite3 --without-ssh2 --with-openssl

No LLD macros or preprocessor steps were used.

Versions of Zabbix dependencies are:

dev-db/mysql-connector-c-6.1.11-r2
dev-libs/libevent-2.1.10
dev-libs/libpcre-8.43
dev-libs/openssl-1.1.0k
net-analyzer/net-snmp-5.8-r1
net-misc/curl-7.65.3
sys-devel/gcc-9.3.0
sys-libs/gdbm-1.18.1
sys-libs/glibc-2.30-r8
sys-libs/openipmi-2.0.27-r1
sys-libs/zlib-1.2.11-r2

This is not a fresh installation, however.  It was an upgrade from Zabbix 4.4.  Post upgrade I ran into the unsupported charset or collation for tables error and followed steps identified by the following bug report in order to resolve.

ZBX-17357

I have also since found that creating a new single item produces the same results.

This error still occurs after upgrading to Zabbix 5.0.3.  I have enabled DebugLevel=5 and am attaching the zabbix_server.log.gz file.  "test.client.discovery" and "test_bytes_received" are patterns you can search for to see debug output regarding this issue.  This test discovery is incredibly simple.  No preprocessing, LLD macros, filters, or overrides are being used.  test_bytes_received is of type "Zabbix trapper" so no data is collected for it.

In troubleshooting I have created a new database and updated zabbix_server.conf to use it.  The problem does not occur with a new database and the same binaries.  This issue doesn't seem to be related to compile time options or libraries.