Hi,
A customer is having an issue with Pulse, for some reason after a restart of the service, the web app is not available any longer.
The Services start and there is no error in the logs, but the web page does not open…
in the logs it just stops on the initialization:
they have Pulse v6.5.2, with SQL database as CS… A restart of the services or the OS did not help, they also tried running the installer again for the same version and no luck…
I tried increasing the java JVM memory but it also did not help…
We already checked that the Pulse DB in SQL is available and the User set has permissions to the DB… Pulse services are running with valid service account…
Has anyone seen anything similar or any idea on how to check this issue?
Thanks!
Rodrigo
Following a support call done by @ecarmona
The problem was a clash of requests through localhost via port 8093, which is the SSL port in Pulse.
An environment in Pulse was set to use port 8093 to connect to the monitor where Pulse was installed.
This caused Pulse to generate a request to its own Web Server SSL port, a request that never finished.
The solution was to temporarily disable port 8093 in the server.xml of Pulse and change the environment settings to use port 8094 instead of 8093.
1 Like
Hi @Vincent ,
Thanks, I was about to update it and add the solution here!
Enabling the Debug logs was very helpful to spot this issue with this port, where we could see that it was trying to send a request via port 8093.
How to enable here:
Thanks CODE Team!!
1 Like
