Troubleshooting startup problems due to port conflicts
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
Run the pw sys portcheck command. For details, see pw-system-portcheck.
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.
Configuration of HPOV or Tivoli adapters for TrueSight Infrastructure Management high-availability environment
In a high-availability environment where HPOV or Tivoli adapters are configured, after the TrueSight Infrastructure Managementfails over, the remote Integration Service cannot restart because of a port conflict. To avoid this, start the saadapter process on a port other than 3183. Do the following:
- Log in to the computer where you have installed TrueSight Infrastructure Management, and stop the default pproxy and saadapter services.
- Navigate to the <installation_directory>\BMC Software\BPPMAgent\Agent\pproxy\PNS\bin directory, and take a backup of the pproxsrv.exe file.
- Open the command prompt and navigate to the <installation_directory>\BMC Software\BPPMAgent\Agent\pproxy\PNS\bin directory.
- Run the following command:
pproxsrv4182.exe -install -p 4182 - Run the following commands over the pproxcli to configure the saadapter port:
cd install dir\BMC Software\BPPMAgent\Agent\pproxy\PNS\bin
pproxcli
/connect -host localhost -port 4182 -username admin -password admin
/PATROL/config/setProfileAttribute -profile _SA_DEFAULT_ -port 4183
/PATROL/config/commit - In the Services window, restart the pproxsrv4182.exe service, and start the default pproxy service.
- Configure the HPOV and Tivoli adapters.