Actually I did have a thought. These problems could very well have started when 
an additional CPU was added to the VM!

Regards
Michael Knill

-----Original Message-----
From: Michael Knill <michael.kn...@ipcsolutions.com.au>
Date: Wednesday, 27 September 2017 at 10:56 am
To: AstLinux List <astlinux-users@lists.sourceforge.net>
Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so

Damn it just happened again. I would like to report it to Digium but I suspect 
that they will want a backtrace (
Do you have any suggestions what else I can try?

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lonnie.abelbeck.com>
Reply-To: AstLinux List <astlinux-users@lists.sourceforge.net>
Date: Thursday, 21 September 2017 at 10:11 pm
To: AstLinux List <astlinux-users@lists.sourceforge.net>
Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so

Hi Michael,

I took a look at the Asterisk source and the last "segfault" fix to 
apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. 
(AstLinux 1.2.8)

Asterisk Git Repo:
http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary

Scroll to bottom under "heads", you can compare different versions there, or 
browse the very latest under "master"
--
7 weeks ago     master  shortlog | log | tree
--
Click "tree" on the master head line.

In this case click "apps"
--
-rw-r--r--      376684  app_queue.c     blob | history | raw
--
Click "history" on the app_queue.c line.

Typically a "segfault" fix will be in the commit message, so search in your 
browser.

This exercise implies there are no upstream app_queue segfault fixes.


This is a handy skill to have, particularly when an Asterisk issue is fixed in 
one version and not another.

Lonnie

PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 
which was fixed as noted above.



On Sep 21, 2017, at 2:22 AM, Michael Knill <michael.kn...@ipcsolutions.com.au> 
wrote:

> Oh dear. My busiest system too. Thanks goodness for safe_asterisk
>  
> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 
> 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in 
> app_queue.so[2b1ed1d34000+35000]
> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on 
> signal 11.
>  
> Any ideas?
> Can I get a backtrace from Astlinux?
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot_______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to 
> pay...@krisk.org.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to