• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Big problem with Plesk update

Azurel

Azurel

Silver Pleskian
Panel version 11.5.30 Update #39, last updated at April 6, 2014 03:50 AM
OS CentOS 6.5 (Final)

Today plesk try update to #40 and this not working:
Failed to update Panel. To close this message, click here.
Click to expand...

Side effect. Mysql is down, plesk gui reports 502 (nginx) => I must server reboot.
 
Have you tried install latest MU with autoinstaller in CLI? Any logs?
 
Command line I can test in 14hours.

I think it was a problem with mysql? See red lines below:

InnoDB: Unable to lock ./ibdata1, error: 11

mysql-error.log
Version: '5.5.36-cll-lve' socket: '/var/lib/mysql/mysql.sock' port: 0 MySQL Community Server (GPL) by Atomicorp
140414 3:33:08 [Note] /usr/libexec/mysqld: Normal shutdown

140414 3:33:08 [Note] Event Scheduler: Purging the queue. 0 events
140414 3:33:10 [Warning] /usr/libexec/mysqld: Forcing close of thread 3541115 user: 'admin'

140414 3:33:10 [Warning] /usr/libexec/mysqld: Forcing close of thread 3541114 user: 'admin'

140414 3:33:10 [Warning] /usr/libexec/mysqld: Forcing close of thread 3540981 user: 'admin'

140414 3:33:10 [Warning] /usr/libexec/mysqld: Forcing close of thread 3540977 user: 'admin'

140414 3:33:10 InnoDB: Starting shutdown...
140414 3:33:10 InnoDB: Waiting for 33 pages to be flushed
140414 3:33:11 InnoDB: Shutdown completed; log sequence number 133255195720
140414 3:33:11 [Note] /usr/libexec/mysqld: Shutdown complete

140414 03:33:11 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140414 03:33:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140414 3:33:13 [Note] libgovernor.so not found
140414 3:33:13 [Note] Plugin 'FEDERATED' is disabled.
140414 3:33:13 InnoDB: The InnoDB memory heap is disabled
140414 3:33:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140414 3:33:13 InnoDB: Compressed tables use zlib 1.2.3
140414 3:33:13 InnoDB: Using Linux native AIO
140414 3:33:13 InnoDB: Initializing buffer pool, size = 256.0M
140414 3:33:13 InnoDB: Completed initialization of buffer pool
140414 3:33:13 InnoDB: highest supported file format is Barracuda.
140414 3:33:13 InnoDB: Waiting for the background threads to start
140414 3:33:14 InnoDB: 5.5.36 started; log sequence number 133255195720
140414 3:33:14 [Note] Event Scheduler: Loaded 0 events
140414 3:33:14 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.36-cll-lve' socket: '/var/lib/mysql/mysql.sock' port: 0 MySQL Community Server (GPL) by Atomicorp
140414 3:33:37 [Note] /usr/libexec/mysqld: Normal shutdown

140414 3:33:37 [Note] Event Scheduler: Purging the queue. 0 events
140414 3:33:37 InnoDB: Starting shutdown...
140414 3:33:39 InnoDB: Shutdown completed; log sequence number 133255294368
140414 3:33:39 [Note] /usr/libexec/mysqld: Shutdown complete

140414 03:33:39 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140414 03:33:51 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140414 3:33:51 [Note] libgovernor.so not found
140414 3:33:51 [Note] Plugin 'FEDERATED' is disabled.
140414 3:33:51 InnoDB: The InnoDB memory heap is disabled
140414 3:33:51 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140414 3:33:51 InnoDB: Compressed tables use zlib 1.2.3
140414 3:33:51 InnoDB: Using Linux native AIO
140414 3:33:51 InnoDB: Initializing buffer pool, size = 256.0M
140414 3:33:51 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140414 3:33:51 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140414 03:33:52 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140414 03:34:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140414 3:34:58 [Note] libgovernor.so not found
140414 3:34:58 [Note] Plugin 'FEDERATED' is disabled.
140414 3:34:58 InnoDB: The InnoDB memory heap is disabled
140414 3:34:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140414 3:34:58 InnoDB: Compressed tables use zlib 1.2.3
140414 3:34:58 InnoDB: Using Linux native AIO
140414 3:34:58 InnoDB: Initializing buffer pool, size = 256.0M
140414 3:34:58 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140414 3:34:58 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.

same lines again and again.....

140414 03:54:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140414 03:59:04 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140414 3:59:04 [Note] libgovernor.so not found
140414 3:59:04 [Note] Plugin 'FEDERATED' is disabled.
140414 3:59:04 InnoDB: The InnoDB memory heap is disabled
140414 3:59:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140414 3:59:04 InnoDB: Compressed tables use zlib 1.2.3
140414 3:59:04 InnoDB: Using Linux native AIO
140414 3:59:04 InnoDB: Initializing buffer pool, size = 256.0M
140414 3:59:04 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140414 3:59:04 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140414 03:59:05 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Click to expand...


sw-engine.log
[14-Apr-2014 03:33:15] NOTICE: Terminating ...
[14-Apr-2014 03:33:15] NOTICE: exiting, bye-bye!

is not restartet. Restartet with server reboot...

