WKC connector pod in CrashLoopBackoff state

Check the following settings if the Watson Connector pod is in the CrashLoopBackoff or Error state.

Check that there are no Watson Knowledge Catalog export policies that are in running state when you perform any changes to Watson Knowledge Catalog connector application configuration.

Check the settings for the following environment variables if you are using IBM Cloud® Watson Knowledge Catalog:

WKC_API_KEY

Check the correct value for the following parameter if you are using IBM Cloud Watson Knowledge Catalog:

WKC_BASE_URI

Check the settings for the following environment variables if you are using an on-premises Watson Knowledge Catalog :

WKC_BASE_URI 
WKC_AUTH_URI
WKC_CONNECTION_MAP

After successfully exporting records, if you change an environment variable to an invalid value and then export records again, you can end up with unprocessed messages in the Kafka buffer. You must clear these messages before you can change the invalid environment variable to the correct value. Run the following commands to clear the Kafka queue and then restart the Watson Knowledge Catalog connector application.

Clear Queue

/opt/kafka/bin/kafka-topics.sh --delete --zookeeper localhost:2181 --topic WKCConnector_work

Recycle Pod

oc -n ibm-data-cataloging delete pod -l role=wkcconnector

If the Watson Knowledge Catalog connector pod remains down after you have performed the above steps, do the following:

If the Watson Knowledge Catalog connector (WKC connector) pod in IBM Data Cataloging cannot be started, delete the existing pod using the following command:
```
oc -n ibm-data-cataloging delete pod -l role=wkcconnector
```
Retrieve the logs from the WKC connector pod using the following command:
```
oc -n ibm-data-cataloging logs deployment/isd-wkcconnector
```

Check for errors in the logs by running the following command:

oc -n ibm-data-cataloging logs deployment/isd-wkcconnector | grep error

If the log terminates with an exception, check the policy engine log for errors by using the following command:
```
pollog | grep error
```

Check if the following error message appears at the time of the exception:

<time_stamp> - policy.policyapiservice - ERROR - b'Error: Cannot update application, 'WKCConnector, it is in use by the following policies: ["<policy_id>"]. Please stop these policies’

The WKC connector pod might not start until the error shown in step 5 is resolved.
Go to the Tag Management Policies section in the user interface and stop all running policies.
Once the policies are stopped, then restart the WKC connector pod by deleting it:
```
oc -n ibm-data-cataloging delete pod -l role=wkcconnector
```