Error while booting Tuxedo on Linux machine

Question

Hi,
I am getting following o/p when I run tmboot -y
(testing)itrtrc[0]:/home/modula/itrtrc/sys-conf>tmboot -y
Booting all admin and server processes in /home/modula/itrtrc/sys-conf/tuxconfig
INFO: BEA Tuxedo, Version 8.0
INFO: Serial #: 454493271161-2312432531016, Expiration 2007-07-10, Maxusers 1000000
INFO: Licensed to: BEA Evaluation Customer
Booting admin processes ...
exec BBL -A :
CMDTUX_CAT:819: INFO: Process id=4621 Assume started (pipe).
Booting server processes ...
exec TMUSREVT -A :
CMDTUX_CAT:819: INFO: Process id=4622 Assume started (pipe).
exec TMSYSEVT -A :
CMDTUX_CAT:819: INFO: Process id=4623 Assume started (pipe).
exec TMS -A :
CMDTUX_CAT:819: INFO: Process id=4624 Assume started (pipe).
exec TMS -A :
CMDTUX_CAT:819: INFO: Process id=4625 Assume started (pipe).
exec NormalizeE -A :
CMDTUX_CAT:819: INFO: Process id=4626 Assume started (pipe).
exec NormalizeE -A :
CMDTUX_CAT:819: INFO: Process id=4627 Assume started (pipe).
exec NormalizeE -A :
and at the end it says 39 processes started but none exists.
Thanx in advance

Answer 1

The CMDTUX_CAT:819 message usually means that the newly booted process died
before it was able to synchronize with tmboot.
In your configuration, you are able to execute tmboot but you cannot execute
any other Tuxedo process. You may want to verify the following:
- Does the value of TUXDIR in your TUXCONFIG file match the directory in
your path for `whence tmboot`? If the TUXDIR in TUXCONFIG points to a
directory containing binaries for some other hardware architecture, then it
would be logical for all of the binaries to be unable to run.
- Is your operating system version a version that has been certified by BEA?
- Verify the executable file type of the binaries using "file
$TUXDIR/bin/BBL". Does the 32-bit/64-bit setting match what you expect, and
are the binaries for the OS that you expect?
- Is there any outstanding shared memory on the system with the IPCKEY
specified in $TUXCONFIG? Tuxedo will detect most such errors by examining a
magic value, but it's possible that the magic value might accidentally match
while the rest of the shared memory is of the wrong format.
I hope this is of help.
Ed
<Kaustubh Deoghare> wrote in message news:[email protected]...
Hi,
I am getting following o/p when I run tmboot -y
(testing)itrtrc[0]:/home/modula/itrtrc/sys-conf>tmboot -y
Booting all admin and server processes in
/home/modula/itrtrc/sys-conf/tuxconfig
INFO: BEA Tuxedo, Version 8.0
INFO: Serial #: 454493271161-2312432531016, Expiration 2007-07-10, Maxusers
1000000
INFO: Licensed to: BEA Evaluation Customer
Booting admin processes ...
exec BBL -A :
CMDTUX_CAT:819: INFO: Process id=4621 Assume started (pipe).
Booting server processes ...
exec TMUSREVT -A :
CMDTUX_CAT:819: INFO: Process id=4622 Assume started (pipe).
exec TMSYSEVT -A :
CMDTUX_CAT:819: INFO: Process id=4623 Assume started (pipe).
exec TMS -A :
CMDTUX_CAT:819: INFO: Process id=4624 Assume started (pipe).
exec TMS -A :
CMDTUX_CAT:819: INFO: Process id=4625 Assume started (pipe).
exec NormalizeE -A :
CMDTUX_CAT:819: INFO: Process id=4626 Assume started (pipe).
exec NormalizeE -A :
CMDTUX_CAT:819: INFO: Process id=4627 Assume started (pipe).
exec NormalizeE -A :
and at the end it says 39 processes started but none exists.
Thanx in advance