Updating container Nexus 3.0.0 to 3.1.0 -

1,938 views
Skip to first unread message

Vincent Berruchon

unread,
Aug 26, 2016, 11:34:20 AM8/26/16
to Nexus Users
Hi,

Is there some migration procedure from Nexus 3.0 to 3.1 ?
I didn't find anything for the moment so I just tried to update my image but it doesn't start.


I've tried to update my Nexus 3 image previously based on docker repo "sonatype/nexus3:3.0.0"
with the new repo version "sonatype/docker-nexus3:3.0.1"

No problem to run a new container with this new image without existing data.

But if I try to start the container using my existing data directory from my nexus instance used as Docker Registry and persisted with volume binding and it doesn't start.

I'm surprised to see in the logs, some reference to the previous version I used : "3.0.0-03"

---- ...
2016-08-26 15:12:24,957+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Starting: org.eclipse.jetty.server.Server@4b987234
2016-08-26 15:12:24,960+0000 INFO  [jetty-main-1] *SYSTEM org.eclipse.jetty.server.Server - jetty-9.3.7.v20160115
2016-08-26 15:12:25,033+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.osgi.BootstrapListener - Initializing
2016-08-26 15:12:25,079+0000 WARN  [jetty-main-1] *SYSTEM org.ops4j.pax.url.mvn.internal.AetherBasedResolver - Error resolving artifactcom.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03:Could not find artifact com.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact com.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03
        at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) [org.ops4j.pax.url.mvn:2.4.5]
        at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) [org.ops4j.pax.url.mvn:2.4.5]
...
----
I could send more logs but it mainly repeat this "Could not find artifact com.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03"

Did I miss a migration step needed?
Would you have some hints to check?

Thank you

Vincent

Peter Lynch

unread,
Aug 26, 2016, 11:55:35 AM8/26/16
to Vincent Berruchon, Nexus Users
On Fri, Aug 26, 2016 at 12:34 PM, Vincent Berruchon <vberr...@gmail.com> wrote:
Hi,

Is there some migration procedure from Nexus 3.0 to 3.1 ?

I think you mean 3.0.1?
 
I didn't find anything for the moment so I just tried to update my image but it doesn't start.


I've tried to update my Nexus 3 image previously based on docker repo "sonatype/nexus3:3.0.0"
with the new repo version "sonatype/docker-nexus3:3.0.1"

No problem to run a new container with this new image without existing data.

But if I try to start the container using my existing data directory from my nexus instance used as Docker Registry and persisted with volume binding and it doesn't start.

I'm surprised to see in the logs, some reference to the previous version I used : "3.0.0-03"


The instructions to prevent this are in this article:


Inside your previous Data Directory, manually create an empty file named clean_cache

Alternately you can delete the ${karaf.data}/cache directory entirely. That is what the presence of the clean_cache file does automatically anyways.


 
---- ...
2016-08-26 15:12:24,957+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Starting: org.eclipse.jetty.server.Server@4b987234
2016-08-26 15:12:24,960+0000 INFO  [jetty-main-1] *SYSTEM org.eclipse.jetty.server.Server - jetty-9.3.7.v20160115
2016-08-26 15:12:25,033+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.osgi.BootstrapListener - Initializing
2016-08-26 15:12:25,079+0000 WARN  [jetty-main-1] *SYSTEM org.ops4j.pax.url.mvn.internal.AetherBasedResolver - Error resolving artifactcom.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03:Could not find artifact com.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact com.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03
        at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) [org.ops4j.pax.url.mvn:2.4.5]
        at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) [org.ops4j.pax.url.mvn:2.4.5]
...
----
I could send more logs but it mainly repeat this "Could not find artifact com.sonatype.nexus.assemblies:nexus-oss-feature:xml:features:3.0.0-03"

Did I miss a migration step needed?
Would you have some hints to check?

Thank you

Vincent

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users+unsubscribe@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/CAGGugxrvtG0fQ6Eq%2B5QNZkPUc_cRoUdKT2k9gnBRBQJTC2BjEA%40mail.gmail.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

Vincent Berruchon

unread,
Aug 28, 2016, 9:09:34 AM8/28/16
to Peter Lynch, Nexus Users
Hi Peter,
I'm actually really talking about an update of a 3.0.0 instance to a 3.1.0 version in Docker mode.
It seems this 3.1 image is just fresh.
but I'll test to clean the cache probably tomorrow, that could probably help.

Thank you

Vincent Berruchon

unread,
Aug 29, 2016, 11:27:17 AM8/29/16
to Peter Lynch, Nexus Users
Hi Peter, 
just for confirmation: I did touch a "clean_cache" file in the {karaf.data} directory in my test environment and the fresh 3.1.0 version is now working good with my previous data.

Thank you
Vincent

Olivier Dupré

unread,
Dec 28, 2016, 10:40:11 AM12/28/16
to Nexus Users
Hi,

Thank you very much for this answer Peter. It's working and it made my day!

By the way, one must know that Nexus Repository does not support upgrading directly from 3.0.2 to 3.2.0. I had to migrate from 3.0.2 to 3.1.0 then again from 3.1.0 to 3.2.0.

For the sake of memory, here are the links needed to download each version so one can upgrade to latest Nexus repository version:
http://download.sonatype.com/nexus/3/nexus-3.2.0-01-unix.tar.gz
http://download.sonatype.com/nexus/3/nexus-3.1.0-04-unix.tar.gz

Cheers,
Olivier

Peter Lynch

unread,
Dec 28, 2016, 11:35:30 AM12/28/16
to Olivier Dupré, Nexus Users
On Wed, Dec 28, 2016 at 11:40 AM, Olivier Dupré <dupre....@gmail.com> wrote:
Hi,

Thank you very much for this answer Peter. It's working and it made my day!

By the way, one must know that Nexus Repository does not support upgrading directly from 3.0.2 to 3.2.0. I had to migrate from 3.0.2 to 3.1.0 then again from 3.1.0 to 3.2.0.

It may not be obvious, but going from 3.0.2 to 3.2.0 should work fine - as long as you take note of the special layout and property changes between 3.0.2 or 3.1.0.


 

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users+unsubscribe@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.

Olivier Dupré

unread,
Dec 28, 2016, 12:08:30 PM12/28/16
to Nexus Users, dupre....@gmail.com
Yep. Ready the release notes and checking the directory structures, I thought so. But in practice... I just waste part of my day yesterday trying to do this. While starting, Nexus 3.2.0 was always complaining about somethin (OrientDB lock, then some "part 23" already used, ...) No self explaining log. Thus I decided to go through 3.1.0 first and succeeded...
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.

To post to this group, send email to nexus...@glists.sonatype.com.
Reply all
Reply to author
Forward
0 new messages