Troubleshooting startup problems due to port conflicts
When you start or restart the Presentation Server, the configured ports are checked to verify that they are available. In case of conflicts, the Presentation Server start-up process is aborted.
The port availability check is performed when you restart the Presentation Server through any of the following methods:
- Using the
tssh server startcommand.
- Using Microsoft Windows services.
- Restarting the Presentation Server host computer.
Any port conflicts are logged in the log file PortConflicts.log located in the InstalledDirectory\TrueSightPServer\truesightpserver\logs directory.
If you use the
tssh server start command to restart the Presentation 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 HTTP connector port||80 (Windows)|
|Tomcat Apache server HTTPS connector port||443 (Windows)|
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
You can run the following commands to check the port availability from the <Presentation Server Installation Directory>\truesightpserver\bin directory:
- (supported only with TrueSight Presentation Server version 11.3.02 and later)
tssh component portcheck. For details, see Checking a component port availability from the Presentation Server.
tssh server portcheck
Details of the busy and available ports are displayed, similar to the following example:
Checking configured ports availability Tomcat connector port 80 is busy. Tomcat redirect port 443 is busy. Database port 5432 is busy. Index Server port 9300 is busy. Event gateway port 1900 is busy. Check C:\auto_product\tsps\truesightpserver\logs\PortConflicts.log log file for output.