# Reindexing failures after upgrade

**URL:** https://community.sonatype.com/t/reindexing-failures-after-upgrade/2869
**Category:** Sonatype Nexus Repository
**Created:** [November 7, 2019, 1:05am UTC](https://community.sonatype.com/t/reindexing-failures-after-upgrade/2869 "2019-11-07T01:05:20Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![jeremiah](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@jeremiah](https://community.sonatype.com/u/jeremiah)
#### Post date: [November 7, 2019, 1:05am UTC](https://community.sonatype.com/t/reindexing-failures-after-upgrade/2869/1 "2019-11-07T01:05:20Z")

</div>

Upgrading from nexus-3.1.0-04 to nexus-3.19.1-01.

Post-upgrade, the service wrongly started as user root. I fixed it so it correctly runs under user nexus.

However, the service will not fully start. From the log:

> \*SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskJob - Task 5eee8148-b121-4a5f-8d17-631c93cc0c68 : ‘Reindex npm repository - (npm-proxy)’ [repository.npm.reindex] execution failure"  
> \*SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskJob - Task 1b6fdac4-e72b-4581-84e4-82dd86722482 : ‘Repair - Rebuild repository search’ [repository.rebuild-index] execution failure

I’ve uploaded the full log to [https://franz.com/nexus.txt](https://franz.com/nexus.txt) and I do have a full pre-upgrade backup of the sonatype-work directory.

Any help is enormously appreciated!

Cheers,

j

---

<div class="post-metadata">

### Author: ![rseddon](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/rseddon/32/341_2.png) [@rseddon](https://community.sonatype.com/u/rseddon)
#### Post date: [November 7, 2019, 3:13pm UTC](https://community.sonatype.com/t/reindexing-failures-after-upgrade/2869/2 "2019-11-07T15:13:50Z")

</div>

This forum isn’t the right place to debug technical problems.

If you have a support contract with us you can use our support system at [https://support.sonatype.com](https://support.sonatype.com/). Please note that the support system is for licensed customers only.

Otherwise you can try raising an issue at [https://issues.sonatype.org](https://issues.sonatype.org/) in the “Dev - Nexus” issue.

Either way, provide a [support zip file](https://support.sonatype.com/hc/en-us/articles/223243768-Support-Ticket-Best-Practices#nexus3) if you can get to the Nexus Repo UI. Or provide the complete nexus.log file otherwise.

Regards,

Rich

---

<div class="post-metadata">

### Author: ![jeremiah](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@jeremiah](https://community.sonatype.com/u/jeremiah)
#### Post date: [November 7, 2019, 7:29pm UTC](https://community.sonatype.com/t/reindexing-failures-after-upgrade/2869/3 "2019-11-07T19:29:07Z")

</div>

Ah ok. My bad but thanks for redirecting me!

---

<div class="post-metadata">

### Author: ![jhonny.oliveira](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/jhonny.oliveira/32/1844_2.png) [@jhonny.oliveira](https://community.sonatype.com/u/jhonny.oliveira)
#### Post date: [June 29, 2021, 4:29pm UTC](https://community.sonatype.com/t/reindexing-failures-after-upgrade/2869/4 "2021-06-29T16:29:42Z")

</div>

I’m having the same problem. How did you sort this out?
