Question

0

MySQL takes ages to load (only when using WP)

rated 0 times [ 0] [ 0] / answers: 1 / hits: 1472 / 1 Year ago, mon, december 12, 2022, 1:29:25

I'm not sure what's happening but it's since a while that I'm experiencing using my dev site (running on a VM) on the local Ubuntu machine.
The site runs on a Wordpress instance using MySQL setup to use innodb table on a separate folder.
I don't have permission problems, as far as I know.

It I try to use MySQL CLI I can query the database without problems; the same using phpmyadmin.
But when it comes to access via the site it takes ages and more often than not I need to stop the service.

And that's again another symptom something doesn't work as it should.
Stopping the service via sudo service mysql stop I can see it immediately stops (phpmyadmin can't log in anymore) but the command line prompt keep on hold like it is working.
The only way I have to get the CLI ready is to brutally stop the service with a CTRL+C.

Any idea of what's wrong?
Thanks

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

alliulet

Add To Favorites

Follow

Total Points: 46

Total Questions: 109

Total Answers: 97

Location: Svalbard and Jan Mayen

Member since Sat, Oct 10, 2020

4 Years ago

alliulet questions

1 Git "fatal: detected dubious ownership in repository"

Wed, Aug 25, 21, 13:06, 3 Years ago

1 Random keyboard actions after upgrade from 21.10 to 22.04

Fri, Apr 21, 23, 01:41, 1 Year ago

1 Raspberry: "do-release-upgrade" thinks 'Jammy Jellyfish' is still in development

Sun, Apr 16, 23, 14:41, 1 Year ago

1 Find all files with given extension in subfolders, and add substring corresponding to subfolder

Thu, Apr 13, 23, 01:07, 1 Year ago

1 KDE Plasma icons showing in UBUNTU DESKTOP

Thu, May 20, 21, 22:06, 3 Years ago

View All

answered 1 Year ago exceeeelh · Accepted Answer

As suggested from @Oli in the other other it was a matter of DNS and name resolution. However, it was not in the same direction as he suggested.

It turned out to be that MySQL was trying to do IP resolution on each call, causing a DNS lookup. Because the db server is internal and had no connection to the outside world, the lookup would eventually timeout.

I resolved the problem by adding the skip-name-resolve directive in the my.conf SQL configuration file located beneath /etc/mysql of my VM.

Now my local WP rocks.