Can't remove Percona-XtraDB-Cluster-server with yum/rpm

Bug #1069829 reported by Sheeri K. Cabral
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released
Undecided
Raghavendra D Prabhu

Bug Description

When trying to yum remove Percona-XtraDB-Cluster-server, the removal just hangs, and if I hit Ctrl-C I get:

Error in PREUN scriptlet in rpm package Percona-XtraDB-Cluster-server

Similarly, removing with rpm also just hangs, and if I hit Ctrl-C I get:

error: %preun(Percona-XtraDB-Cluster-server-1:5.5.27-23.6.356.rhel6.x86_64) scriptlet failed, signal 2

Full transcripts, with information:

[<email address hidden> ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 6.3 (Santiago)
Kernel \r on an \m
[<email address hidden> ~]# rpm -qa | grep -i percona
Percona-XtraDB-Cluster-galera-2.0-1.114.rhel6.x86_64
Percona-XtraDB-Cluster-shared-5.5.27-23.6.356.rhel6.x86_64
percona-xtrabackup-2.0.3-470.rhel6.x86_64
Percona-XtraDB-Cluster-server-5.5.27-23.6.356.rhel6.x86_64
Percona-XtraDB-Cluster-client-5.5.27-23.6.356.rhel6.x86_64
[<email address hidden> ~]# rpm -qa | grep -i mysql
[<email address hidden> ~]# yum remove Percona-XtraDB-Cluster-server Percona-XtraDB-Cluster-client
Loaded plugins: rhnplugin, security
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package Percona-XtraDB-Cluster-client.x86_64 1:5.5.27-23.6.356.rhel6 will be erased
--> Processing Dependency: mysql for package: percona-xtrabackup-2.0.3-470.rhel6.x86_64
---> Package Percona-XtraDB-Cluster-server.x86_64 1:5.5.27-23.6.356.rhel6 will be erased
--> Running transaction check
---> Package percona-xtrabackup.x86_64 0:2.0.3-470.rhel6 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

==================================================================================================
 Package Arch Version Repository Size
==================================================================================================
Removing:
 Percona-XtraDB-Cluster-client x86_64 1:5.5.27-23.6.356.rhel6 @percona 29 M
 Percona-XtraDB-Cluster-server x86_64 1:5.5.27-23.6.356.rhel6 @percona 68 M
Removing for dependencies:
 percona-xtrabackup x86_64 2.0.3-470.rhel6 @percona 11 M

Transaction Summary
==================================================================================================
Remove 3 Package(s)

Installed size: 108 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
^CError in PREUN scriptlet in rpm package Percona-XtraDB-Cluster-server
[<email address hidden> ~]# rpm -e Percona-XtraDB-Cluster-server Percona-XtraDB-Cluster-client percona-xtrabackup
^Cerror: %preun(Percona-XtraDB-Cluster-server-1:5.5.27-23.6.356.rhel6.x86_64) scriptlet failed, signal 2
[<email address hidden> ~]#

Tags: pkg

Related branches

Revision history for this message
Sheeri K. Cabral (awfief) wrote :

seems the problem is /etc/init.d/mysql stop is taking forever, hence why it seems "hung". It would have saved a lot of grief if a message like "Stopping mysqld" would appear, so users know what's going on. Package removal shouldn't take 60 seconds, but stopping MySQL might.

So I'd say this can be "fixed" with a one-line addition that prints out "stopping mysqld" or similar just before it stops mysql.

Changed in percona-xtradb-cluster:
status: New → Confirmed
Alexey Bychko (abychko)
tags: added: pkg
Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-24.8
assignee: nobody → Ignacio Nin (ignacio-nin)
Changed in percona-xtradb-cluster:
assignee: Ignacio Nin (ignacio-nin) → Raghavendra D Prabhu (raghavendra-prabhu)
status: Confirmed → Fix Committed
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1249

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.