Table of Contents
This chapter describes error messages that may occur in common modules.
Type | ERROR |
Description | An error occurred while allocating the specified size of memory. |
Action | Check the available physical memory. |
Type | ERROR |
Description | An error occurred while allocating the specified size of memory. |
Action | Check the available physical memory. |
Type | ERROR |
Description | An error occurred while allocating the specified size of memory. |
Action | Confirm that a specified size is available. |
Type | ERROR |
Description | An error occurred while allocating the specified size of memory. |
Action | Check the available physical memory. |
Type | FATAL |
Description | An error occurred while allocating the specified size of memory. |
Action | Check the available physical memory. If the error occurs while booting the system, the configuration file is likely to become damaged. Reboot the system after performing CFL again. |
Type | ERROR |
Description | An error occurred while allocating the specified size of memory. |
Action | Check for memory leaks in the application or in system memory. |
Type | ERROR |
Description | Could not open a file (Filename) in a defined route. |
Action | Check the file name and access authentication. Check the maximum number value of the file descriptor (fd) defined in the operating system. In case of a Korn shell, an opened file will be checked using "ulimit -a". |
Type | FATAL |
Description | Could not open the temporary file through tmpfile. |
Action | Check the file name and access authentication. Check the maximum number value of the file descriptor (fd) defined in the operating system. In case of a Korn shell, an opened file will be checked using "ulimit -a". |
Type | ERROR |
Description | Could not read the contents of a file as an exact size. |
Action | Check the file size. If the ReturnValue is negative, please refer to the system error messages. |
Type | ERROR |
Description | Could not read the contents of a file as an exact size. |
Type | ERROR |
Description | Could not write the contents of a file as an exact size. |
Action | Check file access authentication and disk space. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Could not use a file in a defined route. |
Action | Check the file name and access authentication. |
Type | ERROR FATAL |
Description | Could not execute a file in a defined path or not enough resources are available. |
Action | Check the file name and access authentication. Check the error message to remove unnecessary processes or secure memory. |
Type | ERROR |
Description | Failed to use a system function (fcntl). |
Action | Refer to the fcntl.h file and then contact a system administrator for more information. |
Type | ERROR |
Description | Failed to use a system function (file lock). |
Action | Refer to the unistd.h file and then contact a system administrator for more information. |
Type | ERROR |
Description | Failed to initialize a UNIX domain socket. |
Action | Contact a system administrator. |
Type | ERROR |
Description | Failed to initialize a UNIX domain socket. |
Action | Check the file name and access authentication. Then check the status of the named pipe (Filename) in PATHDIR. |
Type | ERROR |
Description | Failed to connect to a UNIX domain socket. |
Action | Check the status of the named pipe (Filename) in PATHDIR. Check the maximum number value of the file descriptor (fd) defined in the operating system. In the case of a Korn shell, it can be checked using "ulimit -a". |
Type | ERROR |
Description | Failed to initialize a UNIX domain socket. |
Action | Check the file name and access authentication. Check the status of the named pipe (Filename) in PATHDIR. Note: Please check the maximum number value of the file descriptor (fd) defined in the operating system. In case of a Korn shell, check it using "ulimit -a". |
Type | ERROR |
Description | Failed to close a UNIX domain socket. |
Action | Please contact a system administrator. |
Type | ERROR |
Description | Failed to send data to a UNIX domain socket. |
Action | Check the status of the named pipe (Filename) in PATHDIR. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to send data to a UNIX domain socket. |
Action | Confirm that a specified WriteSize is available. Please check the status of the named pipe (Filename) in PATHDIR. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to send data to a UNIX domain socket. |
Action | Check the operation status of server processes. Check the status of the named pipe (Filename) in PATHDIR. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a UNIX domain socket. |
Action | Check the status of the named pipe (Filename) in PATHDIR. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a UNIX domain socket. |
Action | Confirm that a specified ReadSize is available. Check the status of the named pipe (Filename) in PATHDIR. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a UNIX domain socket. |
Action | Check the operation status of server processes. Check the status of the named pipe (Filename) in PATHDIR. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to initialize a TCP/IP socket. |
Action | Contact a system administrator for more information. |
Type | ERROR |
Description | Failed to initialize a TCP/IP socket. |
Action | Check for duplicate use of a port. It can be checked by using netstat. Contact a system administrator for more information. |
0042 socket listen error : errno portno
0042 socket listen error, we’ll retry after 10 seconds : errno portno
0042 socket listen error, we’ll retry after 10 seconds : errno = %d, portno = %d
0042 socket listen error : errno = %d, portno = %d
0042 socket listen error, we’ll retry after 5 seconds : errno = %d, portno = %d
Type | ERROR |
Description | Failed to initialize a TCP/IP socket. Failed to listen to the socket. If a port is being used, a retry will be attempted after a certain time interval. |
Action | Check for duplicate use of the port. It can be checked by using netstat. Contact a system administrator for more information. If the error does not stop occurring, check the network status of the system. |
Type | ERROR |
Description | Failed to connect a TCP/IP socket. |
Action | Check for communication interference in the client. Check the maximum number of the file descriptor (fad) value defined in the operating system. In the case of a Korn shell, it can be checked using "ulimit -a". |
Type | ERROR |
Description | Failed to connect a TCP/IP socket. |
Action | Check for communication interference between nodes defined in the Tmax configuration file. |
Type | ERROR |
Description | Failed to connect a TCP/IP socket. |
Action | 1) Confirm that HostName and PortNo are used correctly. 2) Confirm that the Tmax system has started. 3) Check for communication interference. 4) Check the maximum number of the file descriptor (fd) value defined in the operating system. In case of a Korn shell, it can be checked using "ulimit -a". |
Type | ERROR |
Description | Failed to connect a TCP/IP socket. |
Action | 1) Confirm that HostName and PortNo are used correctly. 2) Confirm that the Tmax system has started. 3) Check for communication interference between nodes defined in the Tmax configuration file. |
Type | ERROR |
Description | Failed to connect to a TCP/IP socket. |
Action | 1) Confirm that HostName and PortNo are used correctly. 2) Confirm that Tmax system has started. 3) Check for communication interference between nodes defined in the Tmax configuration file. |
Type | ERROR |
Description | Failed to close a TCP/IP socket. |
Action | Contact a system administrator for more information. |
Type | ERROR |
Description | Failed to send data to a TCP/IP socket. |
Action | Check for communication interference between nodes defined in the Tmax configuration file. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to send data to a TCP/IP socket. |
Action | 1) Confirm that the WriteSize is available. 2) Check for communication interference between nodes defined in the Tmax configuration file. 3) If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to send data to a TCP/IP socket. |
Action | Check for communication interference between clients and the Tmax engine module. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to send data to a TCP/IP socket. |
Action | 1) Confirm that the WriteSize is available. 2) Check for communication interference between clients and the Tmax engine module. 3) If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to send data to a TCP/IP socket. |
Action | Check for communication interference between clients and the Tmax engine in the engine module. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a TCP/IP socket. |
Action | Check for communication interference between the defined nodes. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a TCP/IP socket. |
Action | 1) Confirm that the WriteSize is available. 2) Check for communication interference between defined nodes in the Tmax configuration file. 3) If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a TCP/IP socket. |
Action | Check for communication interference between clients and the Tmax engine in the engine module. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a TCP/IP socket. |
Action | 1) Confirm that the WriteSize is available. 2) Check for communication interference between clients and the Tmax engine in the engine module. 3) If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | Failed to receive data from a TCP/IP socket. |
Action | Check for communication interference between clients and the Tmax engine in the engine module. If the ReturnValue is negative, refer to the system error messages. |
Type | ERROR |
Description | A Windows client failed to initialize winsock. |
Action | Confirm that winsock.dll can be used. |
Type | ERROR |
Description | The version of Winsock is not matched. |
Action | Confirm that the version of winsock.dll is 2.0. |
Type | ERROR |
Description | An error occurred while configuring a TCP/IP socket option. |
Action | Contact a system administrator about the option. |
Type | ERROR |
Description | Failed to get a network address from a hostname by using the gethostbyname system call. |
Action | 1) Confirm that the hostname is correct. It can be checked using the hostname command. 2) Confirm that the domain name server (DNS) defined in the system is operating properly. Check that the hostname is registered in the /etc/hosts file if a DNS is not being used. |
Type | INFO |
Description | Making a TCP/IP connection to the server. |
Type | ERROR |
Description | An error occurred while using the select system call internally. |
Action | Refer to the system error messages. |
Type | ERROR |
Description | An error occurred while using the pipe system call internally. |
Action | 1) Refer to the system error message. 2) Check the maximum number of the file descriptor (fd) value defined in the operating system. In case of a Korn shell, it can be checked using "ulimit -a". |
Type | ERROR |
Description | Failed to call dup2 system. |
Action | Check the maximum number of the file descriptor (fd) value defined in the operating system. In case of a Korn shell, it can be checked using "ulimit -a". Refer to the system error messages for more information. |
Type | ERROR |
Description | Failed to perform fseek (or lseek). |
Action | Check if the seeksize exceeds the file size. If the ReturnValue is negative, refer to the system error message. |
Type | FATAL ERROR |
Description | Failed to initialize shared memory. |
Action | Check for the duplicate use of shmkey. It can be checked using "ipcs -m". |
Type | FATAL ERROR |
Description | Failed to initialize shared memory. |
Action | Check for the duplicate use of shmkey. It can be checked using "ipcs -m". |
Type | FATAL ERROR |
Description | Failed to initialize shared memory. |
Action | Check for the duplicate use of shmkey. It can be checked using "ipcs -m" on the console. |
Type | ERROR |
Description | Failed to initialize shared memory. |
Action | If the error occurs while terminating the Tmax engine, remove the shared memory by using ipcrm. |
Type | ERROR |
Description | Failed to initialize shared memory. |
Action | Remove the shared memory by using ipcrm. |
Type | FATAL |
Description | A mmap() error occurred. |
Action | Refer to the system error message. |
Type | ERROR |
Description | The environment variable (EnvName) was not defined. |
Action | Define EnvName correctly. |
Type | WARNING |
Description | SigNum (signal number=SigNum) was ignored. |
Action | Refer to the signal.h file. |
Type | ERROR |
Description | SigNum (signal number=SigNum) occurred. |
Action | Remove the error in reference to signal.h. Contact a TmaxSoft administrator for more information. |
Type | WARNING |
Description | Failed to initialize the signal processor. |
Action | Check SigNum in reference to signal.h. |
Type | WARNING |
Description | There is no response from "where" within a defined time. |
Action | Check for a network failure or a UNIX domain socket failure. |
Type | FATAL |
Description | Failed to retrieve a thread context in a multi-tasking environment. |
Action | Check whether the thread has called tpstart or not. Or, check whether a context has been set through tpsetctxt or not. |
Type | FATAL |
Description | An internal error from config file has occurred. |
Action | Contact the TmaxSoft technical support team. |
Type | ERROR |
Description | The data received from a socket was damaged. |
Action | 1) Check for communication interference between clients and the Tmax engine module. 2) Inform a TmaxSoft administrator of the service codes, Number1 and Number2. |
Type | ERROR |
Description | An invalid option was used while starting server processes. |
Action | Check the related server options in the SERVER section of the configuration file. Refer to the "Tmax Administrator's Guide" for more information. |
Type | ERROR |
Description | An invalid option was used while starting the Tmax engine process (such as Tm, cl, and clh). |
Action | Contact the TmaxSoft technical support team. |
Type | ERROR |
Description | An invalid option was used while starting up a Tmax tool (such as tmadmin, tmboot, tmdown, fdlc, and sdlc). |
Action | Input the related options correctly. Refer to the following if necessary: "Tmax Administrator's Guide" and "Tmax Reference Guide". |
Type | WARNING |
Description | A message value (Field Value) received via a UNIX domain socket from a Source was invalid. The message was ignored. |
Action | Check for the value in PATHDIR. |
Type | WARNING |
Description | A message value (Field Value) received via TCP/IP from a client was invalid. The message was ignored. |
Action | Check for communication interference between the client and the server. |
Type | ERROR |
Description | A message value (Field Value) received via a UNIX domain socket from Source was invalid. The message was ignored. |
Action | Check for the value in PATHDIR. |
Type | ERROR |
Description | A message value (Field Value) received via TCP/IP from a client was invalid. The message was ignored. |
Action | Check for communication interference between the client and the server. |
Type | ERROR |
Description | A message value (Field Value) received via TCP/IP from a client was invalid. The message was ignored. |
Action | Check for communication interference between defined nodes. |
Type | ERROR |
Description | An internal Tmax engine error. |
Action | 1) Check that the version of Tmax modules are not mis-matched. 2) Clean the SVR module's environment variable $(APPDIR), and regenerate binaries following the "cfl → gst → compile" sequence. After following those steps check the network status. |
Type | ERROR |
Description | The message value (Field Value) received from tmadmin was invalid. |
Action | Confirm that tmadmin and the engine version are identical. |
Type | INFO |
Description | tpreturn (TPEXIT) was used to terminated the Tmax system. |
Type | ERROR |
Description | An error occurred in an envfile, which is contained Tmax environment information. |
Action | 1) Rewrite the envfile in reference to grammer_check_msg. 2) Check the envfile specified ENVFILE = envfile in the SVRGROUP section of the Tm and Boot module configuration file. 3) Check that the envfile passed as an argument to tmaxreadenv in the SVR and CLI modules. |
Type | ERROR |
Description | Failed to send data to a remote node. |
Action | 1) Terminate the tmadmin, tmboot, and tmdown utilities manually in the CFL, BOOT, ADM, and DOWN modules. Restart the racd daemon. 2) Check the network status of the Tm and CLH modules. |
Type | ERROR |
Description | Failed to receive data from a remote node. |
Action | 1) Terminate the tmadmin, tmboot, and tmdown utilities manually in the CFL, BOOT, ADM, and DOWN modules. Restart the racd daemon. 2) Check the network status of the Tm and CLH modules. |
Type | ERROR |
Description | Could not find the hostname. |
Action | Contact a system administrator. |
Type | ERROR |
Description | A binary configuration file contains no information about a node (hostname). |
Action | Update the configuration file and regenerate it using "cfl". |
Type | ERROR |
Description | A binary configuration file contains no information about a node (hostname). |
Action | Update the configuration file and regenerate it using "cfl". Check that TMAXDIR is configured. |
Type | ERROR |
Description | An invalid option is specified when starting a Tmax tool (such as tmadmin, tmboot, tmdown, fdlc, and sdlc). |
Action | Refer to the "Tmax Administrator's Guide" and "Tmax Reference Guide" for valid options. |
Type | ERROR |
Description | A Tmax system resets all sockets connected to external system due to network problems. |
Action | Check the system network status. |
Type | ERROR |
Description | Network error recovery. |
Type | ERROR |
Description | Failed to recover a network error. |
Action | Check the system network status. |
Type | INFO |
Description | An invalid file description (FD) found in a system. |
Type | ERROR |
Description | An invalid booting option. |
Action | An administrator must use tmboot to manually boot a process. tmboot is a Tmax system command. |
Type | ERROR |
Description | Failed to initialize a process daemon. |
Action | Refer to the system error message. |
Type | ERROR |
Description | An error occurred while performing ftell. |
Action | Refer to the system error message. |