When trying to start CABI with startServers.sh after configuring HTTPS, it fails to start
search cancel

When trying to start CABI with startServers.sh after configuring HTTPS, it fails to start

book

Article ID: 404395

calendar_today

Updated On:

Products

Network Observability Spectrum

Issue/Introduction

$ ./startServers.sh
Default Postgres database is already running
Default Tomcat server port is 8080 8443
./startServers.sh : tomcat (pid 82005) already running
...
Existing PID file found during start.
Tomcat appears to still be running with PID <PID>. Start aborted.
If the following process is not a Tomcat process, remove the PID file and try again:
...
grep: 8443: No such file or directory
grep: 8443: No such file or directory
11
grep: 8443: No such file or directory
22
^Z
[4]+  Stopped                 ./startServers.sh

Cause

The 8080 connector was left in the server.xml file and the startServers.sh is only expecting one connector entry:

Default Tomcat server port is 8080 8443

Resolution

Either remove or comment out the 8080 connector entry then try to start services once again, for example:

Before:

<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443"/>

 

After:

<!--

<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443"/>

-->