Common Error Messages
This chapter describes error messages that may occur in common modules.
1. Common Error Messages (0001~0100)
0001 memory allocation error : size = Size
Type |
ERROR |
Description |
An error occurred while allocating the specified size of memory. |
Action |
Check the available physical memory. |
0002 memory allocation error : size = Size
Type |
ERROR |
Description |
An error occurred while allocating the specified size of memory. |
Action |
Check the available physical memory. |
0003 memory allocation error : size = Size
Type |
ERROR |
Description |
An error occurred while allocating the specified size of memory. |
Action |
The error may have been caused by a communication failure that corrupted the message. Check the communication status. |
0004 memory allocation error : size = Size
Type |
ERROR |
Description |
An error occurred while allocating the specified size of memory. |
Action |
Check the available physical memory. |
0005 memory allocation error : size = Size
Type |
FATAL |
Description |
An error occurred while allocating the specified size of memory. |
Action |
Check the available physical memory. If this error occurs during system startup, the configuration file may be damaged. Rerun DFL, and then reboot the system. |
0006 memory reallocation error : size = size
Type |
ERROR |
Description |
An error occurred while reallocating the specified size of memory. |
Action |
Check for memory leaks in the application or in system memory. |
0010 file open error : Filename
Type |
ERROR |
Description |
Could not open the file (Filename) in the specified path. |
Action |
Check the file name and access permissions. Also verify the maximum number of the file descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. |
0010C tmpfile open error
Type |
FATAL |
Description |
Could not open the temporary file with tmpfile. |
Action |
Check the file name and access permissions. Also verify the maximum number of the file descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. |
0011 file read error : ReturnValue ReadSize
Type |
ERROR |
Description |
Could not read the file in the specified size. |
Action |
Check the file size. If the return value is negative, refer to the system error message. |
0011A file read error : Filename
Type |
ERROR |
Description |
Could not read the file in the specified size. |
0012 file write error : ReturnValue WriteSize
Type |
ERROR |
Description |
Could not write a file in the specified size. |
Action |
Check the file permissions and available disk space. If the return value is negative, refer to the system error message. |
0013 file access error : Filename
Type |
ERROR |
Description |
Could not use a file in the specified path. |
Action |
Check the file name and permissions. |
0014 exec error : Filename : error
Type |
ERROR|FATAL |
Description |
Could not execute a file in the specified path, or system resources are insufficient. |
Action |
Check the file name and permissions. If the issue is resource-related, review the system error message and terminate unnecessary processes to free memory. This error may also occur if the tmboot process shuts down earlier than its child process forked to start the server. |
0015 fcntl error : Action Value
Type |
ERROR |
Description |
Failed to use a system function (fcntl). |
Action |
Refer to the fcntl.h file and then contact the system administrator. |
0016 file locking error : Action Value
Type |
ERROR |
Description |
Failed to use a system function (file lock). |
Action |
Refer to the unistd.h file and then contact the system administrator. |
0020 socket init error
Type |
ERROR |
Description |
Failed to initialize the UNIX domain socket. |
Action |
Contact the system administrator. |
0021 socket listen error : Filename
Type |
ERROR |
Description |
Failed to initialize the UNIX domain socket. |
Action |
Check the file name and permissions. Also verify if the named pipe (Filename) of PATHDIR is damaged. |
0022 socket accept error
Type |
ERROR |
Description |
Failed to initialize the UNIX domain socket. |
Action |
Verify if the named pipe (Filename) of PATHDIR is damaged. Also check the maximum number of the file descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. |
0023 socket connect error : Filename
Type |
ERROR |
Description |
Failed to initialize the UNIX domain socket. |
Action |
Check the file name and permissions. Verify if the named pipe (Filename) of PATHDIR is damaged. Also check the maximum number of the file descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. |
0024 socket close error
Type |
ERROR |
Description |
Failed to close the UNIX domain docket. |
Action |
Contact the system administrator. |
0025 write error : ReturnValue WriteSize
Type |
ERROR |
Description |
Failed to send data to the UNIX domain socket. |
Action |
Verify if the named pipe (Filename) of PATHDIR is damaged. If the return value is negative, refer to the system error message. |
0026 write error : ReturnValue WriteSize
Type |
ERROR |
Description |
Failed to send data to the UNIX domain socket. |
Action |
Check that the specified WriteSize is available. Verify if the named pipe (Filename) of PATHDIR is damaged. If the return value is negative, refer to the system error message. |
0027 write error : ReturnValue
Type |
ERROR |
Description |
Failed to send data to the UNIX domain socket. |
Action |
Check the operating status of server processes. Verify if the named pipe (Filename) of PATHDIR is damaged. If the return value is negative, refer to the system error message. |
0028 read error : ReturnValue ReadSize
Type |
ERROR |
Description |
Failed to receive data from the UNIX domain socket. |
Action |
Verify if the named pipe (Filename) of PATHDIR is damaged. If the return value is negative, refer to the system error message. |
0029 read error : ReturnValue ReadSize
Type |
ERROR |
Description |
Failed to receive data from the UNIX domain socket. |
Action |
Check that the specified WriteSize is available. Verify if the named pipe (Filename) of PATHDIR is damaged. If the return value is negative, refer to the system error message. |
0030 read error : ReturnValue
Type |
ERROR |
Description |
Failed to receive data from the UNIX domain socket. |
Action |
Check the operating status of server processes. Verify if the named pipe (Filename) of PATHDIR is damaged. If the return value is negative, refer to the system error message. |
0040 socket init error
Type |
ERROR |
Description |
Failed to initialize the TCP/IP socket. |
Action |
Contact the system administrator. |
0041 socket listen error : PortNo
Type |
ERROR |
Description |
Failed to initialize the TCP/IP socket. |
Action |
Check whether the port is already in use. You can verify this with the netstat command. If the issue persists, contact the system administrator. |
0042 socket listen error : PortNo
Related Message |
|
Type |
ERROR |
Description |
Failed to initialize or listen the TCP/IP socket. If the port is already in use, retry after a certain amount of time. |
Action |
Check whether the port is already in use. You can verify this with the netstat command, or contact the system administrator. If the issue persists, check the system network status. |
0043 socket accept error
Type |
ERROR |
Description |
Failed to connect the TCP/IP socket. |
Action |
Check for client communication failure. Also check the maximum number of the file descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. |
0044 socket accept error
Type |
ERROR |
Description |
Failed to connect the TCP/IP socket. |
Action |
Check for communication failure across the nodes registered in the Tmax configuration file. |
0045 socket connects error : HostName PortNo
Type |
ERROR |
Description |
Failed to connect the 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 descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. |
0046 socket connects error : HostName PortNo
Type |
ERROR |
Description |
Failed to connect the 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 failure across the nodes registered in the Tmax configuration file. |
0046A socket connect error : nodename = %s, racport = %d
Type |
ERROR |
Description |
Failed to connect the 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 failure across the nodes registered in the Tmax configuration file. |
0047 socket close error
Type |
ERROR |
Description |
Failed to close the TCP/IP socket. |
Action |
Contact the system administrator. |
0050 write error : ReturnValue WriteSize
Type |
ERROR |
Description |
Failed to send data to the TCP/IP socket. |
Action |
Check for communication failure across the nodes registered in the Tmax configuration file. If the return value is negative, refer to the system error message. |
0051 write error : ReturnValue WriteSize
Type |
ERROR |
Description |
Failed to send data to the TCP/IP socket. |
Action |
1) Check if the specified WriteSize is available. 2) Check for communication failure across the nodes registered in the Tmax configuration file. 3) If the return value is negative, refer to the system error message. |
0052 write error : ReturnValue WriteSize
Type |
ERROR |
Description |
Failed to send data to the TCP/IP socket. |
Action |
Check for communication failure between the client and the Tmax engine modules. If the return value is negative, refer to the system error message. |
0053 write error : ReturnValue WriteSize
Type |
ERROR |
Description |
Failed to send data to the TCP/IP socket. |
Action |
1) Check if the specified WriteSize is available. 2) Check for communication failure between the client and the Tmax engine modules. 3) If the return value is negative, refer to the system error message. |
0054 write error : ReturnValue
Type |
ERROR |
Description |
Failed to send data to the TCP/IP socket. |
Action |
Check for communication failure between the client and the Tmax engine modules. If the return value is negative, refer to the system error message. |
0055 read error : ReturnValue ReadSize
Type |
ERROR |
Description |
Failed to receive data from the TCP/IP socket. |
Action |
Check for communication failure across the nodes registered in the Tmax configuration file. If the return value is negative, refer to the system error message. |
0056 read error : ReturnValue ReadSize
Type |
ERROR |
Description |
Failed to receive data from the TCP/IP socket. |
Action |
1) Check if the specified WriteSize is available. 2) Check for communication failure across the nodes registered in the Tmax configuration file. 3) If the return value is negative, refer to the system error message. |
0057 read error : ReturnValue ReadSize
Type |
ERROR |
Description |
Failed to receive data from the TCP/IP socket. |
Action |
Check for communication failure between the client and the Tmax engine modules. If the return value is negative, refer to the system error message. |
0058 read error : ReturnValue ReadSize
Type |
ERROR |
Description |
Failed to receive data from the TCP/IP socket. |
Action |
1) Check if the specified WriteSize is available. 2) Check for communication failure between the client and the Tmax engine modules. 3) If the return value is negative, refer to the system error message. |
0059 read error : ReturnValue
Type |
ERROR |
Description |
Failed to receive data from the TCP/IP socket. |
Action |
Check for communication failure between the client and the Tmax engine modules. If the return value is negative, refer to the system error message. |
0060 Winsock startup error
Type |
ERROR |
Description |
A Windows client failed to initialize winsock. |
Action |
Confirm that winsock.dll can be used. |
0061 Winsock version error : version1 version2
Type |
ERROR |
Description |
The version of Winsock does not match. |
Action |
Check that the version of winsock.dll is 2.0. |
0062 setsockopt error : [SO_REUSEADDR|SO_KEEPALIVE]
Type |
ERROR |
Description |
An error occurred while configuring an option for the TCP/IP socket. |
Action |
Contact the system administrator to check if the system supports the option. |
0063 gethostbyname error : hostname
Type |
ERROR |
Description |
Failed to get the network address from the 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. If DNS is not used, verify that the hostname is registered in the /etc/hosts file. |
0064 socket connecting :rgwhost port
Type |
INFO |
Description |
Trying to connect the TCP/IP socket. |
0080 select error
Type |
ERROR |
Description |
An error occurred while using the select system call internally. |
Action |
Refer to the system error message. |
0081 pipe error
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 descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. |
0082 fd dup2 error : original_fd new_fd
Type |
ERROR |
Description |
Failed to execute the dup2 system call. |
Action |
Check the maximum number of the file descriptors (fd) allowed by the operating system. In a console, run "ulimit -a" to check the settings. For further information about the error condition, refer to the system error message. |
0083 seek error : whence seeksize
Type |
ERROR |
Description |
Failed to perform fseek (or lseek). |
Action |
Check whether the seeksize exceeded the file size. If the return value is negative, refer to the system error message. |
0090 shared memory attaches error : shmkey
Type |
FATAL ERROR |
Description |
Failed to initialize shared memory. |
Action |
Check if the shmkey value is already in use. In a console, run "ipcs –m" to check the settings. |
0091 shared memory open error : shmkey
Type |
FATAL ERROR |
Description |
Failed to initialize shared memory. |
Action |
Check if the shmkey value is already in use. In a console, run "ipcs –m" to check the settings. |
0092 shared memory truncate error : shmkey
Type |
FATAL ERROR |
Description |
Failed to initialize shared memory. |
Action |
Check if the shmkey value is already in use. In a console, run "ipcs –m" to check the settings. |
0093 shared memory detach error
Type |
ERROR |
Description |
Failed to initialize shared memory. |
Action |
If this error occurs at the time of shutting down the Tmax engine, run the ipcrm command to remove shared memory. |
0094 shared memory revoke error
Type |
ERROR |
Description |
Failed to initialize shared memory. |
Action |
Run the ipcrm command to remove shared memory. |
0095 shared memory map error
Type |
FATAL |
Description |
A mmap() error occurred. |
Action |
Refer to the system error message. |
0100 getenv error : EnvName
Type |
ERROR |
Description |
The environment variable (EnvName) was not defined. |
Action |
Define EnvName correctly. |
2. Common Error Messages (0101~0200)
0111 signal SigNum catched
Type |
ERROR |
Description |
SigNum (signal number=SigNum) occurred. |
Action |
Remove the error by referring to the signa.h file, or contact the Tmax system administrator. |
0112 signal error : SigNum
Type |
WARNING |
Description |
Failed to initialize the signal processor. |
Action |
Check that the SigNum is correct by referring to the signa.h file. |
0113 alarm expired : No response from where
Type |
WARNING |
Description |
No response has been received from where within the specified time period. |
Action |
Check for any network issues or UNIX domain socket failures |
0121 failed to get thread variables
Type |
FATAL |
Description |
Failed to retrieve the thread context in a multi-threaded environment. |
Action |
Check whether the thread has called tpstart, or verify that the context has been set through tpsetctxt. |
0200A magic number error : Number
Type |
FATAL |
Description |
An internal error has corrupted the configuration file. |
Action |
Contact the engineer. |
0200 magic number error : Number1 Number2
Type |
ERROR |
Description |
The data received from the socket has been damaged. |
Action |
1) Check for communication failure between the client and the Tmax engine modules. 2) Provide the Number1 and Number2 service codes to the Tmax administrator. |
3. Common Error Messages (0201~)
0201 unrecognized option : [-opt] [optarg]
Type |
ERROR |
Description |
An invalid option was used when starting server processes. |
Action |
Check the related server options in the SERVER section of the configuration file. For more information, refer to Tmax Administration Guide. |
0202 unrecognized option : [-opt] [optarg]
Type |
ERROR |
Description |
An invalid option was used when starting the Tmax engine processes (e.g., tmm, cll, clh…). |
Action |
Contact Tmax technical support. |
0203 unrecognized option : [-opt] [optarg]
Type |
ERROR |
Description |
An invalid option was used when running a Tmax tool (e.g., tmadmin, tmboot, tmdown, fdlc, sdlc…). |
Action |
Use the option correctly by referring to Tmax Administration Guide and Tmax Reference Guide. |
0204 invalid message from Source : Field Value
Type |
WARNING |
Description |
The message value (Field Value) received via the UNIX domain socket from the source was invalid and has been ignored. |
Action |
Verify whether PATHDIR has been corrupted. |
0205 invalid message from client (host:port) : Field Value
Type |
WARNING |
Description |
The message field value received via the TCP/IP socket from the client was invalid and has been ignored. |
Action |
Check for communication failure between the client and server. |
0206 invalid message from Source : Field Value
Type |
ERROR |
Description |
The message value (Field Value) received via the UNIX domain socket from the source was invalid and has been ignored. |
Action |
Verify whether PATHDIR has been corrupted. |
0207 invalid message from client (host:port) : Field Value
Type |
ERROR |
Description |
The message field value received via the TCP/IP socket from the client was invalid and has been ignored. |
Action |
Check for communication failure between the client and server. |
0208 invalid message from node (host:port) : Field Value
Type |
ERROR |
Description |
The message field value received via the TCP/IP socket from the node was invalid and has been ignored. |
Action |
Check for communication failures across the registered nodes. |
0209 internal error : err_msg
Type |
ERROR |
Description |
An error occurred within the Tmax engine. |
Action |
1) Check that the version of the Tmax module is correct. 2) Delete the SVR module environment variable $(APPDIR), and then run "cfl → gst → compile". Also check the network status. |
0210 invalid message from tmadmin : Field Value
Type |
ERROR |
Description |
The message value received by tmadmin is invalid. |
Action |
Check that the version of tmadmin matches. |
0211 General Infomation : Message
Type |
INFO |
Description |
tpreturn (TPEXIT) was used to terminated the Tmax system. |
0212 env file error : grammer_check_msg
Type |
ERROR |
Description |
An error occurred in the envfile, which is contained in the Tmax configuration 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 TMM and Boot module configuration file. 3) Check that the envfile passed as an argument to tmaxreadenv in the SVR and CLI modules. |
0215 Send to remote node error
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 TMM and CLH modules. |
0216 Receive from remote node error
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 TMM and CLH modules. |
0217 gethostname error
Type |
ERROR |
Description |
Could not find the hostname. |
Action |
Contact the system administrator. |
0218 cannot find hostname in config : hostname
Type |
ERROR |
Description |
The binary configuration file contains no information about a node (hostname). |
Action |
Modify the configuration file and regenerate the binary by running the cfl command. |
0218A failed to find hostname in config : %s or invalid TMAXDIR environment variable
Type |
ERROR |
Description |
The binary configuration file contains no information about a node (hostname). |
Action |
Modify the configuration file and regenerate the binary by running the cfl command. Also verify if TMAXDIR is configured. |
0219 option error : errmsg
Type |
ERROR |
Description |
An invalid option was used when running a Tmax tool (tmadmin, tmboot, tmdown, fdlc, sdlc, …). |
Action |
Use the correct options by referring to Tmax Administration Guide and Tmax Reference Guide. |
0222 possible network layer malfunction, Resetting the network
Type |
ERROR |
Description |
The Tmax system resets all sockets connected to external systems due to a network problem. |
Action |
Check the system network status. |
0223 network error recovered
Type |
ERROR |
Description |
Network error recovery is in progress. |
0224 network error not recovered
Type |
ERROR |
Description |
Network error recovery failed. |
Action |
Check the system network status. |
0225 FD %d is found bad
Type |
INFO |
Description |
An invalid file descriptor (FD) was found in the system. |
0226 invlaid booting option
Type |
ERROR |
Description |
An invalid booting option was used. |
Action |
The administrator must use the Tmax system command (tmboot) to start a process manually. |
0230 daemon init error
Type |
ERROR |
Description |
Failed to initialize a process daemon. |
Action |
Refer to the system error message. |
0237 ftell error
Type |
ERROR |
Description |
An error occurred while executing the ftell function. |
Action |
Refer to the system error message. |
0248 buffer type error(%s). use FIELD type.
Type |
WARNING |
Description |
A non-field type buffer was used in the FDL function. |
Action |
Check the application for potential issues or risks. |
0250 -D %d cannot be less than %d. It was set to %d.
Type |
WARNING |
Description |
The socket buffer size configured using the CLOPT -D option in the SERVER section is smaller than the default socket buffer size. |
Action |
Ensure that the configured size is greater than or equal to the default setting. |