Status: Verified
GOAL:
How to troubleshoot WebSpeed Messenger agent connection issues.
FACT(s) (Environment):
WebSpeed 2.x
FIX:
When you received following errors when running webspeed 2.x, please follow these steps to troubshoot the problem.
WTB: Received a SIGCHLD from a child process. The dying process pid = . (5743)
WTB: No available agents. (5754)
Msngr: Failure sending WEB_CGIIP_GET_PROG message. (5805)
These errores can be caused by several events, including agents dying or the WebSpeed broker not running. The trouble shooting process includes the following steps:
1) Check to make sure the WebSpeed broker is running.
On UNIX, use the ps command and grep for _wtb or the wtbman
-i broker-name -q script.
On Windows NT, use the task manager to look for _wtb.exe or
use the configuration utility.
2) Check to make sure agents are available.
On UNIX, use the ps command and grep for _wta or
the wtbman -i broker-name -q script.
On Windows NT, use the task manager to look for _wta.exe or
use the configuration utility (check the status tab and show
details button).
3) Check the "broker-name_errs.log" for errors.
You might see errors such as:
WTB: Received a SIGCHLD from a child process. The dying
process PID=xxx. ( 5743 )
[This means the agent died.]
Your license for <product name> has expired. (4782)
Unable to find server <name> with protocol TCP in file
SERVICES or SERVICES not found in expected location
(5192)
4) Check to make sure the Messenger is configured correctly.
On UNIX, check the messenger and make sure the following
variables are set correctly:
DLC, PROMSGS, PROCFG, and WEBSPEEDCNF
5) If you cannot get your agents to spawn correctly, start them
with just the default parameters.
-p web/objects/web-disp.p -cpstream iso8859-1 -
weblogerror
If the agents start now, start trouble shooting the other
parameters on the agent.
6) Another thing to try is to start the _wta on UNIX or the
_wta.exe on Windows NT.
This brings up a Progress Procedure Editor. Try to connect
to the database. Any errors display immediately. Fix those
problems.
Once you can connect cleanly to the database, use the
connection parameters that worked to connect to the database
in the webspeed.cnf file or the startup parameter line in
the Configuration Utility.
NOTE: If you are still on WebSpeed 2.0, upgrade to 2.1 for
some fixes to problems associated with this error.