Automatically starting MQIPT

If we install MQIPT as a Windows service, or as a UNIX or Linux init.d system service, it starts when the system is started. If the service does not start correctly, follow the steps in this topic.


On Windows systems

Always try starting MQIPT manually before installing it as a Windows Service, to confirm correct installation. See Automatically starting MQIPT on Windows for more details.

If the MQIPT service does not start correctly, complete the following steps:

  1. Open the Windows Registry Editor and navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MQInternetPassThru key. Check that the ConfigFilePath setting contains the correct path to the mqipt.conf configuration file. Also, check that the ImagePath setting contains the correct path to mqiptService.exe.
  2. Run the mqiptService -debugevents command from an Administrator Command Prompt to write service startup information in the Windows application event log. Additional information is also displayed in the Command Prompt console window. Examine the diagnostic information to determine the cause of the failure.
  3. If the cause of the failure is still not clear, use Windows file explorer to navigate to the directory specified in ConfigFilePath where mqipt.conf is located. Examine the contents of the errors subdirectory to look for FDC files containing FFST records.
  4. If the cause of the failure is still not clear, enable trace by setting the Trace property to 5 in the [global] section of mqipt.conf. Restart the MQIPT service. A trace file is be written in the MQIPT errors directory. If necessary, contact IBM Software Support and supply the trace file along with any FDC files and the diagnostic output from the mqiptService -debugevents command.


On UNIX and Linux systems

Always try starting MQIPT manually before installing it as a service, to confirm correct installation. See Automatically starting MQIPT on UNIX or Linux for more details.

If the MQIPT service does not start correctly, complete the following steps as the root user:

  1. Check that the MQIPT service is installed. You might need to uninstall and reinstall the service. To check that the service is installed:

    • On AIX, run the command lsitab mqipt and check that the output shows the correct installation directory. Here is an example of the output for an MQIPT service running from the /usr/opt/mqipt installation: 
      mqipt:2:once:/usr/opt/mqipt/bin/mqipt /usr/opt/mqipt > /dev/console 2>&1
      Check that the MQIPT executable named exists and is executable by the root user.
    • On Linux, check for the existence of the MQIPT init.d script named /etc/init.d/mqipt. The script must exist and must be executable by the root user.

  2. Ensure that the installation directory contains the mqipt.conf file, which must be readable by the root user.
  3. Check the output from the MQIPT startup.

    • On AIX, the MQIPT output is sent to /dev/console.
    • On Linux, the output is sent to a file named console.log in the logs directory of the MQIPT installation.

    Look for any MQIPT errors and address the cause. If no console output is present then MQIPT was not started by the operating system. Consult your operating system documentation for details of how to diagnose service startup failures.

  4. If the cause of the failure is still not clear, navigate to the MQIPT installation directory where mqipt.conf is located. Examine the contents of the errors subdirectory to look for FDC files containing FFST records.
  5. If the cause of the failure is still not clear, enable trace by setting the Trace property to 5 in the [global] section of mqipt.conf. Restart the MQIPT service. A trace file is written in the MQIPT errors directory. If necessary, contact IBM Software Support and supply the trace file along with any FDC files and the diagnostic output from /dev/console (on AIX) or console.log (on Linux).

Parent topic: Troubleshooting IBM MQ Internet Pass-Thru