[asterisk-bugs] [JIRA] (ASTERISK-23265) Preloading Certain Modules in Asterisk 12 causes a core dump

Andrew Nagy (JIRA) noreply at issues.asterisk.org
Fri Feb 7 13:03:03 CST 2014


    [ https://issues.asterisk.org/jira/browse/ASTERISK-23265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214976#comment-214976 ] 

Andrew Nagy commented on ASTERISK-23265:
----------------------------------------

IRC logs for clarifiation
{code}
[10:36am] tm1000: file: mjordan http://pastebin.com/sZXDbFK6
[10:36am] mjordan: hm.
[10:36am] file: hrm
[10:37am] file: yup, we initialize presence stuff afterwards
[10:37am] mjordan: gr. Preload.
[10:38am] tm1000: mjordan: do I need to reload pjsip correctly
[10:38am] mjordan: we've got to do something about the module loader.
[10:38am] mjordan: tm1000: turns out, it isn't PJSIP's fault.
[10:38am] mjordan: this is just pure Asterisk guts being wrong. And stupid.
[10:39am] tm1000: mjordan: anything I can do?
[10:39am] mjordan: tm1000: do you have a preload directive in your modules.conf?
[10:39am] tm1000: mjordan: yes
[10:39am] mjordan: tm1000: which module(s)?
[10:40am] tm1000: http://pastebin.com/HhJd5Lqw
[10:40am] file: pbx_config.so.
[10:40am] mjordan: what happens if you remove pbx_config and chan_local?
[10:40am] mjordan: chan_local no longer exists...
[10:40am] mjordan: so there's that. 
[10:41am] tm1000: mjordan: tonyclewis is the one who said pbx_config needs to be there
[10:41am] mjordan: he may not be wrong, but right now, let's just see if it removes the crash
[10:41am] tonyclewis: We had to preload before for a issue with queues
[10:42am] mjordan: tm1000: the short story is that Asterisk's module loader is antiquated and needs an overhaul.
[10:42am] mjordan: tonyclewis: Device state not showing up for Queues on load?
[10:42am] tonyclewis: Yes thats it
[10:43am] mjordan: tonyclewis: how long ago was that?
[10:44am] tonyclewis: Couple years
[10:44am] tm1000: mjordan: ok that works
[10:44am] tm1000: it starts fine now
[10:44am] tm1000: and lets me register
[10:44am] mjordan: k. We might have fixed that, since pbx_config has a module load priority before app_queue now
[10:44am] mjordan: tm1000: that's a work around, the long answer is we have to go fix the module loader
{code}
                
> Preloading Certain Modules in Asterisk 12 causes a core dump
> ------------------------------------------------------------
>
>                 Key: ASTERISK-23265
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23265
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 12.1.0
>         Environment: CentOS 6.5
>            Reporter: Andrew Nagy
>         Attachments: backtrace.txt
>
>
> Preloading pbx_config.so and chan_local.so causes asterisk to Core Dump. The original module.conf is below:
> {code}
> [modules]
> autoload=yes
> preload = pbx_config.so
> preload = chan_local.so
> noload = pbx_gtkconsole.so
> noload = pbx_kdeconsole.so
> noload = app_intercom.so
> noload = chan_modem.so
> noload = chan_modem_bestdata.so
> noload = chan_modem_i4l.so
> noload = app_trunkisavail.so
> noload = chan_alsa.so
> noload = chan_oss.so
> noload = app_directory_odbcstorage.so
> noload = app_voicemail_odbcstorage.so
> noload = chan_modem_aopen.so
> load = format_wav.so
> load = format_pcm.so
> load = format_mp3.so
> load = res_musiconhold.so
> {code}
> Removing the two preloads allows asterisk to function normally
> {code}
> [modules]
> autoload=yes
> noload = pbx_gtkconsole.so
> noload = pbx_kdeconsole.so
> noload = app_intercom.so
> noload = chan_modem.so
> noload = chan_modem_bestdata.so
> noload = chan_modem_i4l.so
> noload = app_trunkisavail.so
> noload = chan_alsa.so
> noload = chan_oss.so
> noload = app_directory_odbcstorage.so
> noload = app_voicemail_odbcstorage.so
> noload = chan_modem_aopen.so
> load = format_wav.so
> load = format_pcm.so
> load = format_mp3.so
> load = res_musiconhold.so
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list