• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Mysql upgraded today and doesn't start anymore

M

mr-wolf

Silver Pleskian
Plesk Guru
I have a Plesk server running CentOs 6.8
Just now MySQL stopped working and after some troubleshooting I found out it was due to an upgrade performed.
I believe the upgrade is initiated by Plesk, but I'm not sure.

Anyone knows how to resolve?

Code: 
# /etc/init.d/mysqld start
MySQL Daemon failed to start.
Starting mysqld:                                           [FAILED]

# ls -l /usr/bin/mysqld_safe
-rwxr-xr-x. 1 root root 26K Mar 10 17:30 /usr/bin/mysqld_safe


Code: 
# grep -i mysql /var/log/yum.log
Jan 04 15:46:20 Updated: plesk-mysql-server-17.0.17-cos6.build1700161028.14.x86_64
Jan 04 16:42:01 Updated: atomic-php54-php-mysqlnd-5.4.45-54.el6.art.x86_64
Jan 04 16:47:22 Installed: plesk-php71-mysql-7.1.0-centos6.16120617.x86_64
Jan 04 18:40:24 Updated: atomic-php56-php-mysqlnd-5.6.26-40.el6.art.x86_64
Jan 04 18:40:35 Updated: atomic-php70-php-mysqlnd-7.0.11-11.el6.art.x86_64
Jan 04 18:40:45 Updated: atomic-php55-php-mysqlnd-5.5.38-38.el6.art.x86_64
Jan 24 04:12:50 Updated: plesk-php56-mysql-5.6.30-centos6.17012012.x86_64
Jan 24 04:12:50 Updated: plesk-php70-mysql-7.0.15-centos6.17011919.x86_64
Jan 24 04:12:51 Updated: plesk-php71-mysql-7.1.1-centos6.17011917.x86_64
Feb 20 14:55:45 Updated: plesk-php70-mysql-7.0.16-centos6.17021709.x86_64
Feb 20 14:55:45 Updated: plesk-php71-mysql-7.1.2-centos6.17021713.x86_64
Mar 14 09:33:54 Updated: mysql-libs-5.5.54-36.x86_64
Mar 14 09:33:55 Updated: mysql-5.5.54-36.x86_64
Mar 14 09:33:55 Updated: mysql-devel-5.5.54-36.x86_64
Mar 14 09:33:57 Updated: mysql-server-5.5.54-36.x86_64
 
Hi mr-wolf,

did you consider to inspect the MySQL - log, to investigate the root cause of the failed start of MySQL? ( i.e. /var/log/mysql )
 
Hi,

I am experiencing the same problem. Mysql was updated last night.

Yum log

Code: 
Mar 13 21:12:20 Updated: openssl-1.0.1e-48.el6_8.4.x86_64
Mar 13 21:12:22 Updated: mysql-libs-5.5.54-36.x86_64
Mar 13 21:12:22 Updated: libuuid-2.17.2-12.24.el6_8.3.x86_64
Mar 13 21:12:23 Updated: libblkid-2.17.2-12.24.el6_8.3.x86_64
Mar 13 21:12:26 Updated: util-linux-ng-2.17.2-12.24.el6_8.3.x86_64
Mar 13 21:12:29 Updated: initscripts-9.03.53-1.el6.centos.2.x86_64
Mar 13 21:12:30 Updated: mysql-5.5.54-36.x86_64
Mar 13 21:12:35 Updated: kernel-firmware-2.6.32-642.15.1.el6.noarch
Mar 13 21:12:38 Updated: selinux-policy-3.7.19-292.el6_8.3.noarch
Mar 13 21:12:57 Updated: selinux-policy-targeted-3.7.19-292.el6_8.3.noarch
Mar 13 21:13:02 Installed: kernel-2.6.32-642.15.1.el6.x86_64
Mar 13 21:13:05 Updated: mysql-server-5.5.54-36.x86_64
Mar 13 21:13:11 Installed: kernel-lt-devel-3.10.105-1.el6.elrepo.x86_64
Mar 13 21:13:12 Updated: kernel-headers-2.6.32-642.15.1.el6.x86_64
Mar 13 21:13:14 Updated: tzdata-2017a-1.el6.noarch
Mar 13 21:13:19 Installed: kernel-lt-3.10.105-1.el6.elrepo.x86_64

Mysql log
Code: 
170313 21:13:30 [Note] /usr/libexec/mysqld: Normal shutdown

170313 21:13:30 [Note] Event Scheduler: Killing the scheduler thread, thread id 1
170313 21:13:30 [Note] Event Scheduler: Waiting for the scheduler thread to reply
170313 21:13:30 [Note] Event Scheduler: Stopped
170313 21:13:30 [Note] Event Scheduler: Purging the queue. 0 events
170313 21:13:32 [Warning] /usr/libexec/mysqld: Forcing close of thread 284844  user: 'admin'

170313 21:13:32  InnoDB: Starting shutdown...
170313 21:13:34  InnoDB: Shutdown completed; log sequence number 10104835692
170313 21:13:34 [Note] /usr/libexec/mysqld: Shutdown complete

