Upgrade Error from v16 to 18.0 (Build 450)

[ipt_dude]

We have a 3CX PROD on prem and I just attempted to upgrade. All seemed to go well until I saw this error in the logs:

• 3CX was successfully updated.
  
  3CX Phone System Management Console ID: 10009 03/19/2022 8:09:36 AM
• Service started
  
  SIP Server ID: 4097 03/19/2022 8:09:32 AM
• Trunk L:90000(WebMeeting bridge) has changed status to registered.
  
  SIP Server ID: 4100 03/19/2022 8:09:32 AM
• Service got signal to stop: stop service
  
  SIP Server ID: 4098 03/19/2022 8:02:32 AM
• Service got signal to stop: 15
  
  SIP Server ID: 4098 03/19/2022 8:02:32 AM
• Your 3CX Debian OS failed to update
  
  3CX Phone System Management Console ID: 10012 03/19/2022 8:01:58 AM

I also see MANY of these errors:

03/19/2022 8:09:35 AM - [CM101008]: The '' feature is disabled in currently activated licenseBLF

03/19/2022 8:09:35 AM - [CM101008]: The '' feature is disabled in currently activated licenseBLF

03/19/2022 8:09:35 AM - [CM101008]: The '' feature is disabled in currently activated licenseBLF

And these:

03/19/2022 8:09:33 AM - [CM101004]: License Limit: Call Queues are not covered under current license

03/19/2022 8:09:33 AM - [CM101004]: License Limit: Call Queues are not covered under current license

03/19/2022 8:09:33 AM - [CM101004]: License Limit: Call Queues are not covered under current license

03/19/2022 8:09:33 AM - [CM101004]: License Limit: Call Queues are not covered under current license

Please advise!

 

[Evolute IT]

2 things, your v16 was outdated and now cannot activate since the endpoint changed. For that, there's nothing you can do now. The system reverted to the most basic license level.

I would recommend taking a full backup, and installing v18 from scratch. Use the ISO, it's much faster than trying to figure it out.

V16 installs and older were not always exactly the same (different repos, etc.) and that causes issues during the official upgrade script for Debian.

If perpetual, remember to have an active maintenance.

 

[ipt_dude]

2 things, your v16 was outdated and now cannot activate since the endpoint changed. For that, there's nothing you can do now. The system reverted to the most basic license level.

I would recommend taking a full backup, and installing v18 from scratch. Use the ISO, it's much faster than trying to figure it out.

V16 installs and older were not always exactly the same (different repos, etc.) and that causes issues during the official upgrade script for Debian.

If perpetual, remember to have an active maintenance.

I logged into the CLI and this is what I see. If I'm not mistaken, that IS the upgraded OS version that v18 runs upon, correct? Perhaps that error message was erroneous?


root@3cx:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
root@3cx:~#

 

[Evolute IT]

I logged into the CLI and this is what I see. If I'm not mistaken, that IS the upgraded OS version that v18 runs upon, correct? Perhaps that error message was erroneous?


root@3cx:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
root@3cx:~#

Or perhaps the upgrade did work but not 100%. There's no way to know.

You usually get an error log file by email when the upgrade fails. Did you get that?

 

[ipt_dude]

Or perhaps the upgrade did work but not 100%. There's no way to know.

You usually get an error log file by email when the upgrade fails. Did you get that?

So I have this successful email alert:

3CX was successfully updated.
Your installation at <FQDN> is now running the latest version and all 3CX Services are up and running.
We recommend your installation is always on the latest version for potential security fixes, new and improved features, as well as better compatibility with SIP Trunks and IP Phones.

And an OLDER failure alert - I'm not remembering that when I logged into the 3CX MC and initiated the "UPGRADE" - the MC immediately terminated and brought me right back to the LOGIN dialog box - where I logged in and initiated the upgrade a second time.

If you look at this failure log - it alludes to the fact that the upgrade is ALREADY underway and I suspect that this "Failure" alert was because of my second request to UPGRADE.

See failure email alert:
3CX attempted to update your 3CX Debian OS at <FQDN> 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.

See failure email alert log snippet here:

33m====== [08:01:58] Preparation: Script path is /tmp/update.sh[39m
[33m====== [08:01:58] Preparation: Upgrade script update.sh seeems to be already running. Found /tmp/UPDATE_RUNNING[39m

 

[Evolute IT]

That's how it works. When you start the upgrade it logs you off.

That's probably the error you got then. Simply because it was already doing the upgrade.

 

[ipt_dude]

That's how it works. When you start the upgrade it logs you off.

That's probably the error you got then. Simply because it was already doing the upgrade.

This was my first 3CX production upgrade so it was a little nerve wracking. All in all - I see no issues at this time gratefully.

 

[ipt_dude]

That's how it works. When you start the upgrade it logs you off.

That's probably the error you got then. Simply because it was already doing the upgrade.

Now I've been informed that non of my Call Flow Designer DIDs are working. When calling any of those DIDs - you get ring no answer. But if I call a DID that is mapped to a phone (not a CFD app) - it rings in and provides two way audio with no issues.

 

[Evolute IT]

Now I've been informed that non of my Call Flow Designer DIDs are working. When calling any of those DIDs - you get ring no answer. But if I call a DID that is mapped to a phone (not a CFD app) - it rings in and provides two way audio with no issues.

You need to update your CFD designer, then reopen your projects to build them using the v18 CFD. There was changes in there too.

 

[Evolute IT]

This was my first 3CX production upgrade so it was a little nerve wracking. All in all - I see no issues at this time gratefully.

Glad your not having any! If you do, the best thing will be a simple reinstall using backup/restore. This usually clears out every issues.

 

[ipt_dude]

So I have this successful email alert:

3CX was successfully updated.
Your installation at <FQDN> is now running the latest version and all 3CX Services are up and running.
We recommend your installation is always on the latest version for potential security fixes, new and improved features, as well as better compatibility with SIP Trunks and IP Phones.

And an OLDER failure alert - I'm not remembering that when I logged into the 3CX MC and initiated the "UPGRADE" - the MC immediately terminated and brought me right back to the LOGIN dialog box - where I logged in and initiated the upgrade a second time.

If you look at this failure log - it alludes to the fact that the upgrade is ALREADY underway and I suspect that this "Failure" alert was because of my second request to UPGRADE.

See failure email alert:
3CX attempted to update your 3CX Debian OS at <FQDN> 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.

See failure email alert log snippet here:

33m====== [08:01:58] Preparation: Script path is /tmp/update.sh[39m
[33m====== [08:01:58] Preparation: Upgrade script update.sh seeems to be already running. Found /tmp/UPDATE_RUNNING[39m

Thank you for editing out my FQDN! I quickly scanned that file before I posted but didn't think about that.

Best,
Amir

 

[ChrisC_3CX]

Thank you for editing out my FQDN!

No worries!

 

[ipt_dude]

No worries!

Thank you Chris. Always appreciate the customer and 3CX forum feedback and support!