Fail to update Atlassian Universal Plugin Manager

[Denis]

I have problem to update universal plugin manager. I try to update on version v. 3.0.2, but i get error: "An error was encountered while updating the UPM. See the logs for more details." Can you please help me to solve this problem, so i can update to new version.

[Hung Nguyen]

I got the same error, and the post here reminded me to review the Base URL setting.

My base URL setting was NOT matching the real URL I am using to access the site. So I have to go back and fix that.

What I meant is:  Administration->System->General Configuration->Base URL

After fixing this to match what my real URL is, then the UPM seemed to upgrade successfully.

I hope that it would help you too.

[Jimmy Seddon]

Thank you @Hung Nguyen!  I was having this issue on our test server after restoring the DB from our production instance.  This was my issue as well.  Thanks for the reminder!

-James

[Azfar Masut]

i have DC setup, so was having this problem when I tried to update from one of the nodes URL. Access the general URL and it works!

[Michael Gloeckner]

Thank you. It works.

[Leirbag Assuab]

Hi! I have encountered the same problem. I have followed instructions at "Updating the Universal Plugin Manager", methods #1 and #2 with no success. Both errors and behaviour were as @Denis described in his post.

I was preparing method #3 when I found another error configuring an add-on we have developed internally. Our add-on options page couldn't connect to its REST service. That made me think...

In our installation we have configured a base URL that is visible on Internet. But I was accessing Jira through intranet URL by mistake! I didn't notice this because most things were going ok.

Once I have correctly accessed Jira through base URL I have been able to upgrade UPM from Add-ons manager page simply by pressing "update" button. When I was logged on through intranet URL I supose that in some moment the process was trying to connect through "base URL" but it was logged off from that context.

I know it has been a while from first post, but I hope it can be useful to someone.

[João Bispo dos Santos Filho]

Hi 

I did what you informed him and it worked

@Grigory Salnikov 

Thank you.

[Grigory Salnikov]

Hi @Denis and welcome to our Community!

So what does the log says?

[Denis]

I try to find but i can't figure out where to find that logs? Can you help me?

[Grigory Salnikov]

You'll need to find the atlassian-jira.log file. Usually, it's located under <jira-home>/log directory.

[Denis]

I think that i find it. I got this last message:

192.168.x.x 695x2914x1 supp [11/Feb/2019:11:35:15 +0100] "GET /rest/plugins/1.0/pending/79180bfd-8481-4f40-804d-0e4c2d63c6df?_=1549881129256 HTTP/1.1" 202 476 0 "http://192.168.x.x:8008/plugins/servlet/upm/manage/user-installed" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36" "1mxn6t9"

[Grigory Salnikov]

Are you sure this is not the web-server logs? It looks just like it. What's the name of the file we're looking at?

I'd do it this way:

1) Open the log file (on Linux system)

tail -f atlassian-jira.log

2) Reproduce the issue (try to update UPM)

3) See what new messages emerge

4) Post them here

[Denis]

Name of file that i look: access_log-2019-02-11. I don't have Linux. Jira is installed on Windows Server 2016, and i use Jira, that i log in to my browser with IP address.

[Grigory Salnikov]

It's ok.

Access_log-... seems to be web server logs indeed. We need to find Atlassian ones.

Try to locate Jira-home directory. Check this location:

C:\Program Files\Atlassian\Application Data\JIRA 

[Denis]

I think i find it:

2019-02-11 12:00:17,584 http-nio-8008-exec-3 WARN supp 720x2971x4 1a8utmh 192.168.x.x /rest/plugins/1.0/installed-marketplace [c.a.upm.pac.PacClientImpl] The request to check for add-on updates may take longer than expected because 192 user-installed add-ons are installed. This may impact the performance of loading the Manage Add-ons page.

2019-02-11 12:00:32,744 UpmAsynchronousTaskManager:thread-4 INFO supp 588x362x2 3himvp 192.168.x.x /rest/plugins/1.0/installed-marketplace [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be installed

2019-02-11 12:00:32,791 UpmAsynchronousTaskManager:thread-4 INFO supp 588x362x2 3himvp 192.168.x.x /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.DefaultPluginManager] Updating plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin' from version '3.0.1' to version '3.0.1'

2019-02-11 12:00:32,791 UpmAsynchronousTaskManager:thread-4 INFO supp 588x362x2 3himvp 192.168.x.x /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.DefaultPluginManager] Disabling com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin

2019-02-11 12:00:32,869 UpmAsynchronousTaskManager:thread-4 DEBUG supp 588x362x2 3himvp 192.168.x.x /rest/plugins/1.0/installed-marketplace [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] onPluginDisabledEvent removing delegate for [com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin]

2019-02-11 12:00:32,884 UpmAsynchronousTaskManager:thread-4 INFO supp 588x362x2 3himvp 192.168.x.x /rest/plugins/1.0/installed-marketplace [c.a.plugin.loaders.ScanningPluginLoader] Removed plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin'

2019-02-11 12:00:32,900 UpmAsynchronousTaskManager:thread-4 INFO supp 588x362x2 3himvp 192.168.x.x /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin], 300 seconds remaining

2019-02-11 12:04:59,007 UpmAsynchronousTaskManager:thread-1 INFO supp 586x225x3 3himvp 192.168.x.x /rest/plugins/1.0/available/featured [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be installed

2019-02-11 12:04:59,054 UpmAsynchronousTaskManager:thread-1 INFO supp 586x225x3 3himvp 192.168.x.x /rest/plugins/1.0/available/featured [c.a.plugin.manager.DefaultPluginManager] Updating plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin' from version '3.0.1' to version '3.0.1'

2019-02-11 12:04:59,054 UpmAsynchronousTaskManager:thread-1 INFO supp 586x225x3 3himvp 192.168.x.x /rest/plugins/1.0/available/featured [c.a.plugin.manager.DefaultPluginManager] Disabling com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin

2019-02-11 12:04:59,195 UpmAsynchronousTaskManager:thread-1 DEBUG supp 586x225x3 3himvp 192.168.x.x /rest/plugins/1.0/available/featured [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] onPluginDisabledEvent removing delegate for [com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin]

2019-02-11 12:04:59,226 UpmAsynchronousTaskManager:thread-1 INFO supp 586x225x3 3himvp 192.168.x.x /rest/plugins/1.0/available/featured [c.a.plugin.loaders.ScanningPluginLoader] Removed plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin'

2019-02-11 12:04:59,351 UpmAsynchronousTaskManager:thread-1 INFO supp 586x225x3 3himvp 192.168.x.x /rest/plugins/1.0/available/featured [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin], 300 seconds remaining

[Denis]

Screenshot of error i get from Jira

[Grigory Salnikov]

Yes, that's the one!

It's recommended to perform a manual update:

Updating the Universal Plugin Manager

Try first "Update UPM by file upload"

It may work out.

[Denis]

I try that, and nothing happens. I will attach pictures.

[Grigory Salnikov]

Ok, let's try to update by replacement.

Please, follow the @[deleted]'s instructions here:

An error was encountered while updating the UPM

[Denis]

That method i tried and didn't work. I try to upload app via Jira manager, and didn't work. I also tried restart Windows server where Jira is installed, and try to upload app or install it, also didn't work.

[Carmen Bullock]

I am having the same error and I am on a linux system. I can't seem to update any of the add-ons. I deleted one add on and re-installed and that did not work either.