Upgrade Agent seeming to spin forever

[Matt Benson]

I have successfully connected a configured Nexus 3 server to my Nexus 2 server and am trying to convert a single small hosted repo as a test. Currently I'm in the "Synchronizing" screen. "Scan 1 repositories" shows Completed. "Process changes" shows "977 processed, 14 minutes since last change, press 'Continue' when ready." The "Continue" button is disabled. The log shows repetitions of "Fetching changelog from [NEXUS 2]; Waiting for more changes; read SYNC" as far back as I can see. Target Nexus instance is running 3.4.0-02 and source Nexus instance is running 2.14.4-03. Is this expected behavior?

Thanks,

Matt

[Brian Fox]

It should continue to sync new changes when it's done, which it sounds like is what you're seeing. However, the continue button should be enabled by now.

--
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/bcd3bf88-07b6-4d59-a95a-fd0e277a6b95%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

[Matt Benson]

Thanks Brian! I let the session time out and when I logged back in and went back to the upgrade tab the continue button was enabled.

Am I right in understanding that there is no way to assign a conversion repo to an existing repo of a different name on the Nexus 3 instance?

On Thursday, July 6, 2017 at 7:56:14 PM UTC-5, brianf wrote:

It should continue to sync new changes when it's done, which it sounds like is what you're seeing. However, the continue button should be enabled by now.

On Thu, Jul 6, 2017 at 6:21 PM, Matt Benson <gudna...@gmail.com> wrote:

I have successfully connected a configured Nexus 3 server to my Nexus 2 server and am trying to convert a single small hosted repo as a test. Currently I'm in the "Synchronizing" screen. "Scan 1 repositories" shows Completed. "Process changes" shows "977 processed, 14 minutes since last change, press 'Continue' when ready." The "Continue" button is disabled. The log shows repetitions of "Fetching changelog from [NEXUS 2]; Waiting for more changes; read SYNC" as far back as I can see. Target Nexus instance is running 3.4.0-02 and source Nexus instance is running 2.14.4-03. Is this expected behavior?

Thanks,

Matt

--
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...@glists.sonatype.com.

[Michael Prescott]

Matt, you're correct - the upgrade wizard won't import content from one NXRM 2 repo into an existing NXRM 3 repo, certainly not one with a different name.

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/656a2c13-30b2-4b7a-956c-cd08b9c70de8%40glists.sonatype.com.

[Matt Benson]

I'm going to guess this would be a common scenario:

• Nexus 2 has releases and thirdparty repos.
• User wants to migrate to Nexus 3 maven-releases and maven-thirdparty-releases repos, respectively.

Given the previous response, it's clear that we need to delete the existing Nexus 3 repos and rename the Nexus 2 repos prior to import. In order to do this, I can guess that I might:

• Shut down Nexus 2
• Back up nexus.xml
• Edit nexus.xml renaming repository ids
• Rename corresponding storage directories
• Restart Nexus 2

Is that naive? What if anything is missing from the above recipe?

Thanks,

Matt

On Friday, July 7, 2017 at 8:42:00 AM UTC-5, Michael Prescott wrote:

Matt, you're correct - the upgrade wizard won't import content from one NXRM 2 repo into an existing NXRM 3 repo, certainly not one with a different name.

On 6 July 2017 at 21:13, Matt Benson <gudna...@gmail.com> wrote:

Thanks Brian! I let the session time out and when I logged back in and went back to the upgrade tab the continue button was enabled.

Am I right in understanding that there is no way to assign a conversion repo to an existing repo of a different name on the Nexus 3 instance?

On Thursday, July 6, 2017 at 7:56:14 PM UTC-5, brianf wrote:

It should continue to sync new changes when it's done, which it sounds like is what you're seeing. However, the continue button should be enabled by now.

On Thu, Jul 6, 2017 at 6:21 PM, Matt Benson <gudna...@gmail.com> wrote:

I have successfully connected a configured Nexus 3 server to my Nexus 2 server and am trying to convert a single small hosted repo as a test. Currently I'm in the "Synchronizing" screen. "Scan 1 repositories" shows Completed. "Process changes" shows "977 processed, 14 minutes since last change, press 'Continue' when ready." The "Continue" button is disabled. The log shows repetitions of "Fetching changelog from [NEXUS 2]; Waiting for more changes; read SYNC" as far back as I can see. Target Nexus instance is running 3.4.0-02 and source Nexus instance is running 2.14.4-03. Is this expected behavior?

Thanks,

Matt

--
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...@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/bcd3bf88-07b6-4d59-a95a-fd0e277a6b95%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

--
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...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.

[Brian Fox]

The general idea is that you are effectively "upgrading" from 2 to 3 and as such we designed this to make it possible to run the conversion and then cut over urls / reverse proxies from old to new and everything works the same way. Altering the names of repos is something you'd want to do before or after (before is likely easier given the nx2 storage).

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/4ede8518-6166-4f02-8364-d22fe634fe8d%40glists.sonatype.com.

[Peter Lynch]

On Fri, Jul 7, 2017 at 12:19 PM, Matt Benson <gudna...@gmail.com> wrote:

I'm going to guess this would be a common scenario:

• Nexus 2 has releases   and thirdparty repos.
• User wants to migrate to Nexus 3 maven-releases and maven-thirdparty-releases repos, respectively.

Given the previous response, it's clear that we need to delete the existing Nexus 3 repos and rename the Nexus 2 repos prior to import. In order to do this, I can guess that I might:

• Shut down Nexus 2
• Back up nexus.xml
• Edit nexus.xml renaming repository ids
• Rename corresponding storage directories
• Restart Nexus 2

Is that naive? What if anything is missing from the above recipe?

These steps are correct from the Nexus 2 side. However, on the Nexus 3 side, you basically need to start migration over from scratch, starting with a completely new nexus 3 default configuration as everything in Nexus 3 is going to be replaced by restarting the upgrade process.

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/4ede8518-6166-4f02-8364-d22fe634fe8d%40glists.sonatype.com.

[Matt Benson]

Sure; as I said this was a dry run. When we get the new server up and running the first thing I will do is drop the repositories discussed in preparation to receive them from Nexus 2. Thanks!