Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Debian 10 - cannot install PS 5.7.26 after percona-toolkit

Description

I have first installed percona-toolkit, these are the packages that got installed with it:

notice that mysql-common and mariadb-common both got installed - which is strange and I'm suspecting that this is causing the problem.

After that installing PS 5.7.26:

and it gets stuck there. Service logs show nothing and the service is not fully installed. I had to kill mysqld process to get this unstuck.

/etc/mysql/my.cnf point to this:

so our config from percona-server.conf.d directory is not used, and mariadb one is basically empty.

alternatives.log has this:

If we install PS 5.7.26 first it will install fine and it will select "mysql-common" for installation also and our config will be used.
After that when we install Percona Toolkit it will also install "mariadb-common", but our config will be left working from what I see.

Environment

None

Smart Checklist

Activity

Show:

C W April 9, 2020 at 11:23 AM
Edited

Evgeniy Patlan January 21, 2020 at 8:36 AM

I have finally created libdbd-mysql-perl packages with dependency to libperconaserverclient. Seems the issue should be fixed now. Packages are available in tools experimental repo. So we need to verify that the issue is fixed. During my tests seems everything works well.

we need someone to check this together with PT-1730

David Bennett August 19, 2019 at 6:59 PM

   As we discussed,  this can be solved by distributing our own  Perl DBD driver for Percona Server.

Evgeniy Patlan July 16, 2019 at 11:28 AM

Yes this issue appears only in case if we firstly install toolkit. I think we should mention it in documentation as in order to fix this we need to maje packaging changes for and issue new version for all platforms. what do you think?

Done

Details

Assignee

Reporter

Needs QA

Yes

Time tracking

1d logged

Components

Fix versions

Priority

Smart Checklist

Created July 16, 2019 at 9:39 AM
Updated March 6, 2024 at 12:00 PM
Resolved July 13, 2021 at 4:21 PM