---

6. CMDTUX Messages 500-599

---

500	ERROR: Shutting down bridge, serious network error
	Description	The bridge is shutting down due to a network error.
	Action	Re-try the desired operation; if the problem persists, contact your BEA TUXEDO system Technical Support.
501	ERROR: Shutting down bridge, serious polling error
	Description	The bridge is shutting down due to a polling error.
	Action	Re-try the desired operation; if the problem persists, contact your BEA TUXEDO system Technical Support.
509	ERROR: Local message being nack'd by BRIDGE
	Description	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.
	Action	Contact your BEA TUXEDO system Technical Support.
511	ERROR: Invalid arguments passed to buildclient
	Description	Invalid arguments were passed to the buildclient command.
	Action	Correct the arguments to buildclient and reexecute the command.
	See Also	buildclient(1)
512	ERROR: Cannot execute C compiler prog_name
	Description	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.
	Action	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.
	See Also	buildclient(1)
516	WARN: buildserver -n option requires non-negative argument. Default setting to 0.
	Description	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.
	Action	Make sure that the argument to the -n option for buildserver is greater than or equal to zero.
	See Also	buildserver(1)
520	ERROR: Invalid arguments passed to buildserver
	Description	Invalid arguments were passed to the buildserver command.
	Action	Correct the arguments to buildserver and reexecute the command. If unsure about the proper arguments, refer to the on-line usage message.
	See Also	buildserver(1)
522	ERROR: buildserver cannot open the temporary output file, srcfile,.
	Description	The buildserver cannot open the temporary output file, srcfile.
	Action	Check that the directory for the file exists and has write permissions, and that the file system has sufficient resources for a new file.
	See Also	buildserver(1)
523	WARN: Duplicate service, svc, (function func) is ignored in service dispatch table.
	Description	A service name was specified more than once to the -s option on the command line.
	Action	Check your -s option for buildserver and eliminate any duplicate services.
	See Also	buildserver(1)
530	ERROR: Cannot execute prog_name
	Description	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.
	Action	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.
	See Also	buildtms(1)
533	ERROR: Cannot be a cleanupsrv process - Uunixerr Uunixerr_val, errno errno_val
	Description	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.
	Action	Retry the desired operation; if the problem persists, contact your BEA TUXEDO system Technical Support.
534	ERROR: Cannot be a cleanupsrv process
	Description	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.
	Action	Retry the desired operation; if the problem persists, contact your BEA TUXEDO system Technical Support.
535	ERROR: Could not retrieve server
	Description	While attempting to clean up a server, the BEA TUXEDO system examined system tables located in shared memory to get the entry for the server. However, the server information could not be found.
	Action	Usually, the system will request manual intervention if this cleanup was not possible for some reason. If further assistance is needed, please contact the BEA TUXEDO system Administrator.
536	ERROR: Server to be cleaned up is still running.
	Description	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.
	Action	Contact your BEA TUXEDO system Technical Support.
537	ERROR: Failed to update server
	Description	While cleaning up information about a dead server, the BEA TUXEDO system was unable to update the server table entry for that server.
	Action	Contact your BEA TUXEDO system Technical Support.
538	INFO: Process pid still running - forcing termination (via SIGIOT)
	Description	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.
	Action	Please examine the userlog and the core image saved for further information. If necessary, contact the BEA TUXEDO system Administrator.
539	ERROR: Failed to kill process pid - errmsg
	Description	A server that was targeted to be cleaned up was found to be still running. The BEA 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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
540	ERROR: Cannot find Queue Table Entry
	Description	A server cleanup was underway. The process had been terminated if necessary, and the BEA 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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
541	ERROR: Unable to decode message header
	Description	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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
542	ERROR: Cannot find service to which to forward request
	Description	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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
543	ERROR: Cannot forward message, sending it back
	Description	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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
544	ERROR: Cannot forward message, sending it back
	Description	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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
545	ERROR: Cannot encode message header
	Description	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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
546	ERROR: Cannot decode message header
	Description	A server cleanup was underway. The system was unable to encode a message while trying to send it.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
547	ERROR: Cannot forward message, sending it back
	Description	A server cleanup was underway. The system was unable to forward a message, so the message will be sent back to the sender.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
548	ERROR: Cannot forward message, sending it back
	Description	A server cleanup was underway. The system was unable to forward a message, so the message will be sent back to the sender.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
549	ERROR: Cannot decode message header
	Description	A server cleanup was underway. The system was unable to decode a message header retrieved from the reply queue while draining it.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
550	ERROR: Cannot remove server
	Description	A server cleanup was underway. Request and reply queues had been drained. An attempt to remove the server failed.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
551	INFO: server removed
	Description	A server cleanup was underway. The server was removed successfully.
	Action	Retry the desired operation; if the problem persists, contact your BEA TUXEDO system Technical Support.
