I have one site on a server in France, which is a vanilla installation of CP. I visited it to try something and saw it was saying there was an update for v1.1.1
I clicked on update, but it didn’t happen. I then noticed the disk usage was around 150MB. There were multiple instances of past failed attempts to upgrade in .cagefs>tmp
In wp-content>upgrade the files in the temporary folder did not contain all that they should. I increased the script execution time in php.ini to 300 seconds, but the update stalled well before that. The screen also remained blank during that time, with no progress messages.
There was no maintenance file left over in the root directory, and it didn’t seem to be going into maintenance mode at all.
So I deleted all the temporary files to bring the disk usage back to around 35MB and uploaded a ‘no- content’ version via FTP. The site was then happy and the update notice went away.
Apart from the French location, the only difference between that server and all my others is it doesn’t run LiteSpeed, only Apache.
Just thought I’d mention it, in case it highlights a potential problem. There were no cPanel errors or error log file entries. It just seemed incapable of updating itself. It is running PHP 7.2
It sounds like a similar problem to the one I had, discussed here:
Never really got to the bottom of it, but it seems to be host related. On some sites I was finding the updates folder had failed upgrade files left in there, sometimes multiple folders of them. Sometimes it froze in maintenance mode, but it often never got that far.
I’d be interested to know if it will auto-update. With the last version release all my sites auto-updated perfectly (once I’d cleaned up the wp-config files).
This server is the only one that has the Concurrent Usage plugin in cPanel and I’ve been looking in detail at what it’s telling me.
The IO graph says it includes database usage. For a lot of the daily faults, the traffic in KB/s is very low and should not have triggered a fault even with the 20% restriction. While at other times, the traffic was high, but did not trigger a fault.
So, I can only assume it was database usage that did it. To me, as a layman, it seems interesting that the two should be grouped together, and may help to understand why the update stalled.
Since this will depend on a number of other factors such as the server’s download speed and other simultaneous activity on the same site (number of visitors) I don’t think it’s possible to put a hard limit on this.
I would recommend not using a host that may break your site’s file I/O operations without warning.
I remember that it was not that long ago that even expensive reseller accounts here in Australia charged extra to upgrade to SSD hosting, so as to get I/O limits of 2048KB/s.
Admittedly, technology progresses quickly, but I think there are a lot of hosting companies that run a tight ship when it comes to reseller accounts. As always, you get what you pay for - if you’re lucky.