• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • 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.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

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