I try to kill -ABRT on a preproduction platform running ser0.9.9+cvs and
a coredump is generated.
The only difference I see is the system. Preproduction running on Red
Hat 4 wherease the production platform runs under Red Hat 5.
Is that can make any difference ?
Regards,
Adrien.
Le lundi 12 oc
On Oct 12, 2009 at 10:54, inge wrote:
> A command issued by the FIFO can lead to a restart of how we see in the
> logs "messages" ?
If "kill" is sent over the fifo, you will see only one of the DBG()s:
"SIGTERM received, program terminates". Note that you will see it in the
log only if debug>4, o
A command issued by the FIFO can lead to a restart of how we see in the
logs "messages" ?
Regards,
Adrien.
Le lundi 12 octobre 2009 à 10:47 +0200, Andrei Pelinescu-Onciul a
écrit :
> On Oct 12, 2009 at 09:57, inge wrote:
> > Hello Andrei,
> >
> > Thank for having replied.
> >
> > SER runs as
On Oct 12, 2009 at 09:57, inge wrote:
> Hello Andrei,
>
> Thank for having replied.
>
> SER runs as root user without anything in the config file concerning a
> "-u" option, even in a "ps aux", all the process are started without
> options.
>
> We have checked and it seems that no one shoot the
Hello Andrei,
Thank for having replied.
SER runs as root user without anything in the config file concerning a
"-u" option, even in a "ps aux", all the process are started without
options.
We have checked and it seems that no one shoot the process at the time
crash happened.
I attached to this
On Oct 09, 2009 at 20:33, inge wrote:
> Hello Andrei,
>
> We are now running to 0.9.9+cvs20090925 since 10 days.
>
> Today SER crash/stop without coredump. Do you know if we need to
> configure something for enable this option ?
No, coredump it's enabled by default since 0.9.3.
However note tha
Hello Andrei,
We are now running to 0.9.9+cvs20090925 since 10 days.
Today SER crash/stop without coredump. Do you know if we need to
configure something for enable this option ?
With the previous crash, we got in /var/log/messages something like a
CHILD which firstly crashed and then all the pr
On Sep 29, 2009 at 10:25, inge wrote:
> Hello Andrei, Henning,
>
> So we will up the PKG_MEM_POOL_SIZE to 4MB.
>
> Andrei : we have update to the lastest CVS snapshot ser-0.9.9
> +cvs20090925. Is that correct for avoid the lastest problem ?
Yes, it is.
Andrei
Hello Andrei, Henning,
So we will up the PKG_MEM_POOL_SIZE to 4MB.
Andrei : we have update to the lastest CVS snapshot ser-0.9.9
+cvs20090925. Is that correct for avoid the lastest problem ?
Thanks for your detailed answers !
Regards,
Adrien.
Le lundi 28 septembre 2009 à 20:24 +0200, Andrei P
On Sep 28, 2009 at 18:53, inge wrote:
> Hi Henning,
>
> 40MB x Number of child ? isn't it ?
It doesn't use 40 MB x number of process physical memory.
In your case it will use as much as needed to temporary load the
location table on startup, but only in _one_ process. The rest of the
processes w
On Sep 28, 2009 at 11:02, inge wrote:
> Hello Andrei,
>
> We need to wait for 0.9.9 ?
>
> Or should we just patch the current 0.9.8 to avoid the bug ?
No, just apply the patch (the same patch will be in 0.9.9).
>
> Otherwise, do you have an idea of the value we should set for
> "PKG_MEM_POOL_
On Montag, 28. September 2009, inge wrote:
> 40MB x Number of child ? isn't it ?
>
> So the parameter can be set to "40 x 1024 x 1024" ?
>
> The database contains something than 4500 users. The server runs with
> 4GB of memory.
Hi Inge,
ok, then i think that 40 MB is a bit too much for you, 10MB
Hi Henning,
40MB x Number of child ? isn't it ?
So the parameter can be set to "40 x 1024 x 1024" ?
The database contains something than 4500 users. The server runs with
4GB of memory. How many users do you have on your server ?
Regards,
Adrien
Le lundi 28 septembre 2009 à 14:32 +0200, Hennin
On Montag, 28. September 2009, inge wrote:
> [..]
> Otherwise, do you have an idea of the value we should set for
> "PKG_MEM_POOL_SIZE" and avoid a truncate of location to restart SER ?
Hi Inge,
just increase the memory pool until you can load your subscriber base. You can
use even bigger values
Hello Andrei,
We need to wait for 0.9.9 ?
Or should we just patch the current 0.9.8 to avoid the bug ?
Otherwise, do you have an idea of the value we should set for
"PKG_MEM_POOL_SIZE" and avoid a truncate of location to restart SER ?
Regards,
Adrien.
Le jeudi 24 septembre 2009 à 23:09 +02
On Sep 24, 2009 at 15:49, inge wrote:
> Hi Andrei,
>
> Thanks for the 0.9.8 release.
> We upgraded our proxy yesterday with sucess.
>
> But we had another crash of SER in this morning.
> The cause seem to be defferent than the previous one.
>
> Attached is a backtrace from the coredump.
> Is th
Hi Andrei,
Thanks for the 0.9.8 release.
We upgraded our proxy yesterday with sucess.
But we had another crash of SER in this morning.
The cause seem to be defferent than the previous one.
Attached is a backtrace from the coredump.
Is there a bug related to that in the last 0.9.x version ?
Sinc
On Sep 17, 2009 at 12:38, Andrei Pelinescu-Onciul wrote:
> On Sep 16, 2009 at 21:48, Andrei Pelinescu-Onciul wrote:
> [...]
> >
> > > This has not been modified in t_lookup.c from v0.9.7 nor v2.0 (attached)
> >
> > Yes, but the problem is not in the place where it crashes, it's somewhere
> > el
On Sep 16, 2009 at 21:48, Andrei Pelinescu-Onciul wrote:
[...]
>
> > This has not been modified in t_lookup.c from v0.9.7 nor v2.0 (attached)
>
> Yes, but the problem is not in the place where it crashes, it's somewhere
> else.
> Both 0.9.7 and 0.9.4 are very old and I don't really remember all
On Sep 16, 2009 at 16:11, inge wrote:
> Andrei,
>
> Thanks for your update on this.
> As the conditions for the bug to appear is quite erratic (seems to be
> several INVITE sent to the gateway in a row, that make it sending a "482
> Loop Detected" leading to the crashing ACK), we do not manage to
On Sep 16, 2009 at 10:47, inge wrote:
> Hi Andrei,
>
> I'm Nicolas and I'm working with Adrien on crashes experienced on our
> SER server during the last months.
>
> We had 4 crashes on 11 jun 2009, 13 aug 2009, 11 sept 2009 and 12 sept
> 2009.
> Every of this crash have a similar call flow, as
On Sep 11, 2009 at 19:01, inge wrote:
> Hi Andrei,
>
> A new crash happend today !
>
> It was impossible to restart SER. During this time I could collect logs
> from syslog by activating ser debug (ie. facility local0, etc.).
>
> The solution have consisted in flushing Location table to be able
Hi Andrei,
I'm Nicolas and I'm working with Adrien on crashes experienced on our
SER server during the last months.
We had 4 crashes on 11 jun 2009, 13 aug 2009, 11 sept 2009 and 12 sept
2009.
Every of this crash have a similar call flow, as seen in the one
attached: SER crashes when trying to pr
Hi Andrei,
A new crash happend today !
It was impossible to restart SER. During this time I could collect logs
from syslog by activating ser debug (ie. facility local0, etc.).
The solution have consisted in flushing Location table to be able to
restart SER...
I attach the gdb output and syslog
Hi Andrei,
Thank you for this detailed answer.
Indeed, update to 0.9.7 will be more easier than SER 2.0. Our priority
is to avoid a lot of bugs.
We are not able to reproduce the crash...so we'll see. Probably we will
do an update to 0.9.7.
Regards,
Adrien
Le mercredi 09 septembre 2009 à 13:
On Sep 04, 2009 at 18:06, inge wrote:
> Hello Andrei,
>
> I wonder what is involved in migration to SER 2.0 versus 0.9.5. I read
> that UID is used now to identify the users instead of username for
> example, so we can anticipate impacts on internal processes and SERWeb.
Yes, uid and did (for do
On Freitag, 4. September 2009, inge wrote:
> I wonder what is involved in migration to SER 2.0 versus 0.9.5. I read
> that UID is used now to identify the users instead of username for
> example, so we can anticipate impacts on internal processes and SERWeb.
>
> Can I find a detailed list which the
On Aug 20, 2009 at 10:40, inge wrote:
> Hi Andrei,
>
> As I understand, this changelog only apply to the tm module.
> Is there any clues that this module caused the crash we experienced ?
Yes, according to the backtrace it crashed in tm. It looks like the tag
value was corrupted (one possible ex
Hello Andrei,
I wonder what is involved in migration to SER 2.0 versus 0.9.5. I read
that UID is used now to identify the users instead of username for
example, so we can anticipate impacts on internal processes and SERWeb.
Can I find a detailed list which these changelog ?
Is it not more reason
Hi Andrei,
As I understand, this changelog only apply to the tm module.
Is there any clues that this module caused the crash we experienced ?
We would like to determine which of the known and corrected bug could
have caused the crash, in order to find a short-time workaround letting
us some time
On Aug 17, 2009 at 14:42, inge wrote:
> Hi Andrei,
>
> Hope you are fine.
> Do you have any update on our crash ?
> Is there anything we can do to find the segmentation fault cause, maybe
> as a well-known bug, without bothering you ?
There are lots of changes between 0.9.5-pre and the latest 0
Hi Andrei,
Hope you are fine.
Do you have any update on our crash ?
Is there anything we can do to find the segmentation fault cause, maybe
as a well-known bug, without bothering you ?
Sincerely,
Adrien
Le vendredi 14 août 2009 à 17:03 +0200, inge a écrit :
> Please find the requested informati
Please find the requested information in attached.
I'm aware of the need for an update. It's in the list of tasks to be
done, however, the priority is to troubleshoot the problem and maybe
find a workaround.
Regards,
Adrien
Le vendredi 14 août 2009 à 16:34 +0200, Andrei Pelinescu-Onciul a
écrit
On Aug 14, 2009 at 15:01, inge wrote:
> Hi Andrei,
>
> Thanks for your reply.
>
> I use ser 0.9.5-pre4.
>
> I don't really understand the bug you have identify, where can I find a
> description ?
Sorry, I was wrong (that bug was in RR and appears only in newer code).
Could you run gdb on the
inge schrieb:
Hi Andrei,
Thanks for your reply.
I use ser 0.9.5-pre4.
ser 0.9 is very very old.
I recommend update to never versions, e.g.
- Kamailio 1.5 (stable version of the ser-fork) or
- sip-router: development version of ser/Kamailio join
regards
klaus
I don't really understand
Hi Andrei,
Thanks for your reply.
I use ser 0.9.5-pre4.
I don't really understand the bug you have identify, where can I find a
description ?
Regards,
Adrien
Le vendredi 14 août 2009 à 14:45 +0200, Andrei Pelinescu-Onciul a
écrit :
> On Aug 13, 2009 at 15:32, inge wrote:
> > Hi Klaus,
> >
On Aug 13, 2009 at 15:32, inge wrote:
> Hi Klaus,
>
> Thanks.
>
> I put the output of gdb in attached.
>
> I hope someone can decrypt this. Thank you.
If you are using ser 2.1/latest cvs or sip-router then just update to
the latest cvs or git. It's a known fixed bug (sip router
git 6fcd5e or
Hi Klaus,
Thanks.
I put the output of gdb in attached.
I hope someone can decrypt this. Thank you.
Regards,
Adrien
Le jeudi 13 août 2009 à 13:53 +0200, Klaus Darilion a écrit :
> locate the core file (either in the working dir or /tmp or /)
> then execute:
>
> gdb /usr/local/sbin/ser /path/t
locate the core file (either in the working dir or /tmp or /)
then execute:
gdb /usr/local/sbin/ser /path/to/core
(gdb) bt
regards
klaus
inge schrieb:
Hi all,
My SER process had crashed today with the following logs
in /var/log/messages :
ser[378]: child process 418 exited by a signal 11
s
Hi all,
My SER process had crashed today with the following logs
in /var/log/messages :
ser[378]: child process 418 exited by a signal 11
ser[378]: core was generated
ser[378]: INFO: terminating due to SIGCHLD
ser[421]: INFO: signal 15 received
...
Can someone help me to determine what kind of
40 matches
Mail list logo
