@linuxmaniac so it's okay to have this in log file?
--
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/1189#issuecomment-367384899___
@lgg that has noting to do with this issue. This is about a crash on stop.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@miconda i thinks i still have this issue.
``
kamctl version
/usr/sbin/kamctl 5.0.0
```
```
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
```
Installed ssl libs:
```
root@serv:~# apt list --installed | grep ssl
WARNING: apt does not
@apogrebennyk - pushed to 4.4 branch.
@taurus-forever - thanks, I didn't know they are in a separate apt repo.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thanks @miconda, would you backport this also to the 4.4 branch?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1189.
--
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/1189#event-1189055685___
Kamailio (SER) - Development Mailing List
Should be fixed by the commit referenced above. Pushed in 5.0 branch as well.
Reopen if still an issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It seems to core dump at shut down even with a very basic config and no sip
traffic (just start and then stop):
```
debug=2
log_stderror=no
memdbg=5
memlog=5
log_facility=LOG_LOCAL0
children=1
enable_tls=yes
loadmodule "tls.so"
modparam("tls", "config", "/tmp/kamailio-dev/etc/kamailio/tls.cfg")
@joelsdc after looking closer this morning, yes in my case I do subjectively
think #1172 might be related. I did have an occurrence of Kamailio stopping
processing traffic. In my case these were incoming MESSAGE requests. I don't
have further details as I'm now at work. This is Fedora 26,
@miconda yes, it crashes every time on stop.
--
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/1189#issuecomment-319378919___
Kamailio
Does it happen every time when stopping kamailio?
I guess I have to try to reproduce it in order to dig in more.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I think I may be seeing the same thing on Fedora 26,
openssl-1.1.0f-7.fc26.x86_64, and Kamailio 5.0 branch @ 2d1dc7c
```
Core was generated by `/usr/sbin/kamailio -m 256 -M 8 -P
/run/kamailio/kamailio.pid'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 ossl_init_thread_stop
I'm going to try with the last version of branch 1.1.0
--
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/1189#issuecomment-318005177___
```
Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/lb/kamailio.cfg -P
/var/run/kamailio/kamail'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 ossl_init_thread_stop (locals=0x7f8d615fcd58) at ../crypto/init.c:335
warning: Source file is more recent than executable.
And the rest from my previous comment?
--
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/1189#issuecomment-318004761___
Kamailio (SER) -
just that patch
--
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/1189#issuecomment-318001713___
Kamailio (SER) - Development Mailing List
Btw, did you just use that patch or recompiled all from latest branch 1.1.0 for
openssl?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Can you give the new backtrace to match against the source code? Also, provide
`info locals` and `list` from frame 0.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
FTR, tried with openssl/openssl@4b4bc00 applied same core
--
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/1189#issuecomment-317981985___
The issue on openssl rt seems to be from 2007:
```
Created: | Thu Feb 22 09:48:25 2007
```
Not sure why it was dealt with in 2016. But I think is not relevant here at all.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So there seems to be some fixes in branch 1.1.0 after release of 1.1.0f, your
code is no longer matching their git branch.
Their new patch might be related, so maybe you can recompile the latest libssl
from their 1.1.0 stable branch.
Otherwise, although not really familiar with libssl
This is what I have
```
static struct thread_local_inits_st *ossl_init_get_thread_local(int alloc)
{
struct thread_local_inits_st *local =
CRYPTO_THREAD_get_local();
if (local == NULL && alloc) {
local = OPENSSL_zalloc(sizeof *local);
CRYPTO_THREAD_set_local(,
The link from previous comment goes to a page asking for authentication.
The crash happens inside exit() function, due to a callback registered by
libssl.
Can you check if the version of the libssl you run has the next patch from
about 1 month ago:
*
downloaded openssl source
```
#0 ossl_init_thread_stop (locals=0x7faaf4442d58) at ../crypto/init.c:332
332 if (locals->async) {
(gdb) p locals
$1 = (struct thread_local_inits_st *) 0x7faaf4442d58
(gdb) p *locals
Cannot access memory at address 0x7faaf4442d58
```
--
You are receiving
FTR https://rt.openssl.org/Ticket/Display.html?id=1491 has been closed with
> This is reported against 0.9.8; please open a new ticket if still a problem
> with current releases.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
backporting [0] and [1] didn't help
[0]
https://github.com/kamailio/kamailio/commit/e7c03ce6ce61119fbf5cb9f41b7abcd4c7138d58
[1]
https://github.com/kamailio/kamailio/commit/76efc9b7a1489007f9ff431e730ce4e86b446a6c
--
You are receiving this because you are subscribed to this thread.
Reply to
### Description
We are having cores when stopping the lb service if TLS is enabled.
### Troubleshooting
Debugging Data
```
Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/lb/kamailio.cfg -P
/var/run/kamailio/kamail'.
Program terminated with signal SIGSEGV, Segmentation fault.
27 matches
Mail list logo
