How to restart NRDAv2 Frontdoor
- Former user (Deleted)
Identifying if the Frontdoor service has stopped
Identifying if the Frontdoor service has stopped
There are two ways to identify if the Frontdoor service has stopped running.
1 Admin Section
If you are an Admin on the NRDAv2 application you will be able to navigate to the Admin section at the top of the page.
From the Admin section select the System Monitoring option from the menu
on the left hand side of the screen.
System Monitoring
The system monitoring page shows a list of systems being used by the application and their current health.
If there are multiple Frontdoor services connected to the application then there will multiple rows showing each Frontdoor and their health.
If any of the Frontdoor services are showing Down then you can follow the next section (Restarting Frontdoor) to restarting the Frontdoor.
2 Frontdoor Queue Length
An alternative way of identifying if the Frontdoor has stopped is by navigating to any Dataset and going to the Ingest Rules page.
At the bottom of the page below any Ingest Rules there is a section called "Latest queue length for front door messages".
Below are a few examples for what to look out for when the Frontdoor is Down.
This shows an example of a Frontdoor with no messages
waiting to be consumed. This means that the Frontdoor is
functioning correctly and nothing needs to be done.
This is an example of a Frontdoor with messages waiting to be consumed.
If the numbers shown in the queues do not change for a period of time then
the Frontdoor will need to be restarted.
Restarting Frontdoor Service
When you have identified what Frondoor service has stopped working you will need to remote desktop to the windows server where that Frondoor service is running.
Once you are on the server you can open Internet Information Services (IIS) Manager and open the sites tab on the left to find any running Frontdoor Services.
1. Identifying Specific Frondoor (IIS)
If there are multiple Frontdoor services running and you are unsure which one needs to be restarting then you can do the following to find the name of the Frontdoor service that displayed in NRDAv2 UI.
- Right click on one of the services and click Explore. (This will open file explorer to the location of the service)
- There should be a file called appsettings.json, open this file with a file editor e.g. Notepad
- Once the file is open it will display a json object and the key variable you are looking for is "ServiceName"
- The value of the "ServiceName" is the same name that appeared in the NRDAv2 UI. e.g. "ServiceName": "FrontDoor-DFSData"
2. Navigating to Hangfire Web Address
When you have identified the Frontdoor service in IIS you will need to open a web browser to that service providing the port and adding "/hangfire" to the end of the URL e.g. "http://localhost:4040/hangfire"
A quick way to navigate to the address through IIS is to click the "Browse Website" button on the right hand
side of the screen under the Manage Website Tab.
After the web page has opened you can update the URL by adding "/hangfire" to load the page.
When the page has loaded you should see a Hangfire Dashboard. If this page has loaded successfully then the Frontdoor Service will start processing files again.