Hi all, I got three asterisk-machines, two of them acting as proxies. On one machine (sles11sp1) i got iritating messages about not bing able to find codec's and other stuff, so i thought it might be time for an update: Stupid! I went originally from a almost working machine running: asterisk180-alsa-1.8.3.2-87.1 asterisk180-dahdi-1.8.3.2-87.1 asterisk180-1.8.3.2-87.1 asterisk180-odbc-1.8.3.2-87.1 To a machine that continuously restarts asterisk (+core dumps) running: asterisk180-alsa-1.8.4.2-90.1 asterisk180-dahdi-1.8.4.2-90.1 asterisk180-1.8.3-85.2 asterisk180-odbc-1.8.4.2-90.1 Jun 9 16:35:44 kc3004 kernel: [ 713.970342] asterisk[5122]: segfault at 7fedcb450716 ip 00007fedeff89c8a sp 00007fff4b4d5d38 error 7 in libpthread-2.11.1.so[7fedeff7f000+17000] No change in config or other settings. Any suggestions are very much welcome... (only thing that puzzles me is that the repo contains 1.8.3 for main asterisk, and 1.8.4 for the rest) Hans
On 10/06/2011 5:32 AM, Hans Witvliet wrote:> Hi all, > > I got three asterisk-machines, two of them acting as proxies. > On one machine (sles11sp1) i got iritating messages about not bing able > to find codec's and other stuff, so i thought it might be time for an > update: Stupid! > > I went originally from a almost working machine running: > asterisk180-alsa-1.8.3.2-87.1 > asterisk180-dahdi-1.8.3.2-87.1 > asterisk180-1.8.3.2-87.1 > asterisk180-odbc-1.8.3.2-87.1 > > To a machine that continuously restarts asterisk (+core dumps) running: > asterisk180-alsa-1.8.4.2-90.1 > asterisk180-dahdi-1.8.4.2-90.1 > asterisk180-1.8.3-85.2 > asterisk180-odbc-1.8.4.2-90.1 > > > Jun 9 16:35:44 kc3004 kernel: [ 713.970342] asterisk[5122]: > segfault at 7fedcb450716 ip 00007fedeff89c8a sp 00007fff4b4d5d38 error 7 in libpthread-2.11.1.so[7fedeff7f000+17000] > > No change in config or other settings. > > Any suggestions are very much welcome... > (only thing that puzzles me is that the repo contains 1.8.3 for main > asterisk, and 1.8.4 for the rest) > >One thought comes to mind, I'm not sure if you are using the same computer with the same IP address or if you have set up a different computer with the new installation which probably has a different IP address, if the latter I would suggest you check your configuration file for bindings to specific IP addresses and make sure they match the new machine. Larry.
On Thu, 9 Jun 2011, Hans Witvliet wrote:> I went originally from a almost working machine running: > asterisk180-1.8.3.2-87.1 > > To a machine that continuously restarts asterisk (+core dumps) running: > asterisk180-1.8.3-85.2Any chance you have a mix of Asterisk and module versions? Was Zaptel/Dahdi compiled with the proper set of headers for your kernel? Can you start Asterisk from the command line instead of the usual startup script? What do the first couple of errors look like? Capturing the output via the 'script' command will help. For example*, script foo sudo /usr/sbin/asterisk -C /etc/asterisk/asterisk.conf\ -c -d -d -d -f -g -n -p -q -v -v -v exit Can you turn off auto module loading and start with no modules? *) I'm a 1.2 Luddite, so the command line arguments may have changed... -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST Newline Fax: +1-760-731-3000