Troubleshooting startup problems due to port conflicts
When you start or restart the Infrastructure Management server or remote Integration Service, the configured ports are checked to verify that they are available. In case of conflicts, the Infrastructure Management server or remote Integration Service start-up process is aborted.
Infrastructure Management server
The port availability check is performed when you restart the Infrastructure Management server through any of the following methods:
- Using the pw sys start command.
- Using Microsoft Windows services.
- Restarting the Infrastructure Management server host computer.
Any port conflicts are logged in the log file portsCheck.log located in the InstalledDirectory\TrueSight\pw\pronto\logs directory.
If you use the pw sys start command to restart the Infrastructure Management server, port conflicts, if any, are displayed on the command-line interface.
The following ports are checked for their availability:
Component | Default port number |
|---|---|
Tomcat Apache server | 8080 |
SAP SQL Anywhere database server | 2638 |
Integration Service (Agent controller) | 12124 |
Integration Service (PATROL Agent) | 3183 |
Rate | 15000 |
JServer Event Server | 9149 |
Log Server | 12141 |
JMS | 8093 |
JNDI | 1100 |
Agent Controller | 12123 |
High-availability | 10590 |
During installation, if you specified a custom port for any component, that port is checked instead of the default port.
To manually check for port conflicts
From the pw command prompt window, run the following command:
pw sys portcheck
Details of the busy and available ports are displayed, similar to the following example:
Port 12124 is busy
Port 9149 is busy
Port 8093 is busy
Port 12141 is busy
Port 3183 is busy
Port 1100 is busy
Port 2638 is busy
Port 12123 is busy
Port 8080 is busy
Please check C:\TrueSight\pw\pronto\logs\portsCheck.log file for the command output.
Remote Integration Service
The port availability check is performed when you restart the remote Integration Service through any of the following methods:
- Using the pw IS start command on UNIX.
- Using Microsoft Windows services.
- Restarting the remote Integration Service from the TrueSight console.
- Restarting the remote Integration Service host computer.
Any port conflicts are logged in the log file IS_portCheck.log located in the InstalledDirectory\TSIMAgent\Agent\pronto\logs directory.
The following ports are checked for their availability:
Component | Default port number |
|---|---|
Integration Service (Agent controller) | 12124 |
Integration Service (PATROL Agent) | 3183 |
During installation, if you specified a custom port for the remote Integration Service, that port is checked instead of the default port.
Related topics
pw-system-portcheckTroubleshooting Presentation Server startup problems due to port conflicts