• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue DB query failed: SQLSTATE[HY000] [2002] No such file or directory

perezhuguet

New Pleskian
Server operating system version
Ubuntu
Plesk version and microupdate number
18.0.64
I have been trying to solve this problem since yesterday, but there is no way.
Can someone please give me a hand?

Thank you so much
 
Check over SSH the following commands:


Code:
# service mariadb status
# df -h
# df -i

And provide us the output.

Also, what did you try to do already?
 
Check over SSH the following commands:


Code:
# service mariadb status
# df -h
# df -i

And provide us the output.

Also, what did you try to do already?
Thank you very much for your response.
I attach screenshots of what I get when typing these commands.

I've been having this problem since Thursday and without sleeping.

Right now, what I'm looking for is someone who can solve it for me because I don't see a way out.

Thanks for the help
 

Attachments

  • Captura de pantalla 2025-02-08 a las 11.42.47.png
    Captura de pantalla 2025-02-08 a las 11.42.47.png
    794.5 KB · Views: 5
  • Captura de pantalla 2025-02-08 a las 11.42.54.png
    Captura de pantalla 2025-02-08 a las 11.42.54.png
    286.6 KB · Views: 5
Try this comand and provide the output:
Bash:
journalctl --output=cat -xeu mariadb
 
Right now, what I'm looking for is someone who can solve it for me because I don't see a way out.
Don't hesitate to open a ticket with Plesk support via support.plesk.com to let the Plesk support engineers help you. Support is included with your license if you bought it directly from Plesk. Otherwise, if you got your license from a reseller (for example you provider), you can gets a separate support subscription (of which the first month is free): How to get support directly from Plesk?
 
Try this comand and provide the output:
Bash:
journalctl --output=cat -xeu mariadb
Don't hesitate to open a ticket with Plesk support via support.plesk.com to let the Plesk support engineers help you. Support is included with your license if you bought it directly from Plesk. Otherwise, if you got your license from a reseller (for example you provider), you can gets a separate support subscription (of which the first month is free): How to get support directly from Plesk?
thanks for the response.
Currently my provider is not Plesk directly (which will be soon) and I cannot ask them for help

So if you know of any way to contact them and have them review it, I would appreciate it. Meanwhile I'm still looking for options.
 
Don't hesitate to open a ticket with Plesk support via support.plesk.com to let the Plesk support engineers help you. Support is included with your license if you bought it directly from Plesk. Otherwise, if you got your license from a reseller (for example you provider), you can gets a separate support subscription (of which the first month is free): How to get support directly from Plesk?
Try this comand and provide the output:
Bash:
journalctl --output=cat -xeu mariadb
thanks for the response.
This is what the screen shows.
 

Attachments

  • Captura de pantalla 2025-02-08 a las 15.42.34.png
    Captura de pantalla 2025-02-08 a las 15.42.34.png
    800.4 KB · Views: 3
The issue is above line 54. Your screenshot has only the shutdown part. You might have an InnoDB corruption.
 
Sorry for the previous command. Please try
the following:
Bash:
journalctl -n100 --no-pager -xeu mariadb
 
Thank you all for helping me.
The level of saturation with this problem has been such that I have decided to format the server and start from scratch.
In the end, when I fixed one thing, another appeared. I managed to start it at 3:00 p.m. and at 6:00 p.m. it was down again, which is why I decided to start from scratch.
Thank you all very much for the contributions.
,
 
Back
Top