Re: segfault error 6 in tm.so

Carsten Bock via sr-users <[email protected]> Tue, 17 Mar 2026 14:51:31 +0100
Newsgroups gmane.comp.voip.ser
Message-ID <CADw-rRzy=dPdiNT-0Yoh=zMMNC2e9kV6KqByK+3vk4A=ZrOO1A@mail.gmail.com>
Hi,

I would also dare to ask, if "t_newtran();" in an event_route[] makes sense
at all... it's an event, so no SIP involved, where a transaction would make
sense.

However, I would argue that it should produce an error or a warning and it
should not crash.

Thanks,
Carsten
--
Schöne Grüße aus Hamburg, dem Tor zur Welt,
Carsten Bock

Baron-Voght-Str. 128a I 22607 Hamburg I Germany
T +49 179 2021244 I [email protected]
LinkedIn: https://www.linkedin.com/in/carstenbock/


Am Di., 17. März 2026 um 14:21 Uhr schrieb Henning Westerholt via sr-users <
[email protected]>:

> Hello,
>
>
>
> please try to produce a coredump and then get a backtrace, e.g. as
> described here:
> https://www.kamailio.org/wikidocs/tutorials/troubleshooting/coredumpfile/
>
>
>
> Does it happened only once so far, or frequently?
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> *From:* Сергей Приймак via sr-users <[email protected]>
> *Sent:* Dienstag, 17. März 2026 13:09
> *To:* Benoit Panizzon via sr-users <[email protected]>
> *Cc:* Сергей Приймак <[email protected]>
> *Subject:* [SR-Users] segfault error 6 in tm.so
>
>
>
> Dear All,
>
> kindly asking to have a look at following error. When I use event_route in
> a way like below:
>
>
>
> event_route[dispatcher:dst-down] {
>
>   xlog("Destination down: $rm $rd \n");
>
>   if(is_in_subnet($rd, "192.168.131.0/24")) {
>
>     if(ds_select_dst("1", "0")) {
>
>       xlog("L_ERR", "Next available destination: $dd\n");
>
>       t_newtran();
>
>       http_async_query("
> http://192.168.131.21:8080/recovercall.cgi?oldip=$rd&newip=$dd",
> "HTTP_REPLY");
>
>     }
>
>   }
>
> }
>
>
>
> in case some destination is down, I experiencing following problem:
>
>
>
> 2026-03-17T13:24:53.778421+02:00 kam1 /usr/local/sbin/kamailio[2102]:
> ERROR: <script>: Destination down: OPTIONS 192.168.131.20
>
> 2026-03-17T13:24:53.779095+02:00 kam1 kernel: kamailio[2102]: segfault at
> 678 ip 00007f5eb5395d06 sp 00007fff26462980 error 6 in
> tm.so[112d06,7f5eb5290000+127000] likely on CPU 1 (core 1, socket 0)
>
> 2026-03-17T13:24:53.779138+02:00 kam1 kernel: Code: 8b 05 4e 32 05 00 89
> 10 b8 ff ff ff ff e9 d6 1a 00 00 48 8b 45 c8 48 8b 80 f0 00 00 00 48 8b 95
> 48 ff ff ff 8b 92 78 06 00 00 <89> 90 78 06 00 00 e8 80 56 f5 ff 85 c0 0f
> 89 69 03 00 00 48 8b 05
>
> 2026-03-17T13:24:53.780890+02:00 kam1 /usr/local/sbin/kamailio[2102]:
> ERROR: <script>: Next available destination: 192.168.131.21
>
> 2026-03-17T13:24:53.781758+02:00 kam1 /usr/local/sbin/kamailio[2102]:
> INFO: tm [t_lookup.c:1886]: t_newtran(): attempt to create transaction for
> a faked request - try to avoid it
>
> 2026-03-17T13:24:53.782445+02:00 kam1 /usr/local/sbin/kamailio[2102]:
> NOTICE: tm [tm.c:1748]: w_t_newtran(): transaction already in process
> 0x7f5eb6a550f0
>
> 2026-03-17T13:24:53.836181+02:00 kam1 /usr/local/sbin/kamailio[2127]:
> CRITICAL: <core> [core/pass_fd.c:284]: receive_fd(): EOF on 78
>
> 2026-03-17T13:24:53.837291+02:00 kam1 /usr/local/sbin/kamailio[2053]:
> ALERT: <core> [main.c:815]: handle_sigs(): child process 2102 exited by a
> signal 11
>
> 2026-03-17T13:24:53.837625+02:00 kam1 /usr/local/sbin/kamailio[2053]:
> ALERT: <core> [main.c:819]: handle_sigs(): core was not generated
>
> 2026-03-17T13:24:53.837829+02:00 kam1 /usr/local/sbin/kamailio[2053]:
> INFO: <core> [main.c:842]: handle_sigs(): terminating due to SIGCHLD
>
>
>
> Kamailio version 6.1.1
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions --
> [email protected]
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
>

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!