Under Review V16 to V18 on prem failed

[M.Zanetti]

Hello.
I have several dozens of 3cx hosted (3cx or aws) that I've already upgraded to V18 without any problem.
There also are a couple of installation on premise that failed everytime I tried to upgrade. All of them are built on 3cx official ISOs.
Error message is always the same:

3CX attempted to update your 3CX Debian OS at XXXXXX.my3cx.it from Debian 9 to 10 and failed.
This may be caused by changes made to the OS after installation. The attached log file shows where the update failed.

Error logs (see attached file) stated "There seems to be an apt file lock in place." but i wasn't able to find out how to get update done.
I've seen the troubleshooting post on 3cx website, but the only information regarding this message was:
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.

Thanks in advance.

 

[Charles_3CX]

Before going down the suggested route recommended in the guide, try rebooting the machine, after the reboot try the update again. Do though always make sure that you take a full backup and save it to a safe location, out of the 3cx folders, before attempting any updates.

 

[QueBall]

If it's a standard ISO install and especially if running as a VM just create a new VM with fresh ISO and restore the backup. Very easy. The backups are very robust.

 

[M.Zanetti]

Before going down the suggested route recommended in the guide, try rebooting the machine, after the reboot try the update again.

Rebooting PBX did the job: update was flawless.
The only strange thing was that after upgrade its MAC addres has changed: 3cx was previously dhcp reserved and after upgrade my dhcp server assigned another IP address.
FYI, new mac address is technically wrong: it's not common xx:xx:xx:xx:xx:xx but is this: 7e4817c00001000128ca499cd43d7e4817c0.
The same thing has happened to our own 3cx: after V18 upgrade MAC address changed to the same format.

 

[ChrisC_3CX]

Rebooting PBX did the job: update was flawless.

Glad to hear you got this sorted!

after upgrade my dhcp server assigned another IP address.
FYI, new mac address is technically wrong: it's not common xx:xx:xx:xx:xx:xx but is this: 7e4817c00001000128ca499cd43d7e4817c0.

This we are aware of and comes up with Debian 10 instances. We're currently looking into so I'll update this thread once we have something.

 

[M.Zanetti]

Thank you Chris, so I'm expecting MAC address changes for all PBX not yet updated.