Plesk Error Pleskfatalexception Unable To Connect To Database Mysql_connect
Contents |
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & plesk unable to connect to database 1045 Pricing Support Resources FAQs Forums Knowledge Base Documentation Downloads
Unable To Connect To Plesk Database Can T Connect To Local Mysql Server Through Socket
Plesk University Release notes Blog Become a Partner Russian German French Spanish Chinese
Mysqld Dead But Subsys Locked
Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any Search Unable to connect to database: mysql_connect() function.mysql-connect: Permission denied
Mysql Daemon Failed To Start.
Article ID: 124838, created on Mar 12, 2015, last review on Mar 12, 2015 Applies to: Plesk 11.0 for Linux Plesk 11.5 for Linux Plesk 10.4 for Linux/Unix Symptoms Unable to access Plesk, page shows error: Error message or request description : ERROR: PleskFatalException Unable to connect to database: mysql_connect() function.mysql-connect: Permission denied MySQL service failed trying to restart. In /var/log/mysqld.log these errors can be found: [ERROR] /usr/libexec/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 13) [ERROR] Can't start server: can't create PID file: Permission denied Cause Wrong permissions on MySQL directory. Resolution Make sure that owner and group of /var/run/mysqld/ directory is mysql:mysql and permissions are as below: # ls -ld /var/run/mysqld/ drwxr-xr-x 2 mysql mysql 4096 Jul 14 18:16 /var/run/mysqld/ Correct permissions and start Mysql service. Search Words [function.mysql-connect]: Permission denied ERROR: PleskFatalException common_func.php3:153 ERROR: PleskFatalException: Unable to connect to database: mysql_connect(): Connection refused (auth.php:149) Unable to connect to database: mysql_connect Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 13) Can't start server: can't create PID file: Permission denied a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f aea4cd7bfd353ad7a1341a257ad4724a e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 Em
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base Documentation Downloads Plesk University Release notes Blog Become a Partner Russian German French Spanish Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any Search Unable to log in to Plesk: ERROR: PleskDBException: Unable to connect to database Article ID: 128936, created on May 9, 2016, last review on Sep 8, 2016 Applies to: Plesk for Linux/Unix Symptoms Unable to log in https://kb.plesk.com/en/124838 to Plesk because of issues with connection to database, errors like below may appear: ERROR: PleskDBException: Unable to connect to database: mysql_connect(): No such file or directory /var/lib/mysql/mysql.sock (Error code: 2002). Please check that database server is started and accessible. (Abstract.php:69) General troubleshooting steps First of all, check whether MySQL service is running or not: On CentOS/RHEL: # https://kb.plesk.com/en/128936 service mysqld status On Ubuntu/Debian: # service mysql status If you use MariaDB server: # service mariadb status If it is not running, try to start it with start command, e.g.: # service mysqld start If it does not start, check MySQL log files. You can find the location of log files in MySQL configuration. MySQL configuration files can be found by the following command: # mysql --help | grep -A1 "Default options" Default options are read from the following files in the given order: /etc/my.cnf /etc/mysql/my.cnf /usr/etc/my.cnf ~/.my.cnf The location of MySQL log files is defined by "log-error" setting in "my.cnf" file, for example: # grep -B1 log-error /etc/my.cnf [mysqld_safe] log-error=/var/log/mysqld.log If "log-error" is not defined, you can define it on your own having backed the original file. Please, note that "log-error" option should be defined in "[mysqld_safe]" section. Check if there no hanged mysqld processes using: # ps auxffww | grep mysql Manually kill hanged processes: # kill -9 PID_ID Related issues 128949 Unable to log in to Plesk: Unable to connec
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums https://kb.plesk.com/en/112492 Knowledge Base Documentation Downloads Plesk University Release notes Blog Become a Partner Russian German French Spanish Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any Search Unable to log in to Plesk: saved admin password is incorrect Article ID: 112492, created on Oct 10, 2011, last unable to review on Jul 26, 2016 Applies to: Plesk for Linux/Unix Symptoms Unable to log in to Plesk. The following error is displayed instead of the login screen: ERROR: PleskFatalException Unable to connect to database: saved admin password is incorrect. 0: common_func.php3:93 psaerror(string 'Unable to connect to database: saved admin password unable to connect is incorrect.') 1: auth.php3:127 Cause The password in the file /etc/psa/.psa.shadow, which is used to access the Plesk database, does not match your admin password. OR The "old-passwords=1" option is enabled in /etc/my.cnf (on Debian-like distributions the path is /etc/mysql/my.cnf). Resolution Make sure that option old-passwords = 1 is disabled in the /etc/my.cnf file (on Debian-like distributions the path is /etc/mysql/my.cnf). Obtain the correct Plesk password: # cat /etc/psa/.psa.shadow $AES*** Try connecting to the MySQL database and updating the admin password: # MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -u admin mysql mysql> UPDATE mysql.user SET Password=PASSWORD('$AES***') WHERE User='admin'; Note: If you are unable to connect, enable skip-grant-tables in the /etc/my.cnf file (on Debian-like distributions the path is /etc/mysql/my.cnf), restart MySQL, then update the admin password: # cat /etc/my.cnf ... [mysqld] skip-grant-tables ... # /etc/init.d/mysqld restart # mysql -uadmin mysql mysql> UPDATE mysql.user SET Password=PASSWORD('$AES***') WHERE User='admin'; Do not forget to remove ski