petercooper

Useful information, Otto!

It seems then that 2.1 does this on every request, or at least tracks it needs to still do it at next request (if it fails).. whereas 2.0 only does it on posting. ??

Final update.. I put 2.1 back on again, and it works okay now that the virtual host name I am using resolves from the server in question.

I don’t know why this problem exists more with 2.1 than 2.0, but performing a post update must trigger 2.1 to try and resolve the virtual host’s hostname on every request thereafter.

So.. make sure all your virtual hosts resolve from the server, and not just from your test client ?? Weird bug, but I know someone else will have it sometime!

Sorry for posting so much but I’m hoping this helps someone who gets the same problem as me..

Further info.. it seems it might be DNS related. I’ve added an entry to /etc/hosts on the server with the server’s hostname and the IP address, and the 20 second wait goes away.

I’ve erased the whole thing and moved down to 2.1. Same bug. Then I erased it all again and moved down to 2.0. 2.0 doesn’t have the bug. It seems to take exactly 20 seconds to save a post, but then it works and every page loads fast otherwise. So.. it’s a 2.1 problem.

Exporting then deleting the database, running install.php, and then importing the database again.. and it’s super fast again. All I then do is merely edit a post, click Save, and bam.. it’s 20 seconds for every page again.

Hopefully this is a big clue ??

Also, all plugins are deactivated, and there’s no ping outgoing (there was, but I removed it and pages still take 20 seconds).

No errors in the Apache error logs. Restarting Apache has no effect. Restarting machine has no effect. Restarting MySQL has no effect, and SHOW FULL PROCESSLIST shows no slow SQL, etc.

Seems even the barebones login page now takes 20 seconds to load. Again, everything else on this host is fast (including PHP).