Kbase P177307: Is there any way that the gather script could cause the admin server to fail? say like doing ^C.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/11/2010 |
|
Status: Unverified
GOAL:
Is there any way that the gather script could cause the admin server to fail? say like doing ^C.
GOAL:
If the promon gather script session is terminated with a Control C, will the AdminServer shutdown?
FACT(s) (Environment):
UNIX
Progress 9.x
OpenEdge 10.x
FIX:
If the gather script is run from a UNIX session other than the one that was used to start the AdminServer then the answer is No. Terminating the promon gather script running on UNIX with a Control C (Ctrl-C) will not cause the AdminServer to shutdown.
The promon gather script for UNIX really has nothing to do with the AdminServer. The promon gather script is used for the purpose of collecting information regarding a database and any _progres, _mprosrv, _mprshut, _proapsv and _proutil processes running on the machine where the script is being executed (if the script is being invoked without the perf option).
When the promon gather script is running without the perf option, the script will check for any of the process mentioned in the previous paragraph running on this machine. The script then uses specific utilities for each UNIX Operating System (HP, Solaris, AIX, Linux etc.) to have these processes dump a stack trace file for further review by Progress Technical Support. The use of these specific utilities (pstack, procstack) or signals (kill -s USR1) do not result in the processes being terminated.
Please also realize that the promon gather script runs against a data as a shared memory client. The promon gather script makes use of the -NL (No Lock) option. This does not mean that the promon gather script does make use of locks or latches. It just does not use as many as it would have without the -NL option. If a shared memory client was to terminate their session via a Control C, we would process this as a hang up which is handled appropriately by our signal handler and should not result in a database terminating abnormally either.
If the gather script is run from the same UNIX session to the one that was used to start the AdminServer then the answer is potentially Yes. There is a JAVA issue whereby signals within the same UNIX session, such as CTRL-C, can cascade to previously run JAVA programs even after those JAVA programs (such as the AdminServer) have finished starting successfully. See solution 21166, "Adminserver dies when the user who started the Adminserver's session is terminated" for additional information regarding how to address this behavior specifically for the AdminServer.