Kamailio had an abort happend and does a coredump. Sorry I doesn't have debug symbols on this machine.
Kamailio:
```
root@voip-integration-cust1:~ # kamailio -V
version: kamailio 4.4.0 (amd64/freebsd) d4f23c
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, select, kqueue.
id: d4f23c
compiled on 16:52:24 Apr 30 2016 with clang 3.4
```
Log:
```
May 4 17:55:27 <local0.crit> voip-integration-cust1 kamailio[1177]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 12
May 4 17:55:27 <kern.info> voip-integration-cust1 kernel: pid 1147 (kamailio), uid 986: exited on signal 6 (core dumped)
May 4 17:55:27 <kern.info> voip-integration-cust1 kernel: pid 1146 (kamailio), uid 986: exited on signal 6 (core dumped)
May 4 17:55:27 <local0.alert> voip-integration-cust1 kamailio[1145]: ALERT: <core> [main.c:739]: handle_sigs(): child process 1147 exited by a signal 6
May 4 17:55:27 <local0.alert> voip-integration-cust1 kamailio[1145]: ALERT: <core> [main.c:742]: handle_sigs(): core was generated
May 4 17:55:27 <kern.info> voip-integration-cust1 kernel: pid 1148 (kamailio), uid 986: exited on signal 6 (core dumped)
```
Backtrace:
```
#0 0x000000080110235a in thr_kill () from /lib/libc.so.7
#1 0x0000000801102346 in raise () from /lib/libc.so.7
#2 0x00000008011022c9 in abort () from /lib/libc.so.7
#3 0x0000000800e3195a in pthread_attr_getaffinity_np () from /lib/libthr.so.3
#4 0x0000000800e2d046 in pthread_mutex_destroy () from /lib/libthr.so.3
#5 0x0000000805b436b5 in rpc_reply () from /usr/local/lib/kamailio/modules/tm.so
#6 0x0000000805b23f18 in tm_reply_mutex_lock () from /usr/local/lib/kamailio/modules/tm.so
#7 0x0000000805b34ba2 in reply_received () from /usr/local/lib/kamailio/modules/tm.so
#8 0x000000000057146b in forward_reply ()
#9 0x0000000000570cca in forward_reply ()
#10 0x00000000004682a4 in receive_msg ()
#11 0x0000000000645023 in udp_rcv_loop ()
#12 0x0000000000543cad in main_loop ()
#13 0x00000000005519a5 in main ()
```
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/604
I would like the URI transformations to be more generic so one can pick up the URI scheme, like HTTP: or TEL:
Just an idea
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/592
### Description
During some test on my server I forgot to configure a valid listen network address. It's my fault but Kamailio crashed with a useless message:
> kamailio[4739]: segfault at 0 ip 00007f022ede5e71 sp 00007fff94033f08 error 4 in libc-2.17.so[7f022ec82000+1b6000
I think it's better to abort the startup if no listen address is specified and with an explicit error message, instead of produce a segfault and a crash without any error
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1098
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1087
-- Commit Summary --
* pkg/kamailio: Fix of ticket 1085
-- File Changes --
M pkg/kamailio/centos/7/kamailio.service (2)
M pkg/kamailio/deb/debian/kamailio.service (2)
M pkg/kamailio/deb/jessie/kamailio.service (2)
M pkg/kamailio/deb/sid/kamailio.service (2)
M pkg/kamailio/deb/stretch/kamailio.service (2)
M pkg/kamailio/deb/xenial/kamailio.service (2)
M pkg/kamailio/fedora/17/kamailio.service (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1087.patchhttps://github.com/kamailio/kamailio/pull/1087.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1087
ENV: Debian 8
So on most Linux systems the /var/run folder is a tmpfs and after which clears after each reboot
As I try to start up kamailio after a reboot through kamctl I get the following error.
"ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed"
Because kamailio does not have the permission to write to the /var/run folder as the kamailio user.
Would it be possible to add in the "kamctl" code a section where the SPECIFIED PID LOCATION (/var/run/kamailio) is checked and if it does not exist create it as the root user and chown it to the SPECIFIED USER (kamailio)? The way I have patched it for now is to create a init script that creates a /var/run/kamailio folder and chmods it to kamailio:kamailio
Thanks everyone!
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/231
These warnings should be eliminated in order to make compilation readable:
CC (gcc) [M tls.so] tls_locking.o
tls_locking.c:98:13: warning: 'locking_f' defined but not used [-Wunused-function]
static void locking_f(int mode, int n, const char* file, int line)
^~~~~~~~~
tls_locking.c:83:13: warning: 'dyn_destroy_f' defined but not used [-Wunused-function]
static void dyn_destroy_f(struct CRYPTO_dynlock_value *l,
^~~~~~~~~~~~~
tls_locking.c:65:13: warning: 'dyn_lock_f' defined but not used [-Wunused-function]
static void dyn_lock_f(int mode, struct CRYPTO_dynlock_value* l,
^~~~~~~~~~
tls_locking.c:42:37: warning: 'dyn_create_f' defined but not used [-Wunused-function]
static struct CRYPTO_dynlock_value* dyn_create_f(const char* file, int line)
^~~~~~~~~~~~
CC (gcc) [M tls.so] tls_init.o
tls_init.c: In function 'init_ssl_methods':
tls_init.c:377:2: warning: 'TLSv1_client_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_cli - 1] = TLSv1_client_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1598:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_client_method(void)) /* TLSv1.0 */
^
tls_init.c:378:2: warning: 'TLSv1_server_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_srv - 1] = TLSv1_server_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1597:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_server_method(void)) /* TLSv1.0 */
^
tls_init.c:379:2: warning: 'TLSv1_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1 - 1] = TLSv1_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1596:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_method(void)) /* TLSv1.0 */
^
tls_init.c:382:2: warning: 'TLSv1_1_client_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_1_cli - 1] = TLSv1_1_client_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1604:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_client_method(void)) /* TLSv1.1 */
^
tls_init.c:383:2: warning: 'TLSv1_1_server_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_1_srv - 1] = TLSv1_1_server_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1603:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_server_method(void)) /* TLSv1.1 */
^
tls_init.c:384:2: warning: 'TLSv1_1_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_1 - 1] = TLSv1_1_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1602:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_method(void)) /* TLSv1.1 */
^
tls_init.c:388:2: warning: 'TLSv1_2_client_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_2_cli - 1] = TLSv1_2_client_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1610:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_client_method(void)) /* TLSv1.2 */
^
tls_init.c:389:2: warning: 'TLSv1_2_server_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_2_srv - 1] = TLSv1_2_server_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1609:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_server_method(void)) /* TLSv1.2 */
^
tls_init.c:390:2: warning: 'TLSv1_2_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_2 - 1] = TLSv1_2_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1608:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_method(void)) /* TLSv1.2 */
^
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1075
Kamailio 5 did not compile on solaris 11 anymore due to a missing ast/endian.h included from app_jsdt/duk_config.h. The solution is:
--- kamailio-5.0.1~/src/modules/app_jsdt/duk_config.h 2017-04-05 15:32:38.000000000 +0000
+++ kamailio-5.0.1/src/modules/app_jsdt/duk_config.h 2017-04-15 09:27:14.335213048 +0000
@@ -607,7 +607,7 @@
#define DUK_USE_DATE_FMT_STRFTIME
#include <sys/types.h>
-#include <ast/endian.h>
+#include <sys/byteorder.h>
#include <sys/param.h>
#include <sys/time.h>
#include <time.h>
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1072
The new keepalive module states that it "performs destinations monitoring either for itself, or on the behalf of other modules".
What does that mean?
What are the use cases and which problems does it solve?
Which mechanisms does it use (SIP, ICMP, others?)
Some examples would greatly help in the README to get some context on how to actually use this module.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1082