ASIST Admin: Difference between revisions
Line 31: | Line 31: | ||
Presents as extensive TD Lag. | Presents as extensive TD Lag. | ||
::[[File: lag.png|700px]] | |||
::[[File: | |||
==Server Connection Issue== | ==Server Connection Issue== |
Revision as of 14:55, 15 March 2021
Accessing aSIST
Links TBC
Key Facts
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
Stephen to provide details
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.
Server Connection Issue
Likely identified by the SERVER LINK CONNECTED indication not blinking, or Last Updated not updating.
FLOWCHART TBC
Question Marks
A question mark is displayed if aSIST has been unable to match a service or it does not have a schedule.
Complete Failure
If it is not possible to access aSIST or Portainer then it is likely there is a server issue.