Failed to initialize the readdir() mutex

Cause

accept() failed (%s)

Cause

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

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 errorInvestigate 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.

Status

All versions.

Access error to the file repository %s for %s, port %d: error code = %d

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 directory name

• %2 is the POI connection address

• %3 is the POI connection port

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

Status

Up to version 02.02.XX

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.

Status

All versions.

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.

Status

All versions.

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

Status

All versions.

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

Status

All versions.

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.

Status

Up to version 02.02.XX

Cannot set the SSL certificate

file: %s

Cause

Atheos Gateway could not set the server certificate keyfile. 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 Also, make sure that the certificate key is a valid one and the 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 certificateStatus

From version 02.02.XX

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.

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

Status

From version 02.02.XX

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.

Status

All versions.

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.

Status

All versions.

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.

Status

All versions.

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

Cause

AtheosGW could not use non-blocking socketsbind the listening socket to the address and port given in the configuration file.

Action

This is an internal error. Try restarting the Gateway. If it fails again, contact Amadis supporta 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

Status

All versions.

Error while creating the listening socket. (%s)

CauseAtheosGW

could not accept (start reading and writing) an incoming connectionThe socket accepting the POI connections could not be created.

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 This is a network problem. Another instance of AtheoGW may be running. Make sure that the socket is not used by another program.

Status

All versions.

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.

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

Status

All versions.

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. 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

Status

All versions.

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.

Status

All versions.

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.

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.

Status

All versions.

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.

Status

All versions.

Failed to initialize the Nexo TMS message builder for %s, port %d

Cause

The Nexo TMS message builder could not be initialized. This issue is likely caused by a lack of memory.

Action

The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

• %s is the POI connection address

• %d is the POI connection port

Status

Up to version 02.02.XX

Failed to initialize the readdir() mutex

Cause

Cannot initialize an internal mutex.

Action

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

Status

All versions.

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

Status

All versions.

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

Status

All versions.

Fatal error. Failed to allocate the Nexo TMS parser buffer for %s, port %d

Cause

The Nexo TMS parser buffer could not be allocated. This issue is likely caused by a lack of memory.

Action

The server’s resource usage should be monitored. 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

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating GenericIdentification71(initiatingParty) for POI %s

Cause

The Nexo object GenericIdentification71 could not be dynamically allocated.

Action

It might be cause if the cause wasn’t found. %s is the POI ID for which the object was required.

• %s is the POI connection address

• %d is the POI connection port

Status

Up to version 02.02.XX

Memory allocation failed for %s, port %d

Cause

The Nexo object InitiatingParty, ReceivingParty, Header, MessageInError, AcceptorRejection or TerminalManagementRejection could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating ISODateTime(creationDateTime) for POI %s

Cause

The Nexo object ISODateTime could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating Header27(header) for POI %s

Cause

The Nexo object Header27 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support Status

Up to version 02.02.XX

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.

Status

All versions.

Nexo TMS message builder failed for %s, port %d: error message = %s

Cause

The Nexo message could not be created for the POI at address %s on port %d. The specific causes are given by the substring %s.

Action

Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while getting the configuration file for POI %s

Cause

The parameter . The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

Status

Up to version 02.02.XX

POI management plan (%s) cannot be accessed

Cause

The management plan file for a given POI (%s) 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

Status

All versions.

POI parameter file (%s) cannot be accessed

Cause

The parameter file for a given POI (%s) could not be parsedread from the file system. It is created and maintained programmatically.

Action

The root cause of the issue is likely the AtheosGWController parameter file generator. The incident should be reported to the Amadis Support Team. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating GenericIdentification71(terminalManagerIdentification) for POI %s

Cause

The Nexo object GenericIdentification71 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating AcceptorConfiguration6(acceptorConfiguration) for POI %s

Cause

The Nexo object AcceptorConfiguration6 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Nexo TMS message builder failed for %s, port %d: error message = %s

Cause

The Nexo message could not be created for the POI at address %s on port %d. The specific causes are given by the substring %s.

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

Status

All versions.

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.

Status

All versions.

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.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: DataSet parsing error for the POI = %s

Cause

The parameter file for a given POI (%s) could not be parsed. It is created and maintained programmatically.

Action

The root cause of the issue is likely the AtheosGWController parameter file generator. The incident should be reported to the Amadis Support Team. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating AcceptorConfiguration6(acceptorConfiguration) for POI %s

Cause

The Nexo object AcceptorConfiguration6 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident . The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating GenericIdentification71(initiatingParty) for POI %s

Cause

The Nexo message object GenericIdentification71 could not be created for the POI at address %s on port %d. The specific causes are given by the substring %s.

Action

dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident . The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06WithAlloc: Memory allocation failed for the XML message buffer %s, port %d

Cause

A buffer for the final Nexo message if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating GenericIdentification71(terminalManagerIdentification) for POI %s

Cause

The Nexo object GenericIdentification71 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating

Header27(

header) for POI %s

Cause

The Nexo object ISODateTime Header27 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while creating ISODateTime(creationDateTime) for POI %s

Cause

The Nexo message object ISODateTime could not be created for the POI at address %s on port %d. The specific causes are given by the substring %sdynamically allocated.

Action

Amadis Support should be contacted to report the incident. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

TMSMessageProcessorBuildTerminalManagementRejectionV04WithAlloc: Memory allocation failed for the XML message buffer %s, port %d

Cause

A buffer for the final Nexo message could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: Error while getting the configuration file for POI %s

Cause

The parameter file for a given POI (%s) 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. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06WithAlloc: Memory allocation failed for the XML message buffer %s, port %d

Cause

