Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

LIBTUX Messages 1200-1299

1200	ERROR: Cannot re-attach BB - process lost its BB slot while detached
	Description	The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to the bulletin board, the context for the client or server does not match. This indicates that either the bulletin board is corrupted or the application was re-booted while the client or server was not attached.
	Action	Check with the administrator to see if the application was re-booted. Contact your BEA TUXEDO system Technical Support.
1201	ERROR: Cannot re-attach BB - magic number mismatch
	Description	The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to the bulletin board, the wrong magic number was found. This indicates that either the bulletin board is corrupted or a new release of the application was booted while the client or server was not attached.
	Action	Contact your BEA TUXEDO system Technical Support.
1202	ERROR: Cannot re-attach BB - wrong release of software
	Description	The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to the bulletin board, the wrong release was found. This indicates that either the bulletin board is corrupted or a new release of the application was booted while the client or server was not attached.
	Action	Contact your BEA TUXEDO system Technical Support.
1203	WARN: Cannot override system default access method PROTECTED
	Description	The application called tpinit with the TPSA_FASTPATH flag set, but the configuration has SYSTEM_ACCESS set to PROTECTED,NO_OVERRIDE. tpinit will ignore this flag and run in TPSA_PROTECTED mode.
	Action	Change the application to use TPSA_PROTECTED mode, or contact the administrator about allowing overriding of the SYSTEM_ACCESS mode.
	See Also	tpinit(3c), ubbconfig(5)
1204	WARN: Cannot override system default access method FASTPATH
	Description	The application called tpinit with the TPSA_PROTECTED flag set, but the configuration has SYSTEM_ACCESS set to FASTPATH, NO_OVERRIDE. tpinit will ignore this flag and run in TPSA_FASTPATH mode.
	Action	Change the application to use TPSA_FASTPATH mode, or contact the administrator about allowing overriding of the SYSTEM_ACCESS mode.
	See Also	tpinit(3c), ubbconfig(5)
1205	WARN: Unable to open MACHINE ENVFILE filename for reading
	Description	In the process of booting a server, the ENVFILE specified in the MACHINES section on the configuration could not be opened for reading. The server will still be booted, but the environment will not be modified.
	Action	Check the machine environment file to see that it exists in the correct directory with the right name and with read permission for the configuration administrator. It may be necessary to shut down the server and re-start it with the correct environment.
	See Also	tmboot(1), tmshutdown(1), ubbconfig(5)
1214	ERROR: Cannot perform deferred type/subtype resolution in global tables (type/subtype)
	Description	The application is running with the TMPROTECTED SYSTEM_ACCESS value. An operation was done on a typed buffer, but checking of the type/subtype was deferred. When the checking was finally done, the type/subtype was not recognized by the system.
	Action	Contact your BEA TUXEDO system Technical Support.
1219	ERROR: Invalid parameter
	Description	An invalid parameter was passed to an internal routine during security processing.
	Action	Contact your BEA TUXEDO system Technical Support.
1220	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed during security processing.
	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.
1222	ERROR: Unable to open TUXCONFIG file to Resources section
	Description	While trying to read the configuration file during security processing, the program was unable to open the RESOURCES section.
	Action	Contact your BEA TUXEDO system Technical Support.
1223	ERROR: Unable to open Resources section of TUXCONFIG file
	Description	While trying to read the configuration file during security processing, the program was unable to read the RESOURCES section.
	Action	Contact your BEA TUXEDO system Technical Support.
1224	ERROR: Possibly corrupted key in database
	Description	The system key created and stored in the file APPDIR/.adm/.keydb for use by the WSH in security applications has become corrupted. This error disables the WSH from being able to handle new incoming connections from workstation clients. Note that current implementations of the security interfaces within the BEA TUXEDO system will not generate this error, but future ones may if they have more stringent requirements on the key characteristics used for encryption.
	Action	Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key information correctly.
	See Also	BEA TUXEDO Administrator's Guide
