Perform the checks in this section if the Event Search
tab fails to respond and displays the error message Request posted
to LA failed with 'Request to Operations Analytics - Log Analysis
failed with a network error'
.
About this task
This could be due to a network issue, or to a slow or unresponsive
Operations Analytics - Log Analysis (LA) server.
Procedure
- Review the Web GUI log
for errors which occured before to the
Request posted to LA failed
with 'Request to Operations Analytics - Log Analysis failed with a
network error'
log entry.
- If a 'Read timed out' error occurred it could be due to
either a network issue or an unresponsive Log Analysis server. Example
of a 'Read timed out' error:
[2016-03-04T18:24:50]:SEVERE:HEMJS0596E:[WebContainer : 5]:IBM Operations Analytics - Log Analysis request failed with exception 'Read timed out'.
[2016-03-04T18:24:50]:SEVERE:HEMJS0608E:[WebContainer : 5]:Request posted to LA failed with 'Request to Operations Analytics - Log Analysis failed with a network error. See Web GUI log for more information.'.
- To investigate if the LA server is responsible for the
delay, review the contents of the
UnityApplication.log file
in the LA server's logs directory and look for log
entries similar to the following: 03/04/16 18:21:43:581 GMT [Thread-70] INFO - SolrSearchQuery : Solr Query 14[1/1], search Time: 51261
-
If it is reporting search times in excess of 30 seconds (reported as 30,000ms in the log
entry), the slow query times in LA are causing Web GUI to timeout. Consult
the IBM Operations Analytics - Log Analysis documentation and search for
Hardware and
software requirements
to find the minimum hardware specification required to run LA.