Failed to initialize the readdir() mutex

Cause

Cannot initialize an internal mutex.

Action

Try restarting the Gateway. If it fails again, contact Amadis support.

Connection manager has stopped with errors.

Cause

The Gateway stopped because of some fatal errors.

Action

Look for the previous error. Fix it and restart the Gateway.

Error writing the response to %1, port %2: error code = %3

Cause

The Gateway could not send the response to the POIs. It is mainly caused by a network issue.

• %1 is the IP address of the POI

• %2 is the port used to communicate with the POI

• %3 is the SSL connection state.

Action

Investigate the root cause of this error if it happens too often. It can be a programming error in very rare occasions.

Message body truncated (expected = %1, received = %2) for %3, port %4

Cause

The received message from the POI is shorter than expected. It is mainly caused by a network issue.

• %1 is the expected length in bytes

• %2 is the number of bytes received

• %3 is the IP address of the POI

• %4 is the port used to communicate with the POI

Action

Investigate the root cause of this error if it happens too often. It can be a programming error in very rare occasions.

Error reading the message with %1, port %2: error code = %3

Cause

An error occurred while reading a message from the POI. It is mainly caused by a network issue.

• %1 is the IP address of the POI

• %2 is the port used to communicate with the POI

• %3 is the SSL connection state.

Action

Investigate the root cause of this error if it happens too often. It can be a programming error in very rare occasions.

Wrong message header length (%1) for %2, port %3

Cause

An error occurred while reading a message from the POI. It is mainly caused by a network issue.

• %1 is the length of the header read. It should have been 4 bytes.

• %2 is the IP address of the POI

• %3 is the port used to communicate with the POI

Action

Investigate the root cause of this error if it happens too often. It can be a programming error in very rare occasions.

Cannot create the SSL context: %s

Cause

The connection SSL context could not be created when a POI connected to the Gateway. It is likely a programming error. %s is the SSL library error message.

Action

Try restarting the Gateway. If it fails again, contact Amadis support.

SSL error reason: %s

Cause

This message is related to the previous SSL error. It contains the reason why the SSL operation failed.

Action

If Amadis support is contacted, include this message along with the previous message which is the origin of the error.

Cannot set the SSL certificate file: %s

Cause

Atheos Gateway could not set the server certificate or key file. It is likely an installation problem. From version 02.02.XX, the next message will be associated to the key file.

Action

Make sure that the certificate file location matches the one supplied in the configuration file and its permissions are good. Also, make sure that the certificate is a valid one and the file format complies with the X509 specifications.

Cannot set the SSL certificate key file: %s

Cause

Atheos Gateway could not set the server certificate key. It is likely an installation problem.

Action

Make sure that the certificate key file location matches the one supplied in the configuration file and its permissions are good. Make sure that the certificate key file format complies with the X509 specifications.

Private key (%1) does not match the certificate (%2)

Cause

The private key given in the configuration does not match the public key found in the certificate.

Action

Make sure that the key matches the certificate.

Error while creating the listening socket. (%s)

Cause

The socket accepting the POI connections could not be created.

Action

This is a network problem. Another instance of AtheoGW may be running. Make sure that the socket is not used by another program.

Error while binding the listening socket. address=%1, port=%2 (%3)

Cause

AtheosGW could not bind the listening socket to the address and port given in the configuration file.

Action

This is a network configuration problem. Check if the address exists and it is not used by another process.

• %1 is the address AtheosGW tries to bind to.

• %2 is the associated listening port

• %3 is a specific error message

Failed to listen on the server socket. address=%1, port=%2 (%3)

Cause

AtheosGW could not start listening to incoming POI connections.

Action

This is a network configuration problem or a programming issue. Check if the address exists and it is not used by another process. Try restarting AtheosGW.

• %1 is the address AtheosGW tries to bind to.

• %2 is the associated listening port

• %3 is a specific error message

Failed to set the server socket in a non-blocking state. address=%1, port=%2 (%3)

Cause

