The
txrpt
utility was run with a start time (-s option)
later than the end time (-e option).
Re-run the command with correct start and end options.
txrpt (1)
Too many service names were supplied with the
txrpt
utility's
-n
option, causing an internal
table to overflow.
Re-run the command with fewer service names,
or contact your TUXEDO System Technical Support.
txrpt (1)
The
txrpt
command was called with an invalid parameter for the
-d
option.
Retry the command with a corrected
-d
option.
txrpt (1)
The
txrpt
command was called with an invalid parameter for the
-d
option.
Retry the command with a corrected
-d
option.
txrpt (1)
Bad command line options were specified when booting the
BBL.
Specify correct command line options for booting the
BBL.
tmboot (1)
In a networked application (MP mode), the
BBL
server initialization routine cannot find the
DBBL
entry in the Bulletin Board.
The
DBBL's
copy of the Bulletin Board in its own process space may be corrupted.
Check if the
DBBL
is active.
The
DBBL
should be booted before the
BBL
in a networked application.
Try to shut down the application, remove
IPC,
and then reboot the
DBBL
and
BBL.
If the error persists, contact your TUXEDO System Technical Support.
tmboot (1)
In a networked application (MP mode), the
BBL
server initialization routine cannot find the
DBBL
entry in the Bulletin Board.
The
DBBL's
copy of the Bulletin Board in its own process space may be corrupted.
Check if the
DBBL
is active.
The
DBBL
should be booted before the
BBL
in a networked application.
Try to shut down the application, remove
IPC,
and then reboot the
DBBL
and
BBL.
If the error persists, contact your TUXEDO System Technical Support.
tmboot (1)
The
BBL
server initialization routine cannot find its own entry
in the Bulletin Board.
The Bulletin Board may be corrupted.
Shut down the application, remove IPCs, and reboot the
DBBL
and
BBL.
If the error persists, contact your TUXEDO System Technical Support.
tmboot (1)
The
BBL
server initialization routine cannot update its own entry
in the Bulletin Board.
The Bulletin Board may be corrupted.
Shut down the application, remove
IPC,
then reboot the
DBBL
and
BBL.
If the error persists, contact your TUXEDO System Technical Support.
tmboot (1)
After every interval of value in
scanunit ,
the
BBL
does sanity checks
on the Bulletin Board.
When the BBL detects that the Bulletin Board is insane,
it attempts to recover the Bulletin Board by getting a new one.
When the maximum number of Bulletin Board uploads have
been received, the
BBL
will exit.
The Bulletin Board on the local machine may have been corrupted.
System recovery attempts have failed.
Contact your TUXEDO System Technical Support.
A service request handled by the BBL failed.
The request could be one of
tmadmin
requests,
tmconfig
requests,
tpbroadcast
requests, and others.
If the error is an operating system error, the
Uunixerr
and
errno
will be printed.
Check the userlog for earlier messages on the problem.
Before the
BBL
can shut down, it sends a shutdown message to
its paired
BRIDGE
and
BSBRIDGE .
The paired bridges could not
be brought down; the shutdown message was not created
due to the insufficient memory space.
Contact your TUXEDO System Technical Support.
See LIBTUX_CAT message 683
for further explanation.
Before the
BBL
can shut down, it sends a shutdown message to its paired
BRIDGE
and
BSBRIDGE .
The paired bridges could not
be brought down because sending the shutdown message to the
BRIDGE
process failed.
Contact your TUXEDO System Technical Support.
See LIBTUX_CAT messages 322, 323, 324, and 325
for further explanation.
The
BBL
process has been shut down.
No action required.
tmshutdown (1)
After detecting that the Bulletin Board is corrupted, the
BBL
failed to re-initialize and re-attach to the Bulletin Board.
The Bulletin Board on your machine has been corrupted,
recovery attempts have failed.
Contact your TUXEDO System Technical Support.
The Bulletin Board cleanup process cannot find the
DBBL
entry in the Bulletin Board.
The
DBBL 's
copy of the Bulletin Board
in its own process space may be corrupted.
Contact your TUXEDO System Technical Support.
See messages 18 and 19 above
for further explanation.
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while cleaning the Bulletin Board.
Ensure that the operating system parameters are set correctly
for the amount of memory on the machine and the amount of
memory that can be used by a process.
Reduce the memory usage on the machine or
increase the amount of physical memory on the machine.
The Bulletin Board cleanup process cannot find the
BBL
entry in the Bulletin Board.
The Bulletin Board may be corrupted.
Contact your TUXEDO System Technical Support.
The Bulletin Board cleanup process cannot find the
DBBL
entry in the Bulletin Board.
The
DBBL 's
copy of the Bulletin Board
in its own process space may be corrupted.
Contact your TUXEDO System Technical Support.
See messages 18 and 19
in this chapter for further explanation.
While attempting to clean up the Bulletin Board, the cleanup process was
unable to find the queue entry associated with the
DBBL
in its internal tables.
Contact your TUXEDO System Technical Support.
While attempting to restart the
DBBL ,
the cleanup process cannot
create a temporary file for the Bulletin Board.
Check and clean up space in either
$TMPDIR
or
/tmp
on your machine, or contact your TUXEDO System Technical Support.
While attempting to restart the
DBBL ,
the cleanup process was
unable to write to the Bulletin Board.
Check free space and file permissions either in
$TMPDIR
or
/tmp
on your machine,
or contact your TUXEDO System Technical Support.
The cleanup process attempting to restart the
DBBL
failed.
Possible causes: 1) remote restart failed, 2) the
TUXDIR
environment variable was not set, or 3)
system ()
call failed.
Check the remote connection and the
TUXDIR
environment variable.
Also, check the error returned from
system ()
call, or contact your TUXEDO System Technical Support.
A stray reply message has appeared on the
BBL
reply message queue.
No action required.
The requested service handled by the
BBL
failed.
Check the userlog for additional messages on
the failure.
While the
BBL
is handling a service request, it cannot find
DBBL .
Check for a partitioned network or corrupted shared memory, or
contact your TUXEDO System Technical Support.
While the
BBL
is waiting for requests, it times out and performs
a scan of the
GTT
table every
scanunit
seconds.
An unexpected transaction state was detected in the
GTT
table entry of the Bulletin Board.
No action required.
However, the local groups participating
in the transaction are notified.
If the transaction is already decided, they are sent a commit request.
Otherwise, an abort, timeout, or status request is sent to
the
TMS s.
While the
BBL
is waiting for requests, it times out and performs
a scan of the
GTT
table every
scanunit
seconds.
Based on the
location of the groups in transaction and transaction state,
a different message will be sent to groups. However, an
unexpected flag was detected in the message, and thus, no
message was sent to the
TMS s.
No action required.
After checking for transaction timeout, the
BBL
goes through the registry
table entry list and decrements the
timeleft
field for blocking processes. If the
timeleft
value becomes less than or equal to zero,
the process is sent a message to be woken up.
This error indicates that the
BBL
fails to wake up the blocking process.
No action required.
The
SIGTERM
signal was received and ignored while shutting down the
BBL .
See
tmshutdown
command for shutdown procedures.
tmshutdown (1)
The
UBBCONFIG
file must include a *RESOURCES section.
Add the *RESOURCES section with appropriate values to the
UBBCONFIG
file.
ubbconfig (5)
The
UBBCONFIG
file must include a *MACHINES section.
Add the *MACHINES section with appropriate values to the
UBBCONFIG
file.
ubbconfig (5)
The *GROUPS section is missing in the
UBBCONFIG
file. This is not a fatal error
since groups can be added via
tmconfig.
No action required if the groups will later be added via
tmconfig.
In most cases, a *GROUPS section would exist in the
UBBCONFIG
file.
If the *GROUPS section is desired, it should be added to the
UBBCONFIG
file.
tmconfig (1),
ubbconfig (5)
The SERVERS section is missing in the
UBBCONFIG
file. This is not a fatal error
since servers can be added via
tmconfig.
No action required if the servers will later be added via
tmconfig.
In most cases, a SERVERS section would exist in the
UBBCONFIG
file.
If the SERVERS section is desired, it should be added to the
UBBCONFIG
file.
tmconfig (1),
ubbconfig (5)
The SERVICES section is missing in the
UBBCONFIG
file. This is not a fatal
error since services can be added via
tmconfig.
No action required if the services will later be added via
tmconfig.
In most cases, a SERVICES section would exist in the
UBBCONFIG
file.
If the SERVICES section is desired, it should be added to the
UBBCONFIG
file.
tmconfig (1),
ubbconfig (5)
The *NETWORK section is missing in the
UBBCONFIG
file. This is not a fatal error
since network configurations can be added via
tmconfig.
No action required if the network configuration will later be added via
tmconfig.
In most cases in which the
MP
model and
LAN
option are given,
a *NETWORK section would exist in the
UBBCONFIG
file.
If the *NETWORK section is desired, it should be added to the
UBBCONFIG
file.
If the *NETWORK section is not desired at all, then the
LAN
option and/or
MP
model should be checked.
tmconfig (1),
ubbconfig (5)
1 ERROR: End time is before start time
DESCRIPTION
ACTION
SEE ALSO
10 ERROR: Name table full
DESCRIPTION
ACTION
SEE ALSO
15 ERROR: txrpt: bad -d arg
DESCRIPTION
ACTION
SEE ALSO
16 ERROR: txrpt: bad -d option value arg
DESCRIPTION
ACTION
SEE ALSO
17 WARN: BBL tpsvrinit: bad command line options were specified when booting the BBL
DESCRIPTION
ACTION
SEE ALSO
18 ERROR: BBL tpsvrinit: cannot find the DBBL entry in the Bulletin Board
DESCRIPTION
ACTION
SEE ALSO
19 ERROR: BBL tpsvrinit: cannot update the DBBL entry in the Bulletin Board
DESCRIPTION
ACTION
SEE ALSO
20 ERROR: BBL tpsvrinit: cannot find the BBL entry in the Bulletin Board
DESCRIPTION
ACTION
SEE ALSO
21 ERROR: BBL tpsvrinit: cannot update the BBL entry in the Bulletin Board
DESCRIPTION
ACTION
SEE ALSO
22 ERROR: Exceeds the maximum number of times for the BBL to get a new Bulletin Board
DESCRIPTION
ACTION
23 ERROR: Administrative service request servicename handled by BBL failed - msg
DESCRIPTION
ACTION
24 ERROR: The BBL could not bring down a paired bridge
DESCRIPTION
ACTION
25 ERROR: The BBL could not bring down a paired bridge
DESCRIPTION
ACTION
26 INFO: The BBL is exiting system
DESCRIPTION
ACTION
SEE ALSO
27 ERROR: BBL bbclean: cannot re-attach to the Bulletin Board for recovery
DESCRIPTION
ACTION
28 ERROR: BBL bbclean: cannot find the DBBL entry in the Bulletin Board
DESCRIPTION
ACTION
29 ERROR: Memory allocation failure
DESCRIPTION
ACTION
30 ERROR: BBL bbclean cannot find BBL entries in the Bulletin Board
DESCRIPTION
ACTION
31 ERROR: BBL bbclean cannot find DBBL entry in the Bulletin Board
DESCRIPTION
ACTION
32 ERROR: BBL bbclean cannot find queue entry for DBBL in the Bulletin Board
DESCRIPTION
ACTION
33 ERROR: BBL bbclean cannot open Bulletin Board image, filename, while restarting the DBBL
DESCRIPTION
ACTION
34 ERROR: BBL bbclean cannot write the Bulletin Board for restarting the DBBL
DESCRIPTION
ACTION
36 ERROR: BBL bbclean attempting to restart the DBBL failed
DESCRIPTION
ACTION
37 WARN: BBL received stray reply from the BBL's reply queue
DESCRIPTION
ACTION
38 ERROR: BBL requested service service failed - errmsg
DESCRIPTION
ACTION
39 ERROR: BBL cannot find the DBBL
DESCRIPTION
ACTION
40 WARN: BBL found an unexpected transaction state trans_state
DESCRIPTION
ACTION
41 WARN: BBL found unexpected flag flagval in the message
DESCRIPTION
ACTION
42 WARN: BBL failed to wake up the blocking process - pid
DESCRIPTION
ACTION
43 WARN: SIGTERM was ignored while shutting down the BBL
DESCRIPTION
ACTION
SEE ALSO
44 ERROR: Must have a RESOURCES section
DESCRIPTION
ACTION
SEE ALSO
45 ERROR: Must have a MACHINES section
DESCRIPTION
ACTION
SEE ALSO
46 WARN: Missing GROUPS section
DESCRIPTION
ACTION
SEE ALSO
47 WARN: Missing SERVERS section
DESCRIPTION
ACTION
SEE ALSO
48 WARN: Missing SERVICES section
DESCRIPTION
ACTION
SEE ALSO
49 WARN: Missing NETWORK section
DESCRIPTION
ACTION
SEE ALSO
50 ERROR: Multiple machines cannot be configured for SHM mode