Solved Failed upgrade v16 to v18

[NicoC]

Hi All, I was hoping someone may be able to help out. I have a clients server that is failing to upgrade from v16 to v18. The v16 install was done from the Debian 9 ISO provided on the 3CX page and the upgrade is being performed using the update option on the web GUI. I have looked through the KB articles regarding failed upgrades and the log contains this line at the top

[31m[09:39] Preparation: There seems to be an apt file lock in place. Don't touch anything. - 0[39m


Here is what the article says

Locked APT or DPKG​

Both package managers of Debian can sometimes be busy at the moment you try to run the upgrade of your 3CX System. Combined, this totals to 10% of the cases for an unsuccessful upgrade. Commonly there is nothing to worry about, as the system remained unchanged in v16 from the moment the upgrade was attempted.

Your v16 installation is not affected by the upgrade attempts and returns back to where you left it prior to the upgrade.

Inspection​

The log will contain a line response line:
There seems to be an apt file lock in place.
There seems to be a dpkg file lock in place.

Solution​

It is recommended that you try to upgrade the process again in 30 minutes. If the situation remains unchanged you can debug why APT or DPKG is locked or take the route to reinstall the system via backup and restore functionality onto a new Debian 10 instance. This also clears out any uncertainty if you are not sure how you had installed 3CX previously.

I have tried this two separate times approximately a week apart from each other. I have also attached a copy of the install log

 

[VasilisV_3CX]

Hi @NicoC,

Have you tried restarting the server? I think this would be a better start than looking up process IDs and killing tasks.

 

[dandersonn]

update seems to work after server restart.

 

[VasilisV_3CX]

Great to hear @dandersonn, let me know if you run into issues!