Support » Networking WordPress » Dashboard painfully slow after upgrade

  • Recently upgraded Mac Server OS to 10.6.5
    running WordPress Multisite 3.0.4 – recently upgraded from 3.0

    WordPress Dashboad is painfully slow. Access to sites is fine if not logged in. Apache error log shows:

    Wed Jan 05 01:53:57 2011 error (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:8008 (127.0.0.1) failed
    Wed Jan 05 01:53:57 2011 error ap_proxy_connect_backend disabling worker for (127.0.0.1)

    Have tried removing trailing slash from site name as described here:
    http://codex.wordpress.org/Changing_The_Site_URL
    >> Changing the URL directly in the database

    Tried default theme – no difference
    Tried disabling all plugins – no difference

    errors in apache access log suggest Proxy error?
    see http://webmasterworld.com/apache/3837622.htm
    same error as in my apache log

    tried enabling reverse proxy in Server Admin > Web > Sites > Proxy
    got internal server error

Viewing 11 replies - 1 through 11 (of 11 total)
  • Andrea Rennick

    (@andrea_r)

    Customer Care at Copyblogger Media and Studiopress

    Turn off all the plugins & try again.

    As noted above, I have tried disabling all plugins with no improvement.

    But what the heck I’ll try anything twice, so I disabled the last plugin again – Akismet. No improvement at all. 3-4 minutes to go from link to link in Dashboard. Same to change anything like disabling a plugin.

    Andrea Rennick

    (@andrea_r)

    Customer Care at Copyblogger Media and Studiopress

    Did you do an auto upgrade or a manual one?

    Manual upgrade.

    I am wondering now if the slowdown in the dashboard of WordPpress is due to the htaccess file.
    On the advice of this document on hardening your wordpress installation
    http://codex.wordpress.org/Hardening_WordPress
    I changed the permissions on the htaccess file some time ago. I did not change the permissions back to writeable by wordpress before upgrading. If wordpress had to add to or change the redirect rules in the htaccess file it would not have been able to do that. It would explain the slowdown in the dashboard but not accessing the sites themselves. It would also explain something I saw in the address bar about redirecting (saw it twice but not again but I did copy it):

    http://mydomain.org/wp-login.php?redirect_to=http%3A%2F%2Fmydomain.org%2Fwp-admin%2F&reauth=1

    (where mydomain equals my domain name)

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    That redirect is normal. It just says ‘Hey, you’re not logged in. Lets login and, when you’re done, kick you to wp-admin so you can be a god.’

    My .htaccess isn’t WP writeable and I only have latent dashboard slowness when I log in for the first time. Once everything is cached, it’s faster. Mind you, I’ve got a few things running on my dash that I KNOW slow things down.

    Well the .htaccess that I had was very different from the one that I saw in another install of v. 3.0.4, specifically in the new version this line was added

    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

    and these:

    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]

    The part about adding a trailing slash to /wp-admin had me all excited. However adding these lines to .htaccess did nothing for my slowdown problem. I’m talking several minutes to click from link to link in the dashboard. 2.5 minutes to log in.
    This is not just slow it is extreme slow, and began with the wordpress upgrade.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    You could try grabbing the example htaccess from here: http://codex.wordpress.org/Create_A_Network#.htaccess_and_Mod_Rewrite and see if that helps.

    If you had the old WPMU, your htaccess could be unoptimized.

    I think I was on the wrong track with the .htaccess file. On a hunch and looking at the apache error logs I saw a lot of errors relating to being unable to resolve the fully qualified domain name (a subset of our school domain).
    I added the IP and name of the server to the hosts file and instant relief.
    My particular issue is resolved I’d say. I do wonder why this was not an issue before the WP upgrade but I guess I will wonder fruitlessly.

    Thanks very much for your time. Andrea and Ipstenu (are you really half-elf?)

    Andrea Rennick

    (@andrea_r)

    Customer Care at Copyblogger Media and Studiopress

    She’s half-elf, I’m part Hobbit. 😉

    Yeah, it’s not htacess stuff, but the server could be a “sudden” issue especially if someone did a routine upgrade on some of the parts, overwriting any customizations.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    My mother was an elf. My clumsiness embarrasses her daily 😉 (I think we call that a halfling, Andrea, lest we be sued by LotR).

    But yeah. There have been not and insignificant number of people jacked by server upgrades :/ I run my server on stable releases, and even then sometimes a minor upgrade goes blarrrrgh.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Dashboard painfully slow after upgrade’ is closed to new replies.