22.5 KDEA04000 to KDEA05999 : Hitachi Elastic Application Data Store

KDEA04504-E

An invalid property was detected. (definition file name = aa....aa, property name = bb....bb, property value = cc....cc)

aa....aa: Invalid property file name

bb....bb: Invalid parameter name

cc....cc: Invalid parameter specification value (or blank if there is no value)

Description: An invalid parameter was detected.
Action: Check and, if necessary, revise the parameter indicated in the message.

KDEA04506-E

A data discrepancy in the definition file was detected. (node ID = aa....aa, definition file name = bb....bb)

aa....aa: EADS server ID of the EADS server whose property file does not match the other EADS servers' property files

bb....bb: Name of the property file whose contents do not match those of the other EADS servers' property files

Description

The contents of the property file do not match the contents of the other EADS servers' property files.

Action

Check if the contents of the property file match the contents of the other EADS servers' property files.

If this error occurs again, the EADS server might be accepting heartbeats from another cluster. If this is the case, make sure that the specified destination IP address or port number (eads.failureDetector.heartbeat.address and eads.failureDetector.heartbeat.port parameters in the shared properties) is not duplicated in another cluster.

KDEA04508-E

A boot timeout occurred. (node-list = aa....aa)

aa....aa: List of IP addresses and port numbers of EADS servers that did not finish starting within the specified time period

Description

Not all the EADS servers that make up the cluster finished startup processing within the specified period of time.

Action

Make sure the EADS servers indicated in the message have been started.

This error might occur when the cluster consists of many EADS servers. If this is the case, change the maximum wait time for all EADS servers making up the cluster to start (eads.admin.boot.timeout parameter in the cluster properties). An appropriate value is number of EADS servers making up the cluster [Figure] 5 seconds.

Also consider starting the EADS servers beginning with the EADS server with the smallest EADS server ID.

KDEA04528-E

A data discrepancy between the cluster-definition file and the server-definition file was detected.

Description: There is a discrepancy between the server property file and the cluster property file.
Action: Check whether the EADS server specified in the server property parameters eads.server.address and eads.server.port is specified in the cluster property parameters eads.node.EADS-server-ID.address and eads.node.EADS-server-ID.port.

KDEA04531-E

A server position was duplicated. (duplicated node ID1 = aa....aa, duplicated node ID2 = bb....bb)

aa....aa: EADS server ID of the first EADS server whose position is duplicated

bb....bb: EADS server ID of the second EADS server whose position is duplicated

Description: Two EADS servers making up the cluster have the same position.
Action: Make sure there are no duplicates for the cluster property parameter eads.node.EADS-server-ID.position.

KDEA04540-E

A client connection address was duplicated. (duplicated node ID1 = aa....aa, duplicated node ID2 = bb....bb)

aa....aa: EADS server ID of the first EADS server whose combination of IP address and port number is duplicated

bb....bb: EADS server ID of the second EADS server whose combination of IP address and port number is duplicated

Description: Two EADS servers have the same definition in the cluster property file.
Action: Check the eads.node.EADS-server-ID.address and eads.node.EADS-server-ID.port parameters in the cluster properties for duplications.

KDEA04541-E

The cluster-definition file contains only part of the server position specification.

Description: The cluster property file contains position specifications for only some of the EADS servers.
Action: If you specify the eads.node.EADS-server-ID.position parameter in the cluster properties, you must specify a position for all the EADS servers. If you want to omit some EADS server positions, do not specify any EADS positions.

KDEA04661-E

Participation in the cluster failed. (error code = aa....aa)

aa....aa: Error code

Description

Cluster participation processing failed.

Action

Take the following actions:

If necessary, check the message that was output immediately before this message, determined the cause of the error, and then eliminate it.
Execute the eztool status command to check the cluster status.

If an EADS server's status is shown as lock, it is still locked. In this case, execute the eztool unlock command.
Execute the ezstart or ezserver command to perform startup, restoration, or scale-out processing again.

Note that if a cache failed to resume, but the cache has not been deleted by the eztool deletecache command, the EADS servers cannot be restored. In such a case, execute the eztool deletecache command to delete the cache that failed to resume.

KDEA04664-E

The relation between the number of servers and the number of replications was invalid. (number of servers = aa....aa, number of replications = bb....bb)

aa....aa: Number of EADS servers

bb....bb: Data multiplicity

