ark Murawski
*Sent:* Saturday, August 19, 2023 11:04 PM
*To:* asterisk-users@lists.digium.com
*Subject:* Re: [asterisk-users] Segmentation fault
Hi Federico,
Segfaults are 100% not by design. Typically if something seg faulted,
either there is a logic bug or a component mismatch. The you should
: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Segmentation fault
Hi Federico,
Segfaults are 100% not by design. Typically if something seg faulted, either
there is a logic bug or a component mismatch. The you should definitely be able
to use more than one connection (we use
Hi Federico,
Segfaults are 100% not by design. Typically if something seg faulted,
either there is a logic bug or a component mismatch. The you should
definitely be able to use more than one connection (we use multiple
connections with postgres odbc with no issue).
If Asterisk segfaults whe
On Wed, Aug 16, 2023 at 7:48 PM Federico
wrote:
> I tested this issue with version 13 and version 18.
>
> In res_odbc.conf, if I add a second, new data source like
>
>
>
> [asterisk]
>
> enabled=yes
>
> dsn=asterisk
>
> sanitysql => select 1
>
> isolation => read_committed
>
> username=root
>
> ;
>Setting "batch=yes" in your /etc/asterisk/cdr.conf file may fix this by
moving the database interaction to separate threads away from the call.
I can certainly try this, but I believe the maria-odbc-driver is what is
running as a single thread. Its been a few months since I played with this,
I th
On 8/17/23 12:44, John Harragin wrote:
You should be able to define multiple data sources. However I'm having my
own issues. I have my dialplan accessing one maria database which is hosted
locally on the asterisk server then logging cdr with odbc adaptive which
connects to maria on a remote machi
You should be able to define multiple data sources. However I'm having my
own issues. I have my dialplan accessing one maria database which is hosted
locally on the asterisk server then logging cdr with odbc adaptive which
connects to maria on a remote machine. This works fine except when the
remot
, January 19, 2016 7:38 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Segmentation Fault Asterisk 13.7.0-rc2
(libmysqlclient?)
On Monday 18 Jan 2016, Matthew Murphy wrote:
> Hi everyone,
>
> I am getting a segmentation fault (seems to occur
On Monday 18 Jan 2016, Matthew Murphy wrote:
> Hi everyone,
>
> I am getting a segmentation fault (seems to occur randomly) using Asterisk
> 13.7.0-rc2 with PJProject 2.4.5. It appears to be something that
> libmysqlclient is complaining about when doing a query in
> ps_endpoint_id_ips. We are usi
>
> Information is on the wiki[1] which details how to get a backtrace from a
> core dump which may be present. Otherwise it's unlikely that the problem can
> be located without exact details for reproducing it. If you can get a
> backtrace though you can file an issue on the issue tracker[2].
Recursive wrote:
Dear colleagues,
I just have experienced a segmentation fault with Asterisk 13.5.0 and
PJSIP 2.4.5. Both of them have been compiled on a standard Debian
Wheezy 64 bit. I did not apply any patch or alter the sources of
Asterisk or PJSIP in any way. Before compiling and installing
I see asterisk is finding res_jabber.so not compiled for your asterisk
version. As Tim just said, remove all the modules from
/usr/lib/asterisk/modules and reinstall asterisk.
[2013-01-10 14:20:10] WARNING[27062]: loader.c:804 inspect_module: Module
'res_jabber.so' was not compiled with the same c
First thing to *ALWAYS* check is if you have any Asterisk version specific
modules (Fax for Asterisk, G.729, etc). Ensure these are not loaded (noload in
modules.conf, or simply move them out of the asterisk modules dir).
Tim Nelson
Systems/Network Support
Rockbochs Inc.
(218)727-4332 x105
On 11-08-03 02:01 AM, Richard Zulu wrote:
I have used gdb so that I can perform a backtrace however the program
executes and exits without a stack thus not helpful.
Any help is appreciated!
https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
--
Paul Belanger
Digium, Inc. | Software
- "Rilawich Ango" <[EMAIL PROTECTED]> wrote:
> Segmentation fault occurs after executing the following cmd.
> Dial(SIP/[EMAIL PROTECTED]|35|Ttr)
>
> Is it a bug and how to fix it?
>
> Below is the core dump message converted by gdb.
>
> #0 0x068be1ad in realtime_peer (newpeername=0x1b3784
Adam Lovegrove wrote:
> Asterisk is crashing about once a day with segmentation fault.
>
> This is the error..
>
> /usr/sbin/safe_asterisk: line 111: 3482 Segmentation fault (core
> dumped) nice –n $PRIORITY ${ASTSBINDIR}/asterisk ${CLIARGS} ${ASTARGS}
>>&/dev/${TTY} Asterisk ended with exit st
Did you do a make && make install for add-ons BEFORE doing
so for asterisk?
If so try asterisk first and when all is installed install
add-ons.
--
I tried a make clean && make && make install for asterisk and then for
asterisk-addons but am still getting the segmentation fault on asterisk
Did you do a make && make install for add-ons BEFORE doing
so for asterisk?
If so try asterisk first and when all is installed install
add-ons.
--
I tried a make clean && make && make install for asterisk and then for
asterisk-addons but am still getting the segmentation fault on asterisk
st
On 16:04, Sun 24 Sep 06, kjcsb wrote:
> When Asterisk starts I get a Segmentation fault
> /usr/sbin/safe_asterisk: line 40: 30548 Segmentation fault (core
> dumped) asterisk ${CLIARGS} ${ASTARGS} >&/dev/${TTY} Asterisk ended with exit status 139
> Asterisk exited on signal 11.
>
> If I remo
I had the same problem when I did an SVN of the latest version of the
1.2 branch this past Friday (2/10) and re-made zaptel, libpri and
asterisk. I don't if someone goofed when updating the supposed stable
Asterisk 1.2 branch or what. But here's what I did to fix it...
I'm using Asterisk at H
On Mon, 13 Feb 2006 10:02:28 -0500, Patrick Fortin <[EMAIL PROTECTED]>
wrote:
Hi
Asterisk died this morning with this message
safe_asterisk: line 83: 6828 Segmentation fault (core dumped)
asterisk ${CLIARGS} ${ASTARGS} 1>&/dev/${TTY}
Any idea what is the problem ?
You should post
On Sun, 2005-02-20 at 22:59 +0100, Julius Schwartzenberg wrote:
> I'm using a pretty old system and I have good experiences with Slackware
> on other systems. Here are the specs of the system I'm using:
> IBM/Cyrix PR-200 (@150MHz), 64MB RAM, two HDs which are combined ~2GB.
Here is your troub
Thanks a lot for your message.
Race Vanderdecken schreef:
Ouch,
Do you know how to use gdb, the Gnu Debugger?
That will give you a clue as to where the segmentation fault is coming
from.
No, I once used it being instructed exactly by a developer to solve a
problem in Dosemu, but I never did anythi
OR WANNABE NEWBIES!!! (that oughta stir things up)
--
Jim Van Meggelen
[EMAIL PROTECTED]
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Andrew Kohlsmith
> Sent: Sunday, February 20, 2005 1:39 PM
> To: 'Asterisk Use
On Sun, 2005-02-20 at 13:51 -0500, Paul wrote:
> Or maybe a double fool because he also disrespected Debian GNU/Linux in
> his reply.
*And* recommended Fedora, which makes it triple. I just dumped FC3 and
replaced it with Debian because Fedora's kernels constantly gave me
issues, e.g. with prop
List - Non-Commercial Discussion'
Subject: Re: [Asterisk-Users] Segmentation fault {Writer given
gnu-lashing}
On February 20, 2005 01:11 pm, Race Vanderdecken wrote:
> 1. Why are you running on Slackware?
> Are you trying to prove a point or just enjoy being frustrated?
> Open So
Brian Capouch wrote:
Race Vanderdecken wrote:
Good, then let me move on to the insults and ranting.
1. Why are you running on Slackware? Are you trying to prove a
point or just enjoy being frustrated?
Open Source is like "Broad Spectrum Pesticide", it works but
your results may vary and yo
ch
Sent: Sunday, February 20, 2005 1:26 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Segmentation fault {Writer given
gnu-lashing}
Race Vanderdecken wrote:
> Good, then let me move on to the insults and ranting.
>
> 1. Why are you running on Sla
On February 20, 2005 01:11 pm, Race Vanderdecken wrote:
> 1. Why are you running on Slackware?
> Are you trying to prove a point or just enjoy being frustrated?
> Open Source is like "Broad Spectrum Pesticide", it works but
> your results may vary and you may end up killing your lawn.
Got a prob
Race Vanderdecken wrote:
Good, then let me move on to the insults and ranting.
1. Why are you running on Slackware?
Are you trying to prove a point or just enjoy being frustrated?
Open Source is like "Broad Spectrum Pesticide", it works but
your results may vary and you may end up killing your l
Ouch,
Do you know how to use gdb, the Gnu Debugger?
That will give you a clue as to where the segmentation fault is coming
from.
Good, then let me move on to the insults and ranting.
1. Why are you running on Slackware?
Are you trying to prove a point or just enjoy being frustrated?
- Original Message -
From: "Steven Critchfield" <[EMAIL PROTECTED]>
To: "Asterisk Users Mailing List - Non-Commercial Discussion"
Sent: Saturday, January 22, 2005 4:54 AM
Subject: Re: [Asterisk-Users] Segmentation Fault after Digitnetwork
X100Pinstall
O
On Sat, 2005-01-22 at 04:38 -0600, Rich Adamson wrote:
> > > > Shouldn't you contact your vendor for support and not a different
> > > > vendors support channel?
> > > >
> > > As far I know, although Digium hosts the asterisk-users list and
> > > supports the Asterisk development, Asterisk is stil
> > > Shouldn't you contact your vendor for support and not a different
> > > vendors support channel?
> > >
> > As far I know, although Digium hosts the asterisk-users list and
> > supports the Asterisk development, Asterisk is still a GPL open source
> > project and asterisk-list is not a Digium
On Fri, 2005-01-21 at 09:55 -0800, Asterisk List wrote:
> On Thu, 20 Jan 2005 22:41:08 -0600, Steven Critchfield
> <[EMAIL PROTECTED]> wrote:
> >
> > Shouldn't you contact your vendor for support and not a different
> > vendors support channel?
> >
> As far I know, although Digium hosts the aster
On Thu, 20 Jan 2005 22:41:08 -0600, Steven Critchfield
<[EMAIL PROTECTED]> wrote:
>
> Shouldn't you contact your vendor for support and not a different
> vendors support channel?
>
As far I know, although Digium hosts the asterisk-users list and
supports the Asterisk development, Asterisk is stil
uestion, though, Dave).
regards,
Paul
- Original Message -
From: "Steven Critchfield" <[EMAIL PROTECTED]>
To: "Asterisk Users Mailing List - Non-Commercial Discussion"
Sent: Thursday, January 20, 2005 9:41 PM
Subject: Re: [Asterisk-Users] Segmentation Fault after Dig
On Fri, 2005-01-21 at 16:57 +1300, Dave Green wrote:
> I've just installed a Digitnetworks X100P clone in my * server and run
> the install script for the voicepet-single-x100p tarball. The install
> appeared to run OK with modprobe wcfxo successful and the ztcfg
> reporting "Channel 01: FXS Kew
Henry Devito wrote:
Just download 1.0.3, don't use the voicepet scripts. they are
versions 0.7 and 0.9 of *. If it is a true clone from digit networks
it will work fine with 1.0.3. I just set up 3 different machines with
the cards from digit networks.
Henry
Yes, thanks for that. After posti
Just download 1.0.3, don't use the voicepet scripts. they are versions 0.7
and 0.9 of *. If it is a true clone from digit networks it will work fine
with 1.0.3. I just set up 3 different machines with the cards from digit
networks.
Henry
- Original Message -
From: "Dave Green" <[EM
On Thu, 2004-11-04 at 04:57 +0100, Serge wrote:
> Have anyone some idea ?
> Asterisk - latest cvs,
> RedHat9
> ==
> Asterisk Dynamic Loader Starting:
> == Parsing '/etc/asterisk/modules.conf': Found
> [chan_modem.so] => (Generic Voice Modem Driver)
>
On Tuesday 13 July 2004 08:55, [EMAIL PROTECTED] wrote:
> You missed my point. I'm talking about how it does data handling with
> various loops and memcpys etc. I don't care about the sound quality, nor do
> I care about how well written it is, I'm just making the observation based
> on my previous
On Tue, Jul 13, 2004 at 08:35:17AM -0400, Andrew Kohlsmith wrote:
> On Tuesday 13 July 2004 08:22, [EMAIL PROTECTED] wrote:
> > Ack, I don't like the iLBC code for the quick 3 minutes or so I looked at
> > it, but it wouldn't surprise me if it was overwriting more than it should
> > be on the stack
On Tuesday 13 July 2004 08:22, [EMAIL PROTECTED] wrote:
> Ack, I don't like the iLBC code for the quick 3 minutes or so I looked at
> it, but it wouldn't surprise me if it was overwriting more than it should
> be on the stack.
Why wouldn't it surprise you? I have a PRI and have 10 or 12 iLBC code
Hmm, block is allocated near the top of the stack.
Ack, I don't like the iLBC code for the quick 3 minutes or so I looked at it, but it
wouldn't surprise me if it was overwriting more than it should be on the stack.
Well, I'll hand this off to the developers / people who want to spend longer loo
On Tue, Jul 13, 2004 at 01:24:18PM +0200, Andreas 'TheChaos' Groll wrote:
> [EMAIL PROTECTED] wrote:
>
> >Start off with running ulimit -c unlimited before you start asterisk. Once
> >it crashes, type gdb /path/to/asterisk core
> >
> >>From there, enter the following:
> >
> >bt
> >x/5i $eip
>
[EMAIL PROTECTED] wrote:
Start off with running ulimit -c unlimited before you start asterisk. Once it
crashes, type gdb /path/to/asterisk core
From there, enter the following:
bt
x/5i $eip
info registers
info threads
and quit out. After doing that, you might want to save the output of
uname
>
> Ok, just removed this last module works, asterisk is starting without
> errors anymore, but I wanted to use ILBC codec so it's importan for me.
>
> Can anyone help me, getting this to work?
>
Start off with running ulimit -c unlimited before you start asterisk. Once it
crashes, type gdb /
Sorry about that:
bt gives the following output:
#0 0x401519fc in mallopt () from /lib/i686/libc.so.6
#1 0x40150c61 in malloc () from /lib/i686/libc.so.6
#2 0x40157dd0 in strdup () from /lib/i686/libc.so.6
#3 0x0805603b in cfg_process (tmp=0x80ea890,
_tmpc=0x47a6a26c, _last=0x47a6a270, buf=0x6
I am running Mandrake 9.1 if that makes a difference.
--- Patrick <[EMAIL PROTECTED]> wrote:
> On Wed, 2003-09-24 at 15:41, jerk face wrote:
> > Ok, here is the real gdb output.
> >
> > This GDB was configured as
> > "i586-mandrake-linux-gnu"...
> > Core was generated by `asterisk'.
> > Program
On Wed, 2003-09-24 at 08:41, jerk face wrote:
> Ok, here is the real gdb output.
>
> This GDB was configured as
> "i586-mandrake-linux-gnu"...
> Core was generated by `asterisk'.
> Program terminated with signal 11, Segmentation fault.
> ...
> ...
> ...
>
> Loaded symbols for
> /usr/lib/asterisk/
On Wed, 2003-09-24 at 15:41, jerk face wrote:
> Ok, here is the real gdb output.
>
> This GDB was configured as
> "i586-mandrake-linux-gnu"...
> Core was generated by `asterisk'.
> Program terminated with signal 11, Segmentation fault.
> ...
> ...
> ...
>
> Loaded symbols for
> /usr/lib/asterisk/
Ok, here is the real gdb output.
This GDB was configured as
"i586-mandrake-linux-gnu"...
Core was generated by `asterisk'.
Program terminated with signal 11, Segmentation fault.
...
...
...
Loaded symbols for
/usr/lib/asterisk/modules/cdr_csv.so
Reading symbols from
/usr/lib/asterisk/modules/app_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 23 September 2003 19:04, jerk face wrote:
> I keep getting segmentation faults when I do a reload.
Do what Critchfield and Pycko told you to do, but I'm betting you're using
chan_h323 with a gatekeeper (it's a known bug I think). That's wh
On Tue, 2003-09-23 at 12:04, jerk face wrote:
> I keep getting segmentation faults when I do a reload.
>
> Here are the core file outputs from gdb:
> (I have three of them and they produce the same
> output)
>
> (gdb) core core.6044
you need to run gdb like follows
gdb core.6044 `which asterisk`
actually
gdb /usr/sbin/asterisk core.6044, sorry
On Tue, 23 Sep 2003, jerk face wrote:
> I keep getting segmentation faults when I do a reload.
>
> Here are the core file outputs from gdb:
> (I have three of them and they produce the same
> output)
>
> (gdb) core core.6044
> Core was generated b
gdb /usr/src/asterisk core.6044
then 'bt'
Martin
On Tue, 23 Sep 2003, jerk face wrote:
> I keep getting segmentation faults when I do a reload.
>
> Here are the core file outputs from gdb:
> (I have three of them and they produce the same
> output)
>
> (gdb) core core.6044
> Core was generated
o: '[EMAIL PROTECTED]'
Subject: RE: [Asterisk-Users] Segmentation fault due to SIP registration
NUMBER 2
Hello,
Don't know if this is related but I just got a segmentation fault today
while trying to register my new SNOM200 phone:
*CLI>
*CLI> NOTICE[1125329600]: File chan_s
iled for
'10.10.10.14'
Any idea what causes this? could I have possibly just configured the Snom
incorrectly to cause this?
Thanks,
MATT---
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 4:01 PM
To: [EMAIL PROTECTED]
IL PROTECTED]
Subject: RE: [Asterisk-Users] Segmentation fault due to SIP registration
NUMBER 2
Tim, thanks for your answer.
I tried, all of the options you suggested, and still the same... *
hangs. It is interesting that it does the same think, when it tries to
register my FWD account and there are no
with no major problems.
Any other suggestions?
Senad
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: 11 September 2003 20:14
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] Segmentation fault due to SIP registration
NUMBER 2
I
I assume that from your previous post that you are using iconnect
Is your register line in the format:
Register => 18005551212:[EMAIL PROTECTED]/18005551212
I've had good luck using the IP address vs. the fully qualified
hostname. Remember that the register line goes in the [general] section
of
arrr, errr
try Dial(phone/phone0|5)
the quicknet card is definately NOT a zap device
On Mon, 4 Aug 2003 17:29:55 -0500 (CDT), [EMAIL PROTECTED] wrote:
>When i make a call from x100p to quicknet
>
>-- Executing Dial("Zap/1-1", "Phone/phone0|5") in new stack
>Segmentation fault
>
>
>extension
It's OK.
I change my oh323.conf file and I don't have segmantation fault anymore.
Thanks
Rattana
- Original Message -
From: "Rattana BIV" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 01, 2003 3:42 PM
Subject: Re: [Asterisk-Users] segm
you think ?
(you can see my oh323.conf in attach file)
Rattana
- Original Message -
From: "Michael Manousos" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 01, 2003 3:07 PM
Subject: Re: [Asterisk-Users] segmentation fault with asterisk and OH3
Rattana BIV wrote:
Hi,
I got a segmantation fault When I call to computer (h323) from phone.
I use asterisk-oh323 0.5.4 and chan_capi.0.2.2 drivers.
More info (config files, screen log, backtrace of core file) is needed.
Someone know where the problem ?
Regards
Rattana
Michael.
That is another problem I hope the developers would pay attention to.
ulaw codec segfaulting when it is used by h323 side of connection for
both incoming and outgoing calls. At least with chan_oh323.
If I set alaw codec for h323 it works fine regardless of codec on SIP
side.
Michael
On Thursda
Michael Ulitskiy wrote:
Hi,
I'm trying to interconnect sip and h323 endpoints using asterisk
and asterisk crashes with segmentation fault whenever h323
connection needs to be established. It registers with gatekeeper ok though.
Here are the symptoms.
If the call initiated by SIP device, asterisk
: Mark Thompson [mailto:[EMAIL PROTECTED]
Sent: 17 July 2003 13:07
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] Segmentation fault with chan_oh323
This also happened to me when I was using the same codec with both oh323
and SIP, if I forced it to alaw on oh323 and ulaw on SIP the connection
This also happened to me when I was using the same codec with both oh323
and SIP, if I forced it to alaw on oh323 and ulaw on SIP the connection
worked. I also tried h323 instead of oh323 which works okay but you have
to use earlier versions of pwlib and openh323.
Mark
-Original Message-
F
Can you run with valgrind instead so we can find the true source? install
asterisk with "make valgrind" and then run:
valgrind --attach-gdb=yes ./asterisk -vvvg
and then "asterisk -rx reload" and see where it tries to make you attach.
Talk to Martin for more info ([EMAIL PROTECTED]) next week if
I'd valgrind asterisk or just start by removing everything else
other than e.g. one interface definition in extensions.conf:
[channels]
signalling=...
channel => a-b
Martin
On Fri, 13 Jun 2003, Derek Beaumont wrote:
> I am still getting a segmentation fault when I try to reload asterisk
>
> Her
Check the line 118 of extensions.conf ???
Martin
On Thu, 12 Jun 2003, Derek Beaumont wrote:
> Whenever I issue the reload command, asterisk crashes. Below is the
> output I get from
> (gdb) bt
>
> Any help is appreciated.
>
> ***
> *CL
_sip.c:3928
> #6 0x4003ec6f in pthread_start_thread (arg=0x42c1bbe0) at manager.c:284
> (gdb)
>
>
>
>
>
> -Original Message-
> From: Martin Pycko [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 11:38 AM
> To: '[EMAIL PROTECTED]'
> S
You can run Asterisk with -vvvgc to force it do dump core. Run gdb on the
core and contact me off-list, or find me on IRC.
Mark
On Wed, 2 Apr 2003, Alex Zarubin wrote:
> Configuration:
> Linux wpbx 2.4.9-13 #1 Tue Oct 30 20:11:04 EST 2001 i686 unknown
> P4 2.5 GHz, 1 GB RAM
> T400P with 3 T1s p
Title: RE: [Asterisk-Users] segmentation fault
OK, here it is. On a flow of shorter calls it lasted about an hour.
[EMAIL PROTECTED] asterisk]# gdb asterisk core.12348
GNU gdb Red Hat Linux 7.x (5.0rh-15) (MI_OUT)
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered
asterisk -vvvcg (use g option to generate the coredump file)
than gdb asterisk core.pid
bt
Also you might send a log of "pri intense debug span "
regards
Martin
On Wed, 2 Apr 2003, Alex Zarubin wrote:
> Configuration:
> Linux wpbx 2.4.9-13 #1 Tue Oct 30 20:11:04 EST 2001 i686 unknown
> P4 2.5 G
77 matches
Mail list logo