Kbase P76735: How to trouble shoot WebSpeed agents startup problems?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/04/2009 |
|
Status: Verified
GOAL:
How to trouble shoot WebSpeed agents startup problems?
GOAL:
How to debug WebSpeed broker not starting problem?
GOAL:
What utilities can help trouble shoot WebSpeed agents startup problems?
FACT(s) (Environment):
UNIX
WebSpeed 3.x
OpenEdge 10.x
FIX:
When having difficulties starting WebSpeed agents, typically the server log file will contain very limited information even with increased logging level. When manually spawning _progres is successful, more in-depth procedures can be attempted. Here are the different ways to troubleshoot the issue:
First way:
- From broker log file, cutting the line where _progres is started from JVM, and paste that line to command line for execution, this should start a brief _progres session, and then output pid and "completed" from the session. Make sure prior to starting the process, set JREHOME to point to appropriate location.
Second way:
- Use a wrapper script, which calls _progres with the command line to start the agent. Have the script write stderr to a file, so that we can see any errors
during startup. Run this as the agent startup command.
For example,
a. Put following is a file called test.sh, in $WRKDIR
#!/bin/sh
$DLC/bin/_progres $* 2> $WRKDIR/$$.err
b. Modify ubroker.properties file for following entry
srvrExecFile=$DLC/bin/jvmStart $WRKDIR/test.sh
Third way:
- Remove the jvmStart stuff from srvrExecFile, start the broker and try to start
an agent. See if that has any affect.
For example
srvrExecFile=$DLC/bin/_progres
Fourth way:
- If available, use truss (strace on linux). Start the broker with no agents.
Run truss against the broker process, and have it trace all children. Then start an agent, wait till it dies, and look at the truss output.
For HPUX, since there is no truss utility, tusc can be downloaded and used.
The site to download is http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/tusc-7.7/, After you've downloaded tusc-7.7.shar, read the instructions and unpack the files. For Solaris truss can be used.
srvrExecFile=
(path to your wrk dir where you installed tusc)/tusc
-fo $WRKDIR/tusc.out $DLC/bin/_progres
Again start broker with 0 agents first, then start agents, have customer send the output file tusc.out.