552	WARN: Server cleanup - server vanished
	Description	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.
	Action	Retry the desired operation; if the problem persists, contact your BEA TUXEDO system Technical Support.
555	ERROR: Unable to reply to pid
	Description	A server cleanup was underway. The BEA 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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
556	ERROR: Unable to reset server table entry
	Description	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.
	Action	Examine the userlog for other messages about the error. If necessary, contact the BEA TUXEDO system Administrator or your BEA TUXEDO system Technical Support.
557	ERROR: Automatic Server Recovery failure; Server processes require manual intervention.
	Description	The automatic server recovery has failed. Server processes will require manual intervention.
	Action	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 BEA TUXEDO system boot and shutdown procedures.
	See Also	tmboot(1), tmshutdown(1)
560	ERROR: Cannot be a restartsrv process because of an operating system error, Uunixerr_msg errno_msg
	Description	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).
	Action	Take proper action according to the errno_msg and/or Uunixerr_msg, or contact your BEA TUXEDO system Technical Support.
561	ERROR: Cannot be a restartsrv process
	Description	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.
	Action	Check the userlog for earlier related messages.
562	ERROR: Cannot restart a server
	Description	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.
	Action	Check the current server indicated by the server group and server identifier global variables. Contact your BEA TUXEDO system Technical Support.
563	ERROR: Cannot restart a server
	Description	While attempting to restart a server, the restartsrv process was unable to find the queue entry associated with the server in the internal tables.
	Action	Contact your BEA TUXEDO system Technical Support.
564	ERROR: Server to be restarted, pid, is still running
	Description	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.
	Action	The Bulletin Board may be corrupted. Clean up the Bulletin Board or kill the restartable server and let BBL restart the server. Contact your BEA TUXEDO system Technical Support.
565	ERROR: Server to be restarted, pid, is still running
	Description	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.
	Action	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 BEA TUXEDO system Technical Support.
	See Also	ubbconfig(5)
566	ERROR: Cannot restart a server because the MAXGEN number reached
	Description	Each restartable server can be restarted at most MAXGEN -1 times within the time period specified by GRACE seconds. Both MAXGEN and GRACE parameters are specified in the SERVERS section of the UBBCONFIG file. Currently, the restartsrv process failed because it has restarted the server MAXGEN -1 times within the GRACE period.
	Action	Check your MAXGEN and GRACE value for each server. Re-boot the server manually with tmboot.
	See Also	tmboot(1), ubbconfig(5)
567	ERROR: Cannot restart the server
	Description	The restartsrv process was unable to restart a server because an error occurred in updating the server entry in the Bulletin Board.
	Action	The Bulletin Board may be corrupted. Clean up the Bulletin Board or contact your BEA TUXEDO system Technical Support.
568	ERROR: Cannot restart the server
	Description	The restartsrv process was unable to restart a server because an error occurred in getting the server parameters.
	Action	The Bulletin Board may be corrupted. Clean up the Bulletin Board or contact your BEA TUXEDO system Technical Support.
569	ERROR: Cannot restart the server
	Description	The restartsrv process was unable to restart a server because an error occurred in updating the queue entry in the Bulletin Board.
	Action	The Bulletin Board or the server queue may be corrupted. Clean up the Bulletin Board and the IPCs or contact your BEA TUXEDO system Technical Support.
571	INFO: Server process, pid, is still running; forcing termination via SIGIOT
	Description	As part of restarting a server, the restartsrv process will kill the old server via SIGIOT and leave a core for debugging.
	Action	No action required.
572	ERROR: Cannot kill the process, pid, errno_msg
	Description	The restartsrv process failed to kill the old server. The errno_msg indicates the reason for the failure (based on errno).
	Action	Take appropriate action based on the UNIX errno_msg from kill() or contact your BEA TUXEDO system Technical Support.
	See Also	kill(2) in UNIX system reference manuals
573	ERROR: Cannot restart a server - cannot get information for machine mid
	Description	The restartsrv process was unable to restart a server because an error occurred in retrieving the machine information for mid.
	Action	The Bulletin Board may be corrupted. Clean up the Bulletin Board or contact your BEA TUXEDO system Technical Support.
574	ERROR: Cannot restart the server - fork error
	Description	The restartsrv process cannot fork a new process because the system's process table is full, or the user is not allowed to create any more processes, or possibly because of insufficient memory or swap space.
	Action	Clean up and verify that the UNIX sysgen process parameters are correct such as the maximum number of process table entries, the total number of processes per user, etc. Also, make sure that your machine has sufficient memory or swap space.
	See Also	fork(2) in UNIX system reference manuals
