Bug 2741 - catching SIGSEGV if dynamic loading of authorization modules fails
: catching SIGSEGV if dynamic loading of authorization modules fails
Status: RESOLVED LATER
: GRAM
gt2 Gatekeeper/Jobmanager
: 3.2.1
: PC Windows XP
: P3 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-02-15 10:17 by
Modified: 2012-09-12 13:54 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-02-15 10:17:14
When the loading of a dynamic module by the gatekeeper (gridftp probably as
well) fails e.g., due to missing libraries, unresolved symbols present in the
authorization module that is being loaded the gatekeeper fails with a sigsegv
without protocolling the error in the logs.

I would love to see a signal handler for sigsegv that produces a final message
in the log and helps it to fail gracefully if there is a problem with the module
configuration/deployment - it would also alarm the sysadmin toward an existing
problem with this configuration. Also for debugging it would be great if there
would be a non-forking option for the gatekeeper. The option for not detaching
from the terminal exists, but it still does fork a child for each incomming
request. 

I have added this to a GT3.2 gatekeeper by inserting a "if(!foreground) {   }"
around the forking code about at line 1000 of the code. This way if forground is
selected (e.g., via the debug option) the gatekeeper won't fork children and act
as a single request sequential service, easier for debugging segfaults in gdb
------- Comment #1 From 2012-09-12 13:54:31 -------
We've migrated our issue tracking software to jira.globus.org. Any new issues
should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363

As this issue hasn't been commented on in several years, we're closing it. If
you feel it is still relevant, please add it to jira.