Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Joe Tom
    @joedragons
    https://help.sonatype.com/display/NXRM3/System+Requirements#SystemRequirements-Memory general recommendation is 8, so no surprise there unless Azure's saving you something
    Stephen Attard
    @stv-io
    Hey guys, any idea if it' possible to authenticate pulls from docker.io when using a docker-proxy repository? The question has been answered in https://community.sonatype.com/t/docker-hub-credentials/5375 and there's been no response yet.
    Vincent Letarouilly
    @Opa-
    @stv-io I just replied on the topic, you have a setting for that on the docker-proxy repository's settings page (at the end)
    image.png
    you can fill in docker hub credentials there
    Stephen Attard
    @stv-io
    @Opa- that looks sweet, I'll try it out (didn't expect that to be the solution tbh)
    iamandymcinnes
    @iamandymcinnes

    hi we're using nexus for hosting some of our R libraries and as a proxy for r-cran libraries. A few weeks ago our nexus setup had an issue and it seems to have completely messed up the indexes of some repositories. So if you select a package you get a 404 or errors like this when you click on an artifact: Uncaught TypeError: b.get is not a function (https://nexus3.url.com/static/rapture/nexus-repository-r-prod.js?_v=3.32.0-03&_e=OSS:1)

    I'm also not seeing the proxy work, even to the point I created a new proxy called r-proxy, added the r-cran repo as the remote and then manually tried installing a package using it i.e.

    install.packages('glue', repos='https://username:password@nexus3.url.com/repository/r-proxy')

    But all I get is the following, which is what we were also seeing on our builds using our original r-cran-proxy repo.

    Installing package into ‘C:/Users/username/Documents/R/win-library/4.0’
    (as ‘lib’ is unspecified)
    Warning in install.packages :
    unable to access index for repository https://username:password@nexus3.url.com/repository/r-proxy/src/contrib:
    cannot open URL 'https://username:password@nexus3.url.com/repository/r-proxy/src/contrib/PACKAGES'
    Warning in install.packages :
    package ‘glue’ is not available (for R version 4.0.0)
    Warning in install.packages :
    unable to access index for repository https://username:password@nexus3.url.com/repository/r-proxy/bin/windows/contrib/4.0:
    cannot open URL 'https://username:password@nexus3.url.com/repository/r-proxy/bin/windows/contrib/4.0/PACKAGES'

    4 replies
    Nico Schottelius
    @telmich
    Good evening! I was just trying out the docker image and it seems nexus is not listening on IPv6 for port 8081. So deploying nexus in IPv6 environments fails at the moment. Is it possible to patch the default listener options in the image to support both IPv6 and IPv4?
    1 reply
    Nico Schottelius
    @telmich
    Just seen, the option -Djava.net.preferIPv4Stack=true would need to be removed inside the container
    Nico Schottelius
    @telmich
    Injecting via INSTALL4J_ADD_VM_PARAMS does not work, because the options file is appended afterwards and overwrites the setting
    I believe this line is mistaken/incorrect: INSTALL4J_ADD_VM_PARAMS="$INSTALL4J_ADD_VM_PARAMS $vmoptions_val" - I think it should be INSTALL4J_ADD_VM_PARAMS=" $vmoptions_val $INSTALL4J_ADD_VM_PARAMS" instead
    Nico Schottelius
    @telmich
    Using sed -i 's/0.0.0.0/::/' /opt/sonatype/nexus/etc/nexus-default.properties leads to a crashing server with java.io.IOException: Failed to bind to /0:0:0:0:0:0:0:0:8081 - maybe it's related to the java.net.preferIPv4Stack=true option
    Anton Karasov
    @kanton10062006

    Hi folks,
    I would like to submit PR to Nexus helm charts https://github.com/sonatype/helm3-charts.
    This PR will provide ability to configure ingress resource properly for docker repositories:
    1)Provide ability to set custom hostPath for ingress resource docker repositories;
    2)Provide ability to set custom annotations for ingress resource of docker repositories.

    Thanks in advance.

    image.png
    Anton Karasov
    @kanton10062006
    Sileno O. Brito
    @silenobrito_twitter

    Hi, I would like to add support for freebsd in Nexus, but I need help doing that, I don't know how to work in Nexus. I would like help trying to implement a "nexus-repository-poudriere-binary", but I need someone to discuss whether what I have in mind can be implemented (without having to make significant changes to the nexus) and leave this format open.

    Basically, I imagine doing it in 3 (three) ways:
    1) Use the raw repository: Create a share via webdav or something and use a freebsd machine to actually create the repository structure, so just throw the "*.txz" in a folder and use "pkg repo" to create the indexes and other files to create a compatible repository with poudriere. (the middle ground)

    2) Use the raw repository: Make a script to synchronize all the contents of the ready-made repository on a freebsd machine (where the packages would go to it) and nexus would serve as a cache and access control. (the worst and fastest)

    3) Rewrite pkg (only the parts needed to manage package in relation to repository creation), porting from Unix to Linux and writing a new module "nexus-repository-poudriere" (the most time consuming)

    https://community.sonatype.com/t/is-there-any-project-to-support-freebsd-binaries-with-poudriere-binary-package-txz/7101

    kwon14
    @kwon14
    Hello. I'm using the nexus3 really well. thank you. Currently, I am using nexus3 (OSS 3.33.0-01) as a Pypi repository for sonatype/nexus3 images and NFS storage in a Kubernetes environment.
    However, when the container pod is restarted, both the pypi repository and account are initialized. I earnestly ask if there is a way to keep the data even when the pod restarts. thank you.
    Joe Tom
    @joedragons
    @kwon14 I suspect you have both the Nexus Repository and data in the same pod as that would explain your behavior. If so, that is not intended. See https://hub.docker.com/r/sonatype/nexus3 Persistent Data section. It's not designed specifically for Kubernetes but the concept is the same (esp if you're using docker as your container image).
    I haven't done it specifically for Kubernetes so can't offer exact advice, maybe someone else here has if you need.
    Nils van Lück
    @vanlueckn

    Hi,

    i am using the nexus helm chart for kubernetes and i have an issue with ssl termination. I terminate the ssl connection in haproxy, nexus gets only plain http traffic in our internal network.

    When i try to access nexus i get multiple issues in chrome because of insecure loading of assets (styles, javascript, etc):

    https://img.tkde.link/iXUtQj.png

    How can i config the helm chart for using https:// to load the assets?

    Brett Adcock
    @xbrett

    Hi, last week I attempted to upgrade Nexus from 3.21.1 to 3.32.0 and managed to get in an unrecoverable state. I had to fully recreate and repopulate the instance. I'm looking for a little more insight into what happens to the state of the component DB and Blobstore during a Nexus upgrade. The upgrade appeared to be successful at first, however upon trying to push/pull new artifacts, I ran into the following error

    2021-08-18 03:01:06,291+0000 WARN  [qtp732988231-291] ***** org.sonatype.nexus.transaction.RetryController - Exceeded retry limit: 8/8 (org.sonatype.nexus.repository.storage.MissingBlobException: Blob s3@ECBCE6CC-61FB6BAE-78F2B751-8CB71DFB-03C76B02:5d4d851d-12fa-4618-874b-217d9b352d97 exists in metadata, but is missing from the blobstore)
    2021-08-18 03:01:06,292+0000 WARN  [qtp732988231-291] ****** org.sonatype.nexus.repository.httpbridge.internal.ViewServlet - Failure servicing: GET /repository/maven-snapshots/com/****/****/maven-metadata.xml
    org.sonatype.nexus.repository.storage.RetryDeniedException: Exceeded retry limit
        at org.sonatype.nexus.repository.storage.StorageTxImpl.allowRetry(StorageTxImpl.java:206)
        at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.sonatype.nexus.common.stateguard.SimpleMethodInvocation.proceed(SimpleMethodInvocation.java:53)
        at org.sonatype.nexus.common.stateguard.StateGuardAspect$1.invoke(StateGuardAspect.java:69)
        at com.sun.proxy.$Proxy213.allowRetry(Unknown Source)
        ...
          at java.lang.Thread.run(Thread.java:748)
    Caused by: org.sonatype.nexus.repository.storage.MissingBlobException: Blob s3@ECBCE6CC-61FB6BAE-78F2B751-8CB71DFB-03C76B02:5d4d851d-12fa-4618-874b-217d9b352d97 exists in metadata, but is missing from the blobstore
        at org.sonatype.nexus.repository.storage.StorageTxImpl.requireBlob(StorageTxImpl.java:944)
        at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.sonatype.nexus.common.stateguard.SimpleMethodInvocation.proceed(SimpleMethodInvocation.java:53)
        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.common.stateguard.StateGuardAspect$1.invoke(StateGuardAspect.java:63)
        at com.sun.proxy.$Proxy213.requireBlob(Unknown Source)
        at org.sonatype.nexus.repository.maven.internal.MavenFacetImpl.getAssetAndBlob(MavenFacetImpl.java:239)
        at org.sonatype.nexus.transaction.TransactionalWrapper.proceedWithTransaction(TransactionalWrapper.java:57)
        ... 116 common frames omitte

    I'm curious to know what modifications the upgrade process makes to both the component db and the blobstore. I was under the impression that there would be no modifications to the state of the blobstore during the upgrade, and that if the upgrade failed, I would be able to rollback to a previous snapshot of the Orient DBs and point this at the same blobstore. However, I did not experience this to be the case and I'm looking to gain more understanding as to why this didn't work as I'd expected.

    1 reply
    David Webb
    @prowave
    Hello, I have created an AWS Volume, formatted as ext4, and moved my nexus-data to the volume. I have added it as a persistent volume in Kubernetes but when I try to start the nexus3 docker image in Kubernetes the volume will not mount. MountVolume.MountDevice failed for volume "nexus-data-pv" : rpc error: code = Internal desc = could not format "/dev/xvdbb" and mount it at "/var/lib/kubelet/plugins/kubernetes.io/csi/pv/nexus-data-pv/globalmount": mount failed: exit status 32 Mounting command: mount Mounting arguments: -t ext4 -o defaults /dev/xvdbb /var/lib/kubelet/plugins/kubernetes.io/csi/pv/nexus-data-pv/globalmount Output: mount: /var/lib/kubelet/plugins/kubernetes.io/csi/pv/nexus-data-pv/globalmount: wrong fs type, bad option, bad superblock on /dev/nvme2n1, missing codepage or helper program, or other error. Has anyone encountered this. I can mount the volume on another EC2 instance and read it just fine. Thanks.
    devopsteam605
    @devopsteam605
    Hi, for the past two days we are getting the following error when running the cleanup policy task:
    *SYSTEM org.sonatype.nexus.cleanup.internal.orient.service.OrientCleanupServiceImpl - Failed to delete component.
    org.elasticsearch.action.search.SearchPhaseExecutionException: all shards failed
    at org.elasticsearch.action.search.AbstractSearchAsyncAction.onFirstPhaseResult(AbstractSearchAsyncAction.java:206)
    ....
    the log file became really big (179G and another one that is 250G)
    our nexus version is OSS 3.30.01-01 (running with docker)
    any help will be appreciated ;)
    Joe Tom
    @joedragons
    @devopsteam605 maybe try upgrading? Could be e.g. https://issues.sonatype.org/browse/NEXUS-27014 (if you use docker but there were other fixes over last few releases...didn't look thru them all.
    Amin Vakil
    @aminvakil
    i'm having trouble logging to my docker repositories after upgrading to 3.34.0
    it returns 401 even with admin user
    Amin Vakil
    @aminvakil
    i tried again and i can login using docker login -u user -p password nexus but i can't login using echo password | docker login --username user --password-stdin nexus
    robbo10
    @robbo10
    Hey, we are using the following sonatype/nexus3 image 8716903d1912 and are being presented with the following warning Recommended file descriptor limit is 65536 but count is 4096 i can see that within limits.conf it has 65536 for both soft & hard limits. However when running ulimit -Hn its returning 4096. Any idea how i can update the hard limit as i cant run as root :)
    brewJeffcott
    @brewJeffcott
    when i try to delete a repository from the API i am getting this error message - org.sonatype.nexus.common.stateguard.InvalidStateException: Invalid state: DELETED; allowed: [STARTED] any idea on where to start trying to debug this? i have also tried deleting the repository from the UI as admin and I get Invalid state: DELETED; allowed: [STARTED]. no clue on where to start with this. google didn't seem to have any solutions. Thanks for your help!
    weirdyang
    @weirdyang
    Hi why is my GitHub repo getting referrers from dashboard-prod.data.sonatype.com? I do not use any sonatype products
    robbo10
    @robbo10
    Hi, for upgrading nexus to the latest docker image, is it as simple as stopping the existing docker container, and running the new image pointing to the existing storage on the VM?
    Joe Tom
    @joedragons
    @robbo10 should be for a basic install. As with non-docker upgrades, recommend backing up storage in case something goes awry. Similarly if you have any config on your image that you did after starting the container (e.g. setup SSL) you'd need to redo that.
    Instructions are pretty much the same, it's the particulars that are different :)
    robbo10
    @robbo10
    awesome thanks @joedragons :) in terms of blob stores, currently we are using the EBS volume on an EC2, would you know if its possible to attach another EBS volume onto the container to help with redundancy
    Joe Tom
    @joedragons
    @robbo10 I'd be surprised if it wasn't possible but haven't done it myself.
    christophvw
    @christophvw:matrix.org
    [m]
    does nexus-repository-cpan needs an update to work with the current Nexus version?
    I get 2021-09-29 11:39:20,611+0200 ERROR [qtp909140658-2109] *SYSTEM org.sonatype.nexus.internal.web.ErrorPageServlet - Unexpected exception
    java.lang.NoSuchMethodError: org.sonatype.nexus.repository.storage.StorageTx.setBlob(Lorg/sonatype/nexus/repository/storage/Asset;Ljava/lang/String;Ljava/util/function/Supplier;Ljava/lang/Iterable;Ljava/util/Map;Ljava/lang/String;Z)Lorg/sonatype/nexus/repository/storage/AssetBlob;
    at org.sonatype.nexus.repository.cpan.internal.CpanDataAccess.saveAsset(CpanDataAccess.java:118)
    Moussa Haidous
    @haidousm

    hello, I'm trying to create a new repository format that supports both a proxy and a hosted recipe but I cannot for the life of me get the hosted recipe (that shows up in the list) to open up the "configure repository" view when I click on it. The proxy recipe works just fine and I can configure and create a repo all fine but the hosted recipe just does not open.

    I'm most probably missing something somewhere but what I've got right now is a barebones hosted format with content handlers that do nothing + the js file in the resources. Is there something else that I should be adding that is required for the UI to render?

    thank you

    Odell Joseph
    @dragonpiper
    I just resetup my nexus repository and now on initial npm publish i'm getting
    Unable to authenticate, need: BASIC realm="Sonatype Nexus Repository Manager"
    Odell Joseph
    @dragonpiper
    Even npm adduser --registry= isn't working
    1 reply
    Michele Mauro
    @mimatn
    Hello everyone. Anybody had problems in upgrading 3.33.1->3.34.x ? My containter balks upgrading an OriendtDB wal file, and the server won't start.
    2 replies
    Related question: if a wal file is quite old (3 months in this case) can I assume is a relic of an out-of-disk-space event and delete it?
    esmaeil ramnejadian
    @esmaeilram
    hi dears, nexus iq is free ? i want to install on-permise in ubuntu instance
    1 reply
    Carl Wainwright
    @carlwain74
    Hello, I am having issues building a Docker image from nexus-repository-conan repo.
    Step 13/14 : COPY --from=build /nexus-repository-conan/target/nexus-repository-conan-${CONAN_VERSION}-bundle.kar ${DEPLOY_DIR}
    COPY failed: stat nexus-repository-conan/target/nexus-repository-conan-1.0.23-SNAPSHOT-bundle.kar: file does not exist
    CONAN_VERSION was defaulted as 0.0.6, but I have set NEXUS_VERSION set to 3.34.1 so I also tried 1.0.23-SNAPSHOT - No joy
    Carl Wainwright
    @carlwain74
    here is my Dockerfile
    ARG NEXUS_VERSION=3.34.1
    
    FROM maven:3-jdk-8-alpine AS build
    ARG NEXUS_VERSION=3.34.1
    ARG NEXUS_BUILD=01
    
    COPY . /nexus-repository-conan/
    RUN cd /nexus-repository-conan/; sed -i "s/3.15.1-01/${NEXUS_VERSION}-${NEXUS_BUILD}/g" pom.xml; \
        mvn clean package -PbuildKar;
    
    FROM sonatype/nexus3:$NEXUS_VERSION
    ARG NEXUS_VERSION=3.34.1
    ARG NEXUS_BUILD=01
    ARG CONAN_VERSION=1.0.23-SNAPSHOT
    ARG DEPLOY_DIR=/opt/sonatype/nexus/deploy/
    USER root
    COPY --from=build /nexus-repository-conan/target/nexus-repository-conan-${CONAN_VERSION}-bundle.kar ${DEPLOY_DIR}
    USER nexus
    Though the pom.xml doesn't contain 3.15.1.-01 anywhere
    Carl Wainwright
    @carlwain74
    I believe conan plugin is included in later versions of Nexus, does that mean I can just fire up a sonatype/nexus3 container without any modifications?