Error updating a specific add-on (Discussion) in Confluence 5.10.4

[DropIN Team]

Hi All,

First post here. I am usually successful in self diagnosing issues, but this one has me at my wits ends!

I have updated my confluence server from 5.8.8 to 5.10.4 and the 'Discussion' plugin got marked as 'incompatible' in UPM (the add on manager)

When I try to update it using the 'Update' button, I get the little modal dialog with the progress bar for a few minutes, but eventually get the red error message "An error occurred during installation. Refer to the logs for more information."

The relevant lines that the error log mentions:

[discussion.model.utils.DiscussionUtils] setDiscussionSpaceIndex Error while setting edit restriction for index page

[upm.core.install.DefaultPluginInstallationService] execute Plugin installation failed: Failed to install OBR jar artifact

What I have tried already:

• Set the correct base url (some other addons were not updating because of that, but since I have set up the correct base url, the other addons updated fine)
• Set max allowed packet size to 256mb in mysql (/etc/my.cnf)

Environment:

• Confluence v5.10.4 on a c5.4xlarge AWS instance.
• Custom theme on Brikit Themepress v2.2.2
• UPM is updated to v3.0.2

Please let me know if you would like to know anything else from me. Would be glad if someone could help me sort this out.

Cheers!

[Thomas Buchhorn · Accepted solution]

Have you tried to update it manually?

Maybe take the first compatible version from https://marketplace.atlassian.com/apps/1212012/discussion/version-history (starting with 2.12) and upload it with the upm.

Which version of the plugin is installed btw?

But this is a paided add-on and you could ask the vendor for help.

https://marketplace.atlassian.com/apps/1212012/discussion?hosting=server&tab=support

[DropIN Team]

Manually downloading and uploading the obr file worked!

I had v1.1.4 of the plugin installed, now I am on 2.12

Not a priority, but would be curious to know though why it didn't work through the normal update method if anyone has any idea. Might just be the huge version leap.

Will mark your answer as accepted.

Cheers!

[Thomas Buchhorn]

Great, now you should be able to update the plugin to the lastest version with the update button.

BTW. Always update your plugins to the latest compatible version of your current confluence system pior updating to a newer confluence version.

Why it failed with the normal update process. No clue. Maybe it was picking an older version of the plugin, which was not compatible with your new confluence version.