LIBTUX Messages 200-299
|
|
|
200
ERROR: Invalid service information given
Description
The service requested to be unadvertised is invalid.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
tpunadvertise(3c)
201
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed.
Action
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.
202
ERROR: No bulletin board
Description
The process is currently not attached to the Bulletin Board so the service cannot be offered.
Action
Contact your BEA TUXEDO system Technical Support.
203
ERROR: Invalid service information given, NULL name
Description
Function called without proper parameters - null service to offer.
Action
Contact your BEA TUXEDO system Technical Support.
205
ERROR: Invalid service information given, function name too long
Description
Function called with improper parameters - function name too long.
Action
Contact your BEA TUXEDO system Technical Support.
206
ERROR: Invalid service information given, bad function address
Description
Function called with improper parameters - function address cannot be found.
Action
Contact your BEA TUXEDO system Technical Support.
210
ERROR: tmbbclean failed, couldn't find DBBL
Description
Could not find structures/information associated with the DBBL.
Action
Contact your BEA TUXEDO system Technical Support.
211
ERROR: tmbbclean failed, couldn't find BBL
Description
Could not find structures/information associated with the BBL.
Action
Contact your BEA TUXEDO system Technical Support.
212
ERROR: tmbbclean failed, message send/receive error
Description
Sending of message to the BBL/DBBL to clean up and check status of local Bulletin Board failed.
Action
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.
213
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while allocating space to store tmids.
Action
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.
216
WARN: Process pid died; removing from BB
Description
The process that was attached to the BB died, so the BB is cleaning up.
Action
No action required for BB, but you may want to investigate why the process died.
217
WARN: pid=pid died leaving BB locked; cleaning up
Description
The process that was attached to the BB died and holds a user-level semaphore, so the BB is cleaning up.
Action
No action required for BB, but you may want to investigate why the process died.
218
ERROR: Error cleaning BB owner
Description
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.
Action
Contact your BEA TUXEDO system Technical Support.
221
ERROR: Error putting ENVFILE filename into environment
Description
The server could not process the ENVFILE properly. This includes not being able to find, open, or read it.
Action
Check the path of ENVFILE, and the permissions and owner of the file.
See Also
ubbconfig(5)
222
ERROR: Cannot get service parms for server
Description
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.)
Action
Check the SERVICES section of the UBBCONFIG file for correct parameters.
See Also
ubbconfig(5)
223
WARN: Duplicate server
Description
An instantiation of this server already exists and this is a duplicate. It will exit gracefully.
Action
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.
230
ERROR: Buffer type tables not available
Description
The process is currently not attached to the Bulletin Board so it could not access the type switch table.
Action
Contact your BEA TUXEDO system Technical Support.
236
ERROR: Remote tmnwkill timed out count secs
Description
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.
Action
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.
237
ERROR: semctl err: errno = errno_val, key = key_val
Description
The semctl() call failed. This is possibly due to the semaphore set being removed or differing permissions on the semaphore.
Action
The semaphore set was somehow removed. If this does happen, the system will eventually fail. Contact your BEA TUXEDO system Technical Support.
245
WARN: Invalid LMID specification: PMID=mid
Description
An erroneous LMID has been specified and an attempt to locate it has failed.
Action
Check and edit the UBBCONFIG file such that all specified LMIDs reference the correct machine.
See Also
ubbconfig(5)
248
ERROR: System init function failed, Uunixerr = errno_val
Description
The server has failed to join the application.
Action
See surrounding messages for reasons for failure to join.
See Also
buildserver(1), servopts(5)
250
ERROR: tpsvrinit() failed
Description
A call to tpsvrinit() failed. This may easily be caused by an application-defined tpsvrinit function returning failure.
Action
Check prior specific tpsvrinit() messages or the application specific messages.
See Also
tpsvrinit(3c)
251
ERROR: tpsvrinit() failed with outstanding message handles
Description
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.
Action
Check prior specific tpsvrinit() messages or the application specific messages.
See Also
tpsvrinit(3c)
252
WARN: Cannot synchronize with tmboot...continuing
Description
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.
Action
No action required, although the cause of tmboot/TAGENT dying should be investigated if not known.
See Also
tmboot(1)
253
ERROR: Memory allocation failure
Description
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.
Action
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.
254
ERROR: Memory allocation failure
Description
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.
Action
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.
255
INFO: Duplicate -A option ignored
Description
Multiple -A options were specified to the server in the CLOPT line of the UBBCONFIG file.
Action
Check the CLOPT option in the configuration file.
See Also
ubbconfig(5), servopts(5)
256
WARN: Queue address must be numeric
Description
The queue address, as specified to the server through the -Q option of CLOPT, is non-numeric.
Action
Check the address specified for the -Q option in the configuration file.
See Also
ubbconfig(5), servopts(5)
257
WARN: Invalid lock argument, setting to PROCLOCK
Description
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.
Action
Check the lock argument for the -l option in CLOPT in the configuration file.
See Also
ubbconfig(5), servopts(5) in the System/T reference manual, plock(2) in UNIX system reference manuals
258
WARN: Memory lock plock() failed
Description
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.
Action
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.
See Also
ubbconfig(5), servopts(5) in the System/T reference manual, plock(2) in UNIX system reference manuals
259
WARN: nice() failed
Description
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.
Action
Check that the argument to the -e option of CLOPT is correct in the configuration file.
See Also
ubbconfig(5), servopts(5) in the System/T reference manual, nice(2) in UNIX system reference manuals
260
WARN: Cannot open path as stderr, Uunixerr = Uunixerr
Description
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.
Action
Check that the argument to the -e option of CLOPT is correct in the configuration file.
See Also
ubbconfig(5), servopts(5)
261
WARN: Cannot open path as stdout: Uunixerr = Uunixerr
Description
An attempt to open the file for stout failed. This file may have been specified by the -o 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 -o option.
Action
Check that the argument to the -o option of CLOPT is correct in the configuration file.
See Also
ubbconfig(5), servopts(5)
262
INFO: Standard main starting
Description
The arguments have been successfully processed, and joining the application will continue.
Action
No action required.
263
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while setting up buffers to advertise the services of the application as the server tries to join the application.
Action
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.
264
ERROR: Cannot set server group/id
Description
This cannot happen because code changed to use a local variable, not a passed-in variable.
Action
Contact your BEA TUXEDO system Technical Support.
267
INFO: Duplicate advertisement of service svcname ignored
Description
A request to advertise the same service a second time is ignored.
Action
Check the configuration file for multiple occurrences of the service on the -s option.
See Also
ubbconfig(5), servopts(5)
268
ERROR: Failed to stop serving
Description
The server did not properly shut down.
Action
There may be prior messages to describe the problem. In any case, the BBL should clean up after the process.
270
ERROR: Restart sync error errno
Description
An internal error occurred during a restart of a process. An acknowledgment that the process was restarted was never received.
Action
Contact your BEA TUXEDO system Technical Support.
271
ERROR: System lock semop failure, key = key (errno = errno)
Description
In an attempt to lock the bulletin board, a call to semop(2) failed.
Action
Examine the value returned in the UNIX System errno, and attempt to fix the problem described by the errno. If unable to do so, contact your BEA TUXEDO system Technical Support.
272
ERROR: System unlock semop failure, key = key (errno = errno)
Description
In an attempt to unlock the bulletin board, a call to semop(2) failed.
Action
Examine the value returned in the UNIX System errno and attempt to fix the problem described by the errno. If unable to do so, contact your BEA TUXEDO system Technical Support.
294
ERROR: function: FSCONFIG not or incorrectly set
Description
The variable FSCONFIG is either not set or has been incorrectly set.
Action
Check and edit the UBBCONFIG file and make sure the FSCONFIG environment variable is set correctly.
See Also
ubbconfig(5)
295
ERROR: funcname: corrupted VTOC or different release
Description
An attempt to access the VTOC has failed because the existing VTOC has either been corrupted or was created by a different release of the TUXEDO System.
Action
Contact your BEA TUXEDO system Technical Support.
296
ERROR: funcname: VTOC not initialized
Description
An attempt to access the VTOC has failed because the existing VTOC has not been properly initialized.
Action
Contact your BEA TUXEDO system Technical Support.
297
ERROR: funcname: no space can be allocated for disk table or for VTOC/UDL
Description
An attempt to allocate space within the VTOC has failed because there are no more available slots.
Action
Contact your BEA TUXEDO system Technical Support.
298
ERROR: funcname: Read beyond initialized file boundary.
Description
An attempt to access information in the VTOC has failed because the read has gone past the set boundaries of the VTOC.
Action
Contact your BEA TUXEDO system Technical Support.
299
ERROR: funcname: Write beyond initialized file boundary.
Description
An attempt to write information to the VTOC has failed because the write has gone past the set boundaries of the VTOC.
Action
Contact your BEA TUXEDO system Technical Support.
 |
 |
 |