Solved Upgraded from D9 to D10 and v16 to v18 but Management Console fails

[Kirbi]

Hi all,

debian9to10.log in /var/lib/3cxpbx seems to indicate that the upgrade went through flawlessly but on reboot the Management Console doesn't start.

The error from /var/lib/3cxpbx/Instance1/Data/Logs/3cxManagementConsole.log is

[/B] 2021/11/08 14:58:21.396|670|0001|Inf|MYPHONE: Sending MyPhone.Notifications.WmPollings to WM Gateway 2021/11/08 14:58:21.868|670|0009|Err|MYPHONE: Failed to update WebRTCEndpoint. WebRTC endpoints are not available System.TypeIni tializationException: The type initializer for 'MyPhoneServer.Common.ClientManager' threw an exception. ---> System.AggregateException: One or more errors occurred. (42703: column "closed_at" of relation "chat_results" does not exi st) ---> Npgsql.PostgresException (0x80004005): 42703: column "closed_at" of relation "chat_results" does not exist at Npgsql.NpgsqlConnector.<ReadMessage>g__ReadMessageLong|194_0(NpgsqlConnector connector, Boolean async, DataRowLoadingMode dataRowLoadingMode, Boolean readingNotifications, Boolean isReadingPrependedMessage) at Npgsql.NpgsqlCommand.<Prepare>g__PrepareLong|74_0(NpgsqlCommand command, Boolean async, NpgsqlConnector connector, Cancell ationToken cancellationToken) at MyPhoneServer.Common.DBUtils.<>c__DisplayClass30_0.<<ExecuteNonQueryAsync>b__0>d.MoveNext() --- End of stack trace from previous location --- [B]

I did some searching but can't find another example of this error. Any ideas from anyone (other than that usual rebuild and restore suggestions)?

This is running on a local Hyper-V that was downloaded from it's original place in Azure (it's originally a 3CX Azure Marketplace VM). It's been running perfectly until I attempted this upgrade. As mentioned. The upgrade log indicates that everything went smoothly. I double checked the sections in the upgrade log for the DB and no errors.

Hoping someone can help me avoid a full re-install. BTW: I have attempted manual restarts of 3CX, rebooting, all the normal stuff mentioned in other failed upgrade threads. None if it helps (which I suspected it wouldn't given the nature of the error).

Anyways, any suggestions most welcome. Is there a tool to verify the integrity of the DB?

Thanks

 

[ChrisC_3CX]

This is running on a local Hyper-V that was downloaded from it's original place in Azure (it's originally a 3CX Azure Marketplace VM)

By this do you mean you downloaded a "clone" of the VM like a VHD?

The problem preventing the 3CX Management Console service from starting up seems to be a database error therefore I highly I doubt there's an easy solution, let alone a solution that would be faster and easier that simply re-installing. To be completely honest I would strongly recommend you re-install and restore as this would not only be faster, but will ensure you end up with a "clean" 3CX instance that will not cause similar issues in the future.

Note: Remember to use the latest 3CX ISO which includes Debian 10 and installs 3CX v18. A 3CX v16.0.8.9 backup will work just fine for restoring. Also, do follow our Hyper-V guide since this is the hypervisor you're using.

 

[Kirbi]

I ended up doing the restore, just for expedience. The only issue with the upgrade (from what I can tell) after comparing the two systems is that the database migration either didn't run or failed (without logging). There is definitely a new column in the chat_results table that didn't get created when the upgrade ran. I would really like to know where to find the DB upgrade scripts as this could have easily been resolved by just manually running those to alter that table (and any others that required altering) as part of the upgrade.