Troubleshooting

If you experience any functional issues with the agent, review the following information and supply it to the AppDynamics Support.

  • The agent log. The IIB agent writes status information into the configured log directory, or /tmp/appd if the configuration has not been read at the time the message is logged. The status information can help diagnose issues with the agent.
  • The system log. The IIB broker writes status messages into the system log. The messages include information about the loading and operation of user exits, such as the IIB agent.
  • Abend files in the IIB errors directory. The default location is /var/mqsi/common/errors .
  • Core files, if they exist.
Note: If the user-exit name provided in the controller-info.xml file is not alphanumeric, the broker cannot load the agent and fails to start.

If you have an issue with the agent or if you want to disable it, perform the following:

  1. Stop the broker mqsistop <broker-name>.
  2. Perform the following based on the version applicable to you:
    OptionDescription
    IIB 10 Remove the Splunk AppDynamics user exit mqsichangebroker <broker-name> -x "" -e ""
    ACE 11, ACE 12

    Set the following parameters in the node.conf.yaml file as an empty string:

    UserExits:

    activeUserExitList: ''

    userExitPath: ''
  3. Start the broker mqsistart <broker-name>.