Automatically starting MQIPT

If you install MQIPT as a Windows service, or as a Linux® or AIX® System V init service, it starts when the system is started. If the service does not start correctly, follow the steps in this topic.

Always try to start MQIPT manually before it is installed as a service, to confirm that MQIPT is correctly installed and configured.

For information about using the mqiptService command to start MQIPT automatically, see Starting and stopping MQIPT.

If the MQIPT service does not start correctly, complete the following steps for your platform.

[Windows]

On Windows systems

Note: On Windows, the MQIPT service runs under the LocalSystem account. The service cannot be configured to run under a different user ID.
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 -debugevent 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® Support and supply the trace file along with any FDC files and the diagnostic output from the mqiptService -debugevent command.
[AIX][Linux]

On AIX and Linux systems

[Linux]Note:
  1. [Deprecated]The MQIPT service on Linux is deprecated. The service on Linux uses System V init, which is not supported on some recent versions of Linux.
  2. The MQIPT service is not supported on the following versions of Linux which do not support System V init:
    • Red Hat® Enterprise Linux 9.
    • SUSE Linux Enterprise Server 15.
    On these versions of Linux, use another method, such as systemd, to manage MQIPT as a service.

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:
    • [AIX]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.
    • [Linux]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. The file must be readable by the root user.
  3. Check the output from the MQIPT startup.
    • [AIX]On AIX, the MQIPT output is sent to /dev/console.
    • [Linux]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 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).