Confluence Post-Upgrade Checks
This article provides a list of items for Confluence Administrators to check after a Confluence upgrade to ensure that it has completed successfully. This list is not exhaustive, but it does cover common upgrade mistakes.
Before You Begin
After you have completed an upgrade, you should see the following message in the atlassian-confluence.log file:
2010-03-08 08:03:58,899 INFO [main] [atlassian.confluence.upgrade.AbstractUpgradeManager] entireupgradeFinished Upgrade completed successfully
If you do not see the line in your log similar to the one above, this means that your upgrade may not have completed successfully. Please check our (Archived) Upgrade Troubleshooting documentation to check for a suitable recommendation or fix.
Upgrade Checklist
Here's a recommended list of things to check after completing an upgrade
1. The editor
Edit a page to check your browser can connect to Synchrony, which is required for collaborative editing. See Troubleshooting Collaborative Editing if you are not able to edit a page.
2. Layout and Menu
Visit the Confluence dashboard and check that it is accessible and displays as expected. Test the different Internet browsers that you have in use in your environment. In addition, confirm that the layout appears as expected and that the menus are clickable and functioning.
3. Search
Try searching for content, for example pages, attachments or user names. Check that the expected results are returned. If you notice any problems, you may want to take advantage of the maintenance window to rebuild the indexes from scratch. See Content Index Administration.
4. Permissions
Confirm that you can visit a page that has view restrictions, but you have permission to view. Confirm that you can edit a page that has edit restrictions but you have permission to edit. Make sure that the permissions of child pages are functioning as well. Involve as many space administrators as possible to confirm they are working. Confirm that anonymous or forbidden users cannot access or modify restricted pages.
5. Attachments
Confirm that attachments are accessible and searchable.
6. Marketplace apps
Outdated third-party apps can cause upgrade failure. Quite often, they will just be incompatible and simply do not work anymore. If you discover that your app is no longer working, please check for the latest version for your app in the The Atlassian Marketplace or check for compatibility in the Universal Plugin Manager.