Plugin is not running

  • rick111

    (@rick111)


    2 days, 17 hours ago

    After the latest update, the free plugin is not running.

    0000.002 (0) Free space on disk containing Updraft’s temporary directory: 33136.2 MB
    0000.005 (0) Tasks: Backup files: 1 (schedule: manual) Backup DB: 1 (schedule: manual)
    0000.008 (0) Requesting semaphore lock (fd) (apparently not via scheduler)
    0000.009 (0) Semaphore lock (fd, ********) failed (line 47) (intentionally blanked)
    0000.010 (0) Failed to gain semaphore lock (fd) – another backup of this type is apparently already active – aborting (if this is wrong – i.e. if the other backup crashed without removing the lock, then another can be started after 3 minutes)

    PHP: 8.1.34

Viewing 3 replies - 1 through 3 (of 3 total)
  • chenszo

    (@chenszo)

    2 days, 8 hours ago

    That log is UpdraftPlus thinking a backup is still running. Usually it’s a leftover lock from a backup that got killed mid-run, and updating the plugin while one was going is a classic way to cause it.

    First thing: go to UpdraftPlus > Backup / Restore and look above the Backup Now button. If there’s an in-progress job showing, hit delete/stop on it, wait 5 minutes and try a manual backup again.

    If it still says the same thing every time, the lock isn’t clearing on its own. Two things worth checking: open wp-content/updraft over FTP or file manager and see if there’s a leftover lock file in there you can delete (only while no backup is running), and if your site sits on network storage some hosts don’t play nice with file locks at all. In that case ask your host, or try the backup again after clearing any object cache (Redis/Memcached) since lock info can get stuck there too.

    If none of that does it, post which UpdraftPlus version you updated to and whether WP-Cron is disabled in wp-config. That narrows it down fast.

    Thread Starter rick111

    (@rick111)

    2 days, 4 hours ago

    V  1.26.14

    WP-Cron was disabled in wp-config, and I had a custom cron job, but the previous version worked. I am trying a manual backup, not scheduled. I removed the statement to disable from wp-config.php, and still the backup fails. There are no lock files in the directory, assuming they have some. lock extension, there is a deleteflag….txt file, an index.html file, a web.config file, an .htaccess file, and four log files. Thanks

    • This reply was modified 2 days, 4 hours ago by rick111.
    • This reply was modified 2 days, 3 hours ago by rick111.
    chenszo

    (@chenszo)

    1 day, 12 hours ago

    Since it still fails after 3+ minutes with nothing showing as in progress, the lock row is probably stuck in the database, not on disk. Back up the DB first, then in phpMyAdmin (or WP-CLI) look in wp_options for names starting with updraft_semaphore_ or updraft_last_lock_time_ or updraft_lock_ and delete just those rows. Then try one manual backup.

    If they keep coming back, two things I’d look at. Your custom cron job: if it hits wp-cron.php every minute it can keep waking an old half-dead backup that grabs the lock again. Pause it while you test. And if you have Redis or Memcached object caching on, flush it, since a cached copy of that option can outlive the real one.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.