Description: The number of EADS servers making up the cluster is not at least the number of redundant copies of data 2 - 1.
Action: Check the cluster properties and either increase the number of EADS servers so that the number of EADS servers making up the cluster is at least the number of redundant copies of data 2 - 1 or reduce the number of redundant copies of data plus the original (value of the eads.replication.factor parameter in the shared properties).

KDEA04665-E

A server cannot be added when the number of replications is 1.

Description

If the data multiplicity (the number of redundant copies of data plus the original) is 1, EADS servers cannot be added.

Action

Check and, if necessary, revise the number of redundant copies of data plus the original (value of the eads.replication.factor parameter in the shared properties).

If you have started the cluster with the data multiplicity set to 1, export all needed data, stop all EADS servers, then edit the cluster properties according to the most recent parameter settings. Restart all EADS servers.

KDEA04666-E

The number of servers in the cluster has already reached the maximum.

Description

The number of EADS servers in the cluster has already reached the upper limit.

Action

No more EADS server can be added because 96 EADS servers, which is the maximum number of EADS servers that can make up a cluster, are already participating in the cluster.

Evaluate using another cluster.

KDEA04667-E

In the current state of the cluster, the server cannot participate in the cluster in the specified start type. (start type = aa....aa, cluster state = bb....bb)

aa....aa: Start method

bb....bb: Cluster status

Description

The EADS server cannot use the specified start method to participate in a cluster that is in the current cluster status.

Action

The possible causes are as follows:

The option specified in the ezstart or ezserver command is invalid.
The EADS server was restarted or restored while it was being isolated.
The cluster status is not available (not AVAILABLE).
An attempt was made to add an EADS server when at least one EADS server was isolated.

Check the EADS server start options for any error or missing options. Also check if the cluster status satisfies the conditions for the specified start method, and then restart the EADS server.

KDEA04668-E

The server could not participate in the cluster with the conditions specified in the options. (specified options = aa....aa, details = bb....bb)

aa....aa: Options specified when the EADS server was started

bb....bb: Details

Description

The EADS server could not participate in the cluster with the conditions specified in the options.

Action

The possible causes are as follows:

There is no EADS server with the specified EADS server ID.
An EADS server already exists at the specified EADS server location (hash value).
The range managed by the EADS server with the specified EADS server ID is 1.

Check and, if necessary, revise the option value, and then add the EADS server again.

KDEA04669-E

An attempt to lock the server failed.

Description: An attempt to acquire a lock failed.
Action: Execute the eztool status -v command to check the current processing, wait until the processing is finished, and then restart the EADS server. If the processing has already finished but the lock has not been released, execute the eztool unlock command to release the lock, and then restart the EADS server.

KDEA04691-I

The transmission of cache data will now start. (cache name = aa....aa)

aa....aa: Cache name

Description: Transmission of cache data is beginning.

KDEA04692-I

The cache data was successfully transferred. (cache name = aa....aa)

aa....aa: Cache name

Description: Transmission of cache data was successful.

KDEA04693-E

The transmission of cache data failed. (cache name = aa....aa, error code = bb....bb)

aa....aa: Cache name

bb....bb: Error code

Description

Transmission of cache data failed.

Action

The possible causes are as follows:

An error occurred on an EADS server from which data was sent.
A communication error occurred.
An unexpected error occurred.

Determine the cause of the problem, and then eliminate it.

KDEA04697-E

Transmission of the data failed because a required server was not found.

Description

Transmission of data failed because an active EADS server required for the data transmission was not available.

There is no EADS server that stores required data, or the number of active EADS servers is equal to or less than the number of data copies plus the original.

Action

Take the following actions:

Execute the eztool export command to export required data to a file.
Terminate all active EADS servers.
Start all EADS servers.

KDEA04698-E

An error occurred on the server that sent data.(error code = aa....aa)

aa....aa: Error code

Description

An error occurred on the EADS server that sent data.

Action

The possible causes are as follows:

The transmission timed out.
A communication error occurred.
An unexpected error occurred.
Restoration processing or scale-out processing could not be performed.
An option specified in the ezstart or ezserver command was invalid.

Determine the cause of the error, eliminate it, and then restart the EADS server.

KDEA04703-E

The master switchover failed because a cache operation failed.

Description: Switchover to the source EADS server from which data is to be copied failed because a data operation failed.
Action: Check the messages that were output immediately before this one.

KDEA04722-E

A specified port is already being used. (self address = aa....aa, property name = bb....bb, port number = cc....cc)

