Bugzilla – Bug 4159
Improve container error message when SEG execution fails
Last modified: 2006-04-07 16:36:14
You need to
before you can comment on or make changes to this bug.
The SEG calls dlopen on the scheduler modules . If the necessary env vars are
not set, then the seg fails
without an adequate error message. An error messaging indicating the problem
This problem was discovered when a GT4 container is started without previously
$GLOBUS_LOCATION/globus-user-env.csh or globus-devel-env.csh.
Is it sufficient to record things like this
ERROR monitoring.SchedulerEventGenerator [Thread-5,run:193] SEG Terminated with
error while loading shared libraries:
libglobus_scheduler_event_generator_gcc32dbg.so.0: cannot open shared object
file: No such file or directory
in the container log, or do you want some user level notification (much harder)?
Personally I'd call that sufficient. Besides, I'm not sure what operation such
fault would be in response to.
A fix to do this is committed to trunk and 4.0 branch