170313 21:13:34 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended


Error when starting Mysql service

Code: 
MySQL Daemon failed to start.
Starting mysqld:                                           [FAILED]

It appears it has been updated to 5.5 from 5.1

When running mysql_upgrade I get the following

Code: 
[root@s18254483 ~]# mysql_upgrade
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Error: Failed while fetching Server version! Could be due to unauthorized access.
FATAL ERROR: Upgrade failed
 
Hi, same problem with all my servers with Atomic corp repo enabled.

The problem was solved with:

Code: 
# yum downgrade mysql mysql-server mysql-libs
 
decanet said:
Hi, same problem with all my servers with Atomic corp repo enabled.

The problem was solved with:

Code: 
# yum downgrade mysql mysql-server mysql-libs
Click to expand...

Code: 
yum downgrade mysql mysql-server mysql-libs
Loaded plugins: fastestmirror
Setting up Downgrade Process
Loading mirror speeds from cached hostfile
 * atomic: www4.atomicorp.com
 * epel: ftp.uni-bayreuth.de
Resolving Dependencies
--> Running transaction check
---> Package mysql.x86_64 0:5.5.52-36.el6.art will be a downgrade
---> Package mysql.x86_64 0:5.5.54-36 will be erased
---> Package mysql-libs.x86_64 0:5.5.52-36.el6.art will be a downgrade
---> Package mysql-libs.x86_64 0:5.5.54-36 will be erased
---> Package mysql-server.x86_64 0:5.5.52-36.el6.art will be a downgrade
---> Package mysql-server.x86_64 0:5.5.54-36 will be erased
--> Finished Dependency Resolution
Error: Package: mysql-devel-5.5.54-36.x86_64 (@atomic)
           Requires: real-mysql-libs(x86-64) = 5.5.54-36
           Removing: mysql-libs-5.5.54-36.x86_64 (@atomic)
               real-mysql-libs(x86-64) = 5.5.54-36
           Downgraded By: mysql-libs-5.5.52-36.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.52-36.el6.art
           Available: mysql-libs-5.5.38-24.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.38-24.el6.art
           Available: mysql-libs-5.5.39-25.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.39-25.el6.art
           Available: mysql-libs-5.5.41-27.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.41-27.el6.art
           Available: mysql-libs-5.5.44-30.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.44-30.el6.art
           Available: mysql-libs-5.5.46-31.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.46-31.el6.art
           Available: mysql-libs-5.5.47-32.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.47-32.el6.art
           Available: mysql-libs-5.5.48-33.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.48-33.el6.art
           Available: mysql-libs-5.5.49-33.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.49-33.el6.art
           Available: mysql-libs-5.5.50-34.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.50-34.el6.art
           Available: mysql-libs-5.5.51-35.el6.art.x86_64 (atomic)
               real-mysql-libs(x86-64) = 5.5.51-35.el6.art
           Available: mysql-libs-5.1.73-7.el6.i686 (base)
               Not found
           Available: mysql-libs-5.1.73-8.el6_8.i686 (updates)
               Not found
Error: Package: mysql-devel-5.5.54-36.x86_64 (@atomic)
           Requires: real-mysql(x86-64) = 5.5.54-36
           Removing: mysql-5.5.54-36.x86_64 (@atomic)
               real-mysql(x86-64) = 5.5.54-36
           Downgraded By: mysql-5.5.52-36.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.52-36.el6.art
           Available: mysql-5.5.38-24.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.38-24.el6.art
           Available: mysql-5.5.39-25.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.39-25.el6.art
           Available: mysql-5.5.41-27.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.41-27.el6.art
           Available: mysql-5.5.44-30.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.44-30.el6.art
           Available: mysql-5.5.46-31.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.46-31.el6.art
           Available: mysql-5.5.47-32.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.47-32.el6.art
           Available: mysql-5.5.48-33.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.48-33.el6.art
           Available: mysql-5.5.49-33.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.49-33.el6.art
           Available: mysql-5.5.50-34.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.50-34.el6.art
           Available: mysql-5.5.51-35.el6.art.x86_64 (atomic)
               real-mysql(x86-64) = 5.5.51-35.el6.art
           Available: mysql-5.1.73-7.el6.x86_64 (base)
               Not found
           Available: mysql-5.1.73-8.el6_8.x86_64 (updates)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I tried the 2 suggestions at the bottom, but it did not downgrade.....
 
You must log in or register to reply here.

Similar threads

K
Issue Docker containers don't start after plesk/extension upgrades
Replies
0
Views
1K
kassi
K
L
Resolved WordPress Permalink's stopped working
Replies
5
Views
2K
smithcreate
S
E.BlackStone
Resolved ERROR: 'NoneType' object has no attribute 'run_sack'
Replies
4
Views
2K
websavers
websavers
M
Resolved Failed to update the Panel (due to autoinstall.plesk.com server problems)
Replies
6
Views
4K
mow
M
mariodieck
Issue MYSQL is down and does not start anymore / SQLSTATE[HY000] [2002] No such file or directory
Replies
8
Views
4K
HammyHavoc
H
Back
Top