I am getting below error at the time of maven build process. If anyone have idea how to resolve this, please let me know. Thanks.
Error:
[ERROR] Unresolveable build extension: Plugin com.vmware.o11n.mojo.pkg:maven-o11n-package- plugin:5.5.2 or one of its dependencies could not be resolved: Failed to collect dependencies for com.vmware.o11n.mojo.pkg:maven-o11n-package-plugin:jar:5.5.2 (): Failed to read artifact descriptor for org.slf4j:slf4j-api:jar:1.6.6: Could not transfer artifact org.slf4j:slf4j-parent:pom:1.6.6 from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused: Connection refused: connect -> [Help 2]
Seems com.vmware.o11n.mojo.pkg:maven-o11n-package-plugin:jar:5.5.2 not valid. You can try with Plug-in SDK. For more detail please refer questions Q1 , Q2 post on vmware community forum.
Related
I am working to connect UiPath studio to snowflake using OBDC DataSource (32bit). I have also installed snowflake driver (32-bit) for connecting purposes. But when after configuring connection, I ran the workflow, It gives the following Error.
ERROR [HY000] [Snowflake][Snowflake] (4)
REST request for URL https://https://oua63383.us-east-1.snowflakecomputing.com:443/session/v1/login-request?requestId=8b755ace-1691-4fb6-b4c9-bfe235e0e2c2&request_guid=4662159a-53ba-4f84-8451-9cb9a375a680
failed: CURLerror (curl_easy_perform() failed) - code=6 msg='Couldn't
resolve host name' osCode=9 osMsg='Bad file descriptor'.
Any help in this regard will be highly appreciated.
Thank you
You have https:// twice in your URL
Jenkins failed in running bower package with error
exit code of #128 fatal: unable to access
'https://github.com/metafizzy/fizzy-ui-utils.git/': Failed to connect
to github.com port 443: Timed out
It was working well before all the time. No package or version is changed but issue is replicating again & again. Server running jenkins is able to access "https://github.com/metafizzy/fizzy-ui-utils.git", no issue accessing site in https.
What is issue here?
Please help.
Turn out to be github changed something recently that broke this:
On February 22, 2018 19:00 UTC (11:00 am PST) GitHub discontinued
support for the cryptographically weak TLS 1.0 & 1.1 protocols and
only support connections with the TLS 1.2 protocol
See the GitHub Engineering blog post for more details about this change:
https://githubengineering.com/crypto-removal-notice/
Solution
Upgrading git client for windows on which jenkins build happens is the solution for the issue
I/we(the company) have a weird issue with Jenkins and the connection between Master and Slave.
After a while the connection is rejected/timed out for some reason.
We tried to start it as a Windows Service but that didn't go well(also error message). We try it again, maybe we didn't start it properly.
Below is the error Message(3) and the error from the Server(1) and slave(2)
How can we/I resolve this?
I read that this is still a bug in Jenkins but is there really no workaround?
1,2,3
I tried to connect slave to jenkins master through java web start but my efforts failed in the end.
I executed java -jar (jar file) (url) to connect and got the following errors.
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at java.net.Socket.connect(Socket.java:528)
at java.net.Socket.<init>(Socket.java:425)
at java.net.Socket.<init>(Socket.java:208)
at hudson.remoting.Engine.connect(Engine.java:321)
at hudson.remoting.Engine.run(Engine.java:210)
Please help. Both Master and Slave use Ubuntu Linux.
First of all, SO is not bug tracker for Jenkins project nor developers.
The Jenkins JIRA is located here: https://issues.jenkins-ci.org/secure/Dashboard.jspa
Secondly, in the wiki pages:
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service
https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds
contains pretty sufficient information that might guide you to fix. Probobly not permanent, but at least temporary.
For your comfort, here is the first link that fits the stack trace:
Check that the JNLP port is opened if you are using a firewall on your server. You can configure its value in Jenkins configuration. By default it is set to use a random port.
Cheers and good luck!
We have Jenkins 1.509.2 + Sonar 3.6.1. And receive the below error, We didn't have the same error with Sonar 3.4.1 from which we upgraded. Could you advise how can we fix the issue?
Exception in thread "main" org.sonar.runner.RunnerException: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
at org.sonar.runner.Runner.delegateExecution(Runner.java:288)
at org.sonar.runner.Runner.execute(Runner.java:151)
at org.sonar.runner.Main.execute(Main.java:84)
at org.sonar.runner.Main.main(Main.java:56)
Caused by: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:82)
at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:72)
at org.sonar.batch.bootstrap.BatchSettings.downloadSettings(BatchSettings.java:96)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
The error is not received every time - more like 90%. After I have upgraded all the Installed plugins, the error disappeared, on the next day - it appeared again.
It appears for ALL the projects, small and big. The Jenkins server is far (network wise) - from the Sonar server on most of the projects, but we also have projects that are in the same location with Sonar - and still receive this issue. Is there a workaround at least to increase the timeout?
We are seeing a similar error after upgrading from 3.4.1 to 3.6. The problem is not as severe as your (maybe 30% rather than 90%). Like your experience it is not limited to one project (errors in 2 out of every 7 builds). Restarting Sonar seems to help but does not always make it go away. Also, call me crazy but adding a -X flag to the maven build command has so far been the most reliable workaround. FYI, our builds are running on the same machine as the Sonar server (and the MySQL server).