Our environment manager is configured for https under a specific port (7445) which is open for connections. The environment manager server process starts without any issues, there are no errors in server or wrapper logs, but it does not listen on the port (which we verified with netstat) and we cannot access the application. The ssl certificate also looks good, so I am unsure where the issue is. Please let me know if anyone has any idea on where this issue could be happening.
Is the process listening on any ports? Is 7445 listed as the server.webapp.secure.port in Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/conf/hq-server.conf and server-5.8.0-EE/hq-engine/hq-server/conf/hq-catalina.properties, and the bio-ssl.https.port in server-5.8.0-EE/hq-engine/catalina.properties and hq-catalina.properties?
-- Greg Wootton | Principal Systems Technical Support Engineer
Hi Greg, no the process is not listening on any ports. Yes, 7445 is listed as the server.webapp.secure.port in Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/conf/hq-server.conf and server-5.8.0-EE/hq-engine/hq-server/conf/hq-catalina.properties and the bio-ssl.https.port in server-5.8.0-EE/hq-engine/catalina.properties and hq-catalina.properties. So the issue is happening from somewhere else.
You will probably need to engage technical support. I would expect an error in the server log if it is configured to bind to a port and fails to do so.
-- Greg Wootton | Principal Systems Technical Support Engineer
Thank you Greg and Yes, I have a ticket open with SAS TS. Somehow the connector in server.xml for https does not seem to work and no clues in the log. I will post the solution here once it is solved.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.