deleted

[Stephan A_]

deleted

[AnnWorley · Accepted solution]

In answer to your edited post, I wanted to let you know that the reason you cannot open a ticket with Support is we updated our support offerings for starter licenses: We’re updating our support offering for server starter (10-user) licenses Starter licenses are eligible for Community support; the Community is staffed with experienced support engineers. You may qualify for standard support by upgrading your user tier.

We don't need to see private configuration info for most questions. We do have a mechanism to work with you privately if we need to comprehensively examine logs.

How is your install going? The error you are reporting is most commonly caused by file system permissions, Nic's checklist is an excellent place to start as well.

[Stephan A_]

What is allowed to write?

[Stephan A_]

NOTHING!

[Stephan A_]

Now I bypassed your "filter". 

I am not allowed to send you any kind of reply that has content or sense. What kind of "support" should this be?

It is a joke and I only can say "Good-bye" Atlassian.

[AnnWorley]

It sounds like you had trouble posting your logs. I created a ticket for you; you will get the notice soon.

[Stephan A_]

I am only able to post a single word here ... when visiting this site by using a Proxy that is comparable to TOR.

Otherwhise nothing with content or sense is accepted to publish.

[AnnWorley]

I hope you have better luck with the JIRA ticket I created for you. We have had issues with logs being flagged as spam on the forum. We are working on it.

[AnnWorley]

Just to circle back with the Community, Stephan fixed the installation issue by making changes to his PostgreSQL user permissions. Then we ran into a performance problem running multiple applications on the same server. It turned out that the database server was only accepting 100 total connections so after Stephan raised it to 600 all the applications started running as expected.

[Nic Brough -Adaptavist-]

You can raise it with Atlassian support if you've got a commercial licence (25+ users), and try with evaluation, but they will refer you here or to their documentation.

You've not said what you've looked at, so here's my list of things to check

1. The confluence user doesn't own and have full access to the file system under the installation and home directories
2. A virus scanner is blocking access to files
3. You are running it as "root".
4. A an application blocker is stopping it - SELinux for example
5. You've set a JAVA_HOME and pointed it at the wrong version of Java for it
6. The database driver is missing from the installation (Check <install>/confluence/WEB-INF/lib for a driver jar)
7. The hostname of the server can not be resolved by itself
8. The server does not have enough memory during installation to set up the database

[Stephan A_]

Thank you, but we already tried all these steps without finding a solution.

[AnnWorley]

I am in Atlassian support and happy to help.

The error "spring application context has not been set" is somewhat generic - we have a knowledgebase article that describes the error and several possible resolutions: Confluence does not start due to Spring Application context has not been set

I hope you get a chance to follow up with us and let us know how you fix it in your case.

[Stephan A_]

As I worte:

N O N E of the articles automatically shown while typing this brought a solution.

So the article you published above TOO.

ALL steps Nic Brough described we already tried without success too.