No access to Web Management Console since last update

Status
Not open for further replies.
Yep, Looks like it was closed within a few days of 3CX discovering the issue.

Any update on this @YiannisH_3CX @norekhov ?
 
Hello,

we are also having a Stopped Services Notification - Following service(s) were stopped recently:
3CXPhoneSystemMC01

The error occurs every second day on a new installation, a reboot of the linux vm and a restart of all services resolves the problem.

do you have any updates for us?
 
The discussion is actually going on a different post https://github.com/dotnet/coreclr/pull/16577 so we don't have an update for resolving the matter yet.
Hi, are there no news ? A few of my customers running on SP2 and I can´t update them.
For a new customers I want to install an server also.
Can you say me if the Processor Intel Celeron J3455 is also effected ? It has also no AVX, but you say that some Special CPU´s has that problem.
Thank you
 
Hi,

I have several Intel NUC6CAYH with Celeron J3455 CPU running, all with the AVX issue.
None of them can be upgraded to SP3 and up because of this issue.
I am also waiting for a fix to restore the YMM registers but this is still under investigation.
 
We have a handful of affected servers as well, all running celerons. Has anybody found a way to manually install SP3 via SSH and then go up to SP4 right away? Or skip SP3 and go right to SP4? Probably that is not possible anyway. Does SP4 have the same issue?
 
Please note that we are waiting for the fix to be included in the next Netcore release. Once it does we will update and we will check if the issue is fixed. The issue is with netcore and not the PBX and we cannot control when issue will be fixed.
Does SP4 have the same issue?
Yes the issue is present in SP4 as well.
 
I have just had this issue come up as well when I went to add an extensions. How is the solution coming along? is there anything i can do to get the MMC up and running again?
 
As i have mentioned above the issue is the .net core. Once the include the fix in the net core we will apply it, test it and include it in the next build. We are waiting for the fix as well.

is there anything i can do to get the MMC up and running again?
A restart of the system might bring the management console back up but there are no guarantees
 
A summary of what the issue is and where we are with the solution.

Since the release of SP3 (15.5.8801) there is an issue with CPU's that lack AVX extensions that could cause the management console service to crash.
To see if your CPU is affected please use the following link:
https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX
https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX2

This is due to an issue in .NET core that is being discussed here: https://github.com/dotnet/coreclr/pull/16577
The fix is said to be released in .NET core 2.0.7 and once it does and we have verified that the issue has been fixed we will include it in our next update to address the issue.

For now if you are affected by the issue it is recommended to stay in SP2 and only upgrade when we confirm that the issue has been resolved. We will post an update here once the issue has been addressed.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,885
Messages
589,545
Members
164,744
Latest member
johnblackwood1