• 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.

Issue ERR [1] SQLSTATE[HY000] [2002] No such file or directory

Mnu555

New Pleskian
After Update to
Plesk Onyx 17.5.3 Update 24
1) i get error :Error message on Plesk home page: The Plesk update failed. Click OK to close the message.
I found this Error message on Plesk home page: The Plesk update failed. Click OK to close the message.

there it is written how to remove this message. But nothing is written about the causes and possible problems after that.
2) I look in panel.log and found error: ERR [1] SQLSTATE[HY000] [2002] No such file or directory
V4IuUFh9.jpg

And not find in https://support.plesk.com/hc/en-us/articles/ anything about this.
I'm worried about this error. Because the previous update - ended with a drop in Plesk and Plesk recovery did not help. I was tired of looking for reasons and I restored the server from snapshot at that time. Now I'm thinking whether new problems will begin. What means "ERR [1] SQLSTATE[HY000] [2002] No such file or directory" in log ? What do i have to do ?
 
Last edited:
Hi Mnu555,

unfortunately you missed the additional links at the mentioned Plesk KB - article, which are all related to your described errors message. Pls. consider to follow each of the links, to investigate YOUR special and unique root cause. ;)
 
Back
Top