General Information

The Atheos Gateway component handles the connections from the POIs. It listens by default on port 55554 for connections from the POIs. Only SSL connections are accepted.

Configuration

The configuration file is typically located in /etc/amadis/atheosgw.conf.

Informational Messages

Accepted a connection from %s, port %d
Cause	AtheosGW accepted a connection from address %s, port %d.
Action	None.
Status	All versions.

Atheos Gateway 02.01.05 started using configuration %s
Cause	AtheosGW startup message
Action	None.
Status	All versions.

Atheos Gateway ended
Cause	AtheosGW processes are ended. The deamon is exiting.
Action	None.
Status	All versions.

Closing the connection with %s, port %d
Cause	AtheosGW is closing the connection with the address %s, port %d.
Action	None.
Status	All versions.

Connection closed by peer %s, port %d
Cause	The connection on from the address %s, port %d has been closed by the remove device.
Action	None.
Status	All versions.

Copyright ©2005-2020 - 9164-4187 QUEBEC INC (“AMADIS”), All Rights Reserved
Cause	AtheosGW copyright during the startup process
Action	None.
Status	All versions.

Error accepting the SSL connection with %s, port %d, code %d
Cause	The SSL connection could not be established with the device at address %s on port %d. The SSL status code is %d.
Action	None.
Status	All versions.

Error reading the message header with %s, port %d
Cause	The header was not received from the remote device. Error messages are given above.
Action	None.
Status	All versions.

Fatal error during the initialization of the Connection Manager. primaryError = %d
Cause	The initialization of the Connection Manager. Error messages are given above.
Action	None.
Status	All versions.

Fatal error during the initialization of the file repositories.
Cause	The initialization of the file repositories. Error messages are given above.
Action	None.
Status	All versions.

Listening for incoming connection on address %s, port %d
Cause	AtheosGW is now accepting connection on address %s, port %d.
Action	None.
Status	All versions.

Log rotation completed
Cause	The rotation of the log file has been performed.
Action	None.
Status	All versions.

No longer accepting connections on address %s, port %d
Cause	AtheosGW is shutting down. It does not accept new connections. The remove device will get a ‘Connection refused’ status.
Action	None.
Status	All versions.

Termination requested by the user
Cause	The termination signal (HUP signal) has been received.
Action	None.
Status	All versions.

The connection manager is shutting down.
Cause	The connection manager is shutting down. AtheowGW is about to stop.
Action	None.
Status	All versions.

Warning Messages

%d connections are still active.
Cause	The termination signal has been received. Still %d connection are active.
Action	None.
Status	All versions.

Terminating the connection with %s.
Cause	The connection was not closed timely during AtheosGW shutdown.
Action	None.
Status	All versions.

Error Messages

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.
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.
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 file. It is likely an installation problem.
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	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.
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 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
Status	All versions.

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

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
Status	All versions.

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06WithAlloc: 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

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06WithAlloc: 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. 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 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 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 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 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 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.
Status	All versions

TMSMessageProcessorBuildManagementPlanReplacementV06WithAlloc: Memory allocation failed for the XML message buffer %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	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	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 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
Status	From version 02.02.XX

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

Amadis

Atheos Gateway Run Book

General Information

Configuration

Informational Messages

Accepted a connection from %s, port %d

Atheos Gateway 02.01.05 started using configuration %s

Atheos Gateway ended

Closing the connection with %s, port %d

Connection closed by peer %s, port %d

Copyright ©2005-2020 - 9164-4187 QUEBEC INC (“AMADIS”), All Rights Reserved

Error accepting the SSL connection with %s, port %d, code %d

Error reading the message header with %s, port %d

Fatal error during the initialization of the Connection Manager. primaryError = %d

Fatal error during the initialization of the file repositories.

Listening for incoming connection on address %s, port %d

Log rotation completed

No longer accepting connections on address %s, port %d

Termination requested by the user

The connection manager is shutting down.

Warning Messages

%d connections are still active.

Terminating the connection with %s.

Error Messages

accept() failed (%s)

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

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

Cannot create the SSL context: %s

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

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

Cannot set the SSL certificate file: %s

Cannot set the SSL certificate file: %s

Cannot set the SSL certificate key file: %s

Connection manager has stopped with errors.

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

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

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

Error while creating the listening socket. (%s)

Error while getting the management plan list %s

Error while getting the parameter list %s

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

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

Failed to allocate memory for a new connection.

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

Failed to initialize the readdir() mutex

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

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

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

Memory allocation failed for %s, port %d

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

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

POI management plan (%s) cannot be accessed

POI parameter file (%s) cannot be accessed

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

SSL error reason: %s

TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: DataSet parsing error for the POI = %s

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

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

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

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

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

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

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

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

TMSMessageProcessorBuildManagementPlanReplacementV06: DataSet parsing error from the POI = %s

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

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

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

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

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

TMSMessageProcessorBuildManagementPlanReplacementV06: Error while creating ManagementPlan6(managementPlan) for POI %s

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

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

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

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

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

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

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

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

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