aa....aa: IP address of the local EADS server

bb....bb: Name of the parameter that represents the port number

cc....cc: Specified port number

Description: The specified port number is already being used.
Action: Specify a port number that is not in use by another process.

KDEA04723-E

An unknown message was received. (source address = aa....aa, source port = bb....bb, header = cc....cc)

aa....aa: IP address of the message delivery source

bb....bb: Port number of the message delivery source

cc....cc: Header of the received message (hexadecimal)

Description: An invalid message was received. Another system is sending a message to a communication port that is in use.
Action: Check and, if necessary, revise the destination IP address or port number so that there is no interference in the delivery of messages from another system.

KDEA04725-E

A message of an unsupported protocol version was received. (source address = aa....aa, source port = bb....bb, protocol version = cc....cc)

aa....aa: IP address of the message delivery source

bb....bb: Port number of the message delivery source

cc....cc: Protocol version of the received message

Description

A message with an unsupported protocol version was received.

Systems using different protocol versions have been mixed.

Action

Check if the protocol version matches the installed EADS version.

KDEA04726-W

A connection timeout occurred during failure detection processing. (destination address = aa....aa, destination port = bb....bb)

aa....aa: IP address of the connection-target EADS server

bb....bb: Port number of the connection-target EADS server

Description

During the check for live servers, a connection could not be established before the timeout period.

Action

If timeouts occur frequently, check the network devices for a failure.

Alternatively, check and, if necessary, revise the value of the eads.failureDetector.connection.timeout parameter in the server properties.

KDEA04727-W

A read timeout occurred during failure detection processing. (destination address = aa....aa, destination port = bb....bb)

aa....aa: IP address of the connection-target EADS server

bb....bb: Port number of the connection-target EADS server

Description

After establishing a connection during the check for live servers, nothing could be received before the timeout period.

Action

If timeouts occur frequently, check the network devices for a failure.

Alternatively, check and, if necessary, revise the eads.failureDetector.read.timeout parameter in the server properties.

KDEA04728-E

An error occurred during establishment of a connection for failure detection processing. (error message = aa....aa)

aa....aa: Error message from the exception that was thrown from the JavaVM

Description

While a connection was being established for the check for live servers, a socket could not be created because an exception was thrown from the JavaVM.

Action

Check whether the file descriptor was set according to estimates.

If the error continues to occur, contact the customer support center.

KDEA04752-I

Processing to isolate a server was successful. (server ID = aa....aa)

aa....aa: EADS server ID of the EADS server that was isolated

Description: Isolation processing has been completed.

KDEA04755-E

Processing to isolate a server failed because a cache operation failed.

Description: Isolation processing failed due to a data operation error.
Action: Check the messages that were output immediately before this one.

KDEA04781-I

A server will now be added to the cluster. (server ID = aa....aa)

aa....aa: EADS server ID of the EADS server that will be added to the cluster

Description: An EADS server is being added to the cluster.

KDEA04783-I

Processing to isolate a server will now start. (server ID = aa....aa)

aa....aa: EADS server ID of the EADS server that will be isolated

Description: The eztool isolate command was executed. The EADS server will now be isolated.

KDEA04785-I

A command lock will now be acquired.

Description: A command lock will now be acquired.

KDEA04786-I

A command lock could not be acquired.

Description: An attempt to acquire a command lock failed because another command already has a lock.
Action: Re-execute the command after the currently executing command has terminated.

KDEA04787-I

Acquisition of a command lock failed. (error code = aa....aa)

aa....aa: Error code

Description

An attempt to acquire a command lock failed.

Action

The possible causes are as follows:

Another cluster was running.
The EADS server was terminated.

Determine the cause of the error, eliminate it, and then re-execute the command.

KDEA04789-I

A command lock will now be released.

Description: A command lock will now be released.

KDEA04790-I

An attempt to release a lock failed. (error code = aa....aa)

aa....aa: Error code

Description

An attempt to release a command lock failed.

Action

The possible causes are as follows:

Another cluster was running.
The EADS server was terminated.

Determine the cause of the error, eliminate it, and then re-execute the eztool unlock command to release the lock.

KDEA04792-I

Now waiting for executing requests to complete...

Description: The system is waiting for the current request processing to be completed.

KDEA04793-I

All requests are complete.

Description

The processing of all requests has been completed.

The system will now start processing the requests that arrived while the system was on standby.