[14-Apr-2014 09:42:10] NOTICE: fpm is running, pid 2187
[14-Apr-2014 09:42:11] NOTICE: ready to handle connections
Click to expand...


yum.log
Apr 14 03:33:06 Updated: pp11.5.30-bootstrapper-11.5.30-cos6.build115140407.17.x86_64
Apr 14 03:33:32 Updated: mysql-libs-5.5.37-22.el6.art.x86_64
Apr 14 03:33:34 Updated: mysql-5.5.37-22.el6.art.x86_64
Apr 14 03:33:52 Updated: mysql-server-5.5.37-22.el6.art.x86_64
Apr 14 03:33:53 Updated: mysql-devel-5.5.37-22.el6.art.x86_64
Apr 14 03:33:56 Updated: psa-phpmyadmin-4.1.12-cos6.build115140407.17.noarch
Click to expand...


cron.log
Apr 14 03:32:01 mail anacron[5469]: Job `cron.daily' started
Apr 14 03:32:01 mail run-parts(/etc/cron.daily)[6093]: starting 00webalizer
Apr 14 03:32:02 mail run-parts(/etc/cron.daily)[6110]: finished 00webalizer
Apr 14 03:32:02 mail run-parts(/etc/cron.daily)[6093]: starting 50plesk-daily
Apr 14 03:35:08 mail run-parts(/etc/cron.daily)[14756]: finished 50plesk-daily
Apr 14 03:35:08 mail run-parts(/etc/cron.daily)[6093]: starting awstats
Apr 14 03:35:08 mail run-parts(/etc/cron.daily)[14764]: finished awstats
Apr 14 03:35:08 mail run-parts(/etc/cron.daily)[6093]: starting logrotate
Apr 14 03:35:16 mail run-parts(/etc/cron.daily)[15067]: finished logrotate
Apr 14 03:35:16 mail run-parts(/etc/cron.daily)[6093]: starting makewhatis.cron
Apr 14 03:35:17 mail run-parts(/etc/cron.daily)[15320]: finished makewhatis.cron
Apr 14 03:38:00 mail anacron[5469]: Job `cron.daily' terminated (mailing output)
Apr 14 03:46:01 mail CROND[2914]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
Apr 14 03:52:01 mail anacron[5469]: Job `cron.weekly' started
Apr 14 03:52:01 mail run-parts(/etc/cron.weekly)[14054]: starting 50plesk-weekly
Apr 14 03:52:01 mail run-parts(/etc/cron.weekly)[14066]: finished 50plesk-weekly
Apr 14 03:52:01 mail anacron[5469]: Job `cron.weekly' terminated
Apr 14 03:52:01 mail anacron[5469]: Normal exit (2 jobs run)
Apr 14 04:01:01 mail CROND[31435]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
Apr 14 04:01:01 mail CROND[31436]: (root) CMD (run-parts /etc/cron.hourly)
Apr 14 04:01:01 mail run-parts(/etc/cron.hourly)[31436]: starting 0anacron
Apr 14 04:01:01 mail run-parts(/etc/cron.hourly)[31450]: finished 0anacron
Apr 14 04:01:01 mail run-parts(/etc/cron.hourly)[31436]: starting plesk-php-cleanuper
Apr 14 04:01:01 mail run-parts(/etc/cron.hourly)[31473]: finished plesk-php-cleanuper
Apr 14 04:16:01 mail CROND[26459]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
Apr 14 04:31:02 mail CROND[21476]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
Apr 14 04:46:01 mail CROND[16877]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
Apr 14 05:01:01 mail CROND[10552]: (root) CMD (run-parts /etc/cron.hourly)
Apr 14 05:01:01 mail CROND[10553]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
Apr 14 05:01:01 mail run-parts(/etc/cron.hourly)[10552]: starting 0anacron
Apr 14 05:01:01 mail run-parts(/etc/cron.hourly)[10563]: finished 0anacron
Apr 14 05:01:01 mail run-parts(/etc/cron.hourly)[10552]: starting plesk-php-cleanuper
Apr 14 05:01:01 mail run-parts(/etc/cron.hourly)[10583]: finished plesk-php-cleanuper
Click to expand...

When update fails, than plesk not reatart all services and try again next day?


EDIT: In CLI is this command?:
# /usr/local/psa/admin/bin/autoinstaller
Click to expand...
 
Last edited:
You must log in or register to reply here.

Similar threads

S
Issue 500 Plesk\Exception\Database || DB query failed: SQLSTATE[HY000] [2054] Server sent charset (0) unknown to the client.
Replies
1
Views
2K
Peter Debik
P
D
Resolved Problems after updating Plesk to version 18.0.57 on AlmaLinux 8.8
Replies
4
Views
2K
Peter Debik
P
H
Question Windows server2019 Plesk - hangs the screen Please Wait
Replies
1
Views
2K
Peter Debik
P
D
Resolved After enabling MSMTP: sw-service unable to start
Replies
2
Views
2K
dbitsch
D
K
Question Error message during Plesk Updates “Warning: install PAM module not successed” (PAMConfig.confset.PAMServiceError: system-auth)
Replies
2
Views
2K
johnrdorazio
J
Back
Top