CIF Processing: Difference between revisions
Line 13: | Line 13: | ||
# <code><user>@acumen-app-server:~$ docker-compose logs download_cif</code> | # <code><user>@acumen-app-server:~$ docker-compose logs download_cif</code> | ||
If there | If there were any issues in downloading and processing the CIF, there would be a corresponding entry in the container logs. | ||
=== Application Logs === | === Application Logs === |
Revision as of 14:45, 7 July 2020
Application servers connect to the NR PPTE (Network Rail - Pre Production Test Environment) to download the POINTA CIF.
Container Logs
As described in the Data Feeds section, the full CIF is taken and processed at initialisation and an incremental CIF is taken and processed at 01:00 Hrs each morning.
The service that obtains and processes the CIF is ran via a cron job and once the CIF is processed, the container stops running; despite this, Administrators can view the last container log entry thus:
- Start an ssh session to the relevant application server;
- At the prompt, enter the following commands:
<user>@acumen-app-server:~$ cd ~/dockerise/
<user>@acumen-app-server:~$ docker-compose logs download_cif
If there were any issues in downloading and processing the CIF, there would be a corresponding entry in the container logs.
Application Logs
To browse the application logs, follow the following steps:
- Identify the ip address of the server in the Administration page;
- Browse to the following url: http://<ip address>:8080/logs/download_cif/
There are numerous logs available that are of interest - the main ones being:
- download_pointa_cif.log;
- extract_cif.log;
- post_processing.log;
- assoc_post_processing.log.
Should any error messages or other log entries of concern be identified, Administrators are requested to update the support ticket with the details.