1225	ERROR: Error while decrypting password
	Description	The security information stored and accessed by the TUXEDO System/T has become corrupted and cannot be processed correctly by the WSH in order to allow workstation clients to access the application. This error disables the WSH from being able to handle new incoming connections from workstation clients.
	Action	Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key information correctly. If this does not clear the problem, then remove TUXCONFIG and security information from all sites and reboot.
	See Also	BEA TUXEDO Administrator's Guide
1226	ERROR: Invalid password in TUXCONFIG file
	Description	The security information stored and accessed by the TUXEDO System/T has become corrupted and cannot be processed correctly by the WSH in order to allow workstation clients to access the application. This error disables the WSH from being able to handle new incoming connections from workstation clients.
	Action	Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key information correctly. If this does not clear the problem, then remove TUXCONFIG and security information from all sites and reboot.
	See Also	BEA TUXEDO Administrator's Guide
1227	ERROR: Unable to open TUXCONFIG file to read MACHINES section
	Description	While trying to read the application password, the program was unable to find the *MACHINES section in the configuration file. This should not occur.
	Action	Contact your BEA TUXEDO system Technical Support.
1233	ERROR: Unable to shutdown, clients/servers still attached
	Description	The BBL was unable to shut itself down because clients and/or servers are still attached to the Bulletin Board. It is the BBL 's responsibility to clean up and remove the Bulletin Board prior to terminating. However, the Bulletin Board was not removed since clients and/or servers were still attached to it.
	Action	First, make sure all application servers have been shut down prior to attempting to shut down the BBL. The tmadmin(1) printserver (psr) command can be used to print server statistics. Shut down all application servers on that site using tmshutdown(1) with the -l option. Second, make sure all application clients have terminated. The tmadmin(1) printclient (pclt) command can be used to print client statistics. The application administrator can force the BBL to shut down, by invoking the tmshutdown(1) command with the -c option. The -c option will allow for the BBL to be shut down even if clients are still attached to the Bulletin Board.
1236	WARN: TMDEBUG contains non-numeric characters in first number
	Description	The format of the TMDEBUG variable is invalid. The allowable formats for TMDEBUG are: number number:regular_expression number1-number2 number1-number2:regular_expression If number is specified, debugging messages with levels less than or equal to number will be printed. If number1 and number2 are specified, debugging messages with levels between number1 and number2, inclusive, will be printed. If regular_expression is appended to the numeric part of the argument, only those messages matching regular_expression will be printed.
	Action	Make sure the TMDEBUG variable is valid. TMDEBUG may be incorrectly set and exported in the environment. It may also be incorrectly set in an environment file using the ENVFILE parameter in the *MACHINES or *SERVERS section of the configuration file.
	See Also	ubbconfig(5)
1237	WARN: TMDEBUG contains non-numeric characters in 2nd part of range
	Description	See Message 1236 above.
	Action	See Message 1236 above.
1238	WARN: TMDEBUG regular expression invalid. Ignoring regular expression.
	Description	See Message 1236 above.
	Action	See Message 1236 above.
1239	ERROR: Failed to change group via setgid()
	Description	The calling process failed to change its group ID while trying to become the administrator. The effective user ID of the calling process is super-user.
	Action	Make sure the calling process has permission to change its group ID to the group ID the BEA TUXEDO system application administrator belongs to.
	See Also	setgid(2) in UNIX reference manuals
1240	ERROR: Failed to change user via setuid()
	Description	The calling process failed to change its user ID while trying to become the administrator. The effective user ID of the calling process is super-user.
	Action	Make sure the calling process has permission to change its user ID to the user ID the BEA TUXEDO system application administrator belongs to.
	See Also	setuid(2) in UNIX system reference manuals
1241	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.
1242	ERROR: Invalid table type
	Description	The calling process failed to open a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for opening configuration tables.
	Action	Contact your BEA TUXEDO system Technical Support.
1243	ERROR: Invalid table type
	Description	The calling process failed to close a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for closing configuration tables.
	Action	Contact your BEA TUXEDO system Technical Support.
