Multiple 3CX Servers hanging at random since 16.0 Release

[Gunnar Brynjólfsson]

@Gunnar Brynjólfsson @Azhar

Can you both confirm if you are using the Instance Manager connected to a Reseller account on the affected machines ?

Hi, I was using "Instance Manager" connected to the Reseller account on the affected machine, those not using instance manager were not affected.

 

[JohnS_3CX]

Thank you for your feedback, the issue reported is under investigation.

For the time being I would suggest to disable the instance manager on the affected machines, and then reboot to clear any stuck processes while we look further into the matter.

 

[BrenttG]

@Gunnar Brynjólfsson @Azhar

Can you both confirm if you are using the Instance Manager connected to a Reseller account on the affected machines ?

We do not use the Instance Manager, but all of our PBXs are registered to our reseller account, and i believe the Instance Manager is turned on, however, i must note, the last several times the problem has occurred for us, including last weekend wheni t hit 30 servers at once, it was within minutes of the automatic update schedule hitting. Im not 100% convinced its the instance manager due to that fact that 2 minutes after the system tries to update, BOOM! And there wasn't even any 3CX updates pending, they were all already up to date, the only update showing was the BETA, which we don't do on production systems.

 

[BrenttG]

I just logged into the two biggest systems that were affected on sunday night, and both do not have instance manager turned on.... it is off. +1 to the scheduled updater having something to do with it.

Note: the 30 servers that went down, were all set to update automatically in 3CX, at 8:00 PM Arizona,USA timezone, on sunday. They all went offline at varying times between 8:02-8:05 PM. The times they went offline are a matter of record because we have active monitoring running against them.

 

[NickD_3CX]

Hi everyone,

Just an update on this. We made a few adjustments to the scripts that are ran in the background by the Instance Manager which should prevent this kind of behavior.
To get the adjustments, all you should need to do is either:

• Stop the Instance Manager, then start it again

or

• Restart the whole machine 3CX is running on

(whatever is easier for you)

I think we haven't missed something, but looking forward to any feedback you may have.