Nexus OSS lost all Repositories after restart

[cyril...@smaato.com]

We have recently migrated all our repositories from Nexus 2.14.11 (EC2 instance with EBS volume) to  the most recent 3.14.0 version (Ubuntu18 based EC2 with Blobs store on S3).

A week later, we made a decision to move the instance to another subnet, therefore the content of sonatype-nexusfolder was copied to another instance without stopping the original one. The new instances started correctly and stopped right after without making a change.

Inspired by successful test, two days later, we tried to do the same again and finally migrate to another instance. However, this time we stopped original instance. After copying sonatype-instance content, neither new nor original one did not see any repositories. All our repositories are gone in Nexus UI.

There are numerous exceptions in logs of original nexus while stopping like:

2018-12-21 16:01:10,067+0000 ERROR [Thread-6]  *SYSTEM com.sonatype.nexus.migration.repository.RepositoryPrepareStep - Failed transition: COMPLETED -> ABORTED
java.lang.RuntimeException: java.lang.RuntimeException: RESTEASY003940: Unable to instantiate MessageBodyReader
        at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:41)

and 

2018-12-21 16:46:34,921+0000 ERROR [quartz-3-thread-2]  *SYSTEM com.google.common.eventbus.EventBus.nexus.async - Could not dispatch event AssetDeletedEvent{metadata=Attac org.sonatype.nexus.common.stateguard.InvalidStateException: Invalid state: STOPPED; allowed: [STARTED]         at org.sonatype.nexus.common.stateguard.StateGuard._ensure(StateGuard.java:115)

 "Reconcile component database from blob store" task also fails with 

2018-12-22 12:19:30,364+0000 INFO [qtp423295968-1512] admin org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task 'reconciledatafromblob' [blobstore.rebuildComponentDB] runNow
2018-12-22 12:19:30,364+0000 INFO [qtp423295968-1512] admin org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task 'reconciledatafromblob' [blobstore.rebuildComponentDB] state change WAITING -> RUNNING
2018-12-22 12:19:30,372+0000 INFO [quartz-3-thread-19] *SYSTEM org.sonatype.nexus.blobstore.restore.RestoreMetadataTask - Task log: /opt/nexus/sonatype-work/nexus3/log/tasks/blobstore.rebuildComponentDB-20181222121930370.log
2018-12-22 12:19:30,372+0000 INFO [quartz-3-thread-19] *SYSTEM org.sonatype.nexus.blobstore.restore.RestoreMetadataTask - ::DRY RUN:: Actions will be logged, but no changes will be made.
2018-12-22 12:19:30,639+0000 WARN [quartz-3-thread-19] *SYSTEM org.sonatype.nexus.blobstore.s3.internal.S3BlobStore - Attempt to access non-existent blob report.properties (S3PropertiesFile{bucket=nexus-repo, key=content/vol-28/chap-08/report-properties.properties})
.....
.....
2018-12-22 12:19:46,226+0000 WARN [quartz-3-thread-19] *SYSTEM org.sonatype.nexus.blobstore.s3.internal.S3BlobStore - Attempt to access soft-deleted blob 3adca743-6dbf-4638-8ce5-56a921a7c71b (S3PropertiesFile{bucket=nexus-repo, key=content/vol-25/chap-16/3adca743-6dbf-4638-8ce5-56a921a7c71b.properties})
2018-12-22 12:19:46,226+0000 WARN [quartz-3-thread-19] *SYSTEM org.sonatype.nexus.repository.storage.StorageTxImpl - Reached max retries: 8/8
2018-12-22 12:19:46,228+0000 WARN [quartz-3-thread-19] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskJob - Task 4baf04dd-1b47-420a-b9ee-10586eb6e993 : 'reconciledatafromblob' [blobstore.rebuildComponentDB] execution failure
org.sonatype.nexus.repository.storage.RetryDeniedException: Reached max retries: 8/8
at org.sonatype.nexus.repository.storage.StorageTxImpl.allowRetry(StorageTxImpl.java:226)
at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
.....
Caused by: org.sonatype.nexus.repository.storage.MissingBlobException: Blob s3-nexus-repo@30B55E85-482EE75F-3AD6BEC6-D67AA14B-86EDA37A:3adca743-6dbf-4638-8ce5-56a921a7c71b exists in metadata, but is missing from the blobstore
at org.sonatype.nexus.repository.storage.StorageTxImpl.requireBlob(StorageTxImpl.java:950)
at sun.reflect.GeneratedMethodAccessor409.invoke(Unknown Source)
... 19 common frames omitted
2018-12-22 12:19:46,228+0000 INFO [quartz-3-thread-19] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task 'reconciledatafromblob' [blobstore.rebuildComponentDB] state change RUNNING -> WAITING (FAILED)

Our build jobs are failing with (may be not related)

*UNKNOWN org.sonatype.nexus.repository.httpbridge.internal.ViewServlet - Failure servicing: GET /content/groups/public/com/ourproject/1.52-SNAPSHOT/ourproject-1.52-20181122.082121-9.pom
org.sonatype.nexus.repository.storage.RetryDeniedException: Reached max retries: 8/8
at org.sonatype.nexus.repository.storage.StorageTxImpl.allowRetry(StorageTxImpl.java:226)
at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

To conclude, Nexus did not survive a restart and our build pipelines are broken. Any inputs/help/ideas are highly appreciated.
I will gladly provide any missing information that can help.

BR,

Cyril

[Michael Martz]

Looks like you are using S3. Are there any files in your S3 bucket? Could you post the full log file for us to peruse for other information? Just based on what you've provided so far I'd guess that the S3 bucket doesn't have the content for some reason.

Michael Martz

--
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/8f94d312-8bee-498e-91b8-a3ce05267128%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

--

Michael Martz

Software Engineer

Sonatype

[cyril...@smaato.com]

Thank you for the response. 

Yes, we are running Nexus OSS 3.14.0 version on Ubuntu18 based EC2 with Blobs store on S3.

S3 is accessible from the instance and has about 326Gb of data.

aws s3 ls nexus-repo
                           PRE content/
2018-12-26 11:21:04         70 30B55E85-482EE75F-3AD6BEC6-D67AA14B-86EDA37A-metrics.properties
2018-12-13 10:56:08         40 metadata.properties

As I mentioned above after migration from Nexus2 to Nexus3, the new service was fully functional about a week. Later we had planned to migrate to another instance in another subnet with the same Nexus version. Please, find attached a log file from the moment when I initiated stopping Nexus and many exceptions with RESTEASY003940 error.

You may notice Disabling repository upgrade capability for 'apache-snapshots' at: http://localhost:8082/nexus/service/siesta/migrationagent in the log. This is our old Nexus2 instance with Upgrade capability enabled.

Many thanks in advance.

Cyril.

[Peter Lynch]

Hi Cyril,

On Tue, Dec 25, 2018 at 3:50 AM cyril.burd via Nexus Users <nexus...@glists.sonatype.com> wrote:

We have recently migrated all our repositories from Nexus 2.14.11 (EC2 instance with EBS volume) to  the most recent 3.14.0 version (Ubuntu18 based EC2 with Blobs store on S3).

A week later, we made a decision to move the instance to another subnet, therefore the content of sonatype-nexusfolder was copied to another instance without stopping the original one. The new instances started correctly and stopped right after without making a change.

It is not clear what you mean by "sonatype-nexus folder". Please review this article and clarify what this directory actually refers to:  

https://support.sonatype.com/hc/en-us/articles/231742807-Understanding-Nexus-Repository-Manager-3-Basic-Directories

For example, copying the contents of the entire Data Directory while Nexus is running against it is not supported and you will more than likely have corrupt files end up in the target directory to which you copied the files.

Simply starting and then stopping immediately an instance referencing the copied data is not a valid test to prove nothing is corrupt.

Inspired by successful test, two days later, we tried to do the same again and finally migrate to another instance. However, this time we stopped original instance. After copying sonatype-instance content, neither new nor original one did not see any repositories. All our repositories are gone in Nexus UI.

You are referring to "sonatype-instance content" now -  we have no idea what directory you mean by this. The actual directory copied matters.

If all your repositories are gone, it implies one of these things:

1) the new Nexus 3 instance is not referring to the correct copied data directory files of the source nexus 3 instance