1244	ERROR: Invalid table type
	Description	The calling process failed to seek a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for seeking configuration tables.
	Action	Contact your BEA TUXEDO system Technical Support.
1245	ERROR: Invalid table type
	Description	The calling process failed to write a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for writing configuration tables.
	Action	Contact your BEA TUXEDO system Technical Support.
1246	ERROR: More than one wild card in entry ranges
	Description	The calling process found more than one wild card in the ranges string, ranges, while parsing the string based on a packed decimal field type.
	Action	Make sure there is no more than one wild card in the ranges string ranges.
	See Also	ubbconfig(5)
1247	ERROR: Cannot have a '-' in front of MAX or MIN
	Description	While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry.
	Action	Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX.
	See Also	ubbconfig(5)
1248	ERROR: Cannot have a '-' in front of MAX or MIN
	Description	While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry.
	Action	Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX.
	See Also	ubbconfig(5)
1249	ERROR: Cannot have a '-' in front of MAX or MIN
	Description	While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry.
	Action	Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX.
	See Also	ubbconfig(5)
1250	ERROR: Cannot have a '-' in front of MAX or MIN
	Description	While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry.
	Action	Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX.
	See Also	ubbconfig(5)
1251	ERROR: Cannot have a '-' and a '+' sign in front of a number
	Description	While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry.
	Action	Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not have '-+' in front of number.
	See Also	ubbconfig(5)
1253	ERROR: shmat failure: errno = errno, key = ipckey
	Description	The calling process failed to create/attach to the Bulletin Board while invoking the shmat(2) system call. shmat(2) returned with errno set to errno.
	Action	shmat(2) will fail and not attach to the Bulletin Board if one or more of the following are true: An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO system Technical Support. The operation was denied to the calling process (EACCESS). In this case make sure the calling process has permission to attach to the Bulletin Board. The available data space is not large enough to accommodate the shared memory segment (ENOMEM). In this case the system administrator may have to reconfigure the UNIX kernel to allow for more shared memory space. The number of shared memory segments attached to the calling process would exceed the system-imposed limit (EMFILE). In this case the system administrator may have to reconfigure the UNIX kernel to allow for more shared memory space.
	See Also	shmat(2) in UNIX reference manuals
1254	ERROR: shmget(creat) failure: errno = errno, key = key
	Description	The calling process failed to create/get to the Bulletin Board while invoking the shget(2) system call with key set to key and the IPC_CREAT flag set. shmget(2) returned with errno set to errno.
	Action	shmget(2) will fail if one or more of the following are true: An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO system Technical Support. One specific case where this occurs is if the OS value for SHMMIN is set too high (in general, it should always be set to 1). The operation was denied to the calling process (EACCESS). In this case make sure the calling process has permission to create/attach to the Bulletin Board. A shared memory identifier does not exist for key (ENOENT). In this case contact your BEA TUXEDO system Technical Support. The system limit on shared memory identifiers was reached (ENOSPC). In this case the system administrator may have to reconfigure the UNIX kernel to allow for more shared memory identifiers. The amount of available memory is not sufficient (ENOMEM). In this case the system administrator may have to reconfigure the UNIX kernel to allow for more shared memory space.
	See Also	shmget(2) in UNIX reference manuals
1255	ERROR: shmctl(chown) failure: errno = errno, key = key
	Description	The calling process failed to perform a shared memory control operation on the Bulletin Board while invoking the shmctl(2) system call with the IPC_SET flag set. The calling process was unable to set the user ID, group ID, and mode of the Bulletin Board. shmctl(2) returned with errno set to errno.
	Action	shmctl(2) will fail if one or more of the following are true: An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO system Technical Support. The operation was denied to the calling process (EACCESS). In this case make sure the calling process has permission to perform operations on the Bulletin Board. Not enough memory (ENOMEM). In this case the system administrator may have to reconfigure the UNIX kernel to allow for more shared memory space.
	See Also	shmctl(2) in UNIX reference manuals
