Troubleshoot System Automation Info Broker

This topic describes the possible error scenarios of the System Automation Info Broker and how you can spot and troubleshoot them.

Data Services Task (DST) issues

Possible error scenarios
  • Wrong procedure name, which is specified with the PROCNAME parameter in the INGKINIT initialization member.
  • Unable to create the pipe, which is specified with the PIPENAME in the INGKINIT initialization member, because the pipe path is a read-only directory.
  • Invalid encoding, which is specified with the CCSID parameter in the INGKINIT initialization member.
Solution
  1. Enable debug in the initialization member INGKINIT.
    DEBUG=ON
  2. Restart the task INGTKDST.
  3. Check the Netlog for error messages.
  4. Also, verify that the INGKINIT configuration that is printed in the Netlog is valid.

System Automation Info Broker startup problems

Possible error scenarios

  • The configuration files directory (that is specified with the IBRKR_CONFIG_HOME parameter in file ing.infobroker.environment) was configured incorrectly.
  • Files do not exist.
  • Wrong permissions to read the files.
  • The working directory of the System Automation Info Broker (that is configured with the IBRKR_WORKING property in file ing.infobroker.environment) is read-only.

Solution

If you experience startup problems with the System Automation Info Broker, you can change the trace option in the JCL (default name is INGEKPRC) that is used to start the component.

  1. Set the logging level of the JCL to trace '+T'.
    // LOGLVL='+T', <Debug LVL: +I(info) +T(trc)>
  2. Restart the System Automation Info Broker.
  3. Go to the end of SYSOUT and check for error messages. Error messages contain the error itself and an explanation of what caused this error.  

JVM startup failure

Possible error scenarios
  • Pipe was configured incorrectly.
  • The directory for temp storage is read-only.
  • Missing files or typos.
Solution
  1. Locate the log file. The location of the log file is either configured in ing.infobroker.logging.xml or the default directory is used: /var/log/ing/infobroker.
  2. Scroll to the end of the log file to check the error messages. Here is one example error.

JVM runtime exceptions

Possible error scenario: No messages are sent and received in the Apache Kafka topic.

Solution

  1. Check if System Automation Info Broker Hub is running by executing the following command in NetView.
    LIST TASK=INGTKDST
    From the command output, you can tell if System Automation Info Broker is active or not.
  2. If the System Automation Info Broker task status is not active, start it.
  3. If the System Automation Info Broker task status is active, check for other reasons. Check the Java™ log for warning from the kafka-producer-network-thread. The default path of the log file is /var/log/ing/infobroker/ing.infobroker.trace.log.
    If you notice the following messages, then either the Apache Kafka Broker is down or the property spring.kafka.bootstrap-servers (in file ing.infobroker.properties) was configured incorrectly.