Solved ManagementConso crash regularly when extension is added

[Lukas Sukdol]

Hi,

after fresh install Debian/3cx PBX v15.5 on minicomp Zotac Zbox CI327 Nano (Celeron N3450, 8GB RAM), I am facing next failure - when new extension is created in Management Console, service 3CXPhoneSystemMC01 crash immediately, with error message on stdout (and dmesg):
traps: ManagementConso[835] trap invalid opcode ip:7f8c0b2b3914 sp:7f8af77a93f0 error:0
in libcoreclr.so[7f8c0b025000+39f000]

Despite of this failure, extension is created and saved, after service restart (service 3CXPhoneSystemMC01 restart) I am able to use it, change it, save again - without any failure...

Same failure could be produced by clicking Terminal link on Dashboard - when I close the terminal Tab (Chrome 65.0 and Safari 11.0 on Mac 10.12.6) service 3CXPhoneSystemMC01 also crash immediately...

Any idea?
Thanks

 

[YiannisH_3CX]

Hello @Lukas Sukdol

You might be interested in the following link. It explains the issue you are facing. In short there is an issue with .NET core that causes the management console to stop
https://www.3cx.com/community/threads/no-access-to-web-management-console-since-last-update.54285
To add to the thread 2.0.7 is out and we are currently testing it to make sure the issue is resolved.
If all is ok the next release will fix the issue you are facing.

 

[Lukas Sukdol]

Thanks @YiannisH_3CX

So the only workaround for me is to create extensions with hands on the server keyboard ...

 

[complex1]

@Lukas Sukdol

The only reliable workaround for now is to downgrade 3CX from SPx to SP2 as describe in this post.
https://www.3cx.com/community/threads/downgrade-v15-update-3-to-2-debian-9.54525/

 

[nb]

This is because .net core from microsoft does not support all the extensions for your current CPU.
This will be fixed in SP5.


If you want a build that fixes this, contact me via pm. But then when the actual release is out, you will need run some commands to go back to production. IF you are ok with this contact me. If not, then keep on creating the extension and ignore this error (because technically you can still proceed) or import extensions and wait for SP5. This will be released in a months time.

 

[Lukas Sukdol]

@nb - thanks for the idea to use import - seems to be pretty straightforward to use csv import/export

 

[nb]

Yes - good - use import feature - add all your extensions at one go.
Restart the service one time after import to ensure that none of the data is corrupted.
Work as it is for now, and soon sp5 will be out and you can add extensions at will on this mini pc with no problems.

 

[pluym]

This is because .net core from microsoft does not support all the extensions for your current CPU.
This will be fixed in SP5.


If you want a build that fixes this, contact me via pm. But then when the actual release is out, you will need run some commands to go back to production. IF you are ok with this contact me. If not, then keep on creating the extension and ignore this error (because technically you can still proceed) or import extensions and wait for SP5. This will be released in a months time.

Please, tell us. We have issues with SP2 and Fanvil provisioning. On SP4 the problem is solved but we cannot upgrade beacause of this DOT NET issue. How can i send you a PM ?