ASIST Admin: Difference between revisions
(Created page with "Things to note: ::*All aSIST tools receive the same data. Therefore, if there is an issue with one tool there is likely to be issues with the others. ::*All aSIST containers...") |
No edit summary |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Accessing aSIST = | |||
<b>TBROC:</b> | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=3A | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=3B | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=COREC | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=CORES | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=CSTB | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=LEWISHAM | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=GROVEPARKA | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=ESWS | |||
<b>Wimbledon ASC:</b> | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=QUEENSTOWN | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=BARNES | |||
<b>WMSC</b>: | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=AYNHOJUNCTION | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=SOHOSJ | |||
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=BARNTGREEN | |||
= Key Facts = | |||
Things to note: | Things to note: | ||
::* | ::*aSIST runs on the 'acumen back-end'. Therefore it is possible an issue affecting one system (message feeds, container issue etc) could be affecting the other. | ||
::*Similarly, all aSIST tools receive the same data. Therefore, if there is an issue with one tool there is likely to be issues with the others. | |||
::*All aSIST containers within Portainer should show as <b>running</b>. | ::*All aSIST containers within Portainer should show as <b>running</b>. | ||
::*pHpmyadmin can be used to see when the Wrong Route Tool has been activated. See the <i>wrongRoutes</i> table. | |||
= aSIST Containers = | |||
All aSIST containers within Portainer should show as <b>running</b>. | |||
::[[File: containers.png|900px]] | |||
=What can go wrong?= | |||
The [[aSIST Support]] page is provided for system users detailing potential issues and initial steps they should take before contacting on-call support e.g. restarting browser, checking internet connection. | |||
If informed of an issue, it would be worthwhile confirming the user has undertaken these initial steps. | |||
However in the event the issue is not at their end, these flow charts detail suggested steps for the on-call technician. | |||
==System Lag Issue== | |||
Presents as extensive TD Lag. | |||
::[[File: lag.png|700px]] | |||
==Server Connection Issue== | |||
Likely identified by the <i>SERVER LINK CONNECTED</i> indication not blinking, or <i>Last Updated</i> not updating. | |||
::[[File: server.png|500px]] | |||
==Question Marks== | |||
A question mark is displayed if aSIST has been unable to match a service or it does not have a schedule. | |||
::[[File: asist_unmatched.png|350px]] | |||
::[[File: FC2.png|450px]] | |||
==Complete Failure== | |||
If it is not possible to access aSIST or Portainer then it is likely there is a server issue. | |||
Contact Stephen/Jon to resolve. | |||
Latest revision as of 15:11, 15 March 2021
Accessing aSIST[edit]
TBROC:
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=3A
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=3B
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=COREC
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=CORES
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=CSTB
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=LEWISHAM
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=GROVEPARKA
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=ESWS
Wimbledon ASC:
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=QUEENSTOWN
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=BARNES
WMSC:
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=AYNHOJUNCTION
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=SOHOSJ
https://asist.tms-uk-rail.co.uk/asist/wrongroutetool/index.php?system=BARNTGREEN
Key Facts[edit]
Things to note:
- aSIST runs on the 'acumen back-end'. Therefore it is possible an issue affecting one system (message feeds, container issue etc) could be affecting the other.
- Similarly, all aSIST tools receive the same data. Therefore, if there is an issue with one tool there is likely to be issues with the others.
- All aSIST containers within Portainer should show as running.
- pHpmyadmin can be used to see when the Wrong Route Tool has been activated. See the wrongRoutes table.
aSIST Containers[edit]
All aSIST containers within Portainer should show as running.
What can go wrong?[edit]
The aSIST Support page is provided for system users detailing potential issues and initial steps they should take before contacting on-call support e.g. restarting browser, checking internet connection.
If informed of an issue, it would be worthwhile confirming the user has undertaken these initial steps.
However in the event the issue is not at their end, these flow charts detail suggested steps for the on-call technician.
System Lag Issue[edit]
Presents as extensive TD Lag.
Server Connection Issue[edit]
Likely identified by the SERVER LINK CONNECTED indication not blinking, or Last Updated not updating.
Question Marks[edit]
A question mark is displayed if aSIST has been unable to match a service or it does not have a schedule.
Complete Failure[edit]
If it is not possible to access aSIST or Portainer then it is likely there is a server issue.
Contact Stephen/Jon to resolve.