-
Bug
-
Resolution: Fixed
-
Medium
-
5.8.2, 5.8.4
-
None
It's not possible to upgrade to 5.8.x using the Confluence installer x64 for Linux. After selecting to Upgrade an existing Confluence installation, a message saying that No directory found in specified location Finishing installation is thrown on the screen, finishing the installation:
[atlassian@quicksilver confluence]$ ./atlassian-confluence-5.8.4-x64.bin Unpacking JRE ... Starting Installer ... Jun 03, 2015 3:52:15 PM java.util.prefs.FileSystemPreferences$2 run INFO: Created system preferences directory in java.home. You do not have administrator rights to this machine and as such, some installation options will not be available. Are you sure you want to continue? Yes [y, Enter], No [n] y This will install Confluence 5.8.4 on your computer. OK [o, Enter], Cancel [c] o Choose the appropriate installation or upgrade option. Please choose one of the following: Express Install (uses default settings) [1], Custom Install (recommended for advanced users) [2, Enter], Upgrade an existing Confluence installation [3] 3 No directory found in specified location Finishing installation ...
Steps to reproduce:
- Install a Confluence 5.x on your server
- Download the Confluence 5.8.x Linux x64 installer
- Run the installer and try to upgrade the existing instance
Solution
- Download the new installers from the Atlassian website and try them. The new installers are marked with the version "5.8.4-1" instead of "5.8.4"
- relates to
-
CONFSERVER-37816 Using atlassian-confluence-5.8.4-x64.bin, user can't install it with "Custom Install" option
-
- Closed
-
-
CONFCLOUD-53897 Can't config custom port during install process
-
- Closed
-
-
CONFSERVER-37813 Can't config custom port during install process
-
- Closed
-
-
CONFSERVER-37796 Linux 64bit Installer uses express installation when I choose custom installation
-
- Closed
-
-
CONFSERVER-37897 Confluence Linux installer
-
- Closed
-
-
CONFSERVER-37972 5.8.4 installer ignores Custom installation type
-
- Closed
-
Hi schroeder5,
That appears to be a separate issue. If it's still an issue, can you raise a support request and we'll do our best to help you out. Thanks!