Nexus throwing NonResolvableTarballNameException and returning a 500

[sagarkhushalani]

What problem are you trying to solve? Nexus throws an exception and returns a 500 intermittently when an npm client is attempting to pull a package. So far, this has been noticed with the following packages:

• @babel/types
• har-validator
• postcss-loader
• resolve-cwd-3.0.0
• npm-run-path

Sample exception:

com.sonatype.nexus.repository.npm.internal.NonResolvableTarballNameException: Could not find package npm-run-path
        at com.sonatype.nexus.repository.npm.internal.orient.OrientNpmProxyFacet.retrievePackageVersionTx(OrientNpmProxyFacet.java:491)
        at org.sonatype.nexus.transaction.TransactionalWrapper.proceedWithTransaction(TransactionalWrapper.java:58)
        at org.sonatype.nexus.transaction.TransactionInterceptor.proceedWithTransaction(TransactionInterceptor.java:66)
        at org.sonatype.nexus.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:55)
        at com.sonatype.nexus.repository.npm.internal.orient.OrientNpmProxyFacet.retrievePackageVersion(OrientNpmProxyFacet.java:480)
        at com.sonatype.nexus.repository.npm.internal.orient.OrientNpmProxyFacet.getUrl(OrientNpmProxyFacet.java:218)
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.logContentOrThrow(ProxyFacetSupport.java:366)
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.doGet(ProxyFacetSupport.java:333)
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.lambda$1(ProxyFacetSupport.java:284)
        at org.sonatype.nexus.common.cooperation2.internal.orient.OrientCooperation2$OrientCooperation2Builder.lambda$1(OrientCooperation2.java:69)
        at org.sonatype.nexus.common.io.CooperatingFuture.performCall(CooperatingFuture.java:123)
        at org.sonatype.nexus.common.io.CooperatingFuture.call(CooperatingFuture.java:65)
        at org.sonatype.nexus.common.io.ScopedCooperationFactorySupport$ScopedCooperation.cooperate(ScopedCooperationFactorySupport.java:99)
        at org.sonatype.nexus.common.cooperation2.internal.orient.OrientCooperation2$OrientCooperation2Builder.cooperate(OrientCooperation2.java:64)
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.get(ProxyFacetSupport.java:294)
        at org.sonatype.nexus.repository.proxy.ProxyFacetSupport.get(ProxyFacetSupport.java:277)
        at org.sonatype.nexus.repository.proxy.ProxyHandler.handle(ProxyHandler.java:53)
        at org.sonatype.nexus.repository.view.Context.proceed(Context.java:88)
        at org.sonatype.nexus.repository.storage.LastDownloadedHandler.handle(LastDownloadedHandler.java:59)
        at org.sonatype.nexus.repository.view.Context.proceed(Context.java:88)
        at org.sonatype.nexus.repository.storage.UnitOfWorkHandler.handle(UnitOfWorkHandler.java:39)
        at org.sonatype.nexus.repository.view.Context.proceed(Context.java:88)
        at org.sonatype.nexus.repository.view.Context$proceed.call(Unknown Source)
        at com.sonatype.nexus.repository.npm.internal.orient.OrientNpmProxyRecipe$_closure1.doCall(OrientNpmProxyRecipe.groovy:295)
        at sun.reflect.GeneratedMethodAccessor383.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)

(there are more lines after this, I can post those if needed)

Do you have a workaround you are using at present?

No. Not entirely sure why this is happening. We are investigating on our end as well. Things I have tried:

• invalidating the cache
• deleting and recreating the repositories

What feature or behavior is this required for? N/A

How could we solve this issue? (Not knowing is okay!) Not sure :(

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

• Nexus v3.57.0

• Server OS: RockyLinux 8

• Database: OrientDB? Whatever Nexus comes with. No modification to database settings.

• Anything else? This started quite suddenly, and I do not know of any changes upstream. It is not consistent. Sometimes, pulling packages will succeed.