Please wait 15 min

Updating my site from 2.2.0 to 2.3.0 gets a fail with “please wait 15 min”.
I have two ClassicPress sites and one updated without a hitch the other gives the fail with “please wait 15 min”. Tried it a day later and still get the error.

Thoughts on how to resolve?

What plugins are you running on the site that fails to update?

@clifgraves,

Perhaps “deactivate” (disable) plugins before conducting the upgrade. This is a common suggestion when doing upgrades to an OS (disable third-party repos) for the same reason.

Once the upgrade is complete, “activate” (enable) plugins one at a time, and see if you experience any issues.

@clifgraves How are you getting on?

The interesting thing about that is I have two classic sites and both use the same plugins, one updated fine and one did not. I will try deactivating plugins and see if it makes a difference.

It says “Another update is currently in progress.” in the error screen. Is there a flag file that is set while the update is in progress? That it is reading to say that another update is in progress?

ok that is easy, it was an update that got stuck (automatic one).

Go in the files, set to “show hidden files” and look for .maintenance file and delete it.

That should show the update as available again so that it triggers and completes without issue.

1 Like

Unfortunately there is no .maintenance file. Wondering how Classic Press triggers the:
" Update ClassicPress
Another update is currently in progress.
It’s possible that an update started, but the server encountered a temporary issue and could not continue.
Or, you may have clicked the update button multiple times.
Please wait 15 minutes and try again.
If you see this message after waiting 15 minutes and trying the update again, please make a post on our support forum" Message.

What event is supposed to go away after 15min?

The idea is that waiting a few minutes will give the current update time to complete. 15 minutes is much longer than necessary, but it’s just playing safe.

The .maintenance.php file will be in your site’s root folder, where the wp-config.php and .htaccess files are. If you can’t see the .htaccess file, as @ElisabettaCarrara said, you need to make sure you can see hidden files.

@clifgraves I do not know if you use FTP or a web based file manager panel offered by your host like CPanel one, but there is a setting in there for the panel that allows you to set hidden files like .htaccess and .maintenance to be shown.

The files ARE THERE, for security the host sets them to hidden because meddling with them can cause harm if one does not know how to use them.

.maintenance is generated to handle what happens DURING an update and CP deletes it when update is done. If the server encounters issues (like fails to update within a certain time or goes down for example) during an update the process stalls and the .maintenance file is not deleted - basically this means no update and a remaining error message triggered by the presence of that file.

When you set your file manager to show hidden files and delete it, CP sees that there is an update to perform and tries again or gives you the notice in dashboard to trigger it manually.

On how to set the files to be shown, assuming you are on CPanel read this article.

If you use another type of panel you can search on Google (how to show hidden files when using xxx panel) and go from there. Similarly if you are using FTP via FileZilla or similar you can set it to show hidden files (another search on Google will help you identify how depending on what software you are using for FTP).

Hope this helps

Again I see all of hidden files and there is no .maintenance.php .htaccess and a few other hidden files are visible. So that is not it. So frustrating.

@clifgraves I suggest you try this plugin: Fix Another Update In Progress – WordPress plugin | WordPress.org

1 Like

There is a database setting that does this, see this link to fix:

Thanks all - that did the trick. So the in-progress flag is set in the database. Apparently a standard way that Wordpress does it.

It seems like a way to force removing the core_updater.log line in the database without editing the database in phpMyAdmin might have been nice.

Again thanks for the help.

I didn’t try the plugin went with editing the db directly. Thanks for the help

1 Like

That’s precisely what the plugin offers.

Nice tip on the plugin Tim.
I just did it using phpMyAdmin the few times I had it happen.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.