A status was passed to the the update routine that was neither
suspended nor not suspended.
Check for corrupted shared memory or an invalid
IPCKEY
(wrong application).
malloc()
failed when an attempt was made to acquire space for a table large
enough to hold a long word entry for all the services in a server.
Check for corrupted shared memory, inappropriate sysgen memory or process
parameters, or if there are too many running processes.
malloc()
failed when an attempt was made to acquire space for a table large
enough to hold a long word entry for each service in a
MSSQ
set.
A status update was being attempted.
Check for corrupted shared memory, inappropriate sysgen memory or process
parameters, or if there are too many running processes.
An attempt was made to send a message to the
DBBL ,
and its whereabouts could not be ascertained either from the
BB
or from a
BRIDGE
process.
Check for a partitioned network, corrupted shared memory, or if all
administrative processes are running.
A message send failed.
The message send failure may have resulted
from a message type switch function failure, from an invalid message length,
or from a low level message send failure.
Check for a partitioned network, corrupted shared memory, if all the
administrative processes are running, or if the sysgen parameters for messages are
appropriate.
Two attempts were made to send a message to a
D(BBL)
and both attempts failed.
Either the recipient was not active (alive), or the sending of the message
send itself failed.
The message send failure may have resulted from a message
type switch function failure, from an invalid message length,
or from a low level message send failure.
Check for a partitioned network, corrupted shared memory, if all the
administrative processes are running, or if the sysgen parameters for messages are
appropriate.
The run server function, which continually dequeues messages (service requests),
called the server dispatch routine with a null message pointer.
This means that the dequeuing of a message failed.
System message resources may be corrupted.
The server dispatch function calls a high level service dispatch
which attempts to find the entry point address of the service
and cannot.
The server dispatch function records this error.
Shared memory may be corrupted, or the ipc application key is not correct.
The server dispatch function calls a high level service dispatch
which attempts to find the entry point address of the service
and cannot.
The server dispatch function conveys this error to
the caller via a message (reply).
If the message send fails, this message appears.
System message resources may be exhausted, the application may
be partitioned, or shared memory is corrupted.
The server dispatch function calls the service.
Control returning after this call is an indication that
tpreturn
failed (it does a longjmp and should
never return after the call), or
tpforward
failed (it gives up control to another server).
These are the only two ways a service can
surrender control after processing a service.
The stack in the service became corrupted.
Try running the service under a debugger.
tpsvrdone (3)
The process invoking the default server termination
function is a client (should be a server).
The default server termination library function was linked into a process not
identified in the SERVERS section of the configuration file,
or shared memory is corrupted.
tpservice (3)
INFO
This message indicates that the system-provided default server
exit routine was used in stopping the server.
No action required.
tpservice (3)
The
tpclose
function failed in the default server exit
function,
tpsvrdone .
An error occurred in closing the resource manager
associated with this server's group.
The
CLOSEINFO
parameter in the *GROUPS section of the configuration may not be correct,
or the resource manager may not be available.
tpservice (3)
The process invoking the default server initialization
function is not a System/T server.
The default server initialization library function was linked into a process not
identified in the SERVERS section of the configuration file,
or shared memory is corrupted.
tpservice (3)
INFO
This message indicates that the system-provided default server
initialization routine was used in starting the server.
No action required.
tpservice (3)
The service start routine, called by the start work routine
(which is called by the service dispatch routine),
failed because the dispatched message contained no service request name.
Verify that the application ipc key is correct, or
that not more than one application is using the same ipc key,
or some other failure occurred with the associated message queues.
The service start routine, called by the start work routine
(which is called by the service dispatch routine),
failed because the bulletin board entry for the requested service
function address contains a zero.
Verify that the application ipc key is correct, or
that not more than one application is using the same ipc key.
The service dispatch routine passed the service start work routine
a null pointer due to a
TPESYSTEM
error that occurred earlier.
This occurred in either a (D)BBL or server
and indicates that a corrupt or invalid message was received.
Verify that the correct machine types are set, or
that the application ipc key is correct, or
that not more than one application is using the same ipc key.
During the service dispatch, the service start function returned
null indicating a failure.
This could be due to a null service name appearing
in the dispatched message, or the requested service cannot be found,
or the bulletin board could not be locked.
Verify that the application ipc key is correct, or
that not more than one application is using the same ipc key,
or that the service is advertised.
When a service returns from dispatch, a flag is checked to see if
the service was started successfully.
If this flag is not set,
the above error message appears.
This flag is only turned on if the service starts,
and turned off only when the service done function completes.
Either the service never started or the
service done function was called more than once.
Check the ulog for additional information about server failures.
An internal function used to create a UNIX system message queue
for Inter-Process Communications failed.
Check with your UNIX System Administrator and increase the appropriate
MSG parameter for your system.
The possible parameters that may need to be increased are
MSGMAX ,
MSGMNB ,
MSGMNI ,
MSGSSZ ,
and
MSGSEG .
An internal function used to create a UNIX system message queue
for Inter-Process Communications failed.
Check with your UNIX System Administrator and increase the appropriate
MSG parameter for your system.
The possible parameters that may need to be increased are
MSGMAX ,
MSGMNB ,
MSGMNI ,
MSGSSZ ,
and
MSGSEG .
"TUXEDO Installation Guide"
An internal function used to remove a UNIX system message queue
for Inter-Process Communications failed.
The UNIX system function
msgctl()
returned an error.
Contact your UNIX System Administrator.
An internal function used to remove a UNIX System message queue
for Inter-Process Communications failed.
The UNIX System function
msgctl()
returned an error.
Contact your UNIX System Administrator.
The
TUXCONFIG
parameter defined in the TUXEDO System configuration file does not
match the current
TUXCONFIG
shell environment variable.
Set the
TUXCONFIG
variable in your current shell to match the value
defined in the configuration file and then export it.
Re-create the binary configuration file by executing
tmloadcf
and then
tmboot .
tmboot (1),
tmloadcf (1),
ubbconfig (5)
INFO
A server has died.
The TUXEDO System will attempt to clean or restart the server according
to the specification of the server in the configuration.
No action required.
ubbconfig (5)
A server had died.
The TUXEDO System was attempting to clean or restart the server according
to the specification of the server in the configuration.
The server was either non-restartable, or the generation count was exceeded.
Determine why the server is dying.
If required, modify the configuration file to increase the generation count
and/or make the server restartable.
ubbconfig (5)
A server had died.
The TUXEDO System was attempting to clean or restart the server according
to the specification of the server in the configuration.
The server was either non-restartable, or the generation count was exceeded.
Determine why the server is dying.
If required, modify the configuration file to increase the generation count
and/or make the server restartable.
ubbconfig (5)
A non-restartable server had died.
The TUXEDO System was attempting to clean up after the aforementioned
incident, but both the clean-up as well the removal of resources allocated
to the server failed.
Contact your TUXEDO System Technical Support.
The TUXEDO System attempted to update the server table that resides in
UNIX System shared memory.
The update was not successful.
Either the server information provided was invalid, or an attempted lock on
the TUXEDO System bulletin board was unsuccessful.
Contact your TUXEDO System Technical Support.
The TUXEDO System attempted to update the server table that resides in
UNIX System shared memory.
The update was not successful.
Either the server information provided was invalid, or an attempted lock on
the TUXEDO System bulletin board was unsuccessful.
Contact your TUXEDO System Technical Support.
The TUXEDO System attempted to clean up a system process, an action not
permitted at that point.
Contact your TUXEDO System Technical Support.
The TUXEDO System attempted to clean up a system process, an action not
permitted at that point.
Contact your TUXEDO System Technical Support.
The TUXEDO System attempted to clean up processes that are running on
a remote computer, and that operation is not permitted at that point.
Contact your TUXEDO System Technical Support.
The TUXEDO System is about to clean up a server that was defined to be
restartable.
No action required.
The TUXEDO System is about to clean up a server table entry.
No action required.
The TUXEDO System environment variable
TUXDIR
was not set.
Set and export the environment variable
TUXDIR
and repeat the operation.
"TUXEDO Installation Guide"
The TUXEDO System application was running on a multi-processor environment.
While attempting to use the
sysmulti()
function, an error was detected.
Contact your UNIX System Administrator.
500 ERROR: Invalid status given
DESCRIPTION
ACTION
501 ERROR: Memory allocation failure
DESCRIPTION
ACTION
502 ERROR: Memory allocation failure
DESCRIPTION
ACTION
503 ERROR: Cannot find DBBL
DESCRIPTION
ACTION
505 ERROR: Send/receive error on remote procedure call
DESCRIPTION
ACTION
506 ERROR: Send/receive error on remote procedure call
DESCRIPTION
ACTION
515 ERROR: Null message buffer, cannot dispatch service
DESCRIPTION
ACTION
516 ERROR: Unknown service request name
DESCRIPTION
ACTION
517 ERROR: Failed sending reply
DESCRIPTION
ACTION
518 ERROR: Service 'name' failed to call tpreturn or tpforward
DESCRIPTION
ACTION
SEE ALSO
521 ERROR: Clients cannot call tpsvrdone
DESCRIPTION
ACTION
SEE ALSO
522 INFO: Default tpsvrdone() function used
DESCRIPTION
ACTION
SEE ALSO
523 ERROR: tpclose failed
DESCRIPTION
ACTION
SEE ALSO
524 ERROR: Only servers allowed to call tpsvrinit
DESCRIPTION
ACTION
SEE ALSO
525 INFO: Default tpsvrinit() function used
DESCRIPTION
ACTION
SEE ALSO
530 ERROR: NULL service name, cannot dispatch service request
DESCRIPTION
ACTION
531 ERROR: Function address set to -1
DESCRIPTION
ACTION
532 ERROR: Invalid message pointer given
DESCRIPTION
ACTION
533 ERROR: Cannot execute service, address not known
DESCRIPTION
ACTION
534 ERROR: Work completed, cannot stop twice
DESCRIPTION
ACTION
536 ERROR: Unable to create request queue
DESCRIPTION
ACTION
537 ERROR: Unable to create reply queue
DESCRIPTION
ACTION
SEE ALSO
538 ERROR: Unable to remove request queue queue_id (errno=err_val)
DESCRIPTION
ACTION
539 ERROR: Unable to remove reply queue queue_id (errno=errno_val)
DESCRIPTION
ACTION
540 ERROR: TUXCONFIG environment value (string) does not match configuration file (string)
DESCRIPTION
ACTION
SEE ALSO
541 WARN: Server group_name/server_id terminated
DESCRIPTION
ACTION
SEE ALSO
542 WARN: Bulletin Board update error error_val
DESCRIPTION
ACTION
SEE ALSO
543 WARN: Bulletin Board update error error_val
DESCRIPTION
ACTION
SEE ALSO
544 ERROR: Unable to delete server group_name/server_id
DESCRIPTION
ACTION
545 ERROR: Unable to update Bulletin Board, error: error_val
DESCRIPTION
ACTION
546 ERROR: Unable to update Bulletin Board, error: error_val
DESCRIPTION
ACTION
547 ERROR: Unable to clean up BBL processes
DESCRIPTION
ACTION
548 ERROR: Unable to clean up BRIDGE processes
DESCRIPTION
ACTION
549 ERROR: Unable to clean up processes on remote node(s)
DESCRIPTION
ACTION
550 WARN: Cleaning up restartable server group_name/server_id
DESCRIPTION
ACTION
551 WARN: Cleaning up server group_name/server_id
DESCRIPTION
ACTION
552 WARN: TUXDIR environment variable not set
DESCRIPTION
ACTION
SEE ALSO
553 ERROR: Multi-processor operation sysmulti failed \(em errno=error_val
DESCRIPTION
ACTION