Juha Heinanen wrote on 09/17/2015 03:05 PM:
> Juha Heinanen writes:
> 
>> any idea why trying to load mod_py breaks sems startup?
> 
> i converted DBGs to INFOs in DSMFactory::preloadModules and
> DSMChartReader::importModule and added some infos.  that produced to
> syslog:
> 
> Sep 17 16:01:14 lohi sems[14949]: [#7f39c1316740] [preloadModules, 
> DSM.cpp:878] INFO:  preloading 'mod_py'...
> Sep 17 16:01:14 lohi sems[14949]: [#7f39c1316740] [importModule, 
> DSMChartReader.cpp:257] INFO:  loaded module 'mod_py' from 
> '/usr/lib/sems/dsm/mod_py.so'
> Sep 17 16:01:14 lohi sems[14949]: [#7f39c1316740] [preloadModules, 
> DSM.cpp:884] INFO:  checking last_loaded
> Sep 17 16:01:14 lohi sems[14949]: [#7f39c1316740] [preloadModules, 
> DSM.cpp:886] INFO:  checking last_loaded->preload
> 
> the only explanation that i can come up with is that
> last_loaded->preload() never returns.
I just tried here, adding preload_mods=mod_py to dsm.conf ran normally:

 [#7fc886262740/30889] [addPayload, AmPlugIn.cpp:718] DEBUG:  payload
'opus/24000' inserted with id 100 and order 200
 [#7fc886262740/30889] [load, AmPlugIn.cpp:231] DEBUG:  loading
lib//dsm.so...
 [#7fc886262740/30889] [loadPlugIn, AmPlugIn.cpp:281] DEBUG:  using
RTLD_NOW | RTLD_GLOBAL to dlopen 'lib//dsm.so'
 [#7fc886262740/30889] [loadDiPlugIn, AmPlugIn.cpp:640] DEBUG:
component 'dsm' loaded.
 [#7fc886262740/30889] [load, AmPlugIn.cpp:240] DEBUG:  AmPlugIn:
modules loaded.
 [#7fc886262740/30889] [load, AmPlugIn.cpp:241] DEBUG:  Initializing 1
plugins...
 [#7fc886262740/30889] [preloadModules, DSM.cpp:878] DEBUG:
preloading 'mod_py'...
 [#7fc886262740/30889] [importModule, DSMChartReader.cpp:257] DEBUG:
loaded module 'mod_py' from '../apps/dsm/mods/lib/mod_py.so'
 [#7fc886262740/30889] [add_env_path, AmUtils.cpp:1043] DEBUG:
setting PYTHONPATH to: 'lib/'
 [#7fc886262740/30889] [preload, ModPy.cpp:66] DEBUG:  Python version
2.7.3 (default, Jun 22 2015, 19:44:33)
[GCC 4.6.3]
 [#7fc886262740/30889] [preloadModules, DSM.cpp:889] INFO:
successfully preloaded 'mod_py'
 [#7fc886262740/30889] [readFile, DSMStateDiagramCollection.cpp:41]
DEBUG:  loading DSM 'test_conference' from 'scripts/test_conference.dsm'
 [#7fc886262740/30889] [importModule, DSMChartReader.cpp:257] DEBUG:
loaded module 'mod_conference' from
'../apps/dsm/mods/lib/mod_conference.so'
 [#7fc886262740/30889] [addState, DSMStateEngine.cpp:121] DEBUG:
adding state 'start'
 [#7fc886262740/30889] [addState, DSMStateEngine.cpp:138] DEBUG:  set
initial state 'start'
 [#7fc886262740/30889] [addState, DSMStateEngine.cpp:121] DEBUG:
adding state 'lobby'
 [#7fc886262740/30889] [decode, DSMChartReader.cpp:652] DEBUG:  new
condition: 'sessionStart'
 [#7fc886262740/30889] [decode, DSMChartReader.cpp:574] DEBUG:  adding
action 'set($is_spkonly=0)'
...

if you attach with gdb to the hanging sems and traceback the threads,
what's the call stack like?

thanks!
Stefan

_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to