[SR-Users] Kamailio TOPOS fail

Julien Chavanton jchavanton at gmail.com
Mon Feb 11 18:07:04 CET 2019


Hi Marco, not sure if it is the same issue, but I am looking at a problem I
am facing where in-dialog requests are failing after 3 minutes.

It seems you are also using topos_redis

Tracing TOPOS traffic is seems some leg related infomation is set to expire
after 3 minutes.

Just sharing in case we can get a quick answer, but I will troubleshoot the
behavior more to understand if this is suppose to be transaction data that
and Dialog data should persist anyway.
Seems like 2 EXPIRE commands are sent, the second one with a low value of
180

https://github.com/kamailio/kamailio/issues/1848



On Mon, Feb 11, 2019 at 3:38 AM Marcos Pytel <marcos.pytel at cotesma.com.ar>
wrote:

> Hi all!
>
> Any clue for this?
>
> Marcos.
> -----Mensaje original-----
> De: Henning Westerholt <hw at kamailio.org>
> Enviado el: martes 5 de febrero del 2019 17:50
> Para: sr-users at lists.kamailio.org
> CC: Marcos Pytel <marcos.pytel at cotesma.com.ar>
> Asunto: Re: [SR-Users] Kamailio TOPOS fail
>
> Am Montag, 4. Februar 2019, 17:11:03 CET schrieb Marcos Pytel:
> > When I activate the TOPOS function, the Kamailio lb fail.
> >
> > This is the traceback
>
> Hello Marcos,
>
> thank you for the report. the best is to open an issue on our github
> tracker
> about this, to better tackle it. Please include more information (you'll
> find pointers there in the template).
>
> Best regards,
>
> Henning
>
> > Program terminated with signal SIGABRT, Aborted.
> >
> > #0  __GI_raise (sig=sig at entry=6) at
> > ../sysdeps/unix/sysv/linux/raise.c:51
> >
> > 51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> >
> > (gdb) backtrace
> >
> > #0  __GI_raise (sig=sig at entry=6) at
> > ../sysdeps/unix/sysv/linux/raise.c:51
> >
> > #1  0x00007f66d5aab42a in __GI_abort () at abort.c:89
> >
> > #2  0x00007f66d5ae7c00 in __libc_message (do_abort=do_abort at entry=2,
> > fmt=fmt at entry=0x7f66d5bdb305 "*** %s ***: %s terminated\n")
> >
> >     at ../sysdeps/posix/libc_fatal.c:175
> >
> > #3  0x00007f66d5b701f7 in __GI___fortify_fail
> > (msg=msg at entry=0x7f66d5bdb29c "buffer overflow detected") at
> > fortify_fail.c:30
> >
> > #4  0x00007f66d5b6e330 in __GI___chk_fail () at chk_fail.c:28
> >
> > #5  0x00007f66b867e097 in memcpy (__len=<optimized out>,
> > __src=<optimized
> > out>, __dest=0x7f66b8892524 <_tps_redis_cbuf+4>)
> >
> >     at /usr/include/x86_64-linux-gnu/bits/string3.h:53
> >
> > #6  tps_redis_load_branch (msg=<optimized out>, md=<optimized out>,
> > sd=0x7ffed3993d30, mode=<optimized out>) at topos_redis_storage.c:744
> >
> > #7  0x00007f66b88b35c0 in tps_request_received
> > (msg=msg at entry=0x7ffed3995f80, dialog=dialog at entry=1) at tps_msg.c:786
> >
> > #8  0x00007f66b88b9255 in tps_msg_received (evp=<optimized out>) at
> > topos_mod.c:332
> >
> > #9  0x000055e1dc07da88 in sr_event_exec (type=<optimized out>,
> > evp=<optimized out>) at core/events.c:211
> >
> > #10 0x000055e1dc0415f5 in receive_msg (
> >
> >     buf=buf at entry=0x55e1dc511d40 <buf> "BYE
> > sip:atpsh-5c4b0f6e-25b2-9 at 10.10.10.2 SIP/2.0\r\nVia: SIP/2.0/UDP
> > 10.10.10.1:5060;branch=z9hG4bK898122669\r\nFrom:
> > <sip:2972426338 at 10.10.10.1>;tag=3296734298\r\nTo:
> > <sip:414533 at 10.10.10.2>;tag=03D2CCF0-5"..., len=381,
> > rcv_info=rcv_info at entry=0x7ffed3996980) at core/receive.c:157
> >
> > #11 0x000055e1dbf5e6e3 in udp_rcv_loop () at core/udp_server.c:554
> >
> > #12 0x000055e1dbef3a9f in main_loop () at main.c:1619
> >
> > #13 0x000055e1dbeea8cb in main (argc=<optimized out>,
> > argv=0x7ffed3996f38) at main.c:2638
> >
> >
> >
> > This is a Kamailio error? I can fix it?
>
>
> --
> Henning Westerholt - https://skalatan.de/blog/ Kamailio services -
> https://skalatan.de/services Kamailio security assessment -
> https://skalatan.de/de/assessment
>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190211/98d4b1c5/attachment.html>


More information about the sr-users mailing list