@jmordica: ok, I understand. I just pushed a commit to fix the originally
reported issue, related to db initialization for dmq worker.
The second one does not seem related, therefore I think it is better to open a
new issue for that case, when you are going to catch it again. I am closing
this
Closed #2642.
--
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/2642#event-4451016703___
Kamailio (SER) - Development Mailing List
Actually since this was on a production machine and the issue relies on lots of
subscription traffic I haven’t had time to reproduce it outside of a production
environment. In order to let it crash id have to put the traffic back on the
kamailio node and let it crash. I’ll have to pick a night
Were you able to get a core dump and full backtrace?
--
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/2642#issuecomment-794146349___
Yes, get the core dump file and then grab the output of `bt full` with gdb.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So I was kind of wrong here. Kamailio runs ok with memory-only presence as long
as there are only a handful of subscriptions happening. I noticed that running
memory-only presence with `modparam("presence", "enable_dmq", 0)` kamailio will
not complain about the originally posted issue but will
Commenting out `modparam("presence", "enable_dmq", 1)` allows the memory-only
presence module to function properly and not crash/lock.
I don't actually need the dmq to work for presence module so that's ok for me
but if you need additional testing I can try to help out.
--
You are receiving
It looks like a crash happening on shutdown, because the log message from
pres_dmq_init_proc() is preventing kamailio to start. You can try to get a core
dump, you need to start as a root and enable core dumping -- some guidelines at:
*
### Description
I've been trying the new in-memory only presence feature in 5.4.x but have run
into an issue:
```
ERROR: presence [presence_dmq.c:109]: pres_dmq_init_proc(): dmq_worker_init:
database not bound
kamailio[8404]: segfault at 0 ip 7f4f8419c4d7 sp 7ffd68ef0130 error 4
in
