icundell

Yes, but since the site owner and host lives two doors down from me I can check with him personally – and no changes have been made.

First few times, identical failure to that in the OP.

Just now:

Downloading update from https://www.ads-software.com/wordpress-3.0.1.zip…

Unpacking the update…

Could not create directory.: /wordpress

Installation Failed

Autoupdate has worked fine(-ish) up to this point, and there have been no other changes to the setup. Empirical evidence points to the autoupdater being borked in some way (when all other things remain equal, the thing that has changed is prime suspect)

Fixed: deleted the .maintenance file.

Why the hell does this get left behind?

UPDATE:

Checking “Enable MySQL standard mode. Use this only if you’re getting MySQL errors. (Needs much more memory!)” APPEARS to clear the problem, (although the file.php error is still there and repeating 4 times)

Same problem. Stopped working 26 April.

Debug mode reports a file ini-set() has been disbaled for security reasons in sitemap-ui.php line 91

Under errors warnings and notices it reports:

Undefined index in /includes/file.php line 25 (repeats 4 times)

And:

Warning: mysql_fetch_object(): 174 is not a valid MySQL result resource in /wp-content/plugins/google-sitemap-generator/sitemap-core.php on line 1910

Sitemap page itself reports success, but the file is still the April version.