Why isn't one-click update working?

What errors do you see when you click update?

You haven’t, as yet, told us what (if any) error messages you see when you try to upgrade? We’re pretty good but we’re not psychic. ??

“An automated WordPress update has failed to complete – please attempt the update again now.”

Try:
– switching to the default theme automatically by renaming your current theme’s folder inside wp-content/themes and adding “-old” to the end of the folder name using FTP or whatever file management application your host provides.

– resetting the plugins folder by FTP or phpMyAdmin.

– re-uploading all files & folders – except the wp-content folder and the wp-config.php & root .htaccess files – from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

– running the upgrade manually via wp-admin/upgrade.php

Switching off the theme would be a last resort. This blog gets millions of visitors. How could the theme break an upgrade?

It might have something to do with a plugin, that’s when we started having problems last night. The Favado plugin crashed everyone’s server last night and ever since then it’s been one weird problem after another.

I’m not using FTP or phpMyAdmin, I have root access. I spend all day in MySQL’s CLI.

Also I’m using Nginx on this site for years now, not using .htaccess.

Is there a way to get a more detailed error message concerning how the upgrade failed? One-click install has worked for this blog before. I don’t want to do manual upgrades for every version.

Try checking your site’s error logs for a more specific error message. Your hosts should be able to help you accessing your site’s error logs.

I am the host ??

So check your server error logs.

Working on that. I have php-fpm logs, nginx logs, yadda yadda.

The problem is I don’t know what I’m grepping for. And you’re assuming there will actually be an error in one of the logs. WordPress errors don’t necessarily end up in server logs.

It would be better if WordPress had its own logging system. Are you listening Matt Mullenweg?

WordPress errors don’t necessarily end up in server logs.

The serious ones do.

It would be better if WordPress had its own logging system.

Then try turning debug on and enabling error logging.

Cool I didn’t know WordPress had its own error log.

Now the error log isn’t working either. Just my luck today.

I added this to wp-config.php and wordpress_error.log is not doing anything. Do I need to touch the file first before logging starts?

@ini_set( ‘log_errors’, ‘On’ );
@ini_set( ‘display_errors’, ‘Off’ );
@ini_set( ‘error_reporting’, E_ALL );
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
@ini_set( ‘error_log’, ‘wordpress_error.log’ );

I added this to wp-config.php

Um… did you review the sections that I linked to above?

Think I found the problem.

Last night somebody started installing WordPress backup plugins and that filled up the disk to 100%.

Yesterday when the problems started the disk had plenty of room :-/