I have FreePBX 10.13.66-2 and am using the System Admin module. I am trying to update to the latest version and am getting errors:
2015-12-29 01:00:01: () Update already in progress (locked)2015-12-30 01:00:01: () Update already in progress (locked)2015-12-31 01:00:02: () Update already in progress (locked)2016-01-01 01:00:01: () Update already in progress (locked)2016-01-02 01:00:01: () Update already in progress (locked)
I have tried to reboot the server and still get the same error. All my modules are up to the latest version, however I can not get the system to update to the latest version.
It sounds like you are having a problem similar to this:
I scheduled an automatic update for last night but when I logged in to check it this morning I find it is stuck. It’s attempting to update from 6.12.65-28 to 6.12.65-29.
The upgrade log for 6.12.65-29 has the following entries:
Sat Nov 21 22:00:07 PST 2015 This appears to be a FreePBX Distro system as it has a Distro Version of 6.12.65-28
VARIABLES SET FOR UPGRADE
asterisk=Asterisk 11.18.0 built by root @
jenkins-builder1.schmoozecom.net on a x86_64 running Linux on 2015-06-08 13:11:11 UTC
I have a feeling that, like in that situation, you have files left from a previous failed installation which are “locking” you out from running an update script again until they are out of the way…
I hope that you have backups before even if you find out what they are and are able to run the rest of the script there is a possibility that your installation might be hosed…
Good luck and have a nice day!
PS: Personally I have always had better luck running the update scripts manually…
from the CLI issue
That fixed the issue. Thanks very much for your assistance. My system is now fully updated to the latest version.
Thank you! Fixed a stuck update for me as well! It said started HA maintenance mode (I don’t have HA) and stopped there.
Worked for me as well. What whould cause this? I poked around to see in any of the temp files and logs and found noting. The upgrade that this happened on was between 10.13.66-17 -> 10.13.66-18.
Thank you for posting this solution, had the same problem during my last update and this command resolved it!
Thanks, worked for me too!
I also just noticed this issue on a 10.13.66-17 system with auto-updates turned on.
Tony to the rescue once again!
One note, when doing the “/usr/sbin/sysadmin_update_system --unlock” command, be logged in as root not your own account.