Event Query service pod does not start
When installing Netcool® Operations Insight® on OpenShift® the
ibm-hdm-analytics-dev-eventsqueryservice
pod fails to start.
Problem
The ibm-hdm-analytics-dev-eventsqueryservice
pod has not started, or is taking a
long time to start.
Cause
The ibm-hdm-analytics-dev-eventsqueryservice
is waiting for the
eventsquery-checkforschema
container.
- Inspect the Event query service log file by running the following
command:
Where:oc logs name-ibm-hdm-analytics-dev-eventsqueryservice-random-string -c eventsquery-checkforschema
name
is the name of your installation instance.random-string
is a random string of numbers and letters.
- Look for a line that contains text similar to the
following.
This log entry indicates that the required schema has only been partially created, causing the connection to the schema to time out, with the result that the dependent{"name":"checkdb","hostname":"noi-204-ibm-hdm-analytics-dev-eventsqueryservice-574cd4bc78ws2g","pid":22,"level":30,"requirements":{"keyspace":true,"events":true,"events_byid":false},"msg":"Requirements not met, re-check timer started.","time":"2020-06-29T22:30:08.610Z","v":0}
ibm-hdm-analytics-dev-eventsqueryservice
pod fails to start.
Resolution
To resolve this issue, proceed as follows:- From the Kubernetes command line, issue the following command to list all of the pods on your
cluster.
oc get pod
- Find the archiving service pod. This pod has a name similar to the
following:
Where:name-ibm-hdm-analytics-dev-archivingservice-random-string
name
is the name of your installation instance.random-string
is a random string of numbers and letters.
mynoi-ibm-hdm-analytics-dev-archivingservice-8656c4dc8b-hxkzh
- Copy the pod name from the previous step for use in the next command.
- Issue the following command to enter the archiving service and create the missing elements of
the
schema.
Whereoc exec -it name-of-archiving-service-pod /app/entrypoint.sh -- npm run setup
name-of-archiving-service-pod
is the name of the archiving service pod.Note: This command will generate a number of harmless errors, which can be ignored.
#5380 July 2020