Support » Fixing WordPress » Upgrading WP fails on VPS running PHP5

  • I’m running WP 3.0.1 on a Hostgator VPS and I manage a WP 3.0.1 website on Liquid Web.

    When the WP installs where on HG Shared and Bluehost, there was no problem doing auto installs or auto updates via the admin panel.

    It seems that once each site was moved to a VPS, the upgrades have stopped.

    Each VPS is running PHP 5.x.x. Each VPS is running MySQL 5.x.x. And Each VPS I hope has enough memory assigned to run.

    And each site has the same problem with not being able to run an auto install or upgrade.

    Adding “AddType x-mapp-php5 .php” to my .htaccess file causes a blank webpage.
    Adding “AddHandler php5-script .php” to my .htaccess causes Firefox to want to physically download the webpage as a file instead of displaying it.

    Somehow, each install worked fine on a shared host, but when the sites went to VPS (On Hostgator and Liquid Web) they fail to upgrade.

    What am I missing on my VPS installs?
    Thanks for the help

Viewing 11 replies - 1 through 11 (of 11 total)
  • The normal things to check are folder permissions and the like.

    Two questions:
    1) Did you upgrade to 3.0.1 on those servers? Or were the sites migrated to that server already upgraded to version 3.0.1?

    2) Have you put in a ticket to Liquid Web to get us to help identify the problem? If not, go ahead and we’ll see what we can do. If so, feel free to post or email me the ticket number, and I’ll take a look.

    another things could be:

    PHP isn’t configured to acept more than XX Megas of uploads
    The runtime in every script in less than 1 minute
    This is very common in hostings with php shared in multiples users,and disabled or strict config by security reasons

    This cause my wordpress don’t update, the solution i’ve tested and work was:

    Download all wordpress system into my pc, download all database, install PHP, and MySQL

    And try to autoupdate from the local copy
    When finish WP upgrade, upload it again to your hosting

    Ok, this is how my php.ini is setup on my VPS:

    upload_max_filesize = 10M
    memory_limit = 256M

    I also have problems upgrading plug-ins on these installs as well. While an entire WP upgrade will fail right at “Unpacking the update…” it seems that my plug-ins actually download as “tmp” files in my wp-content directory and fail to go any further than that.

    Should my upload_max_filesize be increased?

    Thanks

    Moderator Mark Ratledge

    (@songdogtech)

    Forum Moderator

    @liquid_squelch: 256 meg is too much memory to give every php job, unless you have gigs of RAM to spare. Try 64 meg, and then bump it just for WP with this line at the top of wp-config.php:

    define(‘WP_MEMORY_LIMIT’, ‘128M’);

    And check your permissions; that’s probably the cause of the plguins not finishing installing and stopping at the temp file stage:
    http://codex.wordpress.org/Changing_File_Permissions#Permission_Scheme_for_WordPress

    Thanks for the info. I set my limit back to 64M in my php.ini and restarted Apache.

    I’ve set my define(‘WP_MEMORY_LIMIT’, ‘128M’);

    It seems I am getting closer to a solution. I now see this before everything halts:

    The update process is starting. This process may take awhile on some hosts, so please be patient.

    Enabling Maintenance mode…
    Updating Plugin xxxxxx xxxxx xxx (1/1)

    Maintenance mode does set. A tmp file is downloaded.
    When I look at the file owners, I see (example) that the group is ‘Website1’ and the owner is ‘Website1’.

    Thanks for the help. I see a light at the end of the tunnel and I am hoping it isn’t a train 🙂

    Moderator Mark Ratledge

    (@songdogtech)

    Forum Moderator

    Check your php error logs, too, wherever they happen to be on a hostgator VPS.

    My error logs have been clean for the last 15 days.

    Moderator Mark Ratledge

    (@songdogtech)

    Forum Moderator

    php error logs or httpd error logs?

    Httpd error logs are clean, and my php logs for the WP account doesn’t show anything other than [info] tags.

    This is in my error_log when I attempt to do an upgrade:

    [Thu Dec 30 20:05:56 2010] [info] Executing “/home/<account>/public_html/wp-admin/index.php” as UID 507, GID 505
    [Thu Dec 30 20:05:57 2010] [info] Executing “/home/<account>/public_html/wp-cron.php” as UID 507, GID 505
    [Thu Dec 30 20:05:58 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:05:58 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:05:59 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:05:59 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:06:01 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:06:02 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:06:02 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:06:03 2010] [info] Executing “/home/<account>/public_html/wp-admin/update-core.php” as UID 507, GID 505
    [Thu Dec 30 20:06:03 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:06:05 2010] [info] Executing “/home/<account>/public_html/wp-admin/index-extra.php” as UID 507, GID 505
    [Thu Dec 30 20:06:09 2010] [info] Executing “/home/<account>/public_html/wp-admin/update-core.php” as UID 507, GID 505

    And that is where it ends.

    Thank you for the help so far.

    Moderator Mark Ratledge

    (@songdogtech)

    Forum Moderator

    Make an .htaccess file in wp-admin on the server with FTP and add this:

    <IfModule mod_security.c>
    SecFilterInheritance Off
    </IfModule>

    That turns off mod security just for wp-admin

    Definitely getting closer here!!

    I can now see an “upgrade” directory in my WP install.

    There is a directory called wordpress-34.tmp, and sub-directories beyond that. But – there are no files.

    The script still stalls at:

    Update WordPress
    Downloading update from http://wordpress.org/wordpress-3.0.4.zip…
    Unpacking the update…

    Thanks again – and Happy New Year.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Upgrading WP fails on VPS running PHP5’ is closed to new replies.