KDEA04794-I

The wait for the lock to end will now start.

Description: A wait for completion of locking has started.

KDEA04795-I

The wait for the lock to end ended successfully.

Description: The wait for completion of locking has ended.

KDEA04799-E

Processing to isolate a server will now start. (server ID = aa....aa)

aa....aa: EADS server ID of the EADS server that will be isolated

Description

A nonoperational EADS server was detected during cluster monitoring. The EADS server will be isolated.

Action

Verify that the KDEA04752-I message has been output indicating that the isolation processing has been completed. After that, execute one of the following commands to restore the isolated EADS server:

ezstart -r command
ezserver -r command

KDEA04800-E

This server will be stopped because a gap in the data could not be filled.

Description

This EADS server will be terminated because consensus processing can no longer be continued in the cluster.

Action

Check if the size of the area for storing the history of update operations has been set as estimated.

If a sufficient size is not specified, change the value of the eads.replication.external.heapsize parameter in the shared properties.

Restore the EADS server by executing one of the following commands:

ezstart -r command
ezserver -r command

Alternatively, restart all EADS servers in the cluster.

KDEA04801-E

This server will be stopped because a gap in the data could not be filled. (cache name = aa....aa, range ID = bb....bb)

aa....aa: Cache name

bb....bb: Range ID

Description

This EADS server will be stopped because consensus processing can no longer continue in the cluster.

Action

Check if the size of the area for storing the history of update operations has been set as estimated.

If a sufficient size is not specified, change the value of the eads.replication.external.heapsize parameter in the shared properties.

Execute one of the following commands to restore the stopped EADS server:

ezstart -r command
ezserver -r command

Alternatively, restart all EADS servers in the cluster.

KDEA04805-E

Only some of the data are available because a server is isolated. (server ID = aa....aa, aborted positions = bb....bb)

aa....aa: EADS server ID of the EADS server that was isolated

bb....bb: List of the start positions on the consistent hashing in the range of data that cannot be accessed

Description

Some data cannot be accessed because an EADS server has been isolated.

Action

Data cannot be accessed, but the data is still in the cache. Take the following actions:

Execute the eztool export command to export the required data to a file.
Terminate all active EADS servers.
Start all EADS servers.

The cluster cannot be restored to normal status by restoring the EADS server.

KDEA04807-E

The system could not continue building a consensus on distribution among servers in the range.

Description: Consensus processing can no longer continue.
Action: Restart all EADS servers in the cluster.

KDEA04808-E

Only some of the data are available because a server is isolated. Some data were lost. (isolated server ID = aa....aa, lost data start positions = bb....bb, aborted data start positions = cc....cc)

aa....aa: EADS server ID of the EADS server that was isolated

bb....bb: List of the start positions on the consistent hashing in the range of missing data

cc....cc: List of the start positions on the consistent hashing in the range of data that cannot be accessed

Description

Some data cannot be accessed because an EADS server has been isolated.

Alternatively, some data has been lost.

Action

Some existing data cannot be accessed, but it is still in cache. Take the following actions:

Execute the eztool export command to export the required data to a file.
Terminate all active EADS servers.
Start all EADS servers.

The cluster cannot be restored to normal status by restoring the EADS server.

KDEA04809-W

The number of running servers is the minimum required for the cluster to be available. (isolated server ID = aa....aa, start positions of data to be lost = bb....bb, start positions of data to be aborted = cc....cc)

aa....aa: EADS server ID of the EADS server that was isolated

bb....bb: If an EADS server has been isolated, a list of the start positions on the consistent hashing in the range of data that might have been lost

cc....cc: If an EADS server has been isolated, a list of the start positions on the consistent hashing in the range of data that might not be accessible

Description

The number of running EADS servers has reached the minimum required for cluster operation.

If an EADS server has been isolated, some data might be inaccessible or lost.

Action

Restore the isolated EADS server by executing one of the following commands:

ezstart -r command
ezserver -r command

KDEA04810-W

The number of running servers is the minimum required for the cluster to be available. (isolated server ID = aa....aa, start positions = bb....bb)

aa....aa: EADS server ID of the EADS server that was isolated

bb....bb: If an EADS server has been isolated, a list of the start positions on the consistent hashing in the range of data that might not be accessible

Description

The number of running EADS servers has reached the minimum required for cluster operation.

If an EADS server has been isolated, some data might not be accessible.

Action

