Re: [Serusers] is serusers@lists.iptel.org mailing list still in use?

Hi all, I have a serious problem with Ser. Periodically (about every two weeks) SER crashes: cpu grows until 100% caused by ser child process and I must restart it. I attached a debugger to blocked child process and this is the output: 1 child: #0 0x0000003cbacb4ca7 in sched_yield () from /lib64/libc.so.6 #1 0x00002aaaab1197a9 in reply_received (p_msg=0x7b7770) at ../../mem/../fastlock.h:323 #2 0x000000000042e2a7 in forward_reply (msg=0x7b7770) at forward.c:573 #3 0x000000000044e91a in receive_msg ( buf=0x707b00 "SIP/2.0 100 Trying\r\nVia: SIP/2.0/UDP ..., len=527, rcv_info=0x7fffde370b10) at receive.c:221 #4 0x0000000000487493 in udp_rcv_loop () at udp_server.c:495 #5 0x0000000000436f9b in main_loop () at main.c:1011 #6 0x0000000000438331 in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:1600 2 child: (gdb) bt #0 0x0000003cbacb4ca7 in sched_yield () from /lib64/libc.so.6 #1 0x00002aaaab102c51 in retr_buf_handler (ticks=1, tl=<value optimized out>, p=<value optimized out>) at ../../mem/../fastlock.h:323 #2 0x000000000047e50d in slow_timer_main () at timer.c:1026 #3 0x000000000043735d in main_loop () at main.c:1033 #4 0x0000000000438331 in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:1600 3 child (gdb) bt #0 0x0000003cbacb4ca7 in sched_yield () from /lib64/libc.so.6 #1 0x00002aaaab1197a9 in reply_received (p_msg=0x7b7770) at ../../mem/../fastlock.h:323 #2 0x000000000042e2a7 in forward_reply (msg=0x7b7770) at forward.c:573 #3 0x000000000044e91a in receive_msg ( buf=0x707b00 "SIP/2.0 100 Trying\r\nVia: SIP/2.0/UDP ..., len=527, rcv_info=0x7fffde370b10) at receive.c:221 #4 0x0000000000487493 in udp_rcv_loop () at udp_server.c:495 #5 0x0000000000436f9b in main_loop () at main.c:1011 #6 0x0000000000438331 in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:1600 4 child: #0 0x0000003cbacb4ca7 in sched_yield () from /lib64/libc.so.6 #1 0x00002aaaab1197a9 in reply_received (p_msg=0x7b7770) at ../../mem/../fastlock.h:323 #2 0x000000000042e2a7 in forward_reply (msg=0x7b7770) at forward.c:573 #3 0x000000000044e91a in receive_msg ( buf=0x707b00 "SIP/2.0 180 Ringing\r\nVia: SIP/2.0/UDP 213.21.177.229;branch=z9hG4bK862b.63d025c3.2;received=213.21.177.229\r\nVia: SIP/2.0/UDP 213.21.128.189:5060;branch=z9hG4bK189A0F1DE2\r\nFrom: <sip:0464669373@213.21"..., len=543, rcv_info=0x7fffde370b10) at receive.c:221 #4 0x0000000000487493 in udp_rcv_loop () at udp_server.c:495 #5 0x0000000000436f9b in main_loop () at main.c:1011 #6 0x0000000000438331 in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:1600 Log is clean, often ser simply stop to write it. I checked and monitored shared memory and it's always slow. I use SER 2.0 in a centos system with about 2000 registered user. Please, can anyone help me? Thanks in advance and sorry for my bad english. Martina