The Nexo object InitiatingParty, ReceivingParty, Header, MessageInError, AcceptorRejection or TerminalManagementRejection A buffer for the final Nexo message could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06WithAlloc: Nexo TMS message builder failed for %s, port %d

: error message = %s

Cause

The Nexo object InitiatingParty, ReceivingParty, Header, MessageInError, AcceptorRejection or TerminalManagementRejection could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. message could not be created for the POI at address %s on port %d. The specific causes are given by the substring %s.

Action

Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating GenericIdentification71(poiIdentification) for POI %s

Cause

The Nexo object GenericIdentification71 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

Status

From version 02.02.XX

TMSMessageProcessorBuildManagementPlanReplacementV06: DataSet parsing error from the POI = %s

Cause

The management plan file for a given POI (%s) could not be parsed. It is created and maintained programmatically.

Action

The root cause of the issue is likely the AtheosGWController parameter file generator. The incident should be reported to the Amadis Support Team. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

Status

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating GenericIdentification71(

initiatingParty) for POI %s

Cause

The Nexo object GenericIdentification71 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating Header27(header) for POI %s

Cause

The management plan file for a given POI (%s) Nexo object Header27 could not be parsed. It is created and maintained programmatically.dynamically allocated.

Action

The root cause of the issue is likely the AtheosGWController parameter file generator. The incident should be reported to the Amadis Support Team. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating

ISODateTime(

creationDateTime) for POI %s

Cause

The Nexo object ManagementPlan6 ISODateTime could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating GenericIdentification71(

poiIdentification) for POI %s

Cause

The Nexo object GenericIdentification71 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating

GenericIdentification71(

terminalManagerIdentification) for POI %s

Cause

The Nexo object ISODateTime GenericIdentification71 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating

ManagementPlan6(

managementPlan) for POI %s

Cause

The Nexo object Header27 ManagementPlan6 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating ManagementPlanReplacementV06(managementPlanReplacement) for POI %s

Cause

The Nexo object ManagementPlanReplacementV06 could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

TMSMessageProcessorBuildTerminalManagementRejectionV04WithAlloc: Nexo TMS message builder failed for %s, port %d: error message = %s

CauseStatus

All versions

TMSMessageProcessorBuildManagementPlanReplacementV06WithAlloc:

Memory allocation failed for the XML message buffer %s, port %d

Action

Amadis Support should be contacted to report the incident. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

TMSMessageProcessorBuildManagementPlanReplacementV06WithAlloc: Memory allocation failed for the XML message buffer %s, port %d

Cause

Cause

The Nexo object InitiatingParty, ReceivingParty, Header, MessageInError, AcceptorRejection or TerminalManagementRejection could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Access error to the file repository %s for %s, port %d: error code = %d

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 directory name

• %2 is the POI connection address

• %3 is the POI connection port

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

Status

All versions

TMSMessageProcessorBuildTerminalManagementRejectionV04WithAlloc: Error while creating ISODateTime(creationDateTime) for POI %s

Cause

The Nexo object ISODateTime could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildTerminalManagementRejectionV04WithAlloc: Memory allocation failed for %s, port %d

Cause

The Nexo object InitiatingParty, ReceivingParty, Header, MessageInError, AcceptorRejection or TerminalManagementRejection could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

From version 02.02.XX

TMSMessageProcessorBuildTerminalManagementRejectionV04WithAlloc: Memory allocation failed for the XML message buffer %s, port %d

Cause

A buffer for the final Nexo message could not be dynamically allocated.

Action

It might be cause by a lack of memory allocated to AtheosGW. The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

Status

All versions

TMSMessageProcessorBuildTerminalManagementRejectionV04WithAlloc: Nexo TMS message builder failed for %s, port %d: error

message =

%s

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.

The Nexo message could not be created for the POI at address %s on port %d. The specific causes are given by the substring %s.

Action

Amadis Support should be contacted to report the incident. The POI configuration directory (Typically /home/amadis/poi/%s) along with the content of AtheosGWController control directory (/home/amadis/control) including all subdirectories shall be sent to the Amadis Support Team.

Status

All versions

TMSMessageProcessorProcessMessageWithAlloc: Failed to initialize the Nexo TMS message builder for %s, port %d

Cause

The Nexo TMS message builder could not be initialized. This issue is likely caused by a lack of memory.

Action

The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

• %s is the POI connection address

• %d is the POI connection port

Status

From version 02.02.XX

TMSMessageProcessorProcessMessageWithAlloc: Fatal error. Failed to

allocate the Nexo TMS

parser buffer for %s, port %d

Cause

The Nexo TMS message builder parser buffer could not be initializedallocated. This issue is likely caused by a lack of memory.

Action

The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

• %s is the POI connection address

• %d is the POI connection port

Status

From version 02.02.XX

Action

TMSMessageProcessorSaveMessage: Access error to the file repository %s for %s, port %d

Cause

The Nexo TMS parser buffer could not be allocated. This issue is likely caused by a lack of memory.

: error code = %d

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 directory name

• %2 is the POI connection address

• %d %3 is the POI connection port

TMSMessageProcessorProcessMessageWithAlloc: Fatal error. Failed to allocate the Nexo TMS parser buffer for %s, port %d

Cause

The Nexo TMS parser buffer could not be allocated. This issue is likely caused by a lack of memory.

Action

The server’s resource usage should be monitored. Amadis Support should be contacted to report the incident if the cause wasn’t found. %s is the POI ID for which the object was required.

• %s is the POI connection address

• %d is the POI connection port%4 is the return code. This return code is only meaningful to the Amadis Support Team.

Status

From version 02.02.XX

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.

Status

All versions.