The bridge is shutting down due to a network error.
Re-try the desired operation; if the problem persists,
contact your TUXEDO System Technical Support.
The bridge is shutting down due to a polling error.
Re-try the desired operation; if the problem persists,
contact your TUXEDO System Technical Support.
The
BRIDGE
process was incorrectly sent a message
destined for a recipient on the same machine
as the sender.
It should have been sent directly to
the recipient's UNIX message queue,
without any networking or
BRIDGE
involvement.
Contact your TUXEDO System Technical Support.
Invalid arguments were passed to the
buildclient
command.
Correct the arguments to
buildclient
and reexecute the command.
buildclient (1)
The
buildclient
command was unable to execute the C compiler.
The name of the program that
buildclient
attempted to execute is given as part of the error message.
Verify that the compiler has been installed on the machine, that it
is executable, and that the directory containing the compiler is included
in the
PATH
environment variable.
If the name of the compiler is other than the standard
cc ,
set and export the
CC
shell variable to the proper name of the compiler.
Otherwise, verify that the
CC
shell variable is not set to some extraneous value.
buildclient (1)
The -n option for
buildserver
must be specified greater than or equal
to zero. By default, it is set to zero if an invalid value is specified.
Make sure that the argument to the -n option for
buildserver
is greater than or equal to zero.
buildserver (1)
Invalid arguments were passed to the
buildserver
command.
Correct the arguments to
buildserver
and reexecute the command.
If unsure about the proper arguments, refer to the on-line usage message.
buildserver (1)
The
buildserver
cannot open the temporary output file, srcfile.
Check that the directory for the file exists and has write permissions,
and that the file system has sufficient resources for a new file.
buildserver (1)
A service name was specified more than once to the -s option on the
command line.
Check your -s option for
buildserver
and eliminate any duplicate services.
buildserver (1)
The
buildtms
command was unable to execute the
buildserver
command.
The name of the command being executed is given as part of the error message.
If you are compiling executables to run on the same machine type, as
is normally the case, verify that the
TUXDIR
shell variable is properly set, that the program
${TUXDIR}/bin/buildserver
exists, is accessible, and executable, and that the shell variable
XCBINDIR
is not set.
If you are compiling executables for a different machine type, verify that
the shell variable
XCBINDIR
is set and exported, and that the program
${XCBINIDIR}/buildserver
exists, is accessible, and executable.
buildtms (1)
An attempt to execute more than one cleanupsrv
process was encountered.
If the process was started from a terminal, then this message
appears at the terminal, otherwise it is written to the userlog.
The error can occur when one or more processes are to be cleaned up and
the cleanup doesn't finish before the next scan by the
BBL ,
causing
a second cleanup process to be started.
Retry the desired operation; if the problem persists,
contact your TUXEDO System Technical Support.
An attempt to execute more than one cleanupsrv process was encountered.
If the process was started from
a terminal, then this message
appears at the terminal, otherwise it is written to the userlog.
This can occur when one or more processes are to be cleaned up and
the cleanup doesn't finish before the next scan by the BBL, causing
a second cleanup process to be started.
Retry the desired operation; if the problem persists,
contact your TUXEDO System Technical Support.
While attempting to clean up a server, the TUXEDO System examined
system tables located in shared memory to get the entry for the server.
However, the server information could not be found.
Usually, the System will request manual intervention if this cleanup was
not possible for some reason.
If further assistance is needed, please contact the TUXEDO System Administrator.
A request to clean up a server that was either still running or in the
process of being cleaned up was encountered.
Only servers that are dead may be cleaned up.
Contact your TUXEDO System Technical Support.
While cleaning up information about a dead server, the TUXEDO System
was unable to update the server table entry for that server.
Contact your TUXEDO System Technical Support.
A server that was targeted to be cleaned up was found to be still running.
This message informs the user that the process will be terminated and a
dump of the core will be saved for examination.
Please examine the userlog and the core image saved for further information.
If necessary, contact the TUXEDO System Administrator.
A server that was targeted to be cleaned up was found to be still running.
The TUXEDO System attempted to abort the process and cause a dump of core
to be saved.
However, the kill() function failed.
The exact message displayed depends upon the system error that prevented
the process from being terminated.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The process had been terminated if necessary, and the TUXEDO System
turned off the information for that server in the Registry Table,
that is, marked it as not restartable.
The System was attempting to retrieve queue information for that server, and
the operation failed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was attempting to decode message header information for
a message on that server's request queue,
and the operation failed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was attempting to forward a request from the queue of the cleaned-up
server.
Information for the service which should be forwarded was missing or
unable to be accessed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was attempting to forward a request from the queue of the cleaned-up
server.
The System call to enqueue the request failed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was attempting to forward a request from the queue of the cleaned-up
server.
The System enqueued the request successfully, but the following function
to unlock the Bulletin Board failed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was attempting to forward a request from the queue of the cleaned-up
server.
The System was unable to encode the message.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was unable to encode a message while trying to send it.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was unable to forward a message, so the message will be
sent back to the sender.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was unable to forward a message, so the message will be
sent back to the sender.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The System was unable to decode a message header retrieved
from the reply queue while draining it.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
Request and reply queues had been drained. An attempt to remove the server
failed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
The server was removed successfully,
Retry the desired operation; if the problem persists,
contact your TUXEDO System Technical Support.
A server cleanup was underway.
The system was scanning the server table to determine if servers
needed cleaning.
A server list had been created that identified the list of servers to be
cleaned, but the details on a particular server could not be obtained from
the Server Table.
The processing for this server was skipped.
Retry the desired operation; if the problem persists,
contact your TUXEDO System Technical Support.
A server cleanup was underway.
The TUXEDO System was in the process of draining messages from the server
queues,
and was attempting to send a message to the client process informing it that
the server(s) was not alive anymore.
The reply failed.
The value displayed in this message indicates the process ID of the
process that was to receive the reply.
Often, this implies that a client or server has left the application.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
A server cleanup was underway.
As part of the server cleanup, the server table entry was to be reset.
The function used to reset this table failed.
Examine the
userlog
for other messages about the error.
If necessary, contact the TUXEDO System Administrator
or your TUXEDO System Technical Support.
The automatic server recovery has failed. Server processes will
require manual intervention.
Check the userlog for earlier related messages indicating the nature of
the problem.
If enough information is provided, it may be possible to simply
re-boot the failed server.
Otherwise, you need to manually shut down
the servers and clean up the IPC resources, and then reboot the servers.
See
tmboot
and
tmshutdown
for details on TUXEDO boot and shutdown procedures.
tmboot (1),
tmshutdown (1)
When DBBL scans the Bulletin Board, it will restart any dead servers
that are restartable. However, only one restart process is allowed
at a time. Currently, the restartsrv process cannot join the
application due to the operating system error (TPEOS).
Take proper action according to the errno_msg and/or Uunixerr_msg,
or contact your TUXEDO System Technical Support.
When DBBL scans the Bulletin Board, it will restart any dead servers
that are restartable. However, only one restart process is allowed
at a time. Currently, the restartsrv process cannot join the
application due to an non-operating system error.
Check the userlog for earlier related messages.
Before restarting the server, the server table entry is retrieved from
the Bulletin Board.
An error in retrieving the internal server table entry caused
the restartsrv process to fail to restart the server.
Check the current server indicated by the server group and server
identifier global variables.
Contact your TUXEDO System Technical Support.
While attempting to restart a server, the
restartsrv
process was unable
to find the queue entry associated with the server in the internal tables.
Contact your TUXEDO System Technical Support.
While the BBL is scanning the Bulletin Board, it will restart any dead servers
that are restartable. However, the restartsrv process detected that
the restartable server is still alive and running.
The Bulletin Board may be corrupted. Clean up the Bulletin Board
or kill the restartable server and let BBL restart the server.
Contact your TUXEDO System Technical Support.
While the BBL is scanning the Bulletin Board, it will restart any dead servers
that are restartable. However, the
restartsrv
process detected that
the server which was marked as non-restartable server is still alive and
running.
The Bulletin Board may be corrupted.
Clean up the Bulletin Board.
If the server is meant to be restartable, the server should be marked
as "RESTART=Y" in the
UBBCONFIG
file. Contact your TUXEDO System Technical Support.
ubbconfig (5)
500 ERROR: Shutting down bridge, serious network error
DESCRIPTION
ACTION
501 ERROR: Shutting down bridge, serious polling error
DESCRIPTION
ACTION
509 ERROR: Local message being nack'd by BRIDGE
DESCRIPTION
ACTION
511 ERROR: Invalid arguments passed to buildclient
DESCRIPTION
ACTION
SEE ALSO
512 ERROR: Cannot execute C compiler prog_name
DESCRIPTION
ACTION
SEE ALSO
516 WARN: buildserver -n option requires non-negative argument. Default setting to 0.
DESCRIPTION
ACTION
SEE ALSO
520 ERROR: Invalid arguments passed to buildserver
DESCRIPTION
ACTION
SEE ALSO
522 ERROR: buildserver cannot open the temporary output file, srcfile,.
DESCRIPTION
ACTION
SEE ALSO
523 WARN: Duplicate service, svc, (function func) is ignored in service dispatch table.
DESCRIPTION
ACTION
SEE ALSO
530 ERROR: Cannot execute prog_name
DESCRIPTION
ACTION
SEE ALSO
533 ERROR: Cannot be a cleanupsrv process - Uunixerr Uunixerr_val, errno errno_val
DESCRIPTION
ACTION
534 ERROR: Cannot be a cleanupsrv process
DESCRIPTION
ACTION
535 ERROR: Could not retrieve server
DESCRIPTION
ACTION
536 ERROR: Server to be cleaned up is still running.
DESCRIPTION
ACTION
537 ERROR: Failed to update server
DESCRIPTION
ACTION
538 INFO: Process pid still running - forcing termination (via SIGIOT)
DESCRIPTION
ACTION
539 ERROR: Failed to kill process pid - errmsg
DESCRIPTION
ACTION
540 ERROR: Cannot find Queue Table Entry
DESCRIPTION
ACTION
541 ERROR: Unable to decode message header
DESCRIPTION
ACTION
542 ERROR: Cannot find service to which to forward request
DESCRIPTION
ACTION
543 ERROR: Cannot forward message, sending it back
DESCRIPTION
ACTION
544 ERROR: Cannot forward message, sending it back
DESCRIPTION
ACTION
545 ERROR: Cannot encode message header
DESCRIPTION
ACTION
546 ERROR: Cannot decode message header
DESCRIPTION
ACTION
547 ERROR: Cannot forward message, sending it back
DESCRIPTION
ACTION
548 ERROR: Cannot forward message, sending it back
DESCRIPTION
ACTION
549 ERROR: Cannot decode message header
DESCRIPTION
ACTION
550 ERROR: Cannot remove server
DESCRIPTION
ACTION
551 INFO: server removed
DESCRIPTION
ACTION
552 WARN: Server cleanup - server vanished
DESCRIPTION
ACTION
555 ERROR: Unable to reply to pid
DESCRIPTION
ACTION
556 ERROR: Unable to reset server table entry
DESCRIPTION
ACTION
557 ERROR: Automatic Server Recovery failure; Server processes require manual intervention.
DESCRIPTION
ACTION
SEE ALSO
560 ERROR: Cannot be a restartsrv process because of an operating system error, Uunixerr_msgerrno_msg
DESCRIPTION
ACTION
561 ERROR: Cannot be a restartsrv process
DESCRIPTION
ACTION
562 ERROR: Cannot restart a server
DESCRIPTION
ACTION
563 ERROR: Cannot restart a server
DESCRIPTION
ACTION
564 ERROR: Server to be restarted, pid, is still running
DESCRIPTION
ACTION
565 ERROR: Server to be restarted, pid, is still running
DESCRIPTION
ACTION
SEE ALSO