Lucee 6.2 / 7.0 latest upgrades not showing in the admin workaround

news release
,
1

Since 6.2 and 7.0 Lucee retrieves the list of available updates from maven, rather than from the Lucee update server.

Due to a hosting change with maven, we had to modify this process, as newer versions since 6.2.2.64-SNAPSHOT and 7.0.0.275-SNAPSHOT no longer show up as upgrade options from older versions of Lucee.

This is only a problem when trying to upgrade via the admin, if you are upgrading via changing the base docker images, this is not a problem.

The fix in is place since 7.0.0.303-SNAPSHOT / 6.2.2.82-SNAPSHOT

The workaround is to use the fallback s3 update mechanism via the admin, or do drop the latest snapshot / rc / stable into the /deploy folder

TL;DR

To access the s3 update mechanism, simply append old to the url for the updates page in the admin, i.e action=services.update to action=services.updateold

http://localhost:8888/lucee/admin/index.cfm?action=services.updateold

You will only need to do this once.

To verify this afterwards, simply compare what is listed on the download page with the versions list shown in the normal admin update page.

2 Likes
2

When I enter action=services.updateold, I don’t see any updates.
There’s an empty box where I should enter a custom update provider, but which one is it?

immagine
immagine1014×928 56.8 KB

3

Ok. It works.
There are no stable releases, but I see the new RC and Snapshot

immagine
immagine998×928 56.1 KB

2 Likes
4

I’ve added a link to this to the breaking changes document for 6.2

2 Likes
5

I have read this and the breaking changes link, but I can’t seem to figure out how to do this.

I am on 6.2.1.122 , the highest version of 6.x that I can find is a snapshot of 6.2.2.64

I see the screenshot above posted by @Michele_Scaletta but I don’t have the option of Custom Update Provider on my admin

Appreciate any extra guidance.

Thanks

6

Did you manually navigate to the old updates page in the admin action=services.updateold by adding old to the url, from the normal update page?

That should just work, otherwise, you can always just download https://cdn.lucee.org/6.2.2.91.lco and drop it into the lucee-server/deploy folder to perform a manual update

7

Thanks @Zackster ! That was it, I didn’t pick up on what I was supposed to do, sure enough adding ?action=services.updateold to the end was enough to show me the update

Thank you

1 Like
8

I navigated to ?action=services.updateold and tried to update to the 6.2.5.48 version, but got this error:

org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.commons.lang:2.6.0

The my server stopped working, websites as well as Lucee admin. (Error code: 500 500)

I tried to google it, but haven’t found anything useful yet. Any idea why this error? Thank you for any input.

9

Do you have cfspreadsheet 3.0.4 installed?

that has some conflicts, due to that jar being added for 7 compat, the 3.0.3 version should work fine (3.0.4 only adds that for 7 compat)

it’s hitting a combination of bugs ATM

  • LDEV-6145 — OSGiUtil.improveFileName() renames bundle JAR without updating Felix (root cause)
  • LDEV-6144 — loader returns unstarted Felix after cache clear (secondary bug)

A downgrade to 3.0.3 should work as a permanent fix because 3.0.3 doesn’t bundle commons-lang, so there’s nothing to trigger the rename cycle.

I’ve just test locally this workaround for affected Lucee 6.2 instances:

  1. Stop Lucee
  2. Delete org.apache.commons.lang-2.6.0.jar from {lucee-server}/bundles/
  3. Delete {lucee-server}/context/felix-cache
  4. Drop cfspreadsheet-3.0.3.lex into {lucee-server}/deploy/
  5. Start Lucee
10

I do, and thank you for the quick response.

I ended up fixing Lucee by manually downloading the 6.2.5.48 version jar file, and dropping it in, and removing the old. I also restored the config file. Server came back up after restart. Is it ok to update cfscreadsheet to 3.0.5 instead of downgrading?

11

3.0.5 should be totally fine

1 Like