1256	ERROR: shmat failure: errno = errno, id = id
	Description	The calling process failed to create/attach to the Bulletin Board while invoking the shmat(2) system call. shmat(2) was called with shmid set to id and returned with errno set to errno.
	Action	shmat(2) will fail and not attach to the Bulletin Board if one or more of the following are true: An invalid argument was passed (EINVAL). In this case contact your BEA TUXEDO System Technical Support. The operation was denied to the calling process (EACCESS). In this case make sure the calling process has permission to attach to the Bulletin Board. The available data space is not large enough to accommodate the shared memory segment (ENOMEM). In this case the system administrator may have to reconfigure the UNIX kernel to allow for more shared memory space. The number of shared memory segments attached to the calling process would exceed the system-imposed limit (EMFILE). In this case the system administrator may have to reconfigure the UNIX kernel to allow for more shared memory space.
	See Also	shmat(2) in UNIX reference manuals
1257	ERROR: func: bad value of _gp_fsoffset variable or supplied offset
	Description	An invalid VTOC file system offset was passed to func.
	Action	Make sure the FSOFFSET environment variable is set correctly. If the problem persists after resetting the FSOFFSET environment variable, contact your BEA TUXEDO system Technical Support.
1259	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.
1260	ERROR: Service request problem: func
	Description	The calling process failed in a BEA TUXEDO system internal function called func while trying to add a new service table entry.
	Action	Look through the userlog for other messages related to this failure. If found, refer to the appropriate system messages. If not, consult your BEA TUXEDO system Technical Support.
1261	ERROR: Service request problem: string
	Description	The calling process failed in a BEA TUXEDO system internal function because of string while trying to add a new service table entry.
	Action	Look through the userlog for other messages related to this failure. If found, refer to the appropriate system messages. If not, consult your BEA TUXEDO system Technical Support.
1262	ERROR: Permission denied to boot server
	Description	When security is turned on, that is, the SECURITY parameter is specified in the RESOURCES section of the application configuration file, a server may only be booted by the administrator of the application. This means that the user ID and group ID of the user attempting to boot the server should match the user ID and group ID of the application administrator. If they do not match, the server will fail to boot and exit gracefully.
	Action	Make sure that the TUXCONFIG environment variable is set correctly. If it is pointing to the right application, make sure that the UID and GID parameters are properly set in the RESOURCES section of the configuration file. Also verify that the ID of the user that is attempting to boot the server is set correctly using the UNIX id(1) command.
	See Also	ubbconfig(5)
1263	ERROR: tpsvrinit() returned in transaction mode
	Description	The application server has been placed in transaction mode during its initialization in tpsvrinit(). tpsvrinit() returned while still in transaction mode. The BEA TUXEDO system will therefore abort the outstanding transaction and the application server will exit gracefully. Since tpsvrinit() is called after the server has joined the application, transactions may be defined in this routine. However, the transaction must have completed prior to tpsvrinit() returning.
	Action	Verify that if a transaction is started in tpsvrinit(), it should also be completed prior to tpsvrinit() returning. If tpbegin() is called in tpsvrinit(), make sure that either tpabort() or tpcommit() is also called.
	See Also	tpservice(5c)
1264	WARN: Ticket stuck high - retrying
	Description	While monitoring the integrity of the Bulletin Board, the BBL found a BEA TUXEDO system user level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again.
	Action	No action required.
1265	WARN: Ticket stuck high - resetting
	Description	While monitoring the integrity of the Bulletin Board, the BBL found a BEA TUXEDO system user level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. The BBL managed to lock the Bulletin Board, transfer the ownership of the semaphore, and adjust the statistics.
	Action	No action required.
1266	WARN: Ticket stuck high - retrying
	Description	While monitoring the integrity of the Bulletin Board, the BBL found a BEA TUXEDO system user level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again.
	Action	No action required.
