Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-28208

NPM ENOVERSIONS error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: 3.29.0, 3.31.1, 3.32.0, 3.34.1
    • Fix Version/s: None
    • Component/s: NPM, S3
    • Notability:
      3

      Description

      Description:

      We are regularly encountering ENOVERSION errors with our npm repos i.e. 

      npm install @scope/somepackage   
      npm ERR! code ENOVERSIONS
      npm ERR! No valid versions available for undefined 
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /home/ec2-user/.npm/_logs/2021-07-01T10_01_42_739Z-debug.log 

      We are using nexus 3.31.1, running in a Kubernetes (EKS) Cluster. DB is backed by an EFS persistent volume, blob store for the npm repo is in S3. 

      We have attempted deleting, and re-uploading the affected packages, the issue shortly returns after (basically after the 2nd attempt of installing the package. 

      This has been seen across multiple packages and seems to happen intermittently.

      What we tried with no effect

      • Install the latest version of Nexus3
      • Re-upload the affected packages
      • Rebuild index for repo
      • Reconcile from blob store task

      Server Logs

      We see the following server logs when the ENOVERSIONS error is seen, some entries can be seen many times but I've just taken one of each of them.

      2021-07-01 09:53:10,424+0000 WARN  [qtp1916914889-14338]  myuser com.sonatype.nexus.repository.npm.internal.orient.NpmStreamPayload - Missing blob for asset Asset{metadata=AttachedEntityMetadata{schema=asset, document=#15:723668{bucket:#13:55,format:npm,last_updated:Thu Jul 01 09:52:43 UTC 2021,attributes:[5],component:null,name:@scope/somepackage,size:21162,content_type:application/json,created_by:myuser,created_by_ip:10.0.60.94,blob_ref:default@7DD625C1-2708A9E6-A264EF8D-903017B6-40F16316:1e011d8d-2d46-48b6-9d86-8ec3ed5a36ff,last_downloaded:Thu Jul 01 09:47:34 UTC 2021,blob_created:Thu Jul 01 09:36:04 UTC 2021,blob_updated:Thu Jul 01 09:52:43 UTC 2021} v4}, name=@scope/somepackage} and no handler set to recover, for package '@scope/somepackage' and rev 'unknown'2021-07-01 
      
      09:53:10,433+0000 ERROR [qtp1916914889-14338]  svc-nx-mibl-tc com.sonatype.nexus.repository.npm.internal.orient.OrientNpmHostedFacetImpl - Failed to update revision on package root. Asset for id '@scope/somepackage' didn't exist
      
      2021-07-01 09:53:18,437+0000 ERROR [qtp1916914889-14407]  myuser com.google.common.eventbus.EventBus.nexus - Could not dispatch event com.sonatype.nexus.repository.npm.internal.orient.NpmRevisionUpgradeRequestEvent@71f4db9b to subscriber com.sonatype.nexus.repository.npm.internal.orient.OrientNpmHostedFacetImpl$$EnhancerByGuice$$1318655369@658cda44 method [public void com.sonatype.nexus.repository.npm.internal.orient.OrientNpmHostedFacetImpl.on(com.sonatype.nexus.repository.npm.internal.orient.NpmRevisionUpgradeRequestEvent)] 

      This seems very similar to issue https://issues.sonatype.org/browse/NEXUS-26856 . We have seen this issue for a few months now but waited until 3.31 as that ticket suggested. 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              thewire247 Chris B
              Last Updated By:
              Joe Tom Joe Tom
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Date of First Response:

                  tigCommentSecurity.panel-title