Restore the isolated EADS server by executing one of the following commands:

ezstart -r command
ezserver -r command

KDEA04812-E

An unexpected exception occurred. (error code = aa....aa)

aa....aa: Error code

Description: An unexpected exception occurred.
Action: Contact the customer support center.

KDEA04813-E

A sequence number is too large and exceeded the upper limit.

Description: An overflow occurred in the internal sequence numbers due to an extended period of operation.
Action: Contact the customer support center.

KDEA04814-W

Server-to-server communication timed out. (timeout value = aa....aa, destination addresses = bb....bb)

aa....aa: Timeout period

bb....bb: List of IP addresses of the destination EADS servers

Description

Communication between EADS servers timed out.

The possible causes are as follows:

A failure occurred at a target EADS server, host, or network.
The timeout period is not appropriate.

Action

Eliminate the cause of the timeout.

Alternatively, increase the value of the eads.replication.consensus.timeout parameter in the server properties. However, there is no need to change the parameter value in the following cases:

A communication error occurred.
The EADS server was isolated for a reason such as a process error.
The EADS server was isolated by the eztool isolate command.

KDEA04815-E

The cluster status has become NOT_AVAILABLE.

Description

The cluster has been placed in NOT_AVAILABLE status.

Either split-brain has occurred or at least half of the EADS servers in the cluster have failed.

Action

If split-brain has occurred, recover the network.

If at least half of the EADS servers in the cluster have failed, restart all EADS servers in the cluster.

KDEA04816-I

The cluster has recovered from the NOT_AVAILABLE state.

Description

The cluster has recovered from NOT_AVAILABLE status.

The cluster has recovered from split-brain.

KDEA04817-E

A gap was found that the server could not resolve.

Description

An attempt to synchronize delayed EADS server processing failed because the logs required for synchronization were not available.

Action

The possible causes are as follows:

An overflow occurred in the consensus message send queue.
An EADS server was isolated.
A communication error occurred.
An unexpected error occurred.

Determine the cause of the error, eliminate it, and then restore the EADS server by executing one of the following commands:

ezstart -r command
ezserver -r command

KDEA04821-W

Processing to delete part of the history in order to resolve a memory shortage in the history storage area has started.

Description

Deletion processing on the existing history of update operations has started because a space shortage occurred on the area for storing the history of update operations.

Action

Check if the size of the area for storing the history of update operations has been set as estimated.

If a sufficient size is not specified, change the value of the eads.replication.external.heapsize parameter in the shared properties.

KDEA04822-W

During the building of a consensus on distribution among the servers in the cluster, processing to delete part of the history in order to resolve a memory shortage in the history storage area failed. (requested size = aa....aa)

aa....aa: Size of the area requested for storing the history of update operations

Description

Consensus processing was stopped because an attempt was made to delete the existing history of update operations due to a shortage of space for storing the history of update operations, but the required size of area could not be allocated.

Action

Check the network devices for a failure, wait a while, and then re-execute the command.

If the error occurs again, check if the size of the area for storing the history of update operations has been set as estimated.

If a sufficient size is not specified, change the value of the eads.replication.external.heapsize parameter in the shared properties.

KDEA04823-E

During the building of a consensus on distribution among the servers in the cluster, processing to delete part of the history in order to resolve a memory shortage in the history storage area failed. (requested size = aa....aa)

aa....aa: Size of the area requested for storing the history of update operations

Description

All processing terminated abnormally because an attempt was made to delete the existing history of update operations due to a shortage of space for storing the history of update operations, but the required size of area could not be allocated.

Action

Check if the size of the area for storing the history of update operations has been set as estimated.

If a sufficient size is not specified, change the value of the eads.replication.external.heapsize parameter in the shared properties.

KDEA04824-W

During processing to delete part of the history in order to resolve a memory shortage in the history storage area, processing to build a consensus stopped because the memory shortage could not be resolved. (requested size = aa....aa, cache name = bb....bb, range ID = cc....cc)

aa....aa: Size of the area requested for storing the history of update operations

bb....bb: Cache name

cc....cc: Range ID

Description

Consensus processing was stopped because an attempt was made to delete the existing history of update operations due to a shortage of space for storing the history of update operations, but the required size of area could not be allocated.

Action

Check the network devices for a failure, wait a while, and then re-execute the command.

If the error occurs again, check if the size of the area for storing the history of update operations has been set as estimated.