1274	ERROR: tpreturn xa_end TMFAIL returned errstring
	Description	During a call to tpreturn() in transaction mode with the TPFAIL flag, a call to xa_end with the TMFAIL flag failed with the specified errstring.
	Action	Check the error reporting mechanism for the associated resource manager to determine the cause of the problem.
1275	ERROR: tpreturn TPESVCERR xa_end TMSUCCESS returned errstring
	Description	During a call to tpreturn() in transaction mode with the TPSUCCESS flag, a call to xa_end with the TMSUCCESS flag failed with the specified errstring. A service error will be returned to the client.
	Action	Check the error reporting mechanism for the associated resource manager to determine the cause of the problem.
1276	WARN: Forcing deletion of table entries for server group/id
	Description	A server died and the administrative processes were unable to restart or clean up after the server. The server and service entries for the server will be deleted from the bulletin board.
	Action	No action required.
1277	ERROR: NULL input buffer not allowed for service 'service_name', which uses routing
	Description	An application program passed a NULL input buffer to the service service_name, which is defined in the configuration file as using routing. Since the null buffer is not a valid type to perform routing on, the service call was rejected with an error.
	Action	Recode the service call that resulted in the error so that the input buffer is of one of the types specified in the routing criterion that is associated with this service in the UBBCONFIG file.
	See Also	tpcall(5c), ubbconfig(5)
1278	ERROR: Cannot join application - permission denied
	Description	An ATMI function was called in a client before calling tpinit(), and an attempt to join the application failed. The client cannot join the application because it does not have permission to do so or because it did not supply the correct application password. Permission may be denied based on an invalid application password, failure to pass application specific authentication, or use of restricted names.
	Action	This is an application error. If the application has security turned on, then tpinit() must be called explicitly with a TPINIT buffer supplying a valid password before calling any other ATMI functions.
	See Also	tpinit(5c)
1279	ERROR: Cannot join application - accesser limit exceeded
	Description	An ATMI function was called in a client before calling tpinit(), and an attempt to join the application failed. The client cannot join the application because of space limitations.
	Action	This is a application configuration problem. The number of accessers is too small and must be reconfigured to allow more clients.
	See Also	ubbconfig(5)
1285	WARN: tpreturn message send blocked, will try file transfer
	Description	A server process encountered a message queue blocking condition when returning a message to the client via tpreturn().
	Action	The system will automatically attempt to return the message using a temporary file. Performance may be degraded if this occurs frequently. Check the kernel parameters related to message queue size, and increase them if necessary.
	See Also	BEA TUXEDO Installation Guide and Message No. 1286 below.
1286	ERROR: tpreturn could not send reply errno_val
	Description	A server process encountered an error when returning a reply message to the client via tpreturn(). The reply message has been discarded, which may cause the client to time out or block forever waiting for the lost message. The cause may be that the message queue size is too small to receive the reply.
	Action	Check the kernel parameters related to message queue size, and increase them if necessary.
	See Also	BEA TUXEDO Installation Guide
1287	ERROR: Failure to allocate memory for file message transfer, size size
	Description	When receiving a message that was transferred in a file because it was too large to put on a message queue, tprealloc() failed to allocate a typed buffer big enough to hold the message.
	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.
1288	ERROR: File transfer creat failed, file=filename, errno=errno_val
	Description	The UNIX kernel call creat() failed on filename. This temporary file was being created to transfer a large message between two BEA TUXEDO system processes on the same machine.
	Action	Check temporary directory's permissions. Check disk space and inode counts for the temporary file system.
1289	ERROR: File transfer write failed, file=filename, errno=errno_val
	Description	The UNIX kernel call write() failed on filename. This temporary file was being written to transfer a large message between two BEA TUXEDO system processes on the same machine.
	Action	Check directory and file permissions for the temporary files. Check disk space and inode counts for the temporary file system.
1290	ERROR: File transfer close failed, file=filename, errno=errno_val
	Description	The UNIX kernel call close() failed on filename after it had been written. This temporary file was being used to transfer a large message between two BEA TUXEDO system processes on the same machine.
	Action	Check disk space and inode counts for the temporary file system.
