• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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 On 3 server with plesk I have ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002]

M

Mik

New Pleskian
Hi
I have 3 server with Plesk Panel and tonight I cant access none and what I see is that on every server Mysql is not running and my try to start (or restart) fails.
And all web site are down!
I think it depends from some plesk update on every server
The complete error is:
ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory

Additionally, an exception has occurred while trying to report this error: Zend_Exception
No entry is registered for key 'translate' (Abstract.php:144)

Search for related Knowledge Base articles

Plesk please how to repair this?
Its urgent
Thanks
 
there is no /var/log/mysql/error.log
on one server there is /var/log/mysqld.log of about 2Gb (moved)
there is no process loking libdata, there is no mysql running
on all 3 server the same: mysql not running
and there is no socket file
 
What is exact error in mysql.log when you try to start mysql server?
 
# service mysqld start
MySQL Daemon failed to start.
Starting mysqld: [FAILED]
but seem to me that no message is written in the log file
The last row is this (at 03:26 but now is 06:29):
70314 03:26:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
 
Gigaveri, sorry dont understand
IgorG it's not clear why I have 3 server down at same time without nothing done and more how to repair them
 
Mik said:
# service mysqld start
MySQL Daemon failed to start.
Starting mysqld: [FAILED]
but seem to me that no message is written in the log file
The last row is this (at 03:26 but now is 06:29):
70314 03:26:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Click to expand...


Hello

promlem socket

[root@server ~]# mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
[root@server ~]#


don't say the same to you ?
 
IgorG said:
@Mik could you attach mysql.log file from problem server here?

@Gigaveri what is this? Why do you write something incomprehensible about this thread?
Click to expand...


Soryy

[root@server ~]# service mysqld start
MySQL Daemon failed to start.
Starting mysqld: [FAILED]
[root@server ~]#


[root@server ~]# mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
[root@server ~]#

/var/lib/mysql error log no


The same problem with 150 different servers...
 
IgorG dont know how send you the file
From another server the last lines are those:

161226 1:36:05 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.52-cll-lve' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Atomicorp
170314 4:02:35 [Note] /usr/libexec/mysqld: Normal shutdown

170314 4:02:35 [Note] Event Scheduler: Purging the queue. 0 events
170314 4:02:37 [Warning] /usr/libexec/mysqld: Forcing close of thread 3484199 user: 'admin'

170314 4:02:37 [Warning] /usr/libexec/mysqld: Forcing close of thread 3484197 user: 'admin'

170314 4:02:37 InnoDB: Starting shutdown...
170314 4:02:39 InnoDB: Shutdown completed; log sequence number 102239408
170314 4:02:39 [Note] /usr/libexec/mysqld: Shutdown complete

170314 04:02:39 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
 
Gigaveri said:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Click to expand...
Have you tried to search this error in KB articles and apply suggested solutions? There are several KB articles about this issue.
 
Are you serious? again there has been a problem from a plesk update!
Plesk make something please, you cannot leave us in those conditions!
 
Plesk doesn't ship MySQL, it only downloads it from original OS vendor repo. So it is not Plesk problem but system MySQL package, or MySQL from Atomic repository as I see
Mik said:
MySQL Community Server (GPL) by Atomicorp
Click to expand...
So, if you can't apply solutions from multiple KB articles about this issue and this is urgent issue - it would be better to ask assistance from Plesk Support Team - https://support.plesk.com/hc/en-us/requests/new
 
IgorG said:
Have you tried to search this error in KB articles and apply suggested solutions? There are several KB articles about this issue.
Click to expand...
IgorG said:
Plesk doesn't ship MySQL, it only downloads it from original OS vendor repo. So it is not Plesk problem but system MySQL package, or MySQL from Atomic repository as I see

So, if you can't apply solutions from multiple KB articles about this issue and this is urgent issue - it would be better to ask assistance from Plesk Support Team - https://support.plesk.com/hc/en-us/requests/new
Click to expand...


Yes atomic promlem update error

2017-03-14 03:14:14 INFO: pum is called with arguments: ['--update', '--json']
Loading mirror speeds from cached hostfile
* atomic: mirror.veriteknik.net.tr
* base: mirror.venov.net.tr
* epel: mirror.veriteknik.net.tr
* extras: mirror.venov.net.tr
* updates: mirror.dgn.net.tr
2017-03-14 03:14:16 INFO: updating packages: mysql-libs mysql-devel mysql-server mysql
Running rpm_check_debug
Updating: mysql-libs-5.5.54-36.x86_64 165/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1299/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1428/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1604/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 67296/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 132832/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 198368/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 263904/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 329440/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 394976/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 460512/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 526048/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 591584/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 657120/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 722656/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 788192/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 853728/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 919264/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 984800/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1050336/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1115872/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1181408/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1246944/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1312480/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1378016/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1443552/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1509088/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1574624/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1640160/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1705696/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1771232/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1836768/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1902304/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 1967840/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2033376/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2098912/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2164448/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2229984/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2295520/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2361056/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2426592/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2492128/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2557664/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2623200/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2688736/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2754272/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2819808/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2885344/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2950880/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2992496/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 2992640/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3010779/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3013428/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3013886/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3014016/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3014156/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3032611/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3034505/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3040186/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3045848/4296864 [1/8]
Updating: mysql-libs-5.5.54-36.x86_64 3054237/4296864 [1/8]

Cleanup: mysql-devel 100/100 [5/8]
Cleanup: mysql-server 100/100 [6/8]
Cleanup: mysql 100/100 [7/8]
Cleanup: mysql-libs 100/100 [8/8]
Verify: 1/8: mysql-libs.x86_64 0:5.5.54-36 - u
Verify: 2/8: mysql-devel.x86_64 0:5.5.54-36 - u
Verify: 3/8: mysql-server.x86_64 0:5.5.54-36 - u
Verify: 4/8: mysql.x86_64 0:5.5.54-36 - u
Verify: 5/8: mysql-libs.x86_64 0:5.5.52-36.el6.art - ud
Verify: 6/8: mysql.x86_64 0:5.5.52-36.el6.art - ud
Verify: 7/8: mysql-server.x86_64 0:5.5.52-36.el6.art - ud
Verify: 8/8: mysql-devel.x86_64 0:5.5.52-36.el6.art - ud
2017-03-14 03:14:27 INFO: pum completed successfully
2017-03-14 03:14:27 INFO: pum is called with arguments: ['--check']
Loaded plugins: fastestmirror, security
 
You must log in or register to reply here.

Similar threads

S
Issue Server Error - 500 Plesk\Exception\Database
Replies
12
Views
1K
The 8th
The 8th
S
Issue DB query failed: SQLSTATE[HY000] [1045] Access denied for user 'admin'@'localhost' (using password: NO)
Replies
1
Views
389
Kaspar@Plesk
Kaspar@Plesk
C
Resolved Mariadb not working - DB query failed: SQLSTATE[HY000] [2002] No such file or directory
Replies
7
Views
2K
Crash79797
C
A
Issue Unable to login after Plesk (Message SQLSTATE[HY000] [2002] No such file or directory)
Replies
2
Views
2K
A_SH
A_SH
Space Monkey
Issue Help!! Server Error500 Plesk\Exception\Database
Replies
8
Views
2K
Peter Debik
P
Back
Top