3CX PhoneSystem Database Server & Service Keeps Stopping and restarting

[leyanu]

Hello People,

I run a 512SC account on an AWS r5ad.4XLarge instance. Which I upgraded from a C5 instance

I have some robocalls and about 331 Extensions configured.

For the last 2 weeks, I have had the issue of my 3CX PhoneSystem Database Server & Service Keeps Stopping and restarting.

What can I do?

I have attached my system stat and a view of top users of my system resources

I need all the help I can get, the 3CX team isn't responsive.

 

[Alphabetic]

I would start by having a look in the Debian logs to see if anything stands out for you - stick your PBX in to verbose mode.

/var/log/syslog

And can you confirm you've got nothing else running on this machine?

 

[leyanu]

Hello @kieferschild ,

I do not understand much from the data in the syslog.

Would you mind I share this file in your DM?

 

[VasilisV_3CX]

Hi @leyanu,

Our Support team is currently investigating this with priority. Given the nature of the problem, Support is the correct department to be liaising with. As I understand it you spoke with someone from Support recently to find the best possible solution moving forward.

 

[leyanu]

Hello @VasilisV_3CX ,

I have been speaking with support since last week and there has been no single pointer as to what could be the issue,

I have shared several gigabytes of files without any help,

I am stuck as not a lot is happening with the businesses I support at the moment

 

[NickD_3CX]

Hello @VasilisV_3CX ,

I have been speaking with support since last week and there has been no single pointer as to what could be the issue,

I have shared several gigabytes of files without any help,

I am stuck as not a lot is happening with the businesses I support at the moment

We understand both the gravity of the situation and the urgency and I can assure you that our support team is working with the dev team to get to the bottom of this.

If I can say though and slightly explain the delicacy of the matter, crash causes, especially on a system as busy as yours are not always the easiest thing to track down, especially if certain crash logs are retrieved a while after they were generated.

I am confident though from the little I read about the case that we are probably getting closer to the cause.