Troubleshooting Publisher

Download this manual as a PDF file

This section describes some common problems you might encounter while using Publisher, as well as troubleshooting solutions.

Use the following menu options to navigate the SL1 user interface:

  • To view a pop-out list of menu options, click the menu icon ().
  • To view a page containing all of the menu options, click the Advanced menu icon ().

Why do my Publisher pods keep crashing or restarting?

Numerous reasons may exist that cause a pod to restart. The following is one possible issue and solution:

Issue. If a Publisher service is unable to connect to Kafka, it will not work.

Solution. Ensure connectivity between the service, the internal Kafka server, and the external Kafka service, is possible.

Why is Publisher failing to send data even though it is not crashing?

Issue. If you check the pod logs, and you see messages indicating that an exchange is not happening, two likely scenarios could exist.

  1. If the topic that is causing the error is a data type topic, such as "avail.data" or "interface.data", it likely means that the Collector Pipeline is not set up yet, or is not set up as Publisher expects. Investigate the Collector Pipeline, the exchanges it creates, and the data models associated with them.
  2. If the topic that is causing the error is "publisher.subscription.name", it is likely that something is incorrect with the Kafka configuration or the Operator. Reviewing the logs of the Operator or the Publisher service is recommended.

Why is my subscription hanging or not being deleted properly?

Issue. When deleting a subscription, sometimes the "kubectl" command will hang and not return, or the subscription object will fail to be deleted.

Solution. Correct the subscription metadata using the Kubernetes command line to address the problem, as follows:

  1. Either go to the console of the Management Node or use SSH to access the Management Node. Open a shell session on the server. Log in with the system password.

  2. Run the following command to enter the Docker container:

    docker-compose -f docker-compose.external.yml run --rm deploy shell

  3. Enter the following command:

    kubectl patch sub/subscription-name -p '("metadata":{"finalizers":[]}}' --type=merge