Moving Crowd, Jira and Confluence - Need some help

Question

Hi all,

i have to move Crowd, Jira and Confluence to another Server but it fails every time i try. I've made these Steps so far:

* copy content of /opt/atlassian/* to the new server
* copy content of /var/atlassian/* to the new server
* copy the apache webserver configs to the new server
* made a full dump of postgres db and import it to the new server
* creating jira, crowd and confluence user

Crowd and Jira are working (more or less) bur Confluence is makig me cry. Whatever i do i end up in two different errors.

First one is the "call to vacant". Using google i've found this page: https://confluence.atlassian.com/confkb/confluence-generates-confluence-is-vacant-error-on-install-779164449.html but nothing happens.

Next shot was to check the Database as suggested here: https://confluence.atlassian.com/conf64/troubleshooting-external-database-connections-936511519.html but there is nocthing wrong. Everything seems to work fine.

Second error is just "nothing". The Apache webserver ends in a timeout. The catalina.out is not very usefull, all i find is

21-Jun-2018 23:30:12.119 WARNING [ContainerBackgroundProcessor[StandardEngine[Standalone]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread "http-nio-8092-exec-7" (id=185) was previously reported to be stuck but has completed. It was active for approximately 120,228 milliseconds.

Can someone help me please, i am desperate, i am working on this now for a few weeks and my brain is slime now :(

Greetings
Bernd

Zak Laughton · Answer

Hi Bernd,

I understand you're having trouble starting up Confluence after a migration.

It sounds like you went through the proper steps, but I also recommend reading through Migrating Confluence Between Servers to be sure all proper configuration changes are in place.

I'd also be curious to see what is in the application logs (<confluence-home>/logs/atlassian-confluence.log). In this file, do you see a log message from after the migration that reads "...contextInitialized Starting Confluence..."? If so, then tomcat would seems to start up correctly, and there's an issue with the application configuration. If there are no new messages in atlassian-confluence.log, then that would indicate the tomcat initialization is failing, even before starting the application.

Let us know what you find! Thanks!
-Zak

miikhy · Answer

Hi Bernd,

Welcome on Community and sorry for your hard time with the migration!

As it seems very technical, have you tried working with Atlassian Support directly on that? I will also try to get some help from an Atlassian in that thread.

Cheers