1291	ERROR: File transfer fstat failed, file=filename, errno=errno_val
	Description	The UNIX kernel call fstat() failed on filename. This temporary file was being used to transfer a large message between two System/T processes on the same machine.
	Action	Check directory and file permissions for the temporary files, disk space and inode counts for the temporary file system, the PERM parameter in the RESOURCES section of the configuration file, and check for any cron job or other process that might be deleting files from the temporary file directory.
1292	ERROR: File transfer open failed, file=filename, errno=errno_val
	Description	The UNIX kernel call open() failed on filename. This temporary file was being used to transfer a large message between two System/T processes on the same machine.
	Action	Check directory and file permissions for the temporary files, the PERM parameter in the RESOURCES section of the configuration file, and check for any cron job or other process that might be deleting files from the temporary file directory.
1293	ERROR: File transfer read failed, file=filename, errno=errno_val
	Description	The UNIX kernel call read() failed on filename. This temporary file was being used to transfer a large message between two System/T processes on the same machine. It either could not be read, or the wrong number of bytes were read.
	Action	Check directory and file permissions for the temporary files, disk space and inode counts for the temporary file system, the PERM parameter in the RESOURCES section of the configuration file, and for any cron job or other process that might be deleting files from the temporary file directory.
1294	ERROR: File transfer close failed, file=filename, errno=errno_val
	Description	The UNIX kernel call close() failed on filename after it had been read. This temporary file was being used to transfer a large message between two System/T processes on the same machine.
	Action	Contact your BEA TUXEDO system Technical Support.
1295	WARN: File transfer unlink failed, file=filename, errno=errno_val
	Description	The UNIX kernel call unlink() failed on filename after it had been read. This temporary file was being used to transfer a large message between two System/T processes on the same machine. Although the transfer succeeded, the file could not be unlinked (deleted), and still is present in the system's temporary file directory. This might cause the file system to fill up.
	Action	Check directory and file permissions for the temporary files. If the sticky bit is set for the directory, one user might not be able to delete another user's files. Check the PERM parameter in the RESOURCES section of the configuration file. As a temporary measure, delete filename manually. It is no longer needed by the BEA TUXEDO system. If there are many such files, schedule a cron job to periodically delete files older than a certain threshold.
1296	WARN: Cannot retrieve own server group table entry
	Description	While booting, a server was unable to retrieve its own server table entry. This particular failure by itself will not cause the server to be incapable of processing service requests, but may be indicative of problems elsewhere in the system. If the output from tmboot(1) indicates that a prior attempt to boot this same server on a different node had failed, the location of the server group in the bulletin board and the TUXCONFIG file will not be updated to reflect the current location of this server. The server will still be active and able to receive requests, but the first subsequent attempt to migrate the server will restart the server on the same processor where it is now running. Once this first subsequent migration occurs, the server location will be stored consistently. Also, if the configuration is shut down and rebooted, tmboot(1) will first attempt to start this server group on the processor where it is not now running. (Note that the condition mentioned in this paragraph will not normally be the case.)
	Action	In the normal case, where tmboot(1) did not indicate that automatic server migration had occurred for this server's group, no action is required. However, this condition is likely to be indicative of problems elsewhere in the system. If tmboot(1) did indicate that automatic server group migration took place for this server's group, the administrator may wish to shut down and restart this server group so that the group location is stored consistently.
	See Also	tmboot(1), tmadmin(1)
1297	INFO: Boot process migrating location of group group_name to machine machine_name
	Description	The tmboot(1) process was unable to successfully boot group group_name on its current machine. Therefore, tmboot(1) is migrating the location of this group to its alternate machine, machine_name. The first server in the group to be booted writes this message to the userlog. The group's migration is also noted in the output from tmboot(1). The group will remain located on machine_name until it is manually migrated to its former machine by the administrator, or until a subsequent tmboot(1) detects that the group is unable to run on machine machine_name, but is able to run on the original machine name.
	Action	No action required.
	See Also	tmboot(1)