I am trying to migrate Confluence to a clean Ubuntu system, but I keep hitting the same error over and over again. After I test the connection to MySQL I hit next and after a while I see:
When I look at the logs I see:
03-May-2018 16:33:01.478 SEVERE [http-nio-8090-exec-2] org.apache.catalina.core.StandardHostValve.custom Exception Processing ErrorPage[errorCode=500, location=/500page.jsp]
org.apache.jasper.JasperException: java.util.concurrent.CompletionException: com.atlassian.confluence.tenant.VacantException: Confluence is vacant, a call to tenanted [public abstract org.hibernate.Session org.hibernate.SessionFactory.getCurrentSession() throws org.hibernate.HibernateException] is not allowed.
I will spare you all the Java jibberish that is spat out after that.
I looks like the database stays empty:
mysql> USE confluence;
mysql> show tables;
Empty set (0.00 sec)
I found this thread: https://confluence.atlassian.com/confkb/confluence-generates-confluence-is-vacant-error-on-install-779164449.html , but that doesn't seem to help either.
This is quite depressing, how can it be _this hard_ to install your product on a clean server?
root@confluence:/home/ubuntu# ping `cat /etc/hostname`
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.017 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
That seems to work as expected, my hosts file looks like this:
127.0.0.1 localhost confluence
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
_everything_ was a bit too optimistic, I see basic HTML but all assets result in 500 errors:
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Container is not setup
caused by: java.lang.IllegalStateException: Container is not setup
When you run the installer as "root" it does install Confluence under the "confluence" user, but it keeps running under "root" until you do a reboot and the service is started automagically.
I guess things work now... I still don't quite understand why it failed the first ten times.
Please post a screen shot of what Confluence looks like in the browser as well as the lines in the <confluence_home>/logs/atlassian-confluence.log from "starting Confluence" to "Confluence is ready to serve" (if it is ready).
Note: The <confluence_home> directory is the path defined in the following file: <confluence_install>/confluence/WEB-INF/classes/confluence-init.properties
I have just terminated the entire instance, it shouldn't take 2 days to move an application.
I have followed: https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html but this article is effectively useless, I can't log in and when I copy the application-data directory all I see is a 404.
There is no meaningfull information in the logs, I honestly feel for Java developers. How does anyone work with this language?
@AnnWorleyI decided to give it one more try, basically I have ignored the following article: https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html
I just did an XML export followed by a restore, it took me an hour to move this application. (Why doesn't this article mention the export -> import route?)
The import went exactly as planned, but I can't seem to login... again... how can it be this hard to setup a new instance for Confluence!? Either you need to create better documentation / system specs or your developers need to do a better a job. Most of the open source software we work with is easier to setup than Confluence!
I am not sure where the instructions broke down for you but I am glad you got the instance moved using the XML back-up. We don't recommend that method widely because there can be so many complications with the restores.
To log in, please see the instructions on Restore Passwords To Recover Admin User Rights. The recovery mode feature was added after Confluence 6.5 so if you are running a prior version, make sure and choose the right doc for your version from the pulldown on the top right:
The instructions for 5.10 will work for earlier versions as well.
I have finally found the problem, in our old setup Confuence was linked to Jira... so while the internal users table was populated in the database it wasn't used. After changing the configuration on the orginal installation and doing a full database and application backup it seems to work again.
Lessons learned: do not use a single server for confluence/jira/bitbucket. It might seem like a good idea at the time, but just don't do it...
Hi Community, Elaine again from Confluence Cloud Product Management. Most of you have used the new Confluence navigation and Home for some time by now. Not sure what changed or just want to lear...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events