Error when I use bin file upgrade: 'Could not create this file. Shall I try again?'

fanxiao01 March 1, 2020

When I upgrade with the bin file, I go to the extract file and say “/usr/local/confluence/current/jre/./._bin 、Could not create this file. Shall I try again?”. I look in the directory and there is no jre directory

Your instance of Confluence is currently being upgraded.
Checking if Confluence has been shutdown...
Backing up the Confluence installation directory
backup-2020_03_01.zip
backup-2020_02_16.zip

Backing up the Confluence home directory
backup-2020_03_01.zip

com.install4j.runtime.beans.actions.files.CreateZipFileAction failed

Ignore [i, Enter], Quit [q]
Deleting the previous Confluence installation directory...

Extracting files ...
./._bin
/usr/local/confluence/current/jre/./._bin
Could not create this file. Shall I try again?
Yes [y], Cancel [c]
/usr/local/confluence/current/jre/./._bin
Could not create this file. Shall I try again?
Yes [y], Cancel [c]
/usr/local/confluence/current/jre/./._bin
Could not create this file. Shall I try again?
Yes [y], Cancel [c]
y
/usr/local/confluence/current/jre/./._bin
Could not create this file. Shall I try again?
Yes [y], Cancel [c]
y
/usr/local/confluence/current/jre/./._bin
Could not create this file. Shall I try again?
Yes [y], Cancel [c]
c
Rolling back changes ...

1 answer

0 votes
Rocio Razquin June 8, 2022

This question was posted a while ago but since there are no answers to it and I just had the same issue, I'll share my experience here.

In my case, the problem was the installation directory was /opt/atlassian/confluence_vernum and then we had a symbolic link for confluence -> confluence_vernum. As part of the upgrade, the installer backs up the installation dir into a ZIP file and deletes the directory, then it creates it again (probably unzipping) the new version's files.

When the installer stopped with that message "Rolling back changes", I checked the filesystem and saw that I was left with a symbolic link (still existing) pointing to a folder that didn't exist anymore. I therefore deleted the symlink, unzipped the backup that had been taken by the installer and renamed the folder to plain "confluence". I then run the installer once more and the installation finished successfully.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events