Reopen if still crashing with mongo c driver without ssl.
---
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/619#issuecomment-224084037___
Closed #619.
---
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/619#event-683440339___
sr-dev mailing list
sr-dev@lists.sip-router.org
It seems to still be a conflict of openssl lib initializer -- kamailio does it
and then mongo c driver messes it somehow. I would need to dig into mongo c
driver code, but that can take a while.
I compiled mongo c driver 1.3.5 (latest stable version) without ssl support and
all seems to run
upgrade of mongo c driver did not work. I recompiled kamailio too.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
No I am not there. do you want me to join it.
---
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/619#issuecomment-222443587___
sr-dev
hello did you get chance to look into the config
---
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/619#issuecomment-222441936___
sr-dev
> hello @miconda i have shared the credentials on your gmail id please have a
> look into it
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> hello, where can i share the ssh credentials with you
---
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/619#issuecomment-222061827___
The slots field has invalid pointer value, so I suspect a buffer overflow
somewhere, but not revealed by the logs. Could be in the nat_travesal, which I
expect not much used as I know lots using nathelper instead.
Would require investigating in more deep the core files, longs and eventually
> any update
---
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/619#issuecomment-221836086___
sr-dev mailing list
@WhoSunilMore please, again, use the format to insert a quote!
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Here is the output of the above commands.,
(gdb) p nat_table
$1 = (HashTable *) 0x7f26028d7bc8
(gdb) p *nat_table
$2 = {slots = 0x7f26, size = 512}
(gdb)
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So the slot is not a valid pinter. Can you print in the same frame 2:
```
p nat_table
p *nat_table
```
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
the output of the commands is as below
(gdb) frame 2
#2 0x7f25fec371e7 in keepalive_timer (ticks=65354259, data=0x0) at
nat_traversal.c:1597
1597lock_get(>lock);
(gdb) info locals
iteration = 0
contact = 0x0
slot = 0x7f26
now = 1463548257
i = 0
(gdb) p *slot
Cannot
Can you go with in the frame 2 of the core that has:
```
#2 0x7f25fec371e7 in keepalive_timer (ticks=65354259, data=0x0) at
nat_traversal.c:1597
```
Then do the following gdb commands:
```
frame 2
info locals
p *slot
```
---
You are receiving this because you are subscribed to this
hey guys .. any update
---
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/619#issuecomment-221164836___
sr-dev mailing list
Hi,
for the latest test , i was able to get three core files and the output of each
in gdb is as follows
(gdb) bt
#0 0x7f25fec37648 in save_keepalive_state () at nat_traversal.c:1639
#1 0x7f25fec3b5ef in mod_destroy () at nat_traversal.c:1847
#2 0x005af3ac in destroy_modules
Hello,
I am able to reproduce this bt everytime now.
Core was generated by `/usr/local/kamailio/sbin/kamailio -f
/usr/local/kamailio/etc/kamailio/kamailio.'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f104af2a431 in atomic_cmpxchg_int (var=0x7f110007, old=0,
Yesterday was public holiday in most of Europe and next days is the Kamailio
World Conference, with many Kamailio people participating, therefore expect
lower activity on the forums.
The core you got is not the good one, because it is the shutdown procedure. You
have to enable one core file
hey guys any update over the last post
---
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/619#issuecomment-219353697___
sr-dev mailing
tried using '-x qm' kamailio was not up for some reason.
however changed debug level to 3 and found the following logs at crash.
siputils [checks.c:97]: has_totag(): no totag
DEBUG: tmx [tmx_pretran.c:357]: tmx_check_pretran(): matched another
pre-transaction by pid 2438 for
yes i can reproduce this everytime.
removing the nat_traversal module..requires loads of changes in my cfg.
however what I have noticed is, changing the parameter "enable_tls=yes" to
"enable_tls=no" does not cause a crash. but i want to use tls as I would be
using wss.
---
You are receiving
You can reproduce it every time?
Can you try without nat_traversal module (comment its related lines)?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@linuxmaniac i am a newbie here ..please guide me about the formats
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
i reverted back the declaration of "mi_fifo".
output of commands
(gdb) info locals
cb = 0x7f09
__FUNCTION__ = "run_create_callbacks"
(gdb) p *cb
Cannot access memory at address 0x7f09
gdb trace
(gdb) bt
#0 0x7f093abdaf6d in run_create_callbacks (dlg=0x7f093f634028,
But now the frame 0 is missing the details again. Isn't the same backtace as in
your comment:
* https://github.com/kamailio/kamailio/issues/619#issuecomment-218999484
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@WhoSunilMore the markdown format is \`\`\` **not** \`\`\`c and in one line
only. Please
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The output of the commands is
```c
(gdb) info locals
No symbol table info available.
(gdb) p *cb
No symbol "cb" in current context.```
the following is gdb bt for same
```c
#0 0x in ?? ()
#1 0x7fbbf1e3ef86 in run_create_callbacks (dlg=0x7fbbf69981a8,
msg=0x7fbc17338d80)
Can you reproduce it every time?
Send the output from gdb for next commands:
```
info locals
p *cb
```
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hello,
I have changed the order i have declared the modules and just brought "mi_fifo"
to the top. The crash was however there but now frame 0 has some data.
```c
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fdf88f8af6d in run_create_callbacks (dlg=0x7fdf8d7f20e0,
I am using it for sending replies back to nated clients.
---
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/619#issuecomment-218980588___
A side note first: format the messages you add and put the code snippets as
code blocks -- see the github markdown format docs. It is easier to read and
analyse the comments.
I spotted only nat_traversal module that would register callbacks to dialog.
For what are you using it?
---
You are
Here are the load modules and their parameters
loadmodule "tm.so"
modparam("tm", "fr_timer", 1)
modparam("tm", "fr_inv_timer", 18)
modparam("tm", "disable_6xx_block", 1)
loadmodule "tmx.so"
modparam("tmx", "precheck_trans", 1)
loadmodule "sl.so"
loadmodule "tls.so"
modparam("tls",
Frame 0 is missing all the details. The crash seems to be in a module that uses
dialog module. Can you list here the loadmodule statements in your config?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hello All,
Kamailio instance just crashed with the following logs
May 13 06:05:34 P172 /usr/local/kamailio/sbin/kamailio[12693]: CRITICAL:
[pass_fd.c:275]: receive_fd(): EOF on 10
May 13 06:05:34 P172 /usr/local/kamailio/sbin/kamailio[12667]: ALERT:
[main.c:739]: handle_sigs(): child
35 matches
Mail list logo
