search

Icinga / icinga-core

Icinga 1.x, the old core (EOL 31.12.2018)
GNU General Public License v2.0
45 stars 27 forks source link

ido2db fails with mariadb >10.2? #1598

Open optiz0r opened 7 years ago

optiz0r commented 7 years ago

After upgrading mariadb from 10.1 to 10.2.9, ido2db no longer runs with the following error:

Oct 09 20:35:40 localhost ido2db[21633]: Client connected, data available.
Oct 09 20:35:40 localhost ido2db[21633]: Handling client connection...
Oct 09 20:35:40 localhost ido2db[21633]: Error: Could not connect to mysql database: 2059: Plugin pvio_socket could not be loaded: not initialized
Oct 09 20:35:40 localhost ido2db[21633]: Error: database connection failed, forced client disconnect...
Oct 09 20:35:40 localhost ido2db[21633]: Successfully disconnected from mysql database

This looks like it could be similar to this upstream mariadb issue: https://jira.mariadb.org/browse/CONC-277 And this Akonadi bug: https://bugs.kde.org/show_bug.cgi?id=383991#c4 Which was worked around with this change to QtSql: https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08&id=b145f47f000978b9d39edc1882849ec7f6b3ef79

NigelCunningham commented 7 years ago

pam_mysql has a "disconnect_every_op" setting. Can you confirm that it is left at the default (false) value?

optiz0r commented 7 years ago

@NigelCunningham pam_mysql package is not installed, and there is no /etc/pam.d/mysql config file on this system.

dnsmichi commented 6 years ago

This likely affects libdbi then, where we don't have any chance to add a workaround, if I am not mistaken.