Hi Dragomir,
Thanks for the report, but please open a ticket (if not already)
reporting the crash.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 03/26/2018 02
Hello,
I use stable LTS:
version: opensips 2.2.6 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epo
Is there updates on this?
Date: Mon, 16 Jan 2017 09:51:13 -0500
> From: Ahmed Munir
> To: OpenSIPs Users
> Subject: Re: [OpenSIPS-Users] OpenSIPs crashed
> Message-ID:
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> See det
)
P_MEMORY=32
Let me know any other info needed from my end.
Date: Mon, 16 Jan 2017 10:49:37 +0200
> From: Răzvan Crainea
> To: users@lists.opensips.org
> Subject: Re: [OpenSIPS-Users] OpenSIPs crashed
> Message-ID: <1584806e-a154-a5ad-a464-4eef60915...@opensips.org>
> Con
To: users@lists.opensips.org <mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] OpenSIPs crashed
Message-ID: <40f6dada-e121-a2da-b283-69dff891c...@opensips.org
<mailto:40f6dada-e121-a2da-b283-69dff891c...@opensips.org>>
Content-Type: text/plain; ch
my $var(res) db
query, opensips service starts successfully.
Please advise the steps do I need to take to fix above issues.
> From: Răzvan Crainea
> To: users@lists.opensips.org
> Subject: Re: [OpenSIPS-Users] OpenSIPs crashed
> Message-ID: <40f6dada-e121-a2da-b283-69dff891c...@o
ensips for quite a while didn't faced this
kind of issue and there is no changes made on opensips routing script.
From: Răzvan Crainea mailto:raz...@opensips.org>>
To: users@lists.opensips.org <mailto:users@lists.opensips.org>
Subject: Re
here
> a way to backtrace the issue as don't have the core dump? Further added,
> did someone faced this similar issue(s) in past and got this fixed without
> upgrade?
>
> Note: we are running opensips for quite a while didn't faced this kind of
> issue and ther
ast and got this fixed without
upgrade?
Note: we are running opensips for quite a while didn't faced this kind of
issue and there is no changes made on opensips routing script.
> From: Răzvan Crainea
>> To: users@lists.opensips.org
>> Subject: Re: [OpenSIPS-Users] OpenSIPs
The version currently running is 1.6.3. Will try to enable core dump and
share the info if run into the issues again.
From: Răzvan Crainea
> To: users@lists.opensips.org
> Subject: Re: [OpenSIPS-Users] OpenSIPs crashed
> Message-ID: <2b35e2dc-6e11-1787-b87e-33bd29a32...@opensips.or
Hi, Ahmed!
Make sure OpenSIPS is run as root and it is allowed to write in the
/var/spool/abrt/ directory, otherwise it is unable to write the core
dump, therefore we can't inspect it to say what is happening. If this
does not work, make OpenSIPS write the core dump in a writeble directory
by
Hi,
Our OpenSIPs service crashed with below error;
Jan 11 12:16:19 QORBLPSIPROXY05 abrtd: Directory
'ccpp-2017-01-11-12:16:19-2807' creation detected
Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Saved core dump of pid 2807
(/usr/sbin/opensips) to /var/spool/abrt/ccpp-2017-01-11-12:16:19-2807
(702
Hello all,
Just for the sake of completion, the memory leak was identified and
fixed by Liviu . See:
https://github.com/OpenSIPS/opensips/commit/e5ccde131eb72debd9aa400ced2e1e31bd61612d
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 10.09.201
I've modified my init.d file with
/usr/local/sbin/opensips -P /var/run/opensips/opensips.pid *-m 256 -M 8* -u
opensips -g opensips -f /usr/local/etc/opensips/opensips.cfg
wait and see ;)
2014-09-16 15:12 GMT+02:00 Mickael Hubert :
> Hi all,
>
> after upgrade Opensips, I've faced same memory err
Hi all,
after upgrade Opensips, I've faced same memory error (see below).
Have you a help for me please ?
Thanks in advance
Sep 16 15:05:23 asbc2 /usr/local/sbin/opensips[15783]:
ERROR:core:build_res_buf_from_sip_req: out of pkg memory; needs 395
Sep 16 15:05:23 asbc2 /usr/local/sbin/opensips[1
Hi Kevin,
Any chance to get the mem dump after "waiting" ?
Thanks & Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04.09.2014 13:09, Kevin Mathy wrote:
Hi Bogdan,
So, I've faced the problem once again, and followed the "Determining
the cause
Ok thanks for your response,
I'll have upgrade my opensips immediately.
but for me, my memory conf is wrong.
-m 64 -M 4 with 20 childrens: 4Mo * 20 childrens = 80 Mo shared memory, but
with -m option with 64Mo it's impossible no ?
thanks
2014-09-10 13:27 GMT+02:00 Vlad Paiu :
> Hello,
>
> Can
Hello,
Can you please upgrade to the latest 1.11 from GIT ?
There has been a fix related to this on GIT starting from
https://github.com/OpenSIPS/opensips/commit/ea9191b6993a36b6190eb218f318d0a876421311
Best Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 10.09.201
Hi Bogdan,
in addition, we use these options: "-m 64 -M 4" and in opensips.cfg
"children=20"
private memory: 4 Mo
Share memory: 64Mo
We use a server with 16Go of ram
it's good conf ?
Thanks a lot for your help.
2014-09-10 11:44 GMT+02:00 Kevin Mathy :
> Hi Bogdan,
>
> Here's the version of
Hi Bogdan,
Here's the version of opensips we use :
> [root@asbc2b kemathy]# /usr/local/sbin/opensips -V
> version: opensips 1.11.2-notls (x86_64/linux)
> flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
> SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
> ADAPTI
Kevin,
This is stranger as nothing in the dump points to a leak/issue - do you
get the out of mem error during a SB query ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 10.09.2014 09:53, Kevin Mathy wrote:
Hi Bogdan,
Got the same errors on
Hi Kevin,
First just checking if:
- the "out of mem" was reported for pkg memory (and not for shm)
- you sent the SIGUSR1 signal to the process complaining about lack
of mem
IF you look at the dump:
used= 1630504, used+overhead=4188560, free=5744
but there are only 64 fragments with av
Hi Bogdan,
Got the same errors on my second opensips server (second node of the
cluster). Here is the memdump :
https://www.dropbox.com/s/d2gacgrxik3xs1t/memdump_server2_1.txt?dl=0
Thanks for your help,
Kevin
*Bien cordialement, Best Regards, **Kevin MATHY* | Ingénieur VoIP
2014-09-09 14:5
Hi Bogdan,
I've got now a memdump !
https://www.dropbox.com/s/5hb678r0ym9vtt1/memdump1.txt?dl=0
And if you need the list of the opensips processes running at the moment :
https://www.dropbox.com/s/hqurr3ilamc0a0g/opensips_processes_list.txt?dl=0
I hope it'll be ok... If you need more things, I d
Hi Kevin,
yes, that's the right way of getting a mem dump during runtime. Also you
will automatically get one during the shutdown procedure.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 08.09.2014 10:02, Kevin Mathy wrote:
Hi Bogdan,
Hi Bogdan,
Unfortunately, no... I'll try to get that next time it'll happen ! I can do
that with "kill -SIGUSR1 OPENSIPS_PID", that's right ?
Thanks,
*Bien cordialement, Best Regards, **Kevin MATHY* | Ingénieur VoIP
2014-09-04 20:10 GMT+02:00 Bogdan-Andrei Iancu :
> Hi Kevin,
>
> Any chanc
Hi Bogdan,
So, I've faced the problem once again, and followed the "Determining the
cause" part of the link you gave me.
I've waited more than 20 minutes (near an hour), and re-sent some voice
trafic to the problematic opensips server : memory errors just came after
that.
So, I think it's a memor
Hi Bogdan,
Coming back to you after some holidays, and unfortunately, new Opensips
crashes...
Some weeks ago, we upgraded our servers to OpenSIPS 1.11, but we faced a
new crash, always with the "out of pkg memory" error, last week.
Here is the exact version :
> root@asbc2:/home/kemathy# opensips
Hi Kevin,
So it is more a mem leak than a crash. Any chances to get a memdump
after memory is exhausted ? See:
http://www.opensips.org/Documentation/TroubleShooting-OutOfMem
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 20.08.2014 15:35, Kev
Hi Bogdan,
In fact, opensips didn't crashed : we got the previous error messages in
the logs, but then we switched our voice traffic to another server, and
opensips on the 1st one never crashed... We restarted the service in the
following night, to be sure to make it rework well.
So, is there a w
Hi Kevin,
Try to extract at least a backtrace, to see what kind of problem we are
facing. Then we can decide if a mem dump is required or not.
Thanks,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 19.08.2014 12:03, Kevin Mathy wrote:
Hi Bogdan,
Com
Hi Bogdan,
Coming back to you after some holidays, and unfortunately, new Opensips
crashes...
Some weeks ago, we upgraded our servers to OpenSIPS 1.11, but we faced a
new crash, always with the "out of pkg memory" error, last week.
Here is the exact version :
> root@asbc2:/home/kemathy# opensips
Hi Kevin,
Indeed, it looks compiled ok now (with the memory debugger). Keep in
mind to set (in this order):
mem_log=4
mem_dump=1
to avoid runtime logs, but to get the mem dumps.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04.07.201
Hi Bogdan,
We've recompiled OpenSIPS with requested modules (I think) :
> root@asbc2:/home/kemathy# opensips -V
> version: opensips 1.9.2-notls (x86_64/linux)
> flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
> SHM_MMAP, PKG_MALLOC, *DBG_QM_MALLOC*, FAST_LOCK-ADAPTIVE_WAIT
Hi Bogdan,
Hummm, right, opensips doesn't seem to have been compiled with the
requested modules for memory debugging...
root@asbc2:/home/kemathy# opensips -V
> version: opensips 1.9.2-notls (x86_64/linux)
> flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
> SHM_MMAP, PKG_MA
Hi Kevin,
Unfortunately the logs are not correct - are you sure you properly
compiled the mem debug ? like adding the QM_DBG_MALLOC and removing the
FM_MALLOC flags ? As the logs show the standard memory manager (without
debugging).
Check it with "opensips -V" to see the list of compiled flag
Hi Bogdan,
Ooops, I thought my two first mails have been cancelled :-)
I prefer waiting till there's no traffic, so I'll send a SIGUSR1 comme this
evening, and reply to this topic with the log.
I'll try working with MI statistics to make some memory usage graphs better
than with Cacti...
I'll co
Hi Kevin,
There is no need to send your email three times ;). One time is enough.
Waiting and taking the dump when there is not traffic is good (but not a
must) - the idea is to be sure that all temporary memory (used for
processing the current traffic) was freed - so what you still have in
m
Hi Bogdan,
If I want to send a SIGUSR1, may I have to wait 20 minutes after the last
call ? 20 minutes without any call ? I don't understand well this sentence :
> It is highly recommended to do this after waiting about 20 minutes to be
> sure that as much as possile memory is freed - all tempor
Hi Kevin,
There is no need to wait for a crash. From time to time, you can send a
SIGUSR1 to a worker process (or a process you suspect as running out of
pkg mem) -> the process will do a pkg dump to the log.
Also, I would strongly advice upgrading to 1.11 (latest LTS) - 1.9 is no
longer mai
Hi Bogdan,
I've set given options, and now I'm waiting for a new crash of the
service... Where the memdump will be located ? In another logfile than
opensips.log, or in the same ?
Thanks
*Bien cordialement, Best Regards, **Kevin MATHY* | Ingénieur VoIP
2014-06-26 18:32 GMT+02:00 Bogdan-Andr
Kevin,
Restarting should not make you loose ongoing calls (even if you use the
dialog module), do do not worry on that.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 26.06.2014 18:31, Kevin Mathy wrote:
Yes, I'll set those options, and wait
Yes, I'll set those options, and wait 'till the trafic on the server
reduces a lot (tonight I think) to restart opensips.
Unless if you have another method to reload the config without losing calls
?
Thanks a lot,
*Bien cordialement, Best Regards, **Kevin MATHY* | Ingénieur VoIP
2014-06-26
Kevin,
The trick is to set (in this order):
memlog = 4
memdump = 1
This will do no logging at runtime, but it will log the mem dump (at
shutdown or at signal).
Could you try that ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 26.0
Hi Bogdan,
We already have compiled opensips as described, and set memlog=1 in the
configuration file.
But as we had a lot of debug messages about memory usage, we unset memlog=1
in the config, so we don't have any report now.
Is there a way to get those messages in a different log file, instead o
Hi Kevin,
For debugging potential mem leaks, please look into:
http://www.opensips.org/Documentation/TroubleShooting-OutOfMem
If you need help with that, let me know.
Also, cacti is monitoring the system memory which is irrelevant for
OpenSIPS (as OpenSIPS is pre-allocating - from OS - all the
Hi List,
I'm facing a memory usage issue with OpenSIPS 1.9.2 on a Debian 7 server
root@asbc2:/home/kemathy# uname -a
> Linux asbc2 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
>
> root@asbc2:/home/kemathy# opensips -V
version: opensips 1.9.2-notls (x86_64/linux)
> flags: STATS:
Hi Neo,
Can you reproduce the crash ? it looks to happen when you do a CANCEL .
Regards,
Bogdan
Neo Anderson wrote:
> Hi,
>
> Right now I am using OpenSIPS 1.5.3 no-tls version in production.
> Suddenly OpenSIPS got crashed.
> I did check coredump but can not understand it.
> Please help me out
Hi,
Right now I am using OpenSIPS 1.5.3 no-tls version in production.
Suddenly OpenSIPS got crashed.
I did check coredump but can not understand it.
Please help me out to interpret it.
Here is the pastebin link which contains output of bt.
http://pastebin.com/m49520853
Thanks in advance!!!
--
Vo
Carlo Dimaggio wrote:
>
> Il giorno 15/apr/09, alle ore 15:05, Bogdan-Andrei Iancu ha scritto:
>
>> hmmm...
>>
>> how did you do the upgrade ? maybe you have a mixture of
>> installations between the versions
>>
>> This is what I get for the 1.5.1 SVN :
>
> I have downloaded the 1.5.1 src and
Il giorno 15/apr/09, alle ore 15:05, Bogdan-Andrei Iancu ha scritto:
> hmmm...
>
> how did you do the upgrade ? maybe you have a mixture of
> installations between the versions
>
> This is what I get for the 1.5.1 SVN :
I have downloaded the 1.5.1 src and compiled/installed with
sudo make
hmmm...
how did you do the upgrade ? maybe you have a mixture of installations
between the versions
This is what I get for the 1.5.1 SVN :
$ ./opensips -V
version: opensips 1.5.1-notls (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
SHM_MMAP, PKG_MALLO
Il giorno 15/apr/09, alle ore 13:36, Bogdan-Andrei Iancu ha scritto:
> Hi Carlo,
>
> The backtrace looks really broken.it might be a core
> overwrite.
>
> What revision on 1.5.0 are you using (do opensips -V) ? there are
> several mysql related bugs fixed since the 1.5.0 release. If y
Hi Carlo,
The backtrace looks really broken.it might be a core overwrite.
What revision on 1.5.0 are you using (do opensips -V) ? there are
several mysql related bugs fixed since the 1.5.0 release. If you have a
SVN copy, do a SVN update to get the latest fixes. Otherwise I recomand
up
Hi all,
My opensips 1.5.0 has crashed twice in the last 5 days. It had low
load (few registrations)...
In opensipsctlrc I have:
MD5="md5sum"
STORE_PLAINTEXT_PW=0
in opensips.cfg:
modparam("auth_db", "calculate_ha1", 0)
modparam("auth_db", "password_column", "ha1"
55 matches
Mail list logo
