Cloned Server is not reachable

Question

Hi all

I have cloned our prod server as a stage env. It has the same hardware, software, configuration and network setup.

I have followed the following steps from this tutorial: https://confluence.atlassian.com/conf713/create-a-staging-environment-for-upgrading-confluence-1077914833.html

I also followed the tutorial how to create a new server id to avoid conflict with linked product: https://confluence.atlassian.com/confkb/how-to-change-the-server-id-of-confluence-211649693.html

Our server runs as a windows service and it works fine.

Only if restart the stage server I see the following logs:

Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [org.hsqldb.jdbc.JDBCDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [net.sourceforge.jtds.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
Nov 11, 2021 3:41:44 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-90"]
Nov 11, 2021 3:41:44 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8090"]
Nov 11, 2021 3:43:41 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.
Nov 11, 2021 3:43:42 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.
Nov 11, 2021 3:43:42 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.
Nov 11, 2021 3:43:42 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Nov 11, 2021 3:43:44 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-90"]
Nov 11, 2021 3:43:44 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8090"]
Nov 11, 2021 3:43:44 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 6496 ms
Nov 11, 2021 3:43:44 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat-Standalone
Nov 11, 2021 3:43:44 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52
Nov 11, 2021 3:44:53 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-90"]
Nov 11, 2021 3:44:53 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8090"]
Nov 11, 2021 3:44:53 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 69304 ms

Now if I open the browser on the server and type http://localhost:8090 it forward me to the correct domain https://<my-test-domain>/login.action?os_destination=/index.action&permissionViolation=true

But I can't see the login page... I only see that the page can't be reached...

Do you have any idea?

I am truly grateful for any kind of information and help

Thank you

Ramy

Ramy · Answer

Hi @Darryl Lee

Thanks a lot for replying to my issue. It helped me a bit :)  I have found out, that I have to call the page like this: http://localhost:8090/dologin.action

I can see the login page, but I'm not able to login... I'm using the same user as PROD env and we are using the cloned database of PROD.

Darryl Lee · Answer

If your web browser can't reach the page, it could be:

* DNS issues (can you do an nslookup or ping of <my-test-domain> and does it resolve the correct IP address?)
* Firewall issues (is your server set up to allow access on port 443?)
* Do you have a proxy server set up for your staging server? Typically Confluence runs on port 8090, but then some kind of proxy server responds on port 443 to securely forward requests to that port.

Here's some more troubleshooting ideas from Atlassian:

https://confluence.atlassian.com/confkb/can-t-connect-to-your-site-error-in-the-confluence-data-center-and-server-mobile-app-938025680.html