Support » Networking WordPress » Anyone out there know what these errors are since 3.1 Upgrade?

  • Can’t figure these out, my site runs like crap as of 3.1 upgrade, somethings not playing nice with something?

    [Sun Mar 06 12:39:39 2011] [error] [client ] Premature end of script headers: index.php

    [Sun Mar 06 12:41:10 2011] [warn] [client] mod_fcgid: read data timeout in 120 seconds

    [Sun Mar 06 12:41:10 2011] [error] [client] Premature end of script headers: index.php

    [Sun Mar 06 12:42:05 2011] [warn] [client ] mod_fcgid: read data timeout in 120 seconds

    [Sun Mar 06 12:42:05 2011] [error] [client] Premature end of script headers: index.php

    [Sun Mar 06 13:17:44 2011] [error] [client ] File does not exist: /var/chroot/home/content/96/3786296/html/wp-content/uploads/SWB

    [Sun Mar 06 14:02:50 2011] [error] [client] File does not exist: /var/chroot/home/content/96/3786296/html/wp-content/themes/playmaker-theme/images/authors/3.jpg

    [Sun Mar 06 15:03:04 2011] [error] [client] File does not exist: /var/chroot/home/content/96/3786296/html/wp-content/themes/playmaker-theme/images/authors/3.jpg

    [Mon Mar 07 11:37:37 2011] [warn] [client] (110)Connection timed out: mod_fcgid: ap_pass_brigade failed in handle_request function

    [edited log for brevity. Please do not paste full log code, especially if most of it is duplicates.]

Viewing 15 replies - 16 through 30 (of 30 total)
  • Wow, KaelinDesign, must definitely not be a coincidence, i have been on godaddy’s grid since it was in beta, and yes im getting these errors still, it is actually an Apache Module for PHP.
    They are suppose to move me, i started on grid over 2 years ago with only 1375 websites, now in grand godaddy style they have way oversold the server that now serves 3464 websites!
    I spoke to a supervisor on Friday and let them know im leaving for a more reliable host and they said they would move me to a less oversold server, i have not been migrated yet but im waiting to see?

    I got some of my errors fixed via godaddy’s support. This was a new domain transfer and on top of the 3.1 mess my dns got mangled. Now that’s fixed I can focus on 3.1 .

    GoDaddy didn’t have anything to say about the wordpress issues, other than a fresh install of course. Unofficially the implication was to downgrade if possible to 3.0.5 . Which I’m trying now to figure out how to do.

    I’ve been very pleased with support overall, and have been thinking about transferring to dedicated anyway, but truly, I don’t think it’s necessary yet.

    Andrea Rennick

    (@andrea_r)

    Customer Care at Copyblogger Media and Studiopress

    Unofficially the implication was to downgrade if possible to 3.0.5 . Which I’m trying now to figure out how to do.

    upload the wp files for 3.0.5.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    Lead Plugin Wrangler

    Just as an FYI, uploading the 3.0.5 files to an upgraded 3.1 install MAY have database issues. If you have the old DB, that would be best.

    I was afraid of that, Ipstenu. I do not have the old database. It was corrupted horribly whilst trying to get the site setup originally on the old host. If I upload the new files, and then import the xml file of content… would that work? All that I want to save is the uploads and the theme.

    For what it’s worth- I have noticed that I’ve had to repair my database tables frequently since using 3.1, and then the site works mostly as wanted… for a little while.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    Lead Plugin Wrangler

    Yeah, and export/import should work. Make sure you backup your uploads folders!

    For what it’s worth- I have noticed that I’ve had to repair my database tables frequently since using 3.1, and then the site works mostly as wanted… for a little while.

    I would put that down to one of two things:

    1) Your host can’t handle WP 3.1 (unlikely if it ran 3.0)
    2) You have a deadly plugin (very likely)

    I hate to disagree, but my plugins folder is empty. My host (godaddy linux shared hosting) runs WordPress 3.0.5 beautifully. Still need to repair database tables.

    I’ve been watching the Master list with interest, and have gone through all steps, 2010 theme, removed plugins, etc. All my other sites run 3.0.5, and they are wonderful. I’ll head back until 3.1.0.1(or whatever the fix is) comes out.

    Yeah, and export/import should work. Make sure you backup your uploads folders!

    Thanks!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    Lead Plugin Wrangler

    Then we’re at #1 :/ Your host can’t handle 3.1 (I said unlikely, not impossible).

    I would try a CLEAN install of 3.1 for grins and giggles, see if it bombs out.

    Clean install. As in, download zip from wordpress.org, unzip, upload files to host, write in new database details, visit install page?

    I hate to tell you this, but I’ve done that. Twice. I went with a one click install first, then tried to do it as a manual install over again. And then one more time because maybe I didn’t do it right. I’m going to go with, “and Godaddy doesn’t support wordpress 3.1 well.”

    🙁

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    Lead Plugin Wrangler

    Ugh.

    GoDaddy is frustrating. MOST of their servers are fine. But once in a while you get on a shared box that is all jacked up. And I think you are 🙁

    Hmmmm….

    I’m toying with a dedicated server. Is this something that I could install a specific apache or php module for on that server and be fine?

    Andrea Rennick

    (@andrea_r)

    Customer Care at Copyblogger Media and Studiopress

    Usually on dedicated servers you can install whatever you want.

    I figured, but I don’t know what I would need to install to make wordpress 3.1 work correctly. Is there a list of recommended modules somewhere? If some servers work well, and some do not, it follows that I would need something particular on the server for it to work properly.

    Or am I not understanding this properly?

    Andrea Rennick

    (@andrea_r)

    Customer Care at Copyblogger Media and Studiopress

    mod_rewrite. That’s pretty much it.

    oh and setup to read the right folders.

    If you’re on a shared hosts and stuff borks that often, then they have oversold the box.

    Here is the simple fact of GoDaddy, they oversell all their boxes, i started with the grid beta program over 2 years ago when the idea started coming about about multiple servers serving up resources, it was great when only 1300 sites were on I.P adrress 97.74.26.1, then they keep adding: to date 3464 on this single Ip.

    If me & you are on the same one then i suggest you ask them to migrate you to another server, i’m having the exact same issues since 3.1 upgrade, Mod_php times out a lot at only 120 seconds and all kinds of database issues, i have to keep optimizing to keep it running, i am running several plugins but i have ruled out everyone i have now as to be the culprit.
    I was very shocked when Wp_Supercache dorked out time & time again, i had to go manually ftp and clear cache just to get into admin for a week straight, i finally said enough is enough and deleted it.
    Now im using Page_Mod_Speed with extended cache, It appears ok but not like it use to be?

Viewing 15 replies - 16 through 30 (of 30 total)
  • The topic ‘Anyone out there know what these errors are since 3.1 Upgrade?’ is closed to new replies.