[Home]

Summary:ASTERISK-07085: __load_resrouce kills startup.
Reporter:Anthony LaMantia (alamantia)Labels:
Date Opened:2006-06-02 11:10:49Date Closed:2011-06-07 14:02:48
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/Configuration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Well,

I am not sure this is a bug at all, but have written a path and added some logging to prevent this from happening.


if you but a bogus value in modules.conf (ie: a unvalid module.. etc)
load_resrouces() in asterisk.c will fail and asterisk will term' with an exit(1);

///
Asterisk Dynamic Loader Starting:
 == Parsing '/etc/asterisk/modules.conf': Found
[anthonyooooo.so]May 30 10:21:57 WARNING[6631]: loader.c:325 __load_resource: /usr/lib/asterisk/modules/anthonyooooo.so: cannot open shared object file: No such file or directory
May 30 10:21:57 WARNING[6631]: loader.c:499 load_modules: Loading module anthonyooooo.so failed!

now this kills asterisk from booting.
///


load_resrouces fails due to __load_resource ,
i think it's kind of nice to allow illegal module names as long as there is decent logging, but am not sure if this complies with how asterisk should be.

/*
so inside of the configuration file we have

name => value
load => anthony_dym.so  for example
*/


if the value for the load, is invalid then asterisk dies basicly.



the diff i made preforms this action in teh same situation.


load => entry
May 30 10:43:21 WARNING[11082]: asterisk.c:2387 main: Unable To Load All DynamicModules(/usr/lib/asterisk/modules/anthonyooooo.so)  == Manager registered action DBGet
 == Manager registered action DBPut
 == Parsing '/etc/asterisk/enum.conf': Found
Asterisk Ready.
*CLI>

it also adds extended error nodes to load_resources()


-Anthony

Comments:By: Serge Vecher (serge-v) 2006-06-02 11:16:31

1.2.4 is quite old. Is this an issue in 1.2.8?
By: Anthony LaMantia (alamantia) 2006-06-02 11:23:06

let me grab the latest source from the SVN.
By: Serge Vecher (serge-v) 2006-06-02 14:26:40

if this is a problem in the latest 1.2.8, please feel free to reopen. ...