2) there was a problem loading the Nexus 3 databases in the referenced data directory

3) the nexus 2 migration wizard was not fully finalized in the Nexus 3 instance, meaning the nexus 2 migration to Nexus 3 was not explicitly finalized. ie. It was left at the step where Nexus 3 is continuously polling Nexus 2 for more changes.

There are numerous exceptions in logs of original nexus while stopping like:

2018-12-21 16:01:10,067+0000 ERROR [Thread-6]  *SYSTEM com.sonatype.nexus.migration.repository.RepositoryPrepareStep - Failed transition: COMPLETED -> ABORTED
java.lang.RuntimeException: java.lang.RuntimeException: RESTEASY003940: Unable to instantiate MessageBodyReader
        at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:41)

This could suggest item 3 in my list of things that went wrong is to blame.

You've described moving files of a running application. You've also described possibly pointing multiple running instances of nexus at the same S3 blobstore but with different databases in different instances. And finally you described symptoms of trying to use Nexus 3 without finalizing the Nexus 2 -> Nexus 3 migration wizard before shutting down Nexus 3. These are all good ways to corrupt/lose files and make your Nexus 3 instances broken.

At this point I'd suggest going back to the working Nexus 2 instance and replanning the migration to nexus 3 again after getting a better understanding of how it works and how to move a Nexus 3 instance, after Nexus 2-> Nexus 3 migration is complete.

