If you are running Linchpin Intranet Suite 3.0.0, 3.0.1 or 2.0.0 (or earlier) or Linchpin User Profiles 2.19.0, 2.19,1 or 2.18.0 (or earlier), you can identify the problem by one or more of the following observations:
So far, we were able to reproduce this issue on Confluence 6.13, 6.14, and 6.15, but other versions may be affected. If you are unsure whether this applies to your system, or if you need assistance: please open a support request at https://seibert.biz/help
The following versions of Linchpin Intranet Suite are not affected: 2.0.1, 2.0.2, 2.0.3 and all versions since 3.1.0. For Linchpin User Profiles, the following version are not affected: 2.18.1 and all version since 2.20.
If you run one of the affected versions, please perform these steps in the exact order before installing or updating Linchpin Intranet Suite:
Confluence stores the state of apps in the database, more specifically in the PluginManagerStateMap (bandana key "plugin.manager.state.Map"). During installation of the Linchpin Intranet Suite, several apps and app modules are disabled and enabled. During this process a deadlock can occur on the PluginManagerStateMap, since two processes depending on each other might want to alter the state of an app. Uninstalling Linchpin User Profiles, Resetting the map, or removing the entries leading to a potential lock, will circumvent this.
On this page