575	ERROR: Cannot restart a server - exec() failed
	Description	The restartsrv process failed to exec() the server because the server executable file is not found.
	Action	Make sure that your server executable files are located under your application directory specified by the environment variable APPDIR or are in PATH. Make sure that the machine or server ENVFILE doesn't reset PATH so that the server executable can no longer be found.
	See Also	exec(2) in UNIX system reference manuals, buildserver(1), ubbconfig(5)
577	ERROR: Cannot restart the server - no BBL
	Description	An attempt to restart a server failed because there is no BBL available.
	Action	Check for a partitioned network, corrupted shared memory, and all administrative processes.
578	ERROR: Cannot restart the server - no DBBL available
	Description	An attempt to restart a server failed because there is no DBBL available.
	Action	Check for a partitioned network, corrupted shared memory, and all administrative processes.
579	ERROR: Cannot restart a server - unknown process creation error: errno_val
	Description	Server restart failed because there is an unknown error while creating the process.
	Action	Take appropriate action based on the UNIX error indicated, or contact your BEA TUXEDO system Technical Support.
580	INFO: A server process has restarted: pid
	Description	A server process has restarted successfully.
	Action	No action required.
581	WARN: Server restart - server vanished
	Description	While scanning the server table to see if other servers need cleaning, the restartsrv process detected that a server has disappeared from the internal server table entry.
	Action	Shared memory may be corrupted. Contact your BEA TUXEDO system Technical Support.
582	ERROR: Command line option formation error for server servername
	Description	While formatting the command line options for recreating the DBBL server's invocation environment for restart, the restartsrv process detected that there are too many command line options.
	Action	Contact your BEA TUXEDO system Technical Support.
583	ERROR: Too many arguments for server servername
	Description	The restartsrv process failed to restart a server because the command line options string for DBBL server is longer than 256 characters and it cannot be processed.
	Action	Contact your BEA TUXEDO system Technical Support.
584	ERROR: Restart error - retrieving server parameters
	Description	While examining every entry in the SERVERS section of the Bulletin Board, an error is encountered while retrieving server parameters.
	Action	Check for corrupted shared memory or contact your BEA TUXEDO system Technical Support.
585	ERROR: Command line option formation error for server servername
	Description	While formatting the command line options for recreating the server's invocation environment for restart, the restartsrv process detected that there are too many command line options.
	Action	Verify the command line arguments for the server or contact your BEA TUXEDO system Technical Support.
586	ERROR: Too many arguments for server servername
	Description	The restartsrv process failed to restart the server because the command line options string for indicated server is longer than 256 characters and it cannot be processed.
	Action	Verify the command line arguments for indicated server or contact your BEA TUXEDO system Technical Support.
587	INFO: Cannot restart server, scheduling for cleanup
	Description	Some type of transient failure has occurred during the restart process. The current server is marked as "CLEANING" and it will be handled by a subsequent cleanupsrv run.
	Action	No action required.
588	ERROR: Cannot retrieve server information for restarting server
	Description	For cleanup, we need to find the server table entry for the current server in the Bulletin Board and update it. However, there is an error in retrieving the server information from the server table entry.
	Action	The shared memory may be corrupted. Contact your BEA TUXEDO system Technical Support.
589	ERROR: Cannot find registry table entry for restarting server
	Description	The restartsrv process cannot find the registry table entry in the Bulletin Board for restarting server.
	Action	The shared memory may be corrupted. Contact your BEA TUXEDO system Technical Support.
590	ERROR: Cannot update server information for restarting server group/id
	Description	For cleanup, we need to find the server table entry for current server in the Bulletin Board and update it. However, there is an error in updating the server information in the server table entry.
	Action	The shared memory may be corrupted. Contact your BEA TUXEDO system Technical Support.
592	ERROR: Cannot start the cleanupsrv process: errno_val
	Description	The cleanupsrv process can be used by the restartsrv process to remove any dead servers that are not restartable. However, there is an error in starting the cleanupsrv process with no particular server indicated.
	Action	Check the userlog for earlier related messages.
593	ERROR: Automatic server recovery failed, server processes require manual intervention
	Description	The automatic server recovery has failed. Server processes will require manual intervention.
	Action	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 BEA TUXEDO system boot and shutdown procedures.
	See Also	tmboot(1), tmshutdown(1)
594	WARN: *Interrupt* Want to Continue? (y/n):
	Description	The restartsrv process has been interrupted by keyboard interrupt signals.
	Action	You can continue with the restartsrv process by entering y or you can stop the restartsrv process by entering n.
595	WARN: Please answer 'y' or 'n'
	Description	The restartsrv process has been interrupted. See Message 594 above for further explanation.
	Action	You can continue with the restartsrv process by entering y or you can stop the restartsrv process by entering n.

---

---