The service requested to be unadvertised is invalid.
Contact your TUXEDO System Technical Support.
tpunadvertise (3)
Make sure 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 process is currently not attached to the Bulletin Board so the service
cannot be offered.
Contact your TUXEDO System Technical Support.
Function called without proper parameters - null service to offer.
Contact your TUXEDO System Technical Support.
Function called with improper parameters - function name too long.
Contact your TUXEDO System Technical Support.
Function called with improper parameters - function address cannot be found.
Contact your TUXEDO System Technical Support.
Could not find structures/information associated with the
DBBL .
Contact your TUXEDO System Technical Support.
Could not find structures/information associated with the
BBL .
Contact your TUXEDO System Technical Support.
Sending of message to the
BBL/DBBL
to clean up and check status of local Bulletin Board failed.
Check prior messages or check if message queue is blocked. If queue is blocked,
system usage could be heavy and parameters may need to be tuned.
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
allocating space to store tmids.
Make sure 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 process that was attached to the BB died, so the BB is cleaning up.
No action required for BB, but you may want to investigate why the process died.
The process that was attached to the BB died and holds a user-level semaphore,
so the BB is cleaning up.
No action required for BB, but you may want to investigate why the process died.
An error occurred in cleaning up after a dead process.
Either the slot could
not be found, or a prior message indicates a semaphore error.
Contact your TUXEDO System Technical Support.
Either the machine does not have proper atomic increment for the user-level
semaphore, or there are too many signals coming to the process too quickly.
Contact your TUXEDO System Technical Support.
The process has held the lock on the BB for a longer than normal period of
time.
The process could still be alive, but incorrectly holding the
user-level semaphore.
Check the status of the process that is holding the lock.
There could be a problem with the process (hung),
or the process is holding the lock for too long a period of time while doing
work.
The server could not process the
ENVFILE
properly.
This includes not being
able to find, open, or read it.
Check the path of
ENVFILE ,
and the permissions and owner of the file.
ubbconfig (5)
The server could not process the parameters for a service specified in the
TUXCONFIG
file.
This includes a problem with loading the information from
the SERVICES section, or not understanding some of the parameters
(for example, buffer types.)
Check the SERVICES section of the
UBBCONFIG
file for correct parameters.
ubbconfig (5)
An instantiation of this server already exists and this is a duplicate.
It will exit gracefully.
Check that the server that you wish to start is correct.
If the server died unexpectedly or is hung,
the process needs to be killed if hung, and the
bulletin board must be given time to clean up after the killed process before
starting the server again.
A failure occurred when calling the initialization routine for the particular
type switch buffer.
Contact your TUXEDO System Technical Support.
buffer (3),
tuxtypes (5),
typesw (5)
A failure occurred when calling the reinitialization routine for the particular
type switch buffer.
Contact your TUXEDO System Technical Support.
buffer (3),
tuxtypes (5),
typesw (5)
A failure occurred when calling the uninitialization routine for the particular
type switch buffer.
Contact your TUXEDO System Technical Support.
buffer (3),
tuxtypes (5),
typesw (5)
The process is currently not attached to the Bulletin Board so it could not
access the type switch table.
Contact your TUXEDO System Technical Support.
The process tried to signal a remote process, and a message was sent to the
bridge process on the remote side to perform the fill for it.
The reply to indicate the success/failure of the operation did not
return before the operation timed out.
This timeout could be a sign of network congestion, but is not a specific
network failure, other than the operation did not return in time. If the
network is not a problem, then the timeout is too small for the speed with
which the signal request can be met.
The
semctl ()
call failed.
This is possibly due to the semaphore set being removed
or differing permissions on the semaphore.
The semaphore set was somehow removed.
If this does happen, the system will eventually fail.
Contact your TUXEDO System Technical Support.
An erroneous LMID
has been specified and an attempt to locate it has failed.
Check and edit the
UBBCONFIG
file such that all specified
LMIDs reference the correct machine.
ubbconfig (5)
The server has failed to join the application.
See surrounding messages for reasons for failure to join.
buildserver (1),
servopts (5)
A call to
tpsvrinit ()
failed.
This may easily be caused by an application-defined
tpsvrinit
function returning failure.
Check prior specific
tpsvrinit ()
messages or the application specific messages.
tpsvrinit (3)
A call to
tpsvrinit (),
although returning success, failed to receive all outstanding reply
messages and therefore has outstanding handles.
This is probably caused
by an application-defined
tpsvrinit
function.
Check prior specific
tpsvrinit ()
messages or the application specific messages.
tpsvrinit (3)
The connection with
tmboot
was lost by the forking process.
If on the same node where
tmboot
is running, the pipe with
tmboot
was lost and may be due to the
tmboot
process being killed.
If on a remote node, the pipe to the
TAGENT
process was lost, which may be due to the
TAGENT
process being killed.
No action required, although the cause of tmboot/TAGENT
dying should be investigated if not known.
tmboot (1)
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
copying the arguments to
CLOPT
as the server tries to join the application.
Make sure 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.
An attempt dynamically to allocate memory from the operating system using
malloc ()
failed while
copying the arguments to
CLOPT
as the server tries to join the application.
Make sure 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.
Multiple
-A
options were specified to the server in the
CLOPT
line of the
UBBCONFIG
file.
Check the
CLOPT
option in the configuration file.
ubbconfig (5),
servopts (5)
The queue address, as specified to the server through the
-Q
option of
CLOPT ,
is non-numeric.
Check the address specified for the
-Q
option in the configuration file.
ubbconfig (5),
servopts (5)
The lock argument, as specified to the server through the
-l
option in
CLOPT ,
is invalid.
It must be one of
"'t' (TEXTLOCK),"
"'d' (DATALOCK),"
'b'
or
"'p' (PROCLOCK)."
The argument is ignored and is set to
'p'
for
PROCLOCK .
Check the lock argument for the
-l
option in
CLOPT
in the configuration file.
ubbconfig (5),
servopts (5)
in the System/T reference manual,
plock (2)
in UNIX system reference manuals
An attempt to lock the process in core has failed.
This was requested by setting the lock option,
-l ,
on the
CLOPT
option to the server in the configuration file.
The error can occur when the server not being run as
super-user, the requested lock is already on the process, or the system
is out of memory.
Make sure the server is being started as super-user (and that the
tmboot
process is running as super-user).
If the application can run its own
code (tpsvrinit()) first, it might also have put a lock on the process.
ubbconfig (5),
servopts (5)
in the System/T reference manual,
plock (2)
in UNIX system reference manuals
An attempt to change the priority of the process has failed.
This was requested by setting the
-n
option on the
CLOPT
option to the server in the configuration file.
This can be caused by the option to
-n
being negative or greater than 39, and not super-user.
Check that the argument to the
-e
option of
CLOPT
is correct in the configuration file.
ubbconfig (5),
servopts (5)
in the System/T reference manual,
nice (2)
in UNIX system reference manuals
An attempt to open the file for
stderr
failed.
This file may have been specified by the
-e
option on the
CLOPT
option to the server in the configuration file.
This can be caused by the inability to access the path
given as the argument to the
-e
option.
Check that the argument to the
-e
option of
CLOPT
is correct in the configuration file.
ubbconfig (5),
servopts (5)
200 ERROR: Invalid service information given
DESCRIPTION
ACTION
SEE ALSO
201 ERROR: Memory allocation failure
202 ERROR: No bulletin board
DESCRIPTION
ACTION
203 ERROR: Invalid service information given, NULL name
DESCRIPTION
ACTION
205 ERROR: Invalid service information given, function name too long
DESCRIPTION
ACTION
206 ERROR: Invalid service information given, bad function address
DESCRIPTION
ACTION
210 ERROR: tmbbclean failed, couldn't find DBBL
DESCRIPTION
ACTION
211 ERROR: tmbbclean failed, couldn't find BBL
DESCRIPTION
ACTION
212 ERROR: tmbbclean failed, message send/receive error
DESCRIPTION
ACTION
213 ERROR: Memory allocation failure
DESCRIPTION
ACTION
216 WARN: Process pid died; removing from BB
DESCRIPTION
ACTION
217 WARN: pid=pid died leaving BB locked; cleaning up
DESCRIPTION
ACTION
218 ERROR: Error cleaning BB owner
DESCRIPTION
ACTION
219 WARN: BB owned by pid, but not locked
DESCRIPTION
ACTION
220 WARN: BB lock appears stuck: held by pid=pid
DESCRIPTION
ACTION
221 ERROR: Error putting ENVFILE filename into environment
DESCRIPTION
ACTION
SEE ALSO
222 ERROR: Cannot get service parms for server
DESCRIPTION
ACTION
SEE ALSO
223 WARN: Duplicate server
DESCRIPTION
ACTION
226 ERROR: Type switch buffer initialization routine _tminitbuf failure
DESCRIPTION
ACTION
SEE ALSO
228 ERROR: Type switch buffer reinitialization routine _tmreinitbuf failure
DESCRIPTION
ACTION
SEE ALSO
229 ERROR: Type switch buffer uninitialization routine _tmuninitbuf failure
DESCRIPTION
ACTION
SEE ALSO
230 ERROR: Buffer type tables not available
DESCRIPTION
ACTION
236 ERROR: Remote tmnwkill timed out count secs
DESCRIPTION
ACTION
237 ERROR: semctl err: errno = errno_val, key = key_val
DESCRIPTION
ACTION
245 WARN: Invalid LMID specification: PMID=mid
DESCRIPTION
ACTION
SEE ALSO
248 ERROR: System init function failed, Uunixerr = errno_val
DESCRIPTION
ACTION
SEE ALSO
250 ERROR: tpsvrinit() failed
DESCRIPTION
ACTION
SEE ALSO
251 ERROR: tpsvrinit() failed with outstanding message handles
DESCRIPTION
ACTION
SEE ALSO
252 WARN: Cannot synchronize with tmboot...continuing
DESCRIPTION
ACTION
SEE ALSO
253 ERROR: Memory allocation failure
DESCRIPTION
ACTION
254 ERROR: Memory allocation failure
DESCRIPTION
ACTION
255 INFO: Duplicate -A option ignored
DESCRIPTION
ACTION
SEE ALSO
256 WARN: Queue address must be numeric
DESCRIPTION
ACTION
SEE ALSO
257 WARN: Invalid lock argument, setting to PROCLOCK
DESCRIPTION
ACTION
SEE ALSO
258 WARN: Memory lock plock() failed
DESCRIPTION
ACTION
SEE ALSO
259 WARN: nice() failed
DESCRIPTION
ACTION
SEE ALSO
260 WARN: Cannot open path as stderr, Uunixerr = Uunixerr
DESCRIPTION
ACTION
SEE ALSO