3CX instances freezing up in Amazon Lightsail

[drewt]

In the past 4 days I have had two 3cx V18 update 3 build 461 go unresponsive in AWS Lightsail. I am able to stop the instance in the AWS console, takes about 4 minutes, then start the instance, another 4 minutes, and all is back to normal. Is there any insight or consensus on where to find log entries pointing to what may be causing the random freezing? Has happened in the evening both times, around 10pm est.

Thanks for viewing my thread, any replies are greatly appreciated.

 

[Evolute IT]

Check memory and CPU usage. If your instance is too small, it will indeed freeze.

 

[drewt]

Both systems spec as "small" in the hardware requirement page. One system is 9 handsets, 1cpu, 1gb ram 40gb hd. Other system is 9 handsets, 1cpu, 1gb ram 40gb hd. 3CX specs for Debian call for 1cpu 1gb ram at the link below, but a scroll down to the bottom of the page shows the cloud provider specs, and the same "small" spec of 10 handsets or less that is on Debian in the cloud BUMPS UP THE RAM TO 2gb of ram, as denoted by their label "t2.small" in the Lightsail column.

Both of my afflicted Lightsail instances have only 1gb ram. I believe I have found the first step in fixing my problem and will upgrade asap.

3CX requirements: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

Lightsail specs: https://aws.amazon.com/ec2/instance-types/t2/

Excellent discussion: https://www.3cx.com/community/threads/cloud-providers-sizing.67863/

Quote from BrenttG (I use and love pbxmonitor.net !!!)

"Another thing about the core count, remember that if the cloud your deploying to is using intel hyper-threaded CPUs, which 99% of them are, limiting a VM to 1 core, actually equates to half a normal core because hyper-threading splits all cores in half into 2, each getting 50% of the clock cycles. So a single core instance really only gets half a cpu at maximum, 90% of the techs out there either forget this, or never knew it in the first place...."