Bug 4159

Summary: Improve container error message when SEG execution fails
Product: GRAM Reporter: Stuart Martin <smartin@mcs.anl.gov>
Component: wsrf scheduler interfaceAssignee: Joe Bester <bester@mcs.anl.gov>
Status: RESOLVED FIXED    
Severity: normal CC: bester@mcs.anl.gov, lane@mcs.anl.gov, smartin@mcs.anl.gov
Priority: P3    
Version: development   
Target Milestone: 4.0.2   
Hardware: Macintosh   
OS: All   
Bug Depends on:    
Bug Blocks: 2266    

Description From 2006-01-16 11:33:38 
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
is needed.

This problem was discovered when a GT4 container is started without previously
sourcing 
$GLOBUS_LOCATION/globus-user-env.csh or globus-devel-env.csh.
------- Comment #1 From 2006-01-17 12:16:25 ------- 
Is it sufficient to record things like this

ERROR monitoring.SchedulerEventGenerator [Thread-5,run:193] SEG Terminated with
/home/bester/development/globus_4_0_branch/INSTALL/libexec/globus-scheduler-event-generator:
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)?

joe
------- Comment #2 From 2006-01-17 12:20:49 ------- 
Personally I'd call that sufficient. Besides, I'm not sure what operation such
a
fault would be in response to.
------- Comment #3 From 2006-01-17 13:49:40 ------- 
A fix to do this is committed to trunk and 4.0 branch

joe