Problem upgrading plugins after upgrade to Confluence 4.2.4

[Vik Solem]

Hello.

I installed confluence new from ...bin file, setup the database, imported the data from a backup of our "live" version, and them completed the configuration. (connected to JIRA on same server for auth, etc.)

I went to "manage plugins" and it said "A newer version of the Universal Plugin Manager is available. Update now!"

I clicked on "Update now, and got an error. It was related to a mysql problem "logExceptions Packet for query is too large upm". I shutdown httpd, confluence, and jira. I edited /etc/my.cnf on the database server and then restarted mysql. I started jira, confluence, and httpd.

I tried to "Update now!" the plugins and now it says "This version of Confluence is unknown to the plugin information server. It may be too new to appear, or it may be some type of non-standard build. No plugins can be found for unknown product versions."

Also, nothing shows under "Available Updates", "User-installed Plugins", or "System Plugins" (even when I select "Show/Hide System Plugins".

I tried "Disable communication with the Atlassian Marketplace", and then it allows me to see the plugins. It shows the universal plugin as the only installed user plugin, and then it shows the system plugins.

But I don't see any way to get access to manage any plugins at all.

At the bottom it says "

The Universal Plugin Manager (v2.7.2) by Atlassian" and "Powered by Atlassian Confluence 4.2.4, the Enterprise Wik · Report a bug · Atlassian News".

This is our -DEV system, so I can discard and rebuild if needed, but I'd like to update the plugins for our production instance. Please advise as to what actions I should take. I would like to upgrade production.

-Vik Solem

[Septa Cahyadiputra · Accepted solution]

Hi Vik,

Sorry to hear that. I have reproduce your issue on our end and proceed to create a bug report in regards to your issue to raise the attention of our developer:

https://ecosystem.atlassian.net/browse/UPM-2689

THe current workaround is to uninstalled the upgraded UPM with the following steps

1. Access the following URL <tt>http://<server base url>/admin/viewplugins.action</tt>
2. Uninstall Universal Plugin Manager
3. Shutdown Confluence
4. Remove the following directories
   • <tt><confluence-home>/bundled-plugins</tt>
   • <tt><confluence-home>/plugin-cache</tt>
   • <tt><confluence-home>/plugins-osgi-cache</tt>
   • <tt><confluence-home>/plugins-temp</tt>
   • <tt><confluence-home>/bundled-plugins_language</tt>
5. Restart Confluence

Hope it helps.

Cheers,
Septa Cahyadiputra

[Vik Solem]

I'm confused. I received email which pointed me to a site, https://ecosystem.atlassian.net/browse/UPM-2689# which had the following workaround posted.

Workaround

1. Access the following URL <tt>http://<server base url>/admin/viewplugins.action</tt>
2. Uninstall Universal Plugin Manager
3. Shutdown Confluence
4. Remove the following directories
   • <tt><confluence-home>/bundled-plugins</tt>
   • <tt><confluence-home>/plugins-cache</tt>
   • <tt><confluence-home>/plugins-osgi-cache</tt>
   • <tt><confluence-home>/plugins-temp</tt>
5. Restart Confluence

NOW I found this page which has my original post, and which has a workaround which includes deleting from the datbase. I already did the first workaround. Do I need to shutdown and delete from the database too?

At this point I have applied the workaround from "UPM-2689" at ecosystem.atlassian.net to our DEV instance.

I was able to use that work-around to get back to a plug-in screen that lists available updates. It also indicates that there is a newer version of the Universal Plugin Manager available. This appears to match the status of my production Confluence installation.

Obviously, I’d like to have all of the plugins be up to date. How should I proceed? (Or is it too early, because the bug is still being worked?)

In case it would help with debugging, I’m happy to try whatever might be helpful in our DEV instance.

-Vik

[Septa Cahyadiputra]

Hi Vik,

Sorry for the confusion, the workaround from https://ecosystem.atlassian.net/browse/UPM-2689 is the updated workaround. Please refer to that workaround as it is easier to follow.

For now UPM 2.7.2 is still affected by the bug, you might want to consider upgrading to version 2.6.2 while we are working on the bug fix.

Cheers,
Septa Cahyadiputra

[Septa Cahyadiputra]

Hi Vik,

As mentioned on the bug report. This issue has been resolved, you can either upgrade to 2.7.3 or if you still installed 2.7.2 please restart Confluence, this way Confluence will try to create a new connection to UPM and resolve the previous issue.

Cheers,
Septa Cahyadiputra

[Vik Solem]

Thanks Septa. The upgrade of UPM works fine now. It installed 2.7.3. Unfortunately, after that I selected "Upgrade All" of the plugins, and it broke Greenhopper. "License status: Incompatible with product license (wrong type) " I've opened a ticket on that, with the assumption that it's unrelated to the UPM issue. "[SUPPORT] (JSP-138775) After Upgrade of UPM Upgrade of GreenHopper fails with " License status: Incompatible with product license (wrong type) "" Thanks for your help. -Vik

[Septa Cahyadiputra]

Pleasure is all mine :).

Cheers,
Septa Cahyadiputra