HealthCheck Assistance
The Health Check has reported that the NOM is in blocked mode or not operational.
When the NOM is blocked it means that all clients will be redirected to the Buddy Server which will service all requests. This may be intentional or because of a system failure.
When the NOM is reported as being "non-operational", this could indicate a problem other than being blocked. With ENPS 9 and later versions of ENPS, the NOM process is tightly linked to the search engine. Therefore this can indicate an issue with the Solr search service.
For NOM being reported as blocked:
Log into the Buddy Server of the server reported as blocked. This will be highlighted in the alert message you received.
Check that the buddy queue on that server is clear.
If the buddy queue is clear, log into the server that is being report as blocked. At a convenient time, open the NOM Configuration/Status window and uncheck the option to "Block Primary Access".
Ensure all operations are as expected.
Review system Event Logs and any other that may indicate why this action occurred.
If the buddy queue is NOT clear, log into the server that is being reported as blocked. Launch the NOM in block mode by entering F:\NOM\nom.exe /block. If your ENPS data drive is not F:, change the drive letter accordingly. Note that there is a space between exe and /block. Make sure that the buddy queue on the Buddy server starts to empty. Once completely empty, unblock the NOM at a convenient time. If the Buddy queue is not emptying, contact the AP ENPS Helpdesk.
For NOM being reported as non-operational:
Log into the server where the issue is being reported.
Open Computer Management | Services and check the state of the SolrJavaService. If it is in a stopped state, attempt to restart it.
If the restart fails, please contact the AP ENPS Helpdesk.
Should the restart be successful, please follow the steps above to return the server to service.
No thresholds set for this monitoring.