Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Confluence not starting after upgrade to 6.11

I've upgraded confluence from 6.3.2 to 6.11. I've alse upgraded postgres after upgrade, previous version was 9.2 now it's 9.6. Jira is working fine with new postgres so i assume DB upgrade was ok. Problem is I don't see any particular error in catalina.out and there is nothing in a atlassian-confluence.log , since startup doesnt get that far.

I'm getting this when trying to browse to confluence url

HTTP Status 404 – Not Found


Type Status Report

Message /

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.


Apache Tomcat/9.0.10

2 answers

1 vote
Diego Atlassian Team Sep 01, 2018

Hello Matjaz! It seems that you have a system outtage in hands.
The first thing I would check is if the Confluence service is indeed running. For Linux, you can use the following command:

ps -aux | grep confluence

This will show you if Confluence has a process in your system. In Windows you can use the Task Manager to check this. Also, make sure that the older version is not running at the same time. If the process is not running check if your user has enough permissions in <confluence-home> and <confluence-install>.

Further, you can go ahead and check if your server.xml file has the correct settings, should be the same as your pre-upgrade settings. You can find your server.xml file here:

<confluence-install>/conf/server.xml

Also, I advise you to clear your plugin cache before trying to start your upgraded version:

1 Shutdown Confluence
    - Make sure that the process is not running
    - You can check that with ps -aux | grep confluence in linux and via the Process   manager in Windows
2 Go to <confluence-home>
3 Remove the following folders:
    - <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
    - <confluence-home>/journal
4 Check permissions for <confluence-home>
    - The user running Confluence must have *full read/write/execute permission on this folder
    - You can use the following commands to set this. Keep in mind that the user confluence here is just a placeholder, you must use the user that exists in your system
    - sudo chown -R confluence:confluence /path/to/<confluence-home>
    - chmod -R u=rwx,g=rx,o=rx /path/to/<confluence-home>
5 Check permissions for <confluence-install>
    - The user running Confluence must have *full read/write/execute permission on this folder
    - You can use the following commands to set this. Keep in mind that the user confluence here is just a placeholder, you must use the user that exists in your system
    - sudo chown -R confluence:confluence /path/to/<confluence-install>
    - chmod -R u=rwx,g=rx,o=rx /path/to/<confluence-install>
6 Start Confluence
7 Check if the instance starts

Reference

Confluence Installation Guide
Installing Confluence on Windows
Installing Confluence on Linux


Hope this helps your case!

@ortoscale I am facing a similar issue after postgres db and confluence upgrade. Were you able to resolve this?

@Siddarth Murthy  @ortoscale  I'm also facing the same issue.  How did you resolve it?

For those using Docker version of confluence, I encountered this problem after upgrading to a newer image. The problem was that the mounted confluence data folder was previously owned by user id 1, but they changed the docker image somewhere so that the binary runs as user 2002. So the fix is to change the owner (and possibly the group) to 2002 recursively for the mounted confluence data folder, then restart.

chown -R 2002:2002 path/to/data/confluence

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Confluence

What do you think is the most *delightful* Confluence feature? Comment for a prize!

- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...

480 views 24 9
Join discussion

Community Events

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

Events near you