• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Upgrade Failed

guiman

New Pleskian
Hello,

I am stuck after upgrade. I tried to use # plesk repair installation, # plesk repair all but the error is always this:

ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory (Abstract.php:144)
 
Hello Peter,

thank you for your reply. Can you post please the command to restart the database server?

# systemctl restart mysqld
Failed to restart mysqld.service: Unit not found.
 
# service mariadb restart
or
# service mysql restart
or
# service mysqld restart

should do it depending on your OS and database server.
 
Job for mariadb.service failed because a timeout was exceeded. See "systemctl status mariadb.service" and "journalctl -xe" for
 
What error messages appear in /var/log/mysqld.log?
What is the output of "systemctl status mariadb.service"?
 
mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: failed (Result: timeout) since Mon 2018-05-21 22:37:02 CEST; 18min ago
Process: 5718 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=killed, signal=TERM)
Main PID: 12065 (code=exited, status=0/SUCCESS)
Memory: 3.2M
CGroup: /system.slice/mariadb.service
└─control
├─ 5742 fuser /var/lib/mysql/mysql.sock
├─14244 fuser /var/lib/mysql/mysql.sock
└─32244 fuser /var/lib/mysql/mysql.sock

May 21 22:32:02 server.com systemd[1]: Starting MariaDB database server...
May 21 22:37:02 server.com systemd[1]: mariadb.service start-pre operation timed out. Terminating.
May 21 22:37:02 server.com systemd[1]: Failed to start MariaDB database server.
May 21 22:37:02 server.com systemd[1]: Unit mariadb.service entered failed state.
May 21 22:37:02 server.com systemd[1]: mariadb.service failed.
 
I think it is probably safe to run # mysql_upgrade (a recommended solution step if the database server was upgraded and does not restart afterwards), but maybe you should take a look into the installation log files of the upgrade first. Something must have went wrong during the upgrade. You will probably find details on the database scheme upgrade in /var/log/plesk/install/plesk_17.8.11_installation.log . Please look for the plesk_17.8.11_repair.log log, too and autoinstaller3.log. It would be good to find out more detailson the database upgrade or other errors associated with the upgrade, specifically operating system uprades.
 
# mysql_upgrade
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
FATAL ERROR: Upgrade failed
 
This seems to be a rather severe issue with MariaDB. There must be more details in some log on it, because if the database server wasn't touched, it would still work. If you cannot find the entries that identify the error, the last resort is probably official Plesk support.
 
I dont have access to official support because I have bought the license from my host. I am running out of time, have to bring the server online in the next hours.
I am afraid that I have to set up a new linux now if no wonder happens...
 
Thank you Peter, I tried the official support, but he linked me to some posts which I already knew an can be found in google. So I was forced to make a new installation of linux and plesk on my webserver and backup the domains. Anyway, maybe this was the better solution at least, if one issue comes with an update, it can turn out to be a never ending story of issues, so I am ok with the new installation.

If somebody is reading this, I repeat the mantra here: If you make an mayor update of plesk, always backup and be prepared and able to make a new installation from scratch. Otherwise you are f*cked up.
 
Back
Top