I'm following these instruction for setting up Apache Bigtop, to eventually support me running Oozie. I'm trying to use Bigtop because the Oozie website recommends the use of Bigtop if I want to run my Oozie install on Hadoop 2+.
After running the step
make hadoop-deb
I get the following error message (full message HERE):
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary: [INFO] [INFO] Apache Hadoop Main ................................ FAILURE [1:50.288s] [INFO] Apache Hadoop Project POM ......................... SKIPPED ... ... ...
...
...
...
...
...
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:55.412s
[INFO] Finished at: Mon Sep 15 14:14:17 PDT 2014
[INFO] Final Memory: 71M/434M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project hadoop-main: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.3:stage failed: A required class was missing while executing org.apache.maven.plugins:maven-site-plugin:3.3:stage: org/apache/commons/lang/StringUtils
Scouring the web, some people say this can be fixed by manually deleting your /.m2 repo and then rebuilding. I've tried this to no avail.
I'm using Ubuntu 14.04, fully updated, with Java openjdk7. The only different between what I did and the instructions was that I have Maven installed directly from apt-get, and thus I replaced the MAVEN_HOME location the instructions use with my own.
This info might also be helpful...
mherbst#Oozing:~/bigtop$ mvn -version
Apache Maven 3.0.5
Maven home: /usr/share/maven
Java version: 1.7.0_65, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-35-generic", arch: "amd64", family: "unix"
Any ideas what might be the issue? I realize I'm using a slightly newer version of Ubuntu than when the guide was written, but I don't think that's the problem. This seems to be some type of Java/Maven dependency issue.
Where are you getting your BigTop installation instructions? I don't remember running maven as part of the install.
BigTop doesn't work on Ubuntu 14.04. There's a problem with at least one dependency (fuse-utils). Try Ubuntu 12.02 LTS.
Related
When building my project using maven inside my newly setup CentOS 8 VM I get the following error when maven tries to download a dependecy from our internal nexus:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.120 s
[INFO] Finished at: 2020-03-25T17:43:34+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project myproject: Could not resolve dependencies for project our.domain:myproject:jar:1.5.0: Failed to collect dependencies at our.domain.internal:internal-commons:jar:0.12.3: Failed to read artifact descriptor for our.domain.internal:internal-commons:jar:0.12.3: Could not transfer artifact our.domain.internal:internal-commons:pom:0.12.3 from/to nexus-proxy (https://nexus.our.domain/repository/maven-public/): DH ServerKeyExchange does not comply to algorithm constraints -> [Help 1]
The problem also occurs when I try to read any webpage on that nexus:
[root#localhost Daisy]# curl https://nexus.our.domain
curl: (35) error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small
I tried to manually add the key to my known_hosts file using:
ssh-keyscan -p 443 nexus.our.domain >> ~/.ssh/known_hosts
But I returns without any console-output and no change to the file. Running
ssh-keyscan -p 443 nexus.our.domain
also produces no output at all.
I already reported the issue to the internal team that manages our nexus.
I would still appreciate any solution that forces my VM to accept the key of our nexus so I don't have to wait until the key is exchanged. I'm free to handle this in any level of my client (VM)-side (Maven, https, ssl or any lower level).
Versions used:
CentOS: CentOS Linux release 8.1.1911 (Core)
Maven:
[root#localhost Daisy]# mvn --version
Apache Maven 3.5.4 (Red Hat 3.5.4-5)
Maven home: /usr/share/maven
Java version: 11.0.5, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.5.10-2.el8_1.x86_64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.18.0-147.5.1.el8_1.x86_64", arch: "amd64", family: "unix"
SSH: OpenSSH_8.0p1, OpenSSL 1.1.1c FIPS 28 May 2019
Changing the first line in /etc/crypto-policies/back-ends/opensslcnf.config :
- CipherString = #SECLEVEL=2:kEECDH:kRSA:kEDH:kPSK:kDHEPSK:kECDHEPSK:-aDSS:-3DES:!DES:!RC4:!RC2:!IDEA:-SEED:!eNULL:!aNULL:!MD5:-SHA384:-CAMELLIA:-ARIA:-AESCCM8
+ CipherString = #SECLEVEL=1:kEECDH:kRSA:kEDH:kPSK:kDHEPSK:kECDHEPSK:-aDSS:-3DES:!DES:!RC4:!RC2:!IDEA:-SEED:!eNULL:!aNULL:!MD5:-SHA384:-CAMELLIA:-ARIA:-AESCCM8
(changing SECLEVEL=2 to SECLEVEL=1)
For the maven build to run I had to change the jvm-setting as well:
What does "Reason: DHPublicKey does not comply to algorithm constraints" mean?
Remember, this is only a workaround. The setting is a security-setting and should normally not be changed.
I receive error Dependency META-INF/lib/bcel-findbugs-6.0.jar can not be found in sonar-findbugs-plugin-3.0.jar during build on jenkins for all projects using sonarqube:
[INFO]
[INFO] --- sonar-maven-plugin:2.4:sonar (default-cli) # tig-parent ---
[INFO] SonarQube version: 4.4
INFO: Default locale: "en_US", source code encoding: "UTF-8"
INFO: Work directory: /opt/jenkins/workspace/TIG nightly sonar/target/sonar
INFO: SonarQube Server 4.4
[INFO] [16:54:50.855] Load global settings
[INFO] [16:54:51.042] User cache: /var/run/tomcat/jenkins-master-dev.mycompany.com_00/.sonar/cache
[INFO] [16:54:51.055] Install plugins
[ERROR] Dependency META-INF/lib/bcel-findbugs-6.0.jar can not be found in sonar-findbugs-plugin-3.0.jar`
I am not aware of any changes in project sonar configuration, jenkins or sonarqube server. I checked that sonar-findbugs-plugin-3.0.jar plugin contains bcel-findbugs-6.0.jar library. I reinstalled the findbugs plugin without effect.
. You mean that it did work before but it does not work anymore?
. When you say that you are not aware of any changes in configuration, you mean there has not been any upgrade of software?
. No modification in your environment (Java version, path, etc.)
The solution was to delete sonar cache: /var/run/tomcat/jenkins-master-dev.mycompany.com_00/.sonar/cache
This is my first time asking for help in a public forum.
So anyways Microsoft Windows has been my comfort zone as a development environment,recently I have been chucked into a linux environment at work, I seem to have got the hang of things, but when I tried to set up Maven2 I ran into some issues, I will get to the issue part later, but this is how I set up maven
Extracted maven to /usr/local/maven/apache-maven-2.2.1
Created a symbolic link to '/usr/bin' using following command
sudo ln -s /usr/local/maven/apache-maven-2.2.1 /usr/bin/mvn
when I mvn --version
Output :
Apache Maven 2.2.1 (r801777; 2009-08-07 00:46:01+0530) Java version:
1.7.0_25 Java home: /usr/local/java/jdk1.7.0_25/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version:
"2.6.32-24-generic" arch: "i386" Family: "unix"
but when I try to do
mvn clean
Output :
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [clean]
[INFO] ------------------------------------------------------------------------
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom
[WARNING] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2): Error transferring file: repo1.maven.org
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom
[WARNING] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2): Error transferring file: repo1.maven.org
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Maven is trying to download a plugin it needs to to do project cleanup from http://repo1.maven.org/. Do you need to use a proxy to connect to the internet? If so, see this guide: http://maven.apache.org/guides/mini/guide-proxies.html
If not, it might be that the network somewhere between your workstation and repo1.maven.org was having problems, which might be resolved now.
The answer by Ireeder(Thanks man :-) ) did the trick.
My computer was behind a proxy, so I needed to do the following to allow maven access the Internet
Steps to solve it
Open the M2_HOME/conf/settings.xml
Look for this line block in the settings.xml
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username>{username}</username>
<password> {password} </password>
<host>{host}</host>
<port>{port}</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
replace {value} with data relevant to you.
Enjoy!
The command I'm running is:
mvn -U -e versions:use-latest-versions -Dincludes=com.test.engines:engines -DgenerateBackupPoms=false -DallowMajorUpdates=false -DallowMinorUpdates=false -DallowSnapshots=false
I have, in my pom, a version such as 1.2.3-5-SNAPSHOT and I want to update it to the latest released version. This could be, for example, 1.2.3-7, or 1.2.3-5-SNAPSHOT may not have been released yet meaning the latest version is 1.2.3-4.
When running a maven command on my local Windows machine the versions plugin is working as I require it, however when running it on a remote Linux box (where I really need it to) it doesn't.
My local box shows:
When running a maven command on my local Windows machine the versions plugin is working as I require it, however when running it on a remote Linux box (where I really need it to) it doesn't.
[INFO] [versions:use-latest-versions {execution: default-cli}]
[INFO] Incremental version changes allowed
[INFO] Incremental version changes allowed
[INFO] artifact com.test.engines:engines: checking for updates from central
Props: {project.version=12.4.0-10-SNAPSHOT, project.parent.version=1.0.0, project.parent.groupId=com.test.pom, project.artifactId=edge-web, project.groupId=com.test.edge-web, project.parent.artifactId=pom}
[INFO] Updated com.test.engines:engines:jar:12.4.0-41-SNAPSHOT to version 12.4.0-40
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
Whereas the remote box shows:
[INFO] --- versions-maven-plugin:2.0:use-latest-versions (default-cli) # edge-web ---
[INFO] Incremental version changes allowed
[INFO] Incremental version changes allowed
[INFO] artifact com.test.engines:engines: checking for updates from nexus
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
When running:
mvn -Dplugin=versions help:describe
The output on both boxes shows the same version number:
Name: Versions Maven Plugin
Description: Versions Plugin for Maven 2. The Versions Plugin updates the
versions of components in the POM.
Group Id: org.codehaus.mojo
Artifact Id: versions-maven-plugin
Version: 2.0
Goal Prefix: versions
Does anyone know how I can get the same behavior as I do on my local machine? Or have any suggestions as to how I can investigate further?
I was using different versions of Maven. It seems even though the plugin version was the same I guess the method to resolve later versions in the core of maven must be different.
For reference the Mavan version can be checked using:
mvn --version
I also had to do similar to what is described here to allow me to run both Maven 2 and 3 from a single script.
I can't compile netty anymore. mvn compile gives the following:
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) # netty-common ---
[INFO] Compiling 60 source files to /home/dennis/git/netty4/common/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Unable to locate the Javac Compiler in:
/opt/java/jre1.6.0_30/../lib/tools.jar
Please ensure you are using JDK 1.4 or above and
not a JRE (the com.sun.tools.javac.Main class is required).
In most cases you can change the location of your Java
installation by setting the JAVA_HOME environment variable.
[INFO] 1 error
My configuration:
export JAVA_HOME=/opt/java/jre1.6.0_30
export M2_HOME=/opt/apache-maven-3.0.3
export M2=$M2_HOME/bin
export PATH=$JAVA_HOME/bin:$PATH
export PATH=$M2:$PATH
A part of my path:
$echo $PATH
/opt/java/jre1.6.0_30/bin:/opt/apache-maven-3.0.3/bin:/opt/git/bin:[...]
Maven status:
dennis#denpc:~/git/netty4$ mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /opt/apache-maven-3.0.3
Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
Java home: /opt/java/jre1.6.0_30
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "2.6.24-30-generic", arch: "i386", family: "unix"
Any ideas?
Please ensure you are using JDK 1.4 or above and
not a JRE [...]
It might have to do with this line in the error given in your post above. I believe you might want to make sure that you have the path to your JDK set, as well. Otherwise, it's just finding the JRE (jre1.6.0_30).
Note: The JDK might be found in your Java SDK folder.