OSS Nexus 3 dooesn't start anymore

Hello
We had an issue with our OSS Nexus 3 ( nexus-3.20.1-01 ) production issue.

It was frozen, the gui was not responding and it was not willing to shutdown even after multiple attempts and giving it several minutes each time.

We decided to kill the processes. It took kill -9 to finally kill it.

After that it never came back up it was blocked at this step

2020-05-09 11:41:42,661-0400 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task ‘System - Repository Health Check: springframework’ [healthcheck] removed
2020-05-09 11:41:42,664-0400 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task ‘System - Repository Health Check: springframework’ [healthcheck] : state=WAITING
2020-05-09 11:41:42,674-0400 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.scheduling.TaskSchedulerImpl - Task ‘System - Repository Health Check: springframework’ [healthcheck] scheduled: hourly
2020-05-09 11:41:42,675-0400 INFO [FelixStartLevel] *SYSTEM com.sonatype.nexus.plugins.healthcheck.service.impl.HealthCheckTaskManagerImpl - Enabled health check for repository springframework
2020-05-09 11:41:42,690-0400 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task ‘System - Repository Health Check: ods’ [healthcheck] removed
2020-05-09 11:41:42,693-0400 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task ‘System - Repository Health Check: ods’ [healthcheck] : state=WAITING
2020-05-09 11:41:42,699-0400 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.scheduling.TaskSchedulerImpl - Task ‘System - Repository Health Check: ods’ [healthcheck] scheduled: hourly
2020-05-09 11:41:42,700-0400 INFO [FelixStartLevel] *SYSTEM com.sonatype.nexus.plugins.healthcheck.service.impl.HealthCheckTaskManagerImpl - Enabled health check for repository ods

I looked at previous logs and it should have gone to these steps

2020-02-12 11:18:35,101-0500 INFO [FelixStartLevel] *SYSTEM com.sonatype.nexus.plugins.healthcheck.service.impl.HealthCheckTaskManagerImpl - Enabled health check for repository springframework
2020-02-12 11:18:35,119-0500 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task ‘System - Repository Health Check: ods’ [healthcheck] removed
2020-02-12 11:18:35,122-0500 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task ‘System - Repository Health Check: ods’ [healthcheck] : state=WAITING
2020-02-12 11:18:35,126-0500 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.scheduling.TaskSchedulerImpl - Task ‘System - Repository Health Check: ods’ [healthcheck] scheduled: hourly
2020-02-12 11:18:35,127-0500 INFO [FelixStartLevel] *SYSTEM com.sonatype.nexus.plugins.healthcheck.service.impl.HealthCheckTaskManagerImpl - Enabled health check for repository ods
2020-02-12 11:18:35,352-0500 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.QuartzSchedulerSPI - Scheduler put into ready mode
2020-02-12 11:18:35,361-0500 INFO [jetty-main-1] *SYSTEM org.sonatype.nexus.rapture.internal.RaptureWebResourceBundle - UI plugin descriptors:
2020-02-12 11:18:35,365-0500 INFO [jetty-main-1] *SYSTEM org.sonatype.nexus.rapture.internal.RaptureWebResourceBundle - nexus-security-plugin
2020-02-12 11:18:35,366-0500 INFO [jetty-main-1] *SYSTEM org.sonatype.nexus.rapture.internal.RaptureWebResourceBundle - ExtJS UI plugin descriptors:
2020-02-12 11:18:35,367-0500 INFO [jetty-main-1] *SYSTEM org.sonatype.nexus.rapture.internal.RaptureWebResourceBundle - nexus-rapture
2020-02-12 11:18:35,368-0500 INFO [jetty-main-1] *SYSTEM org.sonatype.nexus.rapture.internal.RaptureWebResourceBundle - nexus-blobstore-s3

It never timed out or gave real errors or exceptions. Seems like the scheduler never got ready to start and just blocked

We decided to restore a backup but it has also caused other issues.

Best regards
Sebastien

There’s not a lot to go on here as (as you hint) the log snips you show just show INFO messages, nothing out of the ordinary.
My general recommendation is to review System Requirements and make sure your system is up to spec.
-Joe