Short question. Any ideas on the following stack trace in nexus logs?
I could probably find a solution myself, if I even understand what the error was :)
ERROR [p21752992-57395] - org.sonatype.nexus.proxy.maven.maven2.M2Repository - Got RemoteStorageException in proxy repository "Maven Public Dependencies" [id=mavenpublicdependencies] while retrieving remote artifact "ResourceStoreRequest(requestPath="/org/apache/maven/surefire/surefire-junit4/2.16/surefire-junit4-2.16.pom")" from URL groups:public/, this is 1 (re)try, cause: org.sonatype.nexus.proxy.AccessDeniedException: Access denied on repository ID='public', path='/org/apache/maven/surefire/surefire-junit4/2.16/surefire-junit4-2.16.pom', action='read'!
Related
I have a task of migrating all the repositories from nexus to artifactory. I user nexus2artifactory tool (https://github.com/JFrogDev/nexus2artifactory) for that which didn't work. It was throwing an error like Migration error: Unable to GET api/security/groups: 400 in nexus2artifactory and Migration error: Unable to GET api/security/users: 400 in nexus2artifactory. If someone has already worked on it. Let me know the steps you followed.
Thanks in advance
we have problems with our artifactory server since this morning. When I try to restart Artifactory, we get this error:
2018-04-16 10:11:11,360 [art-init] [WARN ] (o.j.a.c.AccessClientHttpException:27) - Couldn't parse ErrorsModel from Access. Original message: Not Found
2018-04-16 10:11:37,420 [art-init] [ERROR] (o.a.w.s.ArtifactoryContextConfigListener:99) - Application could not be initialized: Waiting for access server to respond timed-out after 90303 milliseconds. java.lang.reflect.InvocationTargetException: null
Can anyone help, we have no idea what's wrong
Thanks
It seems there is an issue with the Access application, which is being started simultaneously with Artifactory.
You should fine relevant logs at the following log file: $ART_HOME/access/logs/access.log
the error message is somewhat misleading. In fact, there was a problem at the database level. the transaction log becomes full on our MSSQL database. We have increased the limit and are working to see how to reduce the size of the log.
I'm trying to develop and deploy some firebase cloud functions using the firebase cli on Windows 7. I'm trying to set up my development environment from my office where the network is behind a corporate proxy.
In the past I have configured node.js and npm to work behind the proxy and I do not have any problems downloading dependencies.
Now when I started a firebase project I did not have any problem logging into my Firebase account. However when I tried to:
firebase use --add
in my project folder I get the following error message:
Error: Server Error. unable to get local issuer certificate
From the firebase-debug.log I get more info:
[debug] [2017-10-16T14:43:42.993Z] >>> HTTP REQUEST GET https://admin.firebase.com/v1/projects Mon Oct 16 2017 16:43:42 GMT+0200 (ora legale Europa occidentale)
[debug] [2017-10-16T14:43:43.587Z] Error: unable to get local issuer certificate at Error (native) at TLSSocket.<anonymous>(_tls_wrap.js:1092:38) at emitNone (events.js:86:13) at TLSSocket.emit (events.js:185:7) at TLSSocket._finishInit (_tls_wrap.js:610:8) at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:440:38)
[error]
[error] Error: Server Error. unable to get local issuer certificate
I tried to use
npm config set cafile "<path-to-a-cert-extracted-from-cacert.pem>"
with no luck.
I really can't figure out what's going on and I couldn't find any solution on the web.
On StackOverflow there's a similar question but the answers seem to point to a different problem.
I would be glad to hear if someone has found a solution to this problem. Thanks.
Ok so basically after 2 days of research I finally came up with a (hack)solution by looking at Node.js documentation on TLS.
Setting the following environment variable does the trick:
set NODE_TLS_REJECT_UNAUTHORIZED=0
I personally don't like this solution but at least it makes me work.
Is this something that has to be fixed?
Or am I missing something on the configuration of npm behind a proxy?
Thanks.
When I try to install error messages, it fails to download. I get error messages like this:
[error] Server access Error: java.security.cert.CertificateException: No subject alternative DNS name matching repo.scala-sbt.org found. url=https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.typesafe.sbt/sbt-pgp/scala_2.10/sbt_0.13/0.8.3/ivys/ivy.xml
I can confirm, when accessing via my browser, that the certificate installed for the domain repo.scala-sbt.org is actually the certificate for repo.typesafe.com, and this seems to be the source of the error. It doesn't appear to be a DNS issue as http://repo.scala-sbt.org/ (insecure) works.
Please see https://github.com/sbt/sbt/issues/2125 for the workarounds. Specifically "http" should not be used.
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
Edit: This issue is now resolved. No workarounds should be required.
As a temporary workaround, add the file ~/.sbt/0.13/plugins/temp.sbt with the following contents:
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
You'll still see the error, but sbt will be able to find the dependency for which it is searching when accessing https://dl.bintray.com/sbt/sbt-plugin-releases directly (the place to which repo.scala-sbt.org presently redirects).
Upgrading nss package on CentOS worked for me.
sudo yum upgrade nss
I have come to a problem which I'm not exactly sure how to resolve.
Following the fabric8.io manual I have configured the maven plugin and placed every single configuration bit where it should be placed.
However once I execute the mvn fabric8:deploy I always get:
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:1.0.0.redhat-355:
deploy (default-cli) on project ag: Failed to retrieve remote metadata com.compa
ny.ag:ag:0.1-00.00.B01-SNAPSHOT/maven-metadata.xml: Could not transfer metadata
com.company.ag:ag:0.1-00.00.B01-SNAPSHOT/maven-metadata.xml from/to fabric8.uplo
ad.repo (http://127.0.0.1:8181/maven/upload/): Error transferring file: Server
returned HTTP response code: 503 for URL: http://127.0.0.1:8181/maven/upload/co
m/company/ag/ag/0.1-00.00.B01-SNAPSHOT/maven-metadata.xml -> [Help 1]
Any suggestion would be really helpful.
Thanks a lot,
Tiho
Maybe you are behind the proxy. Then try to add your computer litteral name to your maven settings.xml in nonProxyHosts section:
<proxies>
<proxy>
<username>proxy_user</username>
<password>proxy_pass</password>
<port>proxy_port</port>
<host>proxy_url</host>
<nonProxyHosts>localhost|127.0.0.1|YourComputerName</nonProxyHosts>
</proxy>