Troubleshooting startup problems due to port conflicts
When you start or restart the TrueSight Presentation Server, the configured ports are checked to verify that they are available. In case of conflicts, the TrueSight Presentation Server start-up process is aborted.
The port availability check is performed when you restart the TrueSight Presentation Server through any of the following methods:
- Using the tssh server start command.
- Using Microsoft Windows services.
- Restarting the TrueSight 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 TrueSight 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) |
PostgreSQL | 5432 |
Elasticsearch | 9200 |
Cell gateway | 1900 |
High-availability | 7800 |
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 InstalledDirectory\TrueSightPServer\truesightpserver\bin directory, run the following command:
tssh server portcheck
Details of the busy and available ports are displayed, similar to the following example:
Tomcat connector port 80 is busy.
Tomcat redirect port 443 is busy.
Database port 5432 is busy.
Index Server port1 9200 is available.
Index Server port2 9300 is busy.
Event gateway port 1900 is busy.
Check C:\auto_product\tsps\truesightpserver\logs\PortConflicts.log log file for output.
Related topics
Presentation-Server-tssh-commandsPresentation Server ports