An automated WordPress update has failed to complete – please attempt the update

  • Hello all,

    I’m currently running WP 5.3.6 on Ubuntu Server 20.04.

    When going in the admin area, I see “An automated WordPress update has failed to complete – please attempt the update again now.” . The link, however, does absolutely nothing. I spent a fair bit of time on google, looking that up, and I saw a lot of posts stating to delete the .maintenance file. I don’t have that anywhere, in any folders on my server. (yes, i know it’s a hidden file, and no, it’s not there).

    Short of doing a manual upgrade (which seems quite intense), is there something else I can try, or any way to pinpoint what’s going wrong?

    thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator t-p

    (@t-p)

    Auto update can fail for a large number of reasons and it is often hard to diagnose the failure due to specific configurations present on each server running the update.

    Try MANUALLY updating. Please read the Manual Update directions first.

    BACKUP: If you haven’t already done, always backup everything (including your database) before doing any actions, just in case something really goes wrong. You can never have enough backups! See https://www.ads-software.com/support/article/wordpress-backups/

    Thread Starter buttersnot

    (@buttersnot)

    Thanks. I’m trying to avoid the manual update tho… Further digging (using the Site Health plugin) shows that there’s a bunch of files that are nor writable by WordPress. Now, I’m very comfortable setting directories to 755 and files to 644, however, the files listed (it only gives a partial list, because there’s so many) are from the wp-includes/ID3 and wp-includes/js directories. The files in question are all links. For example: 

    lrwxrwxrwx  1 www-data www-data    34 Jan 27  2020 getid3.lib.php -> ../../../php/getid3/getid3.lib.php
lrwxrwxrwx  1 www-data www-data    30 Jan 27  2020 getid3.php -> ../../../php/getid3/getid3.php
lrwxrwxrwx  1 www-data www-data    40 Jan 27  2020 module.audio.ac3.php -> ../../../php/getid3/module.audio.ac3.php
lrwxrwxrwx  1 www-data www-data    40 Jan 27  2020 module.audio.dts.php -> ../../../php/getid3/module.audio.dts.php
lrwxrwxrwx  1 www-data www-data    41 Jan 27  2020 module.audio.flac.php -> ../../../php/getid3/module.audio.flac.php
lrwxrwxrwx  1 www-data www-data    40 Jan 27  2020 module.audio.mp3.php -> ../../../php/getid3/module.audio.mp3.php
lrwxrwxrwx  1 www-data www-data    40 Jan 27  2020 module.audio.ogg.php -> ../../../php/getid3/module.audio.ogg.php
lrwxrwxrwx  1 www-data www-data    46 Jan 27  2020 module.audio-video.asf.php -> ../../../php/getid3/module.audio-video.asf.php
lrwxrwxrwx  1 www-data www-data    46 Jan 27  2020 module.audio-video.flv.php -> ../../../php/getid3/module.audio-video.flv.php
lrwxrwxrwx  1 www-data www-data    51 Jan 27  2020 module.audio-video.matroska.php -> ../../../php/getid3/module.audio-video.matroska.php
lrwxrwxrwx  1 www-data www-data    52 Jan 27  2020 module.audio-video.quicktime.php -> ../../../php/getid3/module.audio-video.quicktime.php
lrwxrwxrwx  1 www-data www-data    47 Jan 27  2020 module.audio-video.riff.php -> ../../../php/getid3/module.audio-video.riff.php
lrwxrwxrwx  1 www-data www-data    41 Jan 27  2020 module.tag.apetag.php -> ../../../php/getid3/module.tag.apetag.php
lrwxrwxrwx  1 www-data www-data    40 Jan 27  2020 module.tag.id3v1.php -> ../../../php/getid3/module.tag.id3v1.php
lrwxrwxrwx  1 www-data www-data    40 Jan 27  2020 module.tag.id3v2.php -> ../../../php/getid3/module.tag.id3v2.php
lrwxrwxrwx  1 www-data www-data    42 Jan 27  2020 module.tag.lyrics3.php -> ../../../php/getid3/module.tag.lyrics3.php

    So those are all from /usr/share/php/getid3.

    – Is WordPress supposed to have write access and/or ownership of those as they’re outside of wordpress ?
    – Why would WordPress need id3 tag access?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘An automated WordPress update has failed to complete – please attempt the update’ is closed to new replies.