If a sufficient size is not specified, change the value of the eads.replication.external.heapsize parameter in the shared properties.

KDEA04825-E

During processing to delete part of the history in order to resolve a memory shortage in the history storage area, all processing ended abnormally because the memory shortage could not be resolved. (requested size = aa....aa, cache name = bb....bb, range ID = cc....cc)

aa....aa: Size of the area requested for storing the history of update operations

bb....bb: Cache name

cc....cc: Range ID

Description

All processing terminated abnormally because an attempt was made to delete the existing history of update operations due to a shortage of space for storing the history of update operations, but the required size of area could not be allocated.

Action

Check if the size of the area for storing the history of update operations has been set as estimated.

If a sufficient size is not specified, change the value of the eads.replication.external.heapsize parameter in the shared properties.

KDEA04841-E

A TCP connection was closed because the queue for sending distribution-consensus messages overflowed. (destination address = aa....aa, destination port = bb....bb, queuesize = cc....cc, queuedatasize = dd....dd)

aa....aa: IP address of the connection-target EADS server

bb....bb: Port number of the connection-target EADS server

cc....cc: Number of messages in the send queue

dd....dd: Data size of the messages in the send queue

Description: Connection was closed due to an overflow in the consensus message send queue.
Action: Increase the value of the eads.replication.sendQueue.length or eads.replication.sendQueue.datasize parameter in the server properties.

KDEA04871-E

Initialization of UDP reception failed because an error occurred during initialization of the receiving socket. (error message = aa....aa, multicast address = bb....bb, multicast port = cc....cc)

aa....aa: Error message from the exception that was thrown from the JavaVM

bb....bb: IP address (multicast address)

cc....cc: Port number

Description: Initialization of UDP reception failed because an error occurred during initialization of the receiving socket.
Action: Determine the cause of the error from the displayed exception error message and eliminate it. Also check if the file descriptor has been set as estimated.

KDEA04872-E

Initialization of UDP transmission failed because an error occurred during initialization of the sending socket. (error message = aa....aa, multicast address = bb....bb, multicast port = cc....cc)

aa....aa: Error message from the exception that was thrown from the JavaVM

bb....bb: IP address (multicast address)

cc....cc: Port number

Description: Initialization of UDP transmission failed because an error occurred during initialization of the sending socket.
Action: Determine the cause of the error from the displayed exception error message and eliminate it. Also check if the file descriptor has been set as estimated.

KDEA04881-E

Initialization of TCP/IP reception failed because an error occurred during initialization of the receiving socket. (error message = aa....aa, local address = bb....bb, local port = cc....cc)

aa....aa: Error message from the exception that was thrown from the JavaVM

bb....bb: Local IP address

cc....cc: Local port number

Description

Initialization of TCP/IP reception failed because an error occurred during initialization of the receiving socket.

Action

Check for any of the following messages:

Cannot assign requested address

Check if the local IP address is valid in the OS.
Address already in use

Check if the local port number is in use by another process.
Other

Determine the cause of the error from the displayed exception error message and eliminate it. Also check if the file descriptor has been set as estimated.

KDEA04882-E

Initialization of TCP/IP transmission failed because an error occurred during initialization of the sending socket. (error message = aa....aa, destination address = bb....bb, destination port = cc....cc)

aa....aa: Error message from the exception that was thrown from the JavaVM

bb....bb: Connection-target IP address

cc....cc: Connection-target port number

Description

Initialization of TCP/IP transmission failed because an error occurred during initialization of the sending socket.

Action

Check for any of the following messages:

Connection refused

Check if the connection-target port number is correct.

If the connection-target port number is correct, check if the connection-target EADS server has already started.
Connection Timedout

Check if the connection-target IP address is correct.

If the connection-target IP address is correct, check if the connection-target OS has already started.
java.net.SocketTimeoutException

Check if the connection-target IP address is correct.

If the connection-target IP address is correct, check if the connection-target OS has already started.
Other

Determine the cause of the error from the displayed exception error message and eliminate it. Also check if the file descriptor has been set as estimated.

KDEA04883-I

A different ReceiveBufferSize from the property value will be used. (property name = aa....aa, property value = bb....bb, ReceiveBufferSize = cc....cc)

aa....aa: Parameter name

bb....bb: Specified value of the parameter

cc....cc: Size of consensus message receive buffer that is actually used

Description: A receive buffer size that differs from the specified value was used because the value of the eads.replication.connection.buffersize parameter specified in the server properties exceeds the window size supported by the OS.