https://support.sonatype.com/hc/en-us/articles/360010352014

[Peter Lynch]

On Wed, Dec 26, 2018 at 3:09 PM cyril.burd via Nexus Users <nexus...@glists.sonatype.com> wrote:

Thank you for the response. 

Yes, we are running Nexus OSS 3.14.0 version on Ubuntu18 based EC2 with Blobs store on S3.

S3 is accessible from the instance and has about 326Gb of data.

aws s3 ls nexus-repo
                           PRE content/
2018-12-26 11:21:04         70 30B55E85-482EE75F-3AD6BEC6-D67AA14B-86EDA37A-metrics.properties
2018-12-13 10:56:08         40 metadata.properties

As I mentioned above after migration from Nexus2 to Nexus3, the new service was fully functional about a week. Later we had planned to migrate to another instance in another subnet with the same Nexus version. Please, find attached a log file from the moment when I initiated stopping Nexus and many exceptions with RESTEASY003940 error.

You may notice Disabling repository upgrade capability for 'apache-snapshots' at: http://localhost:8082/nexus/service/siesta/migrationagent in the log. This is our old Nexus2 instance with Upgrade capability enabled.

It doesn't appear the Nexus 2 -> Nexus 3 migration process was finalized before Nexus 3 was shut down. Nexus 3 should not be used for builds or otherwise configured until the Upgrade steps are explicitly ended.

 

To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/657dbbd4-f12a-4c66-8616-9ad577e5c524%40glists.sonatype.com.

[cyril...@smaato.com]

Hi Peter,

Thanks for the reference, by copying the content of sonatype-nexus directory I mean copying nexus3 directory, which is the only directory there. I was not aware about so many options. I created a tar file of sonatype-nexus/nexus3 and un-tared it in target clean Nexus 3.14 system.

Regarding migration process. We migrated data using File System copying transfer method and it took about 40 hours. At least in Nexus UI I did not see any errors and the process was finished and finalized. However, I searched again logs of migration and found the error:

