SIPXCDR High CPU Utilization

[Peter Krautle]

We have a Sipxcom 3-node cluster where the primary server is showing high cpu utilization due to the sipxcdr process. Is there an easy way to reset just the Sipxcdr database via psql/postgres methods ... e.g. drop database sipxcdr and rebuild the database without resetting the entire system? The system is at 17.04.

[Peter Krautle]

I developed a procedure to clear out the Sipxcdr database using psql - the system in question has 500000 entries. I tested the procedure on a lab system - after clearing out the CDR entries, Sipxcom continues to add more CDRs to the database. We'll see if this solves the cpu utilization problem. Peter

[Iuliu Blaga]

Hi, I would also recommend to upgrade to the latest 17, that is 17.10-unstable which adds a lot of fixes. This can be a in place upgrade with minimal impact.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/fb83a298-6061-40ca-91b8-7df9fca7a8c7n%40googlegroups.com.

--

 

Iuliu Blaga Sr. Support Engineer 215.297.4400 x 751 Arbor Way, Arbor Crest I, Suite 150, Blue Bell, PA 19422 coredial.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

[Peter Krautle]

We cleaned up the cdrs table but the postgresql performance for cdrs is still slow. Without rebuilding the system or upgrading to 17.10, is there an easy way to rebuild the SQL database that stores the CDRs?

Many thx in advance.

Peter

[Peter Krautle]

Hi Luliu - I installed 17.04 in the lab and then upgraded to 17.10 unstable - works well except that the centos 6 repos needed to be removed before yum update would work. I have written up the procedure for the client.

Peter

[Iuliu Blaga]

Hi, you need to change not remove the repos to the vault ones

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/cd74c0c1-09ce-4ab5-b144-3f51665049dbn%40googlegroups.com.

[Iuliu Blaga]

https://www.getpagespeed.com/server-setup/how-to-fix-yum-after-centos-6-went-eol

On Monday, September 12, 2022, Peter Krautle <pmkr...@gmail.com> wrote:

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/cd74c0c1-09ce-4ab5-b144-3f51665049dbn%40googlegroups.com.

[Peter Krautle]

Thx - The ssl connection on Centos 6 is dated and required updates. Given that this Sipxcom system was on a private network behind a commercial firewall, it was easier to bypass the Centos 6 updates to move forward. The correct long-term solution is to update to the latest release. Peter

http://vault.epel.cloud/6.10/os/x86_64/repodata/repomd.xml: [Errno 14] problem making ssl connection

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/cd74c0c1-09ce-4ab5-b144-3f51665049dbn%40googlegroups.com.