KDEA04884-I

A different SendBufferSize from the property value will be used. (property name = aa....aa, property value = bb....bb, SendBufferSize = cc....cc)

aa....aa: Parameter name

bb....bb: Specified value of the parameter

cc....cc: Size of consensus message send buffer that is actually used

Description: A send buffer size that differs from the specified value was used because the value of the eads.replication.connection.buffersize parameter specified in the server properties exceeds the window size supported by the OS.

KDEA04887-W

A read timeout occurred in a TCP/IP reception. (local address = aa....aa, local port = bb....bb, destination address = cc....cc, destination port = dd....dd)

aa....aa: Local IP address

bb....bb: Local port number

cc....cc: Connection-target IP address

dd....dd: Connection-target port number

Description: A connection was established, but data could not be received within the timeout period.
Action: If timeouts occur frequently, check and, if necessary, revise the value specified in the server property parameter eads.transfer.timeout.

KDEA04888-W

A send timeout occurred in a TCP/IP transmission. (local address = aa....aa, local port = bb....bb, destination address = cc....cc, destination port = dd....dd)

aa....aa: Local IP address

bb....bb: Local port number

cc....cc: Connection-target IP address

dd....dd: Connection-target port number

Description: A connection was established, but data could not be sent within the timeout period.
Action: If timeouts occur frequently, check and, if necessary, revise the value specified in the server property parameter eads.transfer.timeout.

KDEA04891-E

An unknown message was received. (source address = aa....aa, source port = bb....bb, error message = cc....cc)

aa....aa: IP address of the message delivery source

bb....bb: Port number of the message delivery source

cc....cc: Error message

Description: An invalid message was received. Another system is sending a message to a communication port that is in use.
Action: Check and, if necessary, revise the destination IP address or port number so that there is no interference in the delivery of messages from another system

KDEA04892-W

TCP/IP transmission failed because the server is not running.

Description: TCP/IP transmission processing failed because the EADS server terminated.

KDEA04932-E

An error occurred during cache processing. (exception = aa....aa, cache name = bb....bb)

aa....aa: Exception class name

bb....bb: Cache name (or null if there is no cache name)

Description: An error occurred during cache processing.
Action: Check the messages that were output immediately before this one.

KDEA04962-W

Cache creation was aborted because a consensus on distribution for part of the range is not executable. (cache name = aa....aa, management client = bb....bb)

aa....aa: Cache name

bb....bb: IP address from which the command was executed

Description: Cache creation was cancelled because consensus processing could not be performed in some part of the range.
Action: Restart all EADS servers in the cluster, and then re-execute the command.

KDEA04965-E

Addition of a server to the cluster failed because the system could not continue building a consensus on distribution among the servers in the cluster. (node id = aa....aa)

aa....aa: EADS server ID of the EADS server that was to be added

Description

The processing to add an EADS server to the cluster failed because consensus processing could no longer be continued in the cluster.

Action

Execute the eztool status command to check the cluster status. If the cluster status is AVAILABLE, the EADS server can be restored.

If the cluster status is NOT_AVAILABLE or PARTIALLY_AVAILABLE, the EADS server cannot be restored, in which case you must restart all EADS servers in the cluster.

KDEA04966-E

Processing to isolate a server failed because the system could not continue building a consensus on distribution among the servers in the cluster. (node id = aa....aa)

aa....aa: EADS server ID of the EADS server that was to be isolated

Description

The processing to isolate an EADS server failed because consensus processing could no longer be continued in the cluster.

Action

Execute the eztool status command to check the cluster status. If the cluster status is AVAILABLE, the EADS server can be restored.

If the cluster status is NOT_AVAILABLE or PARTIALLY_AVAILABLE, the EADS server cannot be restored, in which case you must restart all EADS servers in the cluster.

KDEA04967-E

Acquisition of a command lock failed because the system could not continue building a consensus on distribution among the servers in the cluster.

Description: An attempt to acquire a command lock failed because consensus processing could no longer be continued in the cluster.
Action: Execute the eztool status command to check the cluster status, and then re-execute the command on another EADS server.

KDEA04968-E

The release of a lock failed because the system could not continue building a consensus on distribution among the servers in the cluster.

Description: An attempt to release a command lock failed because consensus processing could no longer be continued in the cluster.
Action: Re-execute the eztool unlock command on another EADS server.