2018-12-14 07:36:21,721+0000 ERROR [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.repository.ProcessChangesStep - Failed processing of CREATE central:/org/

springframework/boot/spring-boot-test/1.4.1.RELEASE/spring-boot-test-1.4.1.RELEASE-javadoc.jar, will ignore and move on. Error uploading blob, Cause: We encountered an int

ernal error. Please try again. (Service: Amazon S3; Status Code: 500; Error Code: InternalError; Request ID: 23539BD0CD016A13; S3 Extended Request ID: XWBjT/rdrcB6mY1foZxh

ZuZWt8YdttStov2iTXMMHpyvGGq2EN/mvMTOiy0CbSuQP1kQR1TL+UY=)

org.sonatype.nexus.blobstore.api.BlobStoreException: Error uploading blob, Cause: We encountered an internal error. Please try again. (Service: Amazon S3; Status Code: 500

; Error Code: InternalError; Request ID: 23539BD0CD016A13; S3 Extended Request ID: XWBjT/rdrcB6mY1foZxhZuZWt8YdttStov2iTXMMHpyvGGq2EN/mvMTOiy0CbSuQP1kQR1TL+UY=)

        at org.sonatype.nexus.blobstore.s3.internal.MultipartUploader.upload(MultipartUploader.java:98)

        at org.sonatype.nexus.blobstore.s3.internal.S3BlobStore.lambda$0(S3BlobStore.java:221)

        at org.sonatype.nexus.blobstore.s3.internal.S3BlobStore.create(S3BlobStore.java:258)

        at org.sonatype.nexus.blobstore.s3.internal.S3BlobStore.create(S3BlobStore.java:218)

        at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)

        at org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGuard.java:272)

        at org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(GuardedInterceptor.java:53)

        at org.sonatype.nexus.repository.storage.StorageFacetImpl.createTempBlob(StorageFacetImpl.java:215)

        at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.getTempBlobFromCopy(RepositoryMigratorSupport.java:336)

        at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.getTempBlob(RepositoryMigratorSupport.java:318)

        at com.sonatype.nexus.migration.repository.migrators.Maven2RepositoryMigratorSupport.streamContent(Maven2RepositoryMigratorSupport.java:168)

        at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.ingestContent(RepositoryMigratorSupport.java:209)

        at com.sonatype.nexus.migration.repository.migrators.Maven2ProxyRepositoryMigrator.ingestContent(Maven2ProxyRepositoryMigrator.java:55)

        at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.createOrUpdate(RepositoryMigratorSupport.java:168)

        at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.processChange(RepositoryMigratorSupport.java:146)

        at com.sonatype.nexus.migration.repository.migrators.Maven2ProxyRepositoryMigrator.processChange(Maven2ProxyRepositoryMigrator.java:118)

        at com.sonatype.nexus.migration.repository.RepositoryMigrator$processChange$2.call(Unknown Source)

        at com.sonatype.nexus.migration.repository.ProcessChangesStep$_submit_closure2.doCall(ProcessChangesStep.groovy:333)

        at com.sonatype.nexus.migration.repository.ProcessChangesStep$_submit_closure2.doCall(ProcessChangesStep.groovy)

        at sun.reflect.GeneratedMethodAccessor555.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)

        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)

        at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:264)

        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)

        at groovy.lang.Closure.call(Closure.java:418)

        at groovy.lang.Closure.call(Closure.java:412)

        at groovy.lang.Closure.run(Closure.java:499)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: We encountered an internal error. Please try again. (Service: Amazon S3; Status Code: 500; Error Code: Intern

alError; Request ID: 23539BD0CD016A13; S3 Extended Request ID: XWBjT/rdrcB6mY1foZxhZuZWt8YdttStov2iTXMMHpyvGGq2EN/mvMTOiy0CbSuQP1kQR1TL+UY=)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1638)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1303)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1055)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667)

        at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649)

        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513)

        at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4247)

        at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4194)

        at com.amazonaws.services.s3.AmazonS3Client.doUploadPart(AmazonS3Client.java:3231)

        at com.amazonaws.services.s3.AmazonS3Client.uploadPart(AmazonS3Client.java:3216)

        at org.sonatype.nexus.blobstore.s3.internal.MultipartUploader.upload(MultipartUploader.java:79)

        ... 33 common frames omitted

