...
A description of what you were trying to accomplish
the API call URL. Mask the token value if its value is sensitive or at least a part of it. Leave the token tag.
The API call payload
the The Detailed View of the all the related Application Log Entries which include success and failure messages
The response returned by Atheos to the API calling application.
If the return code from the server is 500, the error logs from Apache2 on Atheos Server are required.
Optionally, a database dump may be given. It might be requested if further information is required to complete the investigation.
An API call doesn’t return the expected results
...
A description of what you were trying to accomplish
The expected results including the difference between the actual results and the expected ones.
the The API call URL. Mask the token value if its value is sensitive or at least a part of it. Leave the token tag.
The API call payload
the Detailed View of the all the related Application Log Entries which include success and failure messages
The response returned by Atheos to the API calling application.
Optionally, a database dump may be given. It might be requested if further information is required to complete the investigation.
A POI configuration is missing some parameters
...
What are the missing parameters including their names and values.
AtheosGateway Controller Logs. Their location and an example are given below.
AtheosGateway Control files. Their location and an example are given below.
The POI configuration files. The complete structure shall be included with the incident report. Their location and an example are given below
Optionally, a database dump may be given. It might be requested if further information is required to complete the investigation.
A POI doesn’t get a newly deployed configuration
...
the Detailed View of the all the related Application Log Entries which include success and failure messages
if possibleThe POI configuration files. The complete structure shall be included with the incident report. Their location and an example are given below.
Optionally, a database dump would be very usefulmay be given. It might be requested if further information is required to complete the investigation.
The configuration building process failed
...
AtheosGateway Controller Logs. Their location and an example are given below.
AtheosGateway Control files. Their location and an example are given below.
The POI configuration files. The complete structure shall be included with the incident report. Their location and an example are given below.
...
Any messages exchanged between the POI and AtheosGateway. Their location and an example are given below.
Atheos Gateway logs. Their location and an example are given below.
POI Configuration
The
...
The POI configuration files. The complete structure shall be included with the incident report. Their location and an example are given below.
The POI doesn’t get
...
configured even if it has received its configuration
...
This problem is likely caused by an incompatible configuration.
If your installation has more than one AtheosGateway, include the artifacts of all them with the incident report.
The artifacts to join to the incident report are:
...
If your installation has more than one AtheosGateway, include the artifacts of all them with the incident report.
POI Configuration
The artifacts to join to the incident report are:
...
A description of what the user was trying to accomplish
The detailed view of the corresponding Application Log entry. An example is given below.
...
Artifact Examples and Locations
UI Crash Dump
This artifact is displayed in the user’s browser window.
...
| Code Block |
|---|
<DataSet><Id><Tp>PARA</Tp><Vrsn>2021-01-28 21:49:45</Vrsn><CreDtTm>2021-01-28T21:52:01</CreDtTm></Id><POIId><Id>SOFT0003</Id><Tp>OPOI</Tp><ShrtNm>SoftPOI #3</ShrtNm></POIId><Cntt><RplcCfgtn>true</RplcCfgtn><Mrch ntParams><ActnTp>UPDT</ActnTp><MrchntId>00000NEXOMER001</MrchntId><Vrsn>2021-01-28 21:49:45</Vrsn></MrchntParams><TMSPrtcolParams><ActnTp>UPDT</ActnTp><TermnlMgrId><Id>ATHEOS-TMS01</Id></TermnlMgrId><MntncSvc>MT MG</MntncSvc><Vrsn>2021-01-28 21:49:45</Vrsn><HstId>TMS001</HstId></TMSPrtcolParams><HstComParams><ActnTp>UPDT</ActnTp><HstId>TMS001</HstId><Adr><Adr><NtwkTp>IPNW</NtwkTp><AdrVal>51.79.49.100:1054</AdrVal></Adr> </Adr></HstComParams> |
Apache2 error log
They are typically found in /var/log/apache2/error.log. The filename may be different depending on your installation. These logs are particularly important when Atheos Server returns a 500 error code.
| Code Block |
|---|
[Wed Mar 31 00:00:01.739566 2021] [mpm_prefork:notice] [pid 1670] AH00163: Apache/2.4.41 (Ubuntu) configured -- resuming normal operations
[Wed Mar 31 00:00:01.739591 2021] [core:notice] [pid 1670] AH00094: Command line: '/usr/sbin/apache2'
[Thu Apr 01 00:00:02.441062 2021] [mpm_prefork:notice] [pid 1670] AH00171: Graceful restart requested, doing restart
AH00112: Warning: DocumentRoot [/var/www/html/atheosserver/public] does not exist
AH00112: Warning: DocumentRoot [/var/www/html/PoiMessagesSinkHole] does not exist
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message |