can't access confluence setup

[Troy Thompson]

After running through the express installation for confluence, I cannot access the setup page to complete the process. myurl.com:8090 just hangs.

64-bit CentOS 6.5 installation running jre 1.7

Port 8090 was verified listening by using netstat -anp | grep 8090 and lsof -i | grep 8090

iptables and selinux are disabled. AWS secuirty group is configured to allow traffic through port 8090

When using the same process to install JIRA, port 8080 (the default) works just fine.

The confluence user has all permissions that are granted during the express installation process.

Confluence was installed as a service. Did I miss anything?

[Troy Thompson]

So there were a couple of things that had to be done to make this work. The issues only partly within confluence.

I followed all of the instructions given in this thread (Thank you all). That includes, permissions to <confluence-install> and <confluence-home>, as well as running the software as a user with those permissions.Once all of the chown -R stuff was done, the server started all the way up.

Next, I had to override IPV6 by assigning environement variables for JAVA_HOME and JAVA_OPTS

Specifically, I had to add the following to .bash_profile of the confluence user:

export JAVA_OPTS="-Djava.net.preferIPv4Stack=true"

export JAVA_HOME="/usr/java/latest"

With IPV4 set to supercede IPV6, permissions configured, and the proper user running the program, I was able to access the setup/welcome page. The kicker is that the corporate network here is blocking 8090 as a non-standard port, so in order to access the thing from the office, I have to proxy through httpd and port 80, which is open.

This page helped: https://confluence.atlassian.com/display/DOC/Cluster+Troubleshooting#ClusterTroubleshooting-PreferIPv4

Find the part that says "Prefer IPV4"

[salehparsa]

I'd recommend you to take a look at this KB:

• Confluence Does Not Start Due to 'Spring Application context has not been set' in Linux

Cheers,

Saleh

[Deividi Luvison]

Also make sure to delete the following directories:

• <confluence-home>/bundled-plugins
• <confluence-home>/plugins-cache
• <confluence-home>/plugins-osgi-cache
• <confluence-home>/plugins-temp
• <confluence-home>/bundled-plugins_language
• <confluence-home>/index

So once confluence starts again with the new service account (with read and write permission) he will rebuild those directories.

Hope it helps.

Thanks and Regards,

David|Atlassian Support

[Troy Thompson]

I'll try this next because I have been running 'service confluence start' as root. I created a /etc/confluence and did chown -R confluence:confluence /etc/confluence. I'm going to edit the /etc/init.d/confluence so that it runs as the user 'confluence' and see what happens.

[Nic Brough -Adaptavist-]

Ah, no, the catalina.out is telling you why the app isn't starting (it is starting, but not fully)

You'll need to work out what this is, and fix it:

SEVERE: Unable to create directory for deployment: /opt/atlassian/confluence/conf/Standalone/localhost

Probably permissions, possibly disk space/quota, but could be something else. Start by logging in as the user running Jira and try to manually create it, that should tell you something more.

[William Zanchet [Atlassian]]

Hi Troy,
You might want to your <home-directory-of-Confluence>/logs and open the atlassian-confluence.log. Search for starting Confluence, and try to see if you can find Confluence is ready to serve message. This means that Confluence is up. If you can't find, it means that Confluence had problems in the startup.
If you could paste here an error snippet log here would be great to understand the problem.

Cheers,
W.

[Troy Thompson]

Except for the fact that, apparently, Confluence is NOT ready to serve.

[Troy Thompson]

Here's the output from the last startup attempt:

2014-05-14 16:06:41,877 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.5 [build 5501 based on commit hash a39771cd4bb7ab00a226a7ea8d6dd65e64226a7f]
2014-05-14 16:06:47,777 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] init Initialising the plugin system
2014-05-14 16:06:48,008 WARN [localhost-startStop-1] [org.twdata.pkgscanner.InternalScanner] findInPackage Unable to find any resources for package 'bucket*'
2014-05-14 16:06:49,885 WARN [localhost-startStop-1] [org.twdata.pkgscanner.InternalScanner] findInPackage Unable to find any resources for package 'org/xml'
2014-05-14 16:06:59,381 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] init Plugin system started in 0:00:11.598
2014-05-14 16:07:01,981 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve

[Nic Brough -Adaptavist-]

There is more before and after that segment in every log I've ever seen.

Except in the case where a plugin was silently killing Confluence dead, but in my case, I'd had it running well enough to install this dubious plugin, and I don't think you could have got that far. Are there ANY warnings or errors outside the block you've posted? In fact, post the lot if you can - from the point of starting, all the way through

[Troy Thompson]

(atlassian-confluence.log) I definitely haven't gotten as far as installing additional plugins. But I am cringing because that's next when I get this thing running. Logfile attached.

[Nic Brough -Adaptavist-]

Hmm. I see what you mean. That log is way too short and unhelpful.

Could you have a look for "Catalina.out" as well? That's the Tomcat log, it might tell us some more.

[Troy Thompson]

(catalina.out.log) Nothing stood out in there either, but here it is.

[Nic Brough -Adaptavist-]

What does the application log file say?