Migrate from 2.8 to 3.5.17 fails with: Error opening ... 'global.logo'

[Peter Binney]

We are upgrading from 2.8 (sic) to 4.3.2 which involves first migrating to 3.5.17

At that stage the migrate fails with:

ERROR … atlassian.confluence.upgrade.UpgradeLauncherServletContextListener contextInitialized 1: Error opening input stream from resource: UploadedResource filename: 'global.logo', file: '/opt/IBwiki/internal-dev-tomcat6/confluence/resources/logo.gif'

For the time being we have prevented the error by adding a confluence/resources/logo.gif file before the upgrade (there isn't one in the 2.8 environment).

But the end result of this is that the specified logo appears in various places in the 4.3.2 UI (eg: next to spaces in the Dashboard).

We want to revert to an as out-of-the-box UI as possible. How do I fix this please?

I notice from select * from BANDANA where BANDANAVALUE like '%logo.gif%'

that there are four BANDANACONTEXT's (including _GLOBAL) with BANDANAVALUE of:

<list> <com.atlassian.confluence.util.resource> <key>logo</key> <relativepathtofile>cblogo.GIF</relativepathtofile> <contenttypeprefix>image</contenttypeprefix> </com.atlassian.confluence.util.resource> </list>

Can I just remove those before the upgrade to fix the problem?

[PeterKoczan · Accepted solution]

Hi,

Have you tried removing the logo or just turning off completely? Please refer to the following documentation for more info: https://confluence.atlassian.com/display/DOC/Editing+the+Global+Logo

Cheers,

Peter

[Peter Binney]

It was turned off. But there was clearly detritus referring to it in the d/b, so, as per your email suggestion, I turned it off by:

1. Turning it on (sic)
2. Clicking "Reset logo to default"

Then on the next migration test run the problem no longer occurred.

Many thanks