Hi, I have a problem with my MySQL sensor with the error "The given key was not present in the dictionary." Previously it looked fine but now I didn't see my live MySQL graph dashboard. Any idea how I can fix it?

DB host : MariaDB version 10.6

Thanks


Article Comments

Hello, I'm afraid our current mysql connector does not support mariadb 10.6 due to the change in the charset definitions in mariadb 10.6. There's a bug on their side. Have a look here:

- https://jira.mariadb.org/browse/MDEV-26105
- https://github.com/mysql/mysql-connector-net/pull/41/files

The Sensor is not able to connect to mariadb 10.6 without that fix being merged I'm afraid.


Feb, 2022 - Permalink

Hello,

the main problem is not mariaDB but the .Net connector. MariaDB just introduced a new datatype.

The patch Timo linked was declined, because the programmer didn't accept the oracle license. But another patch that did the same changes was accepted and merged into version 8.28.

https://github.com/mysql/mysql-connector-net/commit/16ad749586b0e5eb1aad127e3744096692e4a6ae

So now Paessler needs to use a client version >= 8.28 to gain support for mariaDB >= 10.6 .

best regards Benedikt


Mar, 2022 - Permalink

Hello Benedikt,

Yes, you are right. We need to use a client version >= 8.28 to gain support for mariaDB >= 10.6. This is already planned for the upcoming PRTG version 22.x.76 which will be released next month (April 2022).


Mar, 2022 - Permalink

Just a quick question, would this affect MySQL Version 8.0.29? Reason for the question is we have a MySQL v2 sensor giving the "The given key was not present in the dictionary." error out of the blue, but looks like an upgrade to the MySQL package on the server updated this morning.

CentOS Linux release 7.9.2009

[root@cloud snmp]# grep -i updated /var/log/yum.log | grep mysql
Apr 26 04:41:48 Updated: mysql-community-common-8.0.29-1.el7.x86_64
Apr 26 04:41:51 Updated: mysql-community-client-plugins-8.0.29-1.el7.x86_64
Apr 26 04:41:52 Updated: mysql-community-libs-8.0.29-1.el7.x86_64
Apr 26 04:41:54 Updated: mysql-community-client-8.0.29-1.el7.x86_64
Apr 26 04:41:54 Updated: mysql-community-icu-data-files-8.0.29-1.el7.x86_64
Apr 26 04:42:07 Updated: mysql-community-server-8.0.29-1.el7.x86_64
Apr 26 04:42:08 Updated: mysql-community-devel-8.0.29-1.el7.x86_64
Apr 26 04:42:08 Updated: mysql-community-libs-compat-8.0.29-1.el7.x86_64
Apr 26 04:42:21 Updated: mysql-shell-8.0.29-1.el7.x86_64

Apr, 2022 - Permalink

As we updated the MySQL data library that PRTG uses to version 8.0.28, it should not affect version 8.0.29.

You might also find further information to this error in the log files of the affected sensor. For this you can activate the "Store Result" option in the sensor settings. You'll then find the logs on the corresponding probe at "C:\ProgramData\Paessler\PRTG Network Monitor\Logs\sensors".

If you want us to take a closer look as well, feel free to reach out to us directly per mail at support@paessler.com.


Apr, 2022 - Permalink