docker, maven start failed: Connection is still allocated - maven

i use a big project with maven + docker, all build war work fine , but i get a error when maven start last task:
[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.18.1:start > (start) on project mnm-docker: Execution start of goal io.fabric8:docker-maven-plugin:0.18.1:start failed: Connection is still allocated -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :mnm-docker
i can not find any in google search about start failed: Connection is still allocated
All port exposed are not used in my window 10
any have some idea?before reinstall window, all worked fine

resolved
ping localhost not resolve 127.0.0.1
i have changed the DOCKER_HOST with ip 127.0.0.1
set DOCKER_HOST=tcp://127.0.0.1:2375

Related

Build Failed in Azure devops

I'm beginner for this in azure devops.
I'm trying to build with maven, but I got the following error that I don't understand :
[ERROR] Failed to execute goal org.codehaus.mojo:cobertura-maven-plugin:2.7:instrument (package-9af52907-6506-4b87-b16a-9883edee41bc) on project gs-spring-boot: Execution package-9af52907-6506-4b87-b16a-9883edee41bc of goal org.codehaus.mojo:cobertura-maven-plugin:2.7:instrument failed: Plugin org.codehaus.mojo:cobertura-maven-plugin:2.7 or one of its dependencies could not be resolved: Could not find artifact com.sun:tools:jar:0 at specified path /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64/../lib/tools.jar -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
You are missing tools.jar in your JDK/JRE. Make sure your JDK version on Azure Pipeline. It seems Cobertura doesn't support Java 1.8 and later:
https://github.com/mojohaus/cobertura-maven-plugin/issues/30
https://github.com/mojohaus/cobertura-maven-plugin/issues/21
So, switch to JaCoCo.

Command execution failed on project org.wso2.carbon.apimgt.publisher.feature

Hi I got the below error while doing maven build for Carbon API management wso2 repo. I ran npm install already
[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.5.0:exec (npm install
(initialize)) on project org.wso2.carbon.apimgt.publisher.feature:
Command execution failed.: Cannot run program "C:\Program
Files\nodejs\npm" (in directory
"C:\projects\carbon-api\carbon-apimgt\features\apimgt\org.wso2.carbon.apimgt.publisher.feature\src\main\resources\publisher-new"):
CreateProcess error=193, %1 is not a valid Win32 application -> [Help
1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run
Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to
enable full debug logging. [ERROR] [ERROR] For more information about
the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] [ERROR] After correcting the problems, you can resume the
build with the command [ERROR] mvn -rf
:org.wso2.carbon.apimgt.publisher.feature
I ran node related commands separately and removed node commands from appropriate pom.xml. Now the build is success

sonar report failed while compiling build

The bamboo build is failed while compiling the sonar report even We added dependencies packages in pom.xml file. Might be this issue related to dependencies?
Bamboo goal command
-U clean test -Dtest.profile=integration
Bamboo error log
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project auth-server-admin-webapp: There are test failures.
[ERROR] Please refer to /datafiles/itdept/bamboo/xml-data/build-dir/ASA-ASA-IT/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Error Install CAS SERVER 4.0

when i build the folder cas 4.o from maven showme the follow error:
Failed to execute goal
com.mycila.maven-license-plugin:maven-license-plu gin:1.9.0:check
(default) on project cas-server-uber-webapp: Resource D:\Documen
ts\CAS_HOME/src/licensing/header.txt not found in file system,
classpath or URL: unknown protocol: d -> [Help 1] [ERROR] [ERROR] To
see the full stack trace of the errors, re-run Maven with the -e swit
ch. [ERROR] Re-run Maven using the -X switch to enable full debug
logging. [ERROR] [ERROR] For more information about the errors and
possible solutions, please rea d the following articles: [ERROR] [Help
1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
the solution that i found was open the pom.xml i find:
${cs.dir}/src/licensing/header.txt
You can replace whit:
${licenseHeader}
And rebuild whit comand: mvn clean install
mvn package install worked for me!!

Maven clean install unable to get artifact from maven central

After cloning the remote repo on to Linux remote machine, I am getting the following errors when trying to run mvn clean install:
[ERROR] The build could not read 1 project -> [Help 1] [ERROR]
[ERROR] Non-resolvable parent POM: Could not transfer artifact xxxxx
from/to central (http://repo.maven.apache.org/maven2): Connection to http://repo.maven.apache.org refused and 'parent.relativePath' points at wrong local POM # line 4, column 10: Connection timed out -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]
[ERROR] [Help 2]
These errors occur only when running mvn commands on Linux, the project builds successfully after mvn clean install on Windows environment...
Any ideas as to why this is happening on Linux machine?
Thanks
Connection to http://repo.maven.apache.org refused
The above message seems be due to network failure. As you say it builds successfully on windows and not on Linux, I envisage there must be some different network setting in your linux profile. Had you ever added any proxy? Check maven proxy setting and try again.

Resources