PBX Crashing

[Martin Lyel]

Hi

We are having an issue where our client's 3CX system just stops responding altogether roughly every 4 weeks, but there is nothing being logged as far as I can see that is helpful to point me in the right direction; all I end up with is a last logged item and a first one (the most recent occasion, the last was a blacklisted IP and the first a trunk registration). I generated the support info for the system, which I can send if helpful.

For the record, this is easily resolved by restarting the VM, but of course, shouldn't be happening in the first place. The VM is still online when this happens and does appear generally responsive.

If someone can please advise or assist, it would be much appreciated.

Thanks in advance for any pointers you can give.

System is:

Product - Standard Annual
Version Number - 16.0.1078
Server - Debian GNU/Linux 9 PBX VM
Number of Simultaneous Calls - 8
Number of G729 Channels - 8
Number of Simultaneous Meeting Participants - 25
3CX Phone System Pro Edition features - No
VM Hosted on in-house Server, which is completely stable.
Trunk - New Gamma (3CX SIP Port 5060 required)
Firewall checker - passed
Custom phone templates - no

 

[Alphabetic]

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Did you install this via the ISO?

is the VM running any other software?

What are the specs of your VM?

Have you got any tasks set to run every 4 weeks? archiving maybe?

 

[Martin Lyel]

Hi

Thanks for your reply, apologies for my poor attempt at an OP...I've updated the OP to give more info now.

The OS was installed via the ISO a number of years ago and has been fine for a good few years, but over the last 6 months or so, this has been happening.

The VM is running nothing but 3CX, the specs of which are:

CPU Cores - 1
Sockets - 1
Core per Socket - 1
Memory - 8 GB
Hard disk 1 - 40 GB

And in use:

CPU - 65 MHz
Memory - 1.17 GB
Storage - 13.72 GB

And to the best of my knowledge, there are no tasks set to run, no.

 

[Martin Lyel]

Just wondered if anyone had any thoughts on this or assistance they could offer?

 

[SweetAction]

Sometimes, when I run into weird issues that I am unsure if OS related or 3CX related, I take a backup, ensure not saved to the 3CX filesystem, and do a quick reload of the OS, restoring backup when prompted. Easier with a VM since I can save the VHD(x)/VMDK files and revert if the issue is present on the fresh reload.

All settings except host settings + enabling auto-backup are preserved and I can start->finish this in under 15 minutes.

If you want to dig into the issue instead, when it's locked up, what's happening? Can you login via SSH? Can you see if 3CX services are running? Is nginx accepting any connections? etc

 

[cobaltit]

What is the hypervisor? And can you give the machine another core? And yes I'd probably do a backup and restore to a fresh VM off the latest ISO as @SweetAction mentioned

 

[JohnS_3CX]

As above, you will have to try and login via SSH and see whether it is 3CX or the entire VM that stops responding.