The reason for storing the last registation with the subscriber is, as
Alexandr says, so it is permanent. If I have a million accounts I can
see how many have registered within the last month etc, not just how
many are online at one point.
If an event_route can be run when the contact is inser
Looks like kamailio-debuginfo rpm was from older version of kamailio. I'm not
able to reproduce core file anymore. Could somebody please be so kind and
explain why ?
Secondly:
Mar 13 18:12:57 ricvmf-fusion01 kam-scscf[13524]: WARNING: tm
[t_lookup.c:1536]: t_unref(): WARNING: script writer di
Dan,
There are two cores because of a crash in one process followed by a
crash when the other processes are trying to shutdown.
What's interesting is that the bt doesn't show useful pointers. If you
have installed from RPMs make sure the kamailio-debuginfo is from the
same build as the other
On 13 Mar 2014, at 19:51, Alexandr Dubovikov
wrote:
> maybe because after AOR's expire this information will be deleted ?
And now we have an event_route to insert something in any table at that point...
I still don't understand how it belongs to the subscriber table.
/O
>
>
>
>
>
> On Th
Carsten,
Yes, this is something I saw earlier already so this attr is in my config.
Thanks for pointing this out.
On 03/13/2014 02:45 PM, Carsten Bock wrote:
It looks a little bit like a "double free".
You could try to disable the call to "abort()" in case this happens:
mem_safety=1
See: http
Jason,
I've tried multiple combinations for pattern but I'm getting only 2 core files
...
Details:
~]# cat /proc/sys/kernel/core_pattern
/tmp/core.%e.sig%s.%p
~]# lsb_release -a
LSB Version:
:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noa
Hugh W. just recommended something there might be a little chance that core files
are being overwritten. Let me make them unique .. the pattern I'm using now is :
/tmp/core.%p which is not very "unique" apparently.
On 03/13/2014 02:58 PM, Jason Penton wrote:
I don't think these cores indi
I don't think these cores indicate the real crash... I'd like to get some
more detail on what actually happened? Daniel, can you re-create? Keep in
mind that if your core dump config on your box is not configured to name
your cores according to process id or timestamp one core will overwrite the
ot
maybe because after AOR's expire this information will be deleted ?
On Thu, Mar 13, 2014 at 6:49 PM, Olle E. Johansson wrote:
>
> On 13 Mar 2014, at 18:30, Hugh Waite wrote:
>
> Hello,
> We have added a feature to auth_db which will update the time of the last
> successful login in the subs
It looks a little bit like a "double free".
You could try to disable the call to "abort()" in case this happens:
mem_safety=1
See: http://www.kamailio.org/wiki/cookbooks/devel/core#mem_safety
Kind regards,
Carsten
2014-03-13 19:44 GMT+01:00 Carsten Bock :
> It looks a little bit like a "double f
It looks a little bit like a "double free".
You could try to disable the call to "abort()" in case this happens:
2014-03-13 17:22 GMT+01:00 Daniel Ciprus :
> There are no more core files on the filesystem :-(
>
> On 03/13/2014 12:18 PM, Jason Penton wrote:
>
> I'm afraid this is also not the cor
On 13 Mar 2014, at 18:30, Hugh Waite wrote:
> Hello,
> We have added a feature to auth_db which will update the time of the last
> successful login in the subscriber table. This gives an easy way to find the
> number of active users in the past day/week/month etc.
>
> Please send me any comm
Hello,
We have added a feature to auth_db which will update the time of the last
successful login in the subscriber table. This gives an easy way to find the
number of active users in the past day/week/month etc.
Please send me any comments on the attached patch.
There will of course be do
There are no more core files on the filesystem :-(
On 03/13/2014 12:18 PM, Jason Penton wrote:
I'm afraid this is also not the correct core. Can you check the timestamp on
the cores? Can you re-create the crash and send me the correct core?
On Thu, Mar 13, 2014 at 5:36 PM, Daniel Ciprus
ma
I'm afraid this is also not the correct core. Can you check the timestamp
on the cores? Can you re-create the crash and send me the correct core?
On Thu, Mar 13, 2014 at 5:36 PM, Daniel Ciprus wrote:
> So I cleaned up my junkyard and I got 2 core files:
>
> (gdb) bt
> #0 0x005350b0
One note: this is not real HW, this is virtual machine ... I hope this core is
not related to some internal clock which is not in sync with HW clocks.
On 03/13/2014 11:36 AM, Daniel Ciprus wrote:
So I cleaned up my junkyard and I got 2 core files:
(gdb) bt
#0 0x005350b0 in ?? ()
#1 0
So I cleaned up my junkyard and I got 2 core files:
(gdb) bt
#0 0x005350b0 in ?? ()
#1 0x0053542a in ?? ()
#2 0x005356c7 in timer_main ()
#3 0x0046d572 in main_loop ()
#4 0x0047030b in main ()
(gdb) bt full
#0 0x005350b0 in ?? ()
No symbol tab
Hi Daniel,
this is the wrong core file. This is the one created on shutdown of
kamailio. Can you do a bt on the other core file that you probably have...
Cheers
Jason
On Thu, Mar 13, 2014 at 5:05 PM, Daniel Ciprus wrote:
> Folks,
>
> This is happening during the registration on SCSCF.
>
> Ser
Folks,
This is happening during the registration on SCSCF.
Server:: kamailio (4.2.0-dev2 (x86_64/linux))
Build:: mi_core.c compiled on 10:01:09 Mar 13 2014 with gcc 4.4.6
Flags:: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE,
USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PK
Module: sip-router
Branch: master
Commit: 422e55d75aabf1833ad5e6b1cb069f434b9dbf99
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=422e55d75aabf1833ad5e6b1cb069f434b9dbf99
Author: Victor Seva
Committer: Victor Seva
Date: Thu Mar 13 10:41:07 2014 +0100
pkg/kamailio
Module: sip-router
Branch: 4.1
Commit: dfcaf12b49c0fefac9785306d2e57c80a6173103
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=dfcaf12b49c0fefac9785306d2e57c80a6173103
Author: Henning Westerholt
Committer: Carsten Bock
Date: Mon Feb 24 11:23:42 2014 +0100
pdb: ad
Module: sip-router
Branch: 4.1
Commit: f828bbbac1e4e4e6650c3ef5732de6189d405b14
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=f828bbbac1e4e4e6650c3ef5732de6189d405b14
Author: Henning Westerholt
Committer: Carsten Bock
Date: Mon Feb 24 11:23:17 2014 +0100
pdb: re
Module: sip-router
Branch: 4.1
Commit: 376ee52aba344bfc8c617f6290ac15df48c83fe7
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=376ee52aba344bfc8c617f6290ac15df48c83fe7
Author: Henning Westerholt
Committer: Carsten Bock
Date: Mon Feb 24 11:10:22 2014 +0100
pdb: re
Module: sip-router
Branch: 4.1
Commit: e397c90cb1cbc950b8d9166d57153f3790140f91
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e397c90cb1cbc950b8d9166d57153f3790140f91
Author: Henning Westerholt
Committer: Carsten Bock
Date: Mon Feb 24 11:22:50 2014 +0100
pdb: mo
On 12 Mar 2014, at 21:51, Daniel-Constantin Mierla wrote:
> evapi: new module to push event details via tcp to external applications
I think this is a great start - but also (based on my exprience with Asterisk
manager) complex.
Would it be beneficial to have a larger discussion about require
On 13/03/14 01:48, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
evapi: new module to push event details via tcp to external applications
from readme:
1. Overview
This module pushes event details to remote applications, via TCP.
3.1. workers (int)
Number of worker processe
Module: sip-router
Branch: master
Commit: a1de51c55d7bf31c7e9a793ec898073ab158b3cf
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a1de51c55d7bf31c7e9a793ec898073ab158b3cf
Author: Victor Seva
Committer: Victor Seva
Date: Thu Mar 13 00:14:47 2014 +0100
pkg/kamailio
Module: sip-router
Branch: master
Commit: da2e3d712c1025b02df6a047ba06b8d8d7d8c80a
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=da2e3d712c1025b02df6a047ba06b8d8d7d8c80a
Author: Jason Penton
Committer: Jason Penton
Date: Thu Mar 13 10:08:07 2014 +0200
modules/im
28 matches
Mail list logo