Can this be a cause of the problem? A single file that was not migrated properly, left the upgrade process unfinished and led to DB corruption?

If yes, how can I fix it? The migration was done on Dec 14 we did not notice any issues until Dec 21st, hundreds of new artifacts were pushed to the new Nexus. How can I safe the work of the whole RnD department during these days? Why Reconcile component database from blob store" task fails now?

Many thanks for helping me with the issue.

Cyril.

[cyril...@smaato.com]

Nexus3 was not accessible for new builds during the upgrade and I remember that the process was finished and finalized via UI. If you can give me a hint how it should look in logs I can search for the line.

I found the following:

2018-12-14 22:06:00,748+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:01,770+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:02,678+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:03,775+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:04,671+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:05,766+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:06,540+0000 INFO  [Thread-387 <command>sql.select from component where bucket = :bucket</command>]  admin com.orientechnologies.common.profiler.OProfilerS

tub - $ANSI{green {db=component}} [TIP] Query 'SELECT FROM component WHERE bucket = #16:15' returned a result set with more than 10000 records. Check if you really need al

l these records, or reduce the resultset by using a LIMIT to improve both performance and used RAM

2018-12-14 22:06:06,677+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:07,674+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:08,679+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:09,679+0000 DEBUG [qtp501932762-1159]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:10,707+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:11,679+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:12,679+0000 DEBUG [qtp501932762-1445]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:13,683+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:14,690+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:15,689+0000 DEBUG [qtp501932762-1445]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:16,689+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:17,682+0000 DEBUG [qtp501932762-1445]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:18,710+0000 DEBUG [qtp501932762-1182]  admin com.sonatype.nexus.migration.ui.ProgressComponent - read FINISH

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.repository.RepositoryFinishStep - Transitioning: RUNNING -> COMPLETED

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.repository.RepositoryFinishStep - Completed Finish upgrading repository: releases

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.repository.RepositoryFinishStep - Transitioned: COMPLETED

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.plan.StepExecutor - Step finished: Step(name:Finish upgrading repository: releases, phase:FINISH)

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-1]  admin com.sonatype.nexus.migration.plan.StepExecutor - Submitting step: Step(name:Finish upgrading repository: public, phase:FINISH) with isolation: NONE

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-1]  admin com.sonatype.nexus.migration.plan.StepExecutor - Step queued: Step(name:Finish upgrading repository: public, phase:FINISH)

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.plan.StepExecutor - Running step: Step(name:Finish upgrading repository: public, phase:FINISH)

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.repository.RepositoryFinishStep - Transitioning: INITIALIZED -> RUNNING

2018-12-14 22:06:19,559+0000 INFO  [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.repository.RepositoryFinishStep - Running Finish upgrading repository: public

2018-12-14 22:06:19,559+0000 DEBUG [plan-executor-7-thread-4]  admin com.sonatype.nexus.migration.repository.RepositoryFinishStep - Transitioned: RUNNING

2018-12-14 22:06:19,564+0000 INFO  [plan-executor-7-thread-1]  admin com.sonatype.nexus.migration.plan.StepExecutor - Step not runnable: Step(name:End phase: FINISH, phase:FINISH)

Cyril

[Peter Lynch]

Cyril -

The issues you have encountered are not going to be diagnosable on the mailing list. I suggest you provide additional information via the private jira issue instead - https://issues.sonatype.org/browse/NEXUS-18739

To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/c2957ca4-e014-408c-aaba-e697805a96a0%40glists.sonatype.com.

[Rajnish Pandey]

Hi,

Currently i am using Nexus 3.12 version and for cleaning old artifacts i have schedule task like delete snapshot, delete unused snapshot .some important assets deleted by using task. i want to restore all snapshot which got deleted using task schedule. is there way to restore deleted snapshot from nexus?

Could you please help me on this.