Kbase 16063: WTB:received a SIGCHLD from a child process (WebSpeed beta)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
WTB:received a SIGCHLD from a child process (WebSpeed beta)
This kbase addresses the following situation:
You get a Broker started with wtb. You use wtbman <port> status, and
see that a broker is running, but no agents. The error_log file shows
only the message:
WTB: received a SIGCHLD from a child process
The pid of the dying child is: <pid>
In some cases the DEBUG option can be useful (see kbase 16031,
Webspeed Transaction Broker DEBUG option"). In cases where even the
DEBUG option does not help, the following checklist may be useful:
1) Is there a server running for the database as defined in WtaParams?
Try starting a regular progress client against the datbase using the
same parameters:
mpro <database> -H <host> -S <service>
where the <database> <host> and <service> are identical to those in
WtaParams. If this starts a Progress client without errors, then the
server is running, otherwise, you must start a database server. If
there is no server running, or if you are attempting to connect in
single-user mode (one the parameters in WtaParams is -1), be sure
there is no <database>.lk lock file.
2) Are the User and Group specified in the wtb.cnf file valid for
your system? The user must be in the /etc/passwd file, and the
group must be in /etc/group. Also, this user must wave write
permission for WtbRootDirectory.
3) Do you have a client - database version mismatch? If you are
trying to connect as a self-service client or in single-user mode,
the database version MUST match the agent version (8.0B for WebSpeed
BETA). Otherwise, you must connect in client-server mode using the
-H and -S parameters.
The error-reporting mechanism will be much improved for the 1.0
release, and these steps may no longer be necessary.
Progress Software Technical Support Note # 16063