AtheosGW could not use non-blocking sockets.

Action

This is an internal error. Try restarting the Gateway. If it fails again, contact Amadis support.

• %1 is the address AtheosGW tries to bind to.

• %2 is the associated listening port

• %3 is a specific error message

accept() failed (%s)

Cause

AtheosGW could not accept (start reading and writing) an incoming connection.

Action

Investigate the root cause of this error if it happens too often. The connection might have been closed prematurely. It can be a programming error in very rare occasions. %s might give a clue on the cause of this issue.

If all POI connection generates this error message, try restarting AtheosGW. If it still fails, contact Amadis support.

Failed to allocate memory for a new connection.

Cause

AtheosGW could not allocate a dynamically created structure.

Action

It is caused by a lack of memory (RAM) available to AtheosGW or a programming error. Restarting AtheosGW should resolve this issue. Nevertheless, Amadis support should be contacted to report the incident.

Failed to an add a new thread node in the list. Return code = %d

Cause

AtheosGW could not exclusively access a shared memory resource. It is likely cause by a lack of CPU resources or AtheosGW is handling a lot more simultaneous connection that it was designed for.

Action

Resource usage should be checked on the host server. Amadis Support should be contacted to report the incident. The return code %d should be given to Amadis Support along with the error message.

Cannot create a new connection processing thread. Return code = %d

Cause

AtheosGW could not create a POI connection processing thread. This issue might be caused by a lack of memory (RAM) resources. Also, the maximum number of threads that a process may create might be limited by the Operating System. Also, the size of the stack or the available virtual memory may limit the number of threads. AtheosGW might be handling a lot more simultaneous connection that it was designed for.

Action

Resource usage should be checked on the host server. Amadis Support should be contacted to report the incident. The return code %d should be given to Amadis Support along with the error message.

Error initializing the file repository %1 (%2). Error code = %3

Cause

This is an installation problem. Some sub-directories required in the FileRepositoryBaseDir base directory are missing or inaccessible. FileRepositoryBaseDir is typically set in /etc/amadis/atheosgw.conf

Action

Make sure that the directory structure is installed properly and is accessible by AtheosGW.

• %1 is the sub-directory name

• %2 is the path where the directory should be located

• %3 is the return code. This return code is only meaningful to the Amadis Support Team.

Error while getting the parameter list %s

Cause

The parameter files for a given POI could not be retrieved. This file system data structure is created and maintained programmatically.

Action

Make sure that the directory exists and is accessible by AtheosGW. %s is the sub-directory name. Amadis Support should be contacted to report the incident

Error while getting the management plan list %s

Cause

The management plan files for a given POI could not be retrieved. This file system data structure is created and maintained programmatically.

Action

Make sure that the directory exists and is accessible by AtheosGW. %s is the sub-directory name. Amadis Support should be contacted to report the incident

POI management plan (%s) cannot be accessed

Cause

The management plan file for a given POI could not be read from the file system. It is created and maintained programmatically.

Action

Make sure that the file exists and is accessible by AtheosGW. %s is the management file name. Amadis Support should be contacted to report the incident

POI parameter file (%s) cannot be accessed

Cause

The parameter file for a given POI could not be read from the file system. It is created and maintained programmatically.

Action

Make sure that the file exists and is accessible by AtheosGW. %s is the parameter file name. Amadis Support should be contacted to report the incident

Cannot move the POI management plan (%s) to the attic

Cause

The management plan file for a given POI could not be archived. It is created and maintained programmatically.

Action

It is likely an installation issue. Make sure that the attic sub-directory and the file exists and is accessible by AtheosGW. %s is the management file name. Amadis Support should be contacted to report the incident

Cannot move the POI parameter file (%s) to the attic

Cause

The parameter file for a given POI could not be archived. It is created and maintained programmatically.

Action

It is likely an installation issue. Make sure that the attic sub-directory and the file exists and is accessible by AtheosGW. %s is the management file name. Amadis Support should be contacted to report the incident