You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Ascot Moss <as...@gmail.com> on 2016/07/26 11:41:28 UTC

Build Error

Hi,


Please help!
I am trying to build Ambari 2.2.2, got the following error as follows:

Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [04:51
min]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
4.361 s]

[INFO] Ambari Web ......................................... FAILURE [02:55
min]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
ambari-web: Command execution failed. Process exited with an error: 1 (Exit
value: 1) -> [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 <goals> -rf :ambari-web


Any ideas how to resolve it?

Regards

Re: Build Error

Posted by Don Bosco Durai <bo...@apache.org>.
Did you try my updated docker way? 

 

Get the latest script from the patch…

 

> I have updated the JIRA with the updated script. https://issues.apache.org/jira/browse/AMBARI-17944

> Please do the following: 

> 1. docker rmi ambari_dev

> 2. Go to root folder of your Ambari source

> 3. $YOUR_PATH/build_ambari_using_docker.sh

 

 Thanks

Bosco

 

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Monday, August 1, 2016 at 7:18 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

HI,

 

Still have compilation error:

sudo yum install -y python-setuptools

sudo pip install psutil

sudo npm install -g brunch@1.7.20

sudo pip install psutil

mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' 

[INFO] RPM build errors:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [  3.305 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.489 s]

[INFO] Ambari Web ......................................... SUCCESS [04:30 min]

[INFO] Ambari Views ....................................... SUCCESS [  1.530 s]

[INFO] Ambari Admin View .................................. SUCCESS [ 17.835 s]

[INFO] ambari-metrics ..................................... SUCCESS [  1.036 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [  1.104 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  1.936 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  1.398 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  0.990 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.385 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [01:41 min]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.501 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [ 15.498 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [04:55 min]

[INFO] Ambari Server ...................................... SUCCESS [33:51 min]

[INFO] Ambari Agent ....................................... SUCCESS [ 32.124 s]

[INFO] Ambari Client ...................................... SUCCESS [ 15.318 s]

[INFO] Ambari Python Client ............................... FAILURE [ 13.884 s]

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 46:49 min

[INFO] Finished at: 2016-08-01T16:32:25+08:00

[INFO] Final Memory: 325M/2743M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec' -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

        at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)

        at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)

        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

        ... 20 more

[ERROR]

[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 <goals> -rf :python-client

 

On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org> wrote:

I was able to reproduce your issue. It seems, the build user I am creating didn’t have the permission to write to the local folder. I have updated the script to create the build user with the same UID from the host user. I have also using CentOS 6 image to build (as per the documentation).

 

I have updated the JIRA with the updated script. https://issues.apache.org/jira/browse/AMBARI-17944

 

Please do the following:

 

1.       docker rmi ambari_dev

2.       Go to root folder of your Ambari source

3.       $YOUR_PATH/build_ambari_using_docker.sh

 

Let me know how it goes.

 

Thanks

 

Bosco

 

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Thursday, July 28, 2016 at 4:11 PM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi,

yum install -y python-setuptools

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

 * base: mirror.vpshosting.com.hk

 * epel: ftp.cuhk.edu.hk

 * extras: mirror.vpshosting.com.hk

 * updates: mirror.vpshosting.com.hk

Package python-setuptools-0.9.8-4.el7.noarch already installed and latest version

Nothing to do

 

 

"My script should have done the complete build. What is the error you are getting?"

The error as follows:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ FAILURE [  2.135 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 3.035 s

[INFO] Finished at: 2016-07-28T23:09:34+00:00

[INFO] Final Memory: 17M/479M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari: Could not create report parent directory /ambari/target -> [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

 

 

 

 

 

 

On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org> wrote:

> Step 1: run your script

> [INFO] Ambari Main ........................................ FAILURE [  0.521 s]

My script should have done the complete build. What is the error you are getting?

 

> Is "mvn clean install package -DskipTests"  correct command to build Ambari?

Depends what do you want to do? For released versions, Apache Ambari already gives you the final binary bits, including RPM. So shouldn’t be needing to build.

 

(From your very recent build)…

> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' –DskipTests

If you are compiling outside Docker, then try installing “yum install -y python-setuptools”. My script might not be able to take the space in the “python >= 2.6”. But if you want, I can look into it.

 

Thanks

 

Bosco

Re: Build Error

Posted by Don Bosco Durai <bo...@apache.org>.
Amanda, thanks for trying out. I got similar error when I was using an older AMI on AWS. After moving to the latest, it was solved. 

 

Seems this is more of a Docker host issue than the script. So it might not be worth debugging this. 

 

We can revisit this again if anyone else is interested.

 

Thanks

 

Bosco

 

 

 

 

From: Amanda Moran <am...@esgyn.com>
Reply-To: <us...@ambari.apache.org>
Date: Monday, August 8, 2016 at 10:56 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi there Bosco-

I tried this out on Centos 6.7. I did this to install docker:

Edit /etc/yum.repos.d/docker-main.repo :

[docker-main-repo]
name=Docker main Repository
baseurl=https://yum.dockerproject.org/repo/main/centos/$releasever
enabled=1
gpgcheck=1
gpgkey=https://yum.dockerproject.org/gpg

Install docker: yum install docker-engine
Start docker daemon: service docker start

 

I then followed your steps exactly. 

 

I got this error:

Step 8 : ADD https://www.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz.md5 /tools

Downloading [==================================================>]     32 B/32 B

stat /var/lib/docker/devicemapper/mnt/2ffd5d75bab0324b15b8410254a9677673489a01d5204f1db8b75ccab0c4206c/rootfs/tools/tmp: not a directory

+ docker run --rm -it -v /home/centos/ambari:/ambari -w /ambari -v /home/centos/.m2:/home/build/.m2 --user build ambari_dev mvn -B clean install package -DskipTests '-Dpython.ver=python\>=2.6' -Preplaceurl

Unable to find image 'ambari_dev:latest' locally

Pulling repository ambari_dev

Error: image library/ambari_dev:latest not found

 

 

I just wanted to test this out for you since I was curious. Don't worry about debugging this for my use especially if centos 6.7 isn't supported.

 

Thanks! 

 

Amanda 

 

 

On Sun, Aug 7, 2016 at 7:36 PM, Don Bosco Durai <bo...@apache.org> wrote:

Thanks for trying it out. It seems there is a permission issue when the mvn build from the Docker container is accessing your mounted file system. 

 

Can you try this?

 

Login as yourself (or build user)

cd $HOME

sudo rm -rf .m2/repository

tar xfz <ambari src tar file>

cd <ambari source folder> 

wget https://issues.apache.org/jira/secure/attachment/12822494/build_ambari_using_docker.sh

chmod a+x build_ambari_using_docker.sh

./build_ambari_using_docker.sh -build_image

or

sudo ./build_ambari_using_docker.sh -build_image

 

 

Can someone who has Docker, please try it out and let me know it works for you? I have tested the below steps in my Ubuntu host and a fresh AWS EC2 environment and it worked. 

1. If not docker is not installed, please install docker

2. sudo usermod -a -G docker $USER

3. Close terminal and open a new terminal

4. Make sure "id" has group "docker" in the list

5. cd $AMBARI_GIT_SRC_FOLDER or cd $HOME; git clone git://git.apache.org/ambari.git; cd ambari

5. git checkout trunk

6. git pull

7. wget https://issues.apache.org/jira/secure/attachment/12822494/build_ambari_using_docker.sh

8. chmod a+x build_ambari_using_docker.sh

9. ./build_ambari_using_docker.sh 

 

Please let me know your host OS…

 

Thanks

 

Bosco

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Sunday, August 7, 2016 at 6:35 AM


To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

and tried the following:


(run as root)

 

docker rmi ambari_dev   

/build_ambari_using_docker.sh   

[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 1274 licence.

[INFO] 

[INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ ambari ---

[INFO] Reading assembly descriptor: /ambari/ambari-project/src/main/assemblies/empty.xml

[INFO] 

[INFO] --- maven-install-plugin:2.4:install (default-install) @ ambari ---

[INFO] Installing /ambari/pom.xml to /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ FAILURE [  1.722 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 2.071 s

[INFO] Finished at: 2016-08-07T13:33:26+00:00

[INFO] Final Memory: 28M/702M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install) on project ambari: Failed to install artifact org.apache.ambari:ambari:pom:2.2.2.0.0: /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom (Permission denied) -> [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





as already run as root, not sure why still got 
 /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom (Permission denied) 

 

 

 

 

On Sun, Aug 7, 2016 at 9:22 PM, Ascot Moss <as...@gmail.com> wrote:

HI,

Tried again.

 

Added: 
echo $MAVEN_HOME

/opt/apache-maven-3.3.9

 

 

(command)

mvn -B -e clean install package -DskipTests=true

 

(log)

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:

npm WARN notsup Not compatible with your operating system or architecture: fsevents@0.2.1

npm WARN Ambari@2.1.3 No license field.

[INFO] 

[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---

/usr/lib/node_modules/brunch/lib/watch.js:433

            throw new Error("You probably need to execute `npm install` to install brunch plugins. " + error);

            ^

 

Error: You probably need to execute `npm install` to install brunch plugins. SyntaxError: Setter must have exactly one formal parameter.

  at /usr/lib/node_modules/brunch/lib/watch.js:433:19

  at Array.map (native)

  at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)

  at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)

  at /usr/lib/node_modules/brunch/lib/watch.js:458:19

  at /usr/lib/node_modules/brunch/lib/helpers.js:529:16

  at /usr/lib/node_modules/brunch/lib/helpers.js:485:14

  at /usr/lib/node_modules/brunch/node_modules/read-components/index.js:263:16

  at /usr/lib/node_modules/brunch/node_modules/read-components/index.js:72:14

  at FSReqWrap.cb [as oncomplete] (fs.js:257:19)

 

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [  2.577 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.036 s]

[INFO] Ambari Web ......................................... FAILURE [ 22.124 s]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 25.063 s

[INFO] Finished at: 2016-08-07T21:13:30+08:00

[INFO] Final Memory: 32M/991M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

[ERROR] 

[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 <goals> -rf :ambari-web

 

 

 

On Mon, Aug 1, 2016 at 11:21 PM, Amanda Moran <am...@esgyn.com> wrote:

Sorry if you already answered this. 

 

Is maven in your path? 

 

Thanks. 


On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:

HI,

 

Still have compilation error:

sudo yum install -y python-setuptools

sudo pip install psutil

sudo npm install -g brunch@1.7.20

sudo pip install psutil

mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' 

[INFO] RPM build errors:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [  3.305 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.489 s]

[INFO] Ambari Web ......................................... SUCCESS [04:30 min]

[INFO] Ambari Views ....................................... SUCCESS [  1.530 s]

[INFO] Ambari Admin View .................................. SUCCESS [ 17.835 s]

[INFO] ambari-metrics ..................................... SUCCESS [  1.036 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [  1.104 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  1.936 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  1.398 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  0.990 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.385 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [01:41 min]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.501 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [ 15.498 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [04:55 min]

[INFO] Ambari Server ...................................... SUCCESS [33:51 min]

[INFO] Ambari Agent ....................................... SUCCESS [ 32.124 s]

[INFO] Ambari Client ...................................... SUCCESS [ 15.318 s]

[INFO] Ambari Python Client ............................... FAILURE [ 13.884 s]

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 46:49 min

[INFO] Finished at: 2016-08-01T16:32:25+08:00

[INFO] Final Memory: 325M/2743M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec' -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

        at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)

        at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)

        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

        ... 20 more

[ERROR]

[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 <goals> -rf :python-client

 

On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org> wrote:

I was able to reproduce your issue. It seems, the build user I am creating didn’t have the permission to write to the local folder. I have updated the script to create the build user with the same UID from the host user. I have also using CentOS 6 image to build (as per the documentation).

 

I have updated the JIRA with the updated script. https://issues.apache.org/jira/browse/AMBARI-17944

 

Please do the following:

 

1.       docker rmi ambari_dev

2.       Go to root folder of your Ambari source

3.       $YOUR_PATH/build_ambari_using_docker.sh

 

Let me know how it goes.

 

Thanks

 

Bosco

 

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Thursday, July 28, 2016 at 4:11 PM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi,

yum install -y python-setuptools

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

 * base: mirror.vpshosting.com.hk

 * epel: ftp.cuhk.edu.hk

 * extras: mirror.vpshosting.com.hk

 * updates: mirror.vpshosting.com.hk

Package python-setuptools-0.9.8-4.el7.noarch already installed and latest version

Nothing to do

 

 

"My script should have done the complete build. What is the error you are getting?"

The error as follows:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ FAILURE [  2.135 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 3.035 s

[INFO] Finished at: 2016-07-28T23:09:34+00:00

[INFO] Final Memory: 17M/479M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari: Could not create report parent directory /ambari/target -> [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

 

 

 

 

 

 

On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org> wrote:

> Step 1: run your script

> [INFO] Ambari Main ........................................ FAILURE [  0.521 s]

My script should have done the complete build. What is the error you are getting?

 

> Is "mvn clean install package -DskipTests"  correct command to build Ambari?

Depends what do you want to do? For released versions, Apache Ambari already gives you the final binary bits, including RPM. So shouldn’t be needing to build.

 

(From your very recent build)…

> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' –DskipTests

If you are compiling outside Docker, then try installing “yum install -y python-setuptools”. My script might not be able to take the space in the “python >= 2.6”. But if you want, I can look into it.

 

Thanks

 

Bosco

 

 

 

 

 

 



 

-- 

Thanks, 

 

Amanda Moran

Re: Build Error

Posted by Amanda Moran <am...@esgyn.com>.
Hi there Bosco-

I tried this out on Centos 6.7. I did this to install docker:

Edit /etc/yum.repos.d/docker-main.repo :

[docker-main-repo]
name=Docker main Repository
baseurl=https://yum.dockerproject.org/repo/main/centos/$releasever
enabled=1
gpgcheck=1
gpgkey=https://yum.dockerproject.org/gpg

Install docker: yum install docker-engine
Start docker daemon: service docker start

I then followed your steps exactly.

I got this error:
Step 8 : ADD
https://www.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz.md5
/tools
Downloading [==================================================>]     32
B/32 B
stat
/var/lib/docker/devicemapper/mnt/2ffd5d75bab0324b15b8410254a9677673489a01d5204f1db8b75ccab0c4206c/rootfs/tools/tmp:
not a directory
+ docker run --rm -it -v /home/centos/ambari:/ambari -w /ambari -v
/home/centos/.m2:/home/build/.m2 --user build ambari_dev mvn -B clean
install package -DskipTests '-Dpython.ver=python\>=2.6' -Preplaceurl
Unable to find image 'ambari_dev:latest' locally
Pulling repository ambari_dev
Error: image library/ambari_dev:latest not found


I just wanted to test this out for you since I was curious. Don't worry
about debugging this for my use especially if centos 6.7 isn't supported.

Thanks!

Amanda


On Sun, Aug 7, 2016 at 7:36 PM, Don Bosco Durai <bo...@apache.org> wrote:

> Thanks for trying it out. It seems there is a permission issue when the
> mvn build from the Docker container is accessing your mounted file system.
>
>
>
> Can you try this?
>
>
>
> Login as yourself (or build user)
>
> cd $HOME
>
> sudo rm -rf .m2/repository
>
> tar xfz <ambari src tar file>
>
> cd <ambari source folder>
>
> wget https://issues.apache.org/jira/secure/attachment/
> 12822494/build_ambari_using_docker.sh
>
> chmod a+x build_ambari_using_docker.sh
>
> ./build_ambari_using_docker.sh -build_image
>
> or
>
> sudo ./build_ambari_using_docker.sh -build_image
>
>
>
>
>
> Can someone who has Docker, please try it out and let me know it works for
> you? I have tested the below steps in my Ubuntu host and a fresh AWS EC2
> environment and it worked.
>
> 1. If not docker is not installed, please install docker
>
> 2. sudo usermod -a -G docker $USER
>
> 3. Close terminal and open a new terminal
>
> 4. Make sure "id" has group "docker" in the list
>
> 5. cd $AMBARI_GIT_SRC_FOLDER or cd $HOME; git clone git://
> git.apache.org/ambari.git; cd ambari
>
> 5. git checkout trunk
>
> 6. git pull
>
> 7. wget https://issues.apache.org/jira/secure/attachment/
> 12822494/build_ambari_using_docker.sh
>
> 8. chmod a+x build_ambari_using_docker.sh
>
> 9. ./build_ambari_using_docker.sh
>
>
>
> Please let me know your host OS…
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Sunday, August 7, 2016 at 6:35 AM
>
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> and tried the following:
>
>
> (run as root)
>
>
>
> docker rmi ambari_dev
>
> /build_ambari_using_docker.sh
>
> [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
> approved: 1274 licence.
>
> [INFO]
>
> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @
> ambari ---
>
> [INFO] Reading assembly descriptor: /ambari/ambari-project/src/
> main/assemblies/empty.xml
>
> [INFO]
>
> [INFO] --- maven-install-plugin:2.4:install (default-install) @ ambari ---
>
> [INFO] Installing /ambari/pom.xml to /home/build/.m2/repository/
> org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ FAILURE [
> 1.722 s]
>
> [INFO] Apache Ambari Project POM .......................... SKIPPED
>
> [INFO] Ambari Web ......................................... SKIPPED
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Total time: 2.071 s
>
> [INFO] Finished at: 2016-08-07T13:33:26+00:00
>
> [INFO] Final Memory: 28M/702M
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-install-plugin:2.4:install (default-install) on project ambari:
> Failed to install artifact org.apache.ambari:ambari:pom:2.2.2.0.0:
> /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
> (Permission denied) -> [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
>
>
>
>
>
> as already run as root, not sure why still got
>  /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
> (Permission denied)
>
>
>
>
>
>
>
>
>
> On Sun, Aug 7, 2016 at 9:22 PM, Ascot Moss <as...@gmail.com> wrote:
>
> HI,
>
> Tried again.
>
>
>
> Added:
> echo $MAVEN_HOME
>
> /opt/apache-maven-3.3.9
>
>
>
>
>
> (command)
>
> mvn -B -e clean install package -DskipTests=true
>
>
>
> (log)
>
> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@0.2.1
>
> npm WARN Ambari@2.1.3 No license field.
>
> [INFO]
>
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>
> /usr/lib/node_modules/brunch/lib/watch.js:433
>
>             throw new Error("You probably need to execute `npm install` to
> install brunch plugins. " + error);
>
>             ^
>
>
>
> Error: You probably need to execute `npm install` to install brunch
> plugins. SyntaxError: Setter must have exactly one formal parameter.
>
>   at /usr/lib/node_modules/brunch/lib/watch.js:433:19
>
>   at Array.map (native)
>
>   at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)
>
>   at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)
>
>   at /usr/lib/node_modules/brunch/lib/watch.js:458:19
>
>   at /usr/lib/node_modules/brunch/lib/helpers.js:529:16
>
>   at /usr/lib/node_modules/brunch/lib/helpers.js:485:14
>
>   at /usr/lib/node_modules/brunch/node_modules/read-components/
> index.js:263:16
>
>   at /usr/lib/node_modules/brunch/node_modules/read-components/
> index.js:72:14
>
>   at FSReqWrap.cb [as oncomplete] (fs.js:257:19)
>
>
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 2.577 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.036 s]
>
> [INFO] Ambari Web ......................................... FAILURE [
> 22.124 s]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Total time: 25.063 s
>
> [INFO] Finished at: 2016-08-07T21:13:30+08:00
>
> [INFO] Final Memory: 32M/991M
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (compile-brunch) on project ambari-web: Command execution failed. Process
> exited with an error: 1 (Exit value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:212)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:153)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:145)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:116)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:80)
>
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.
> SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at org.apache.maven.lifecycle.internal.LifecycleStarter.
> execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:289)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:229)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:415)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
> DefaultBuildPluginManager.java:134)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at org.apache.commons.exec.DefaultExecutor.executeInternal(
> DefaultExecutor.java:377)
>
> at org.apache.commons.exec.DefaultExecutor.execute(
> DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
> [ERROR]
>
> [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 <goals> -rf :ambari-web
>
>
>
>
>
>
>
> On Mon, Aug 1, 2016 at 11:21 PM, Amanda Moran <am...@esgyn.com>
> wrote:
>
> Sorry if you already answered this.
>
>
>
> Is maven in your path?
>
>
>
> Thanks.
>
>
> On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:
>
> HI,
>
>
>
> Still have compilation error:
>
> sudo yum install -y python-setuptools
>
> sudo pip install psutil
>
> *sudo npm install -g brunch@1.7.20*
>
> *sudo pip install psutil*
>
> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
> >= 2.6' *
>
> [INFO] RPM build errors:
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 3.305 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.489 s]
>
> [INFO] Ambari Web ......................................... SUCCESS
> [04:30 min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 1.530 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [
> 17.835 s]
>
> [INFO] ambari-metrics ..................................... SUCCESS [
> 1.036 s]
>
> [INFO] Ambari Metrics Common .............................. SUCCESS [
> 1.104 s]
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
> 1.936 s]
>
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
> 1.398 s]
>
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
> 0.990 s]
>
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
> 2.385 s]
>
> [INFO] Ambari Metrics Collector ........................... SUCCESS [01:41
> min]
>
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
> 1.501 s]
>
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
> 15.498 s]
>
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [04:55
> min]
>
> [INFO] Ambari Server ...................................... SUCCESS
> [33:51 min]
>
> [INFO] Ambari Agent ....................................... SUCCESS [
> 32.124 s]
>
> [INFO] Ambari Client ...................................... SUCCESS [
> 15.318 s]
>
> [INFO] Ambari Python Client ............................... FAILURE [
> 13.884 s]
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Total time: 46:49 min
>
> [INFO] Finished at: 2016-08-01T16:32:25+08:00
>
> [INFO] Final Memory: 325M/2743M
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
> (default-cli) on project python-client: RPM build execution returned: '1'
> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.
> 2-src/ambari-client/python-client/target/rpm/python-client/SPECS &&
> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.
> 2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client' --target x86_64-redhat-linux
> python-client.spec' -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
> project python-client: RPM build execution returned: '1' executing '/bin/sh
> -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/buildroot --define '_topdir
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client' --target x86_64-redhat-linux
> python-client.spec'
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:212)
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:153)
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:145)
>
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:116)
>
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:80)
>
>         at org.apache.maven.lifecycle.internal.builder.singlethreaded.
> SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
>         at org.apache.maven.lifecycle.internal.LifecycleStarter.
> execute(LifecycleStarter.java:128)
>
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
>
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
>
>         at java.lang.reflect.Method.invoke(Method.java:498)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:289)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:229)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:415)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
> execution returned: '1' executing '/bin/sh -c cd
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/buildroot --define '_topdir
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client' --target x86_64-redhat-linux
> python-client.spec'
>
>         at org.codehaus.mojo.rpm.RPMHelper.buildPackage(
> RPMHelper.java:150)
>
>         at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(
> AbstractRPMMojo.java:792)
>
>         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
> DefaultBuildPluginManager.java:134)
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:207)
>
>         ... 20 more
>
> [ERROR]
>
> [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 <goals> -rf :python-client
>
>
>
> On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org> wrote:
>
> I was able to reproduce your issue. It seems, the build user I am creating
> didn’t have the permission to write to the local folder. I have updated the
> script to create the build user with the same UID from the host user. I
> have also using CentOS 6 image to build (as per the documentation).
>
>
>
> I have updated the JIRA with the updated script.
> https://issues.apache.org/jira/browse/AMBARI-17944
>
>
>
> Please do the following:
>
>
>
> 1.       docker rmi ambari_dev
>
> 2.       Go to root folder of your Ambari source
>
> 3.       $YOUR_PATH/build_ambari_using_docker.sh
>
>
>
> Let me know how it goes.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Thursday, July 28, 2016 at 4:11 PM
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> Hi,
>
> yum install -y python-setuptools
>
> Loaded plugins: fastestmirror
>
> Loading mirror speeds from cached hostfile
>
>  * base: mirror.vpshosting.com.hk
>
>  * epel: ftp.cuhk.edu.hk
>
>  * extras: mirror.vpshosting.com.hk
>
>  * updates: mirror.vpshosting.com.hk
>
> Package python-setuptools-0.9.8-4.el7.noarch already installed and latest
> version
>
> Nothing to do
>
>
>
>
>
> "My script should have done the complete build. What is the error you are
> getting?"
>
> The error as follows:
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ FAILURE [
> 2.135 s]
>
> [INFO] Apache Ambari Project POM .......................... SKIPPED
>
> [INFO] Ambari Web ......................................... SKIPPED
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Total time: 3.035 s
>
> [INFO] Finished at: 2016-07-28T23:09:34+00:00
>
> [INFO] Final Memory: 17M/479M
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (default) on project ambari: Could not create report parent directory
> /ambari/target -> [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
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org>
> wrote:
>
> > Step 1: run your script
>
> > [INFO] Ambari Main ........................................ FAILURE [
> 0.521 s]
>
> My script should have done the complete build. What is the error you are
> getting?
>
>
>
> > Is "mvn clean install package -DskipTests"  correct command to build
> Ambari?
>
> Depends what do you want to do? For released versions, Apache Ambari
> already gives you the final binary bits, including RPM. So shouldn’t be
> needing to build.
>
>
>
> (From your very recent build)…
>
> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm
> -Dpython.ver='python >= 2.6' –DskipTests
>
> If you are compiling outside Docker, then try installing “yum install -y
> python-setuptools”. My script might not be able to take the space in the
> “python >= 2.6”. But if you want, I can look into it.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
>
>
>
>
>
>
>
>



-- 
Thanks,

Amanda Moran

Re: Build Error

Posted by Don Bosco Durai <bo...@apache.org>.
Thanks for trying it out. It seems there is a permission issue when the mvn build from the Docker container is accessing your mounted file system. 

 

Can you try this?

 

Login as yourself (or build user)

cd $HOME

sudo rm -rf .m2/repository

tar xfz <ambari src tar file>

cd <ambari source folder> 

wget https://issues.apache.org/jira/secure/attachment/12822494/build_ambari_using_docker.sh

chmod a+x build_ambari_using_docker.sh

./build_ambari_using_docker.sh -build_image

or

sudo ./build_ambari_using_docker.sh -build_image

 

 

Can someone who has Docker, please try it out and let me know it works for you? I have tested the below steps in my Ubuntu host and a fresh AWS EC2 environment and it worked. 

1. If not docker is not installed, please install docker

2. sudo usermod -a -G docker $USER

3. Close terminal and open a new terminal

4. Make sure "id" has group "docker" in the list

5. cd $AMBARI_GIT_SRC_FOLDER or cd $HOME; git clone git://git.apache.org/ambari.git; cd ambari

5. git checkout trunk

6. git pull

7. wget https://issues.apache.org/jira/secure/attachment/12822494/build_ambari_using_docker.sh

8. chmod a+x build_ambari_using_docker.sh

9. ./build_ambari_using_docker.sh 

 

Please let me know your host OS…

 

Thanks

 

Bosco

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Sunday, August 7, 2016 at 6:35 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

and tried the following:


(run as root)

 

docker rmi ambari_dev   

/build_ambari_using_docker.sh   


[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 1274 licence.

[INFO] 

[INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ ambari ---

[INFO] Reading assembly descriptor: /ambari/ambari-project/src/main/assemblies/empty.xml

[INFO] 

[INFO] --- maven-install-plugin:2.4:install (default-install) @ ambari ---

[INFO] Installing /ambari/pom.xml to /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ FAILURE [  1.722 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 2.071 s

[INFO] Finished at: 2016-08-07T13:33:26+00:00

[INFO] Final Memory: 28M/702M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install) on project ambari: Failed to install artifact org.apache.ambari:ambari:pom:2.2.2.0.0: /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom (Permission denied) -> [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





as already run as root, not sure why still got 
 /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom (Permission denied) 

 

 

 

 

On Sun, Aug 7, 2016 at 9:22 PM, Ascot Moss <as...@gmail.com> wrote:

HI,

Tried again.

 

Added: 
echo $MAVEN_HOME

/opt/apache-maven-3.3.9

 

 

(command)

mvn -B -e clean install package -DskipTests=true

 

(log)

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:

npm WARN notsup Not compatible with your operating system or architecture: fsevents@0.2.1

npm WARN Ambari@2.1.3 No license field.

[INFO] 

[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---

/usr/lib/node_modules/brunch/lib/watch.js:433

            throw new Error("You probably need to execute `npm install` to install brunch plugins. " + error);

            ^

 

Error: You probably need to execute `npm install` to install brunch plugins. SyntaxError: Setter must have exactly one formal parameter.

  at /usr/lib/node_modules/brunch/lib/watch.js:433:19

  at Array.map (native)

  at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)

  at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)

  at /usr/lib/node_modules/brunch/lib/watch.js:458:19

  at /usr/lib/node_modules/brunch/lib/helpers.js:529:16

  at /usr/lib/node_modules/brunch/lib/helpers.js:485:14

  at /usr/lib/node_modules/brunch/node_modules/read-components/index.js:263:16

  at /usr/lib/node_modules/brunch/node_modules/read-components/index.js:72:14

  at FSReqWrap.cb [as oncomplete] (fs.js:257:19)

 

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [  2.577 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.036 s]

[INFO] Ambari Web ......................................... FAILURE [ 22.124 s]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 25.063 s

[INFO] Finished at: 2016-08-07T21:13:30+08:00

[INFO] Final Memory: 32M/991M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

[ERROR] 

[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 <goals> -rf :ambari-web

 

 

 

On Mon, Aug 1, 2016 at 11:21 PM, Amanda Moran <am...@esgyn.com> wrote:

Sorry if you already answered this. 

 

Is maven in your path? 

 

Thanks. 


On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:

HI,

 

Still have compilation error:

sudo yum install -y python-setuptools

sudo pip install psutil

sudo npm install -g brunch@1.7.20

sudo pip install psutil

mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' 

[INFO] RPM build errors:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [  3.305 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.489 s]

[INFO] Ambari Web ......................................... SUCCESS [04:30 min]

[INFO] Ambari Views ....................................... SUCCESS [  1.530 s]

[INFO] Ambari Admin View .................................. SUCCESS [ 17.835 s]

[INFO] ambari-metrics ..................................... SUCCESS [  1.036 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [  1.104 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  1.936 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  1.398 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  0.990 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.385 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [01:41 min]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.501 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [ 15.498 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [04:55 min]

[INFO] Ambari Server ...................................... SUCCESS [33:51 min]

[INFO] Ambari Agent ....................................... SUCCESS [ 32.124 s]

[INFO] Ambari Client ...................................... SUCCESS [ 15.318 s]

[INFO] Ambari Python Client ............................... FAILURE [ 13.884 s]

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 46:49 min

[INFO] Finished at: 2016-08-01T16:32:25+08:00

[INFO] Final Memory: 325M/2743M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec' -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

        at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)

        at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)

        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

        ... 20 more

[ERROR]

[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 <goals> -rf :python-client

 

On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org> wrote:

I was able to reproduce your issue. It seems, the build user I am creating didn’t have the permission to write to the local folder. I have updated the script to create the build user with the same UID from the host user. I have also using CentOS 6 image to build (as per the documentation).

 

I have updated the JIRA with the updated script. https://issues.apache.org/jira/browse/AMBARI-17944

 

Please do the following:

 

1.       docker rmi ambari_dev

2.       Go to root folder of your Ambari source

3.       $YOUR_PATH/build_ambari_using_docker.sh

 

Let me know how it goes.

 

Thanks

 

Bosco

 

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Thursday, July 28, 2016 at 4:11 PM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi,

yum install -y python-setuptools

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

 * base: mirror.vpshosting.com.hk

 * epel: ftp.cuhk.edu.hk

 * extras: mirror.vpshosting.com.hk

 * updates: mirror.vpshosting.com.hk

Package python-setuptools-0.9.8-4.el7.noarch already installed and latest version

Nothing to do

 

 

"My script should have done the complete build. What is the error you are getting?"

The error as follows:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ FAILURE [  2.135 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 3.035 s

[INFO] Finished at: 2016-07-28T23:09:34+00:00

[INFO] Final Memory: 17M/479M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari: Could not create report parent directory /ambari/target -> [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

 

 

 

 

 

 

On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org> wrote:

> Step 1: run your script

> [INFO] Ambari Main ........................................ FAILURE [  0.521 s]

My script should have done the complete build. What is the error you are getting?

 

> Is "mvn clean install package -DskipTests"  correct command to build Ambari?

Depends what do you want to do? For released versions, Apache Ambari already gives you the final binary bits, including RPM. So shouldn’t be needing to build.

 

(From your very recent build)…

> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' –DskipTests

If you are compiling outside Docker, then try installing “yum install -y python-setuptools”. My script might not be able to take the space in the “python >= 2.6”. But if you want, I can look into it.

 

Thanks

 

Bosco

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:

npm WARN notsup Not compatible with your operating system or architecture:
fsevents@0.2.1

npm WARN Ambari@2.1.3 No license field.

[INFO]

[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---

/usr/lib/node_modules/brunch/lib/watch.js:433

            throw new Error("You probably need to execute `npm install` to
install brunch plugins. " + error);

            ^


Error: You probably need to execute `npm install` to install brunch
plugins. SyntaxError: Setter must have exactly one formal parameter.

  at /usr/lib/node_modules/brunch/lib/watch.js:433:19

  at Array.map (native)

  at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)

  at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)

  at /usr/lib/node_modules/brunch/lib/watch.js:458:19

  at /usr/lib/node_modules/brunch/lib/helpers.js:529:16

  at /usr/lib/node_modules/brunch/lib/helpers.js:485:14

  at
/usr/lib/node_modules/brunch/node_modules/read-components/index.js:263:16

  at
/usr/lib/node_modules/brunch/node_modules/read-components/index.js:72:14

  at FSReqWrap.cb [as oncomplete] (fs.js:257:19)


[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [11:52
min]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.057 s]

[INFO] Ambari Web ......................................... FAILURE [03:16
min]

[INFO] Ambari Views ....................................... SKIPPED

On Sun, Aug 7, 2016 at 10:10 PM, Ascot Moss <as...@gmail.com> wrote:

> from  "ambari-web/npm-debug.log", found the following
>
>
> 50491 silly gunzTarPerm extractEntry index.js
>
> 50492 error Error: ENOENT, lstat '/home/ambari/tmp/npm-20999-
> fPHBBMwA/1470578512826-0.6402329006232321/package/.npmignore'
>
> 50493 error If you need help, you may report this log at:
>
> 50493 error     <http://github.com/isaacs/npm/issues>
>
> 50493 error or email it to:
>
> 50493 error     <np...@googlegroups.com>
>
> 50494 error System Linux 3.10.0-327.22.2.el7.x86_64
>
> 50495 error command "node" "/bin/npm" "install"
>
> 50496 error cwd /user/local/apache-ambari-2.2.2-src/ambari-web
>
> 50497 error node -v v0.10.42
>
> 50498 error npm -v 1.3.6
>
> 50499 error path /home/ambari/tmp/npm-20999-fPHBBMwA/1470578512826-0.
> 6402329006232321/package/.npmignore
>
> 50500 error fstream_path /home/ambari/tmp/npm-20999-
> fPHBBMwA/1470578512826-0.6402329006232321/package/.npmignore
>
> 50501 error fstream_type File
>
> 50502 error fstream_class FileWriter
>
> 50503 error code ENOENT
>
> 50504 error errno 34
>
> 50505 error fstream_stack /usr/lib/node_modules/fstream/
> lib/writer.js:284:26
>
> 50505 error fstream_stack Object.oncomplete (fs.js:108:15)
>
> 50506 verbose exit [ 34, true ]
>
>
>
> On Sun, Aug 7, 2016 at 9:35 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> and tried the following:
>>
>> (run as root)
>>
>> docker rmi ambari_dev
>>
>> /build_ambari_using_docker.sh
>>
>>
>> [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
>> approved: 1274 licence.
>>
>> [INFO]
>>
>> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @
>> ambari ---
>>
>> [INFO] Reading assembly descriptor: /ambari/ambari-project/src/mai
>> n/assemblies/empty.xml
>>
>> [INFO]
>>
>> [INFO] --- maven-install-plugin:2.4:install (default-install) @ ambari
>> ---
>>
>> [INFO] Installing /ambari/pom.xml to /home/build/.m2/repository/org
>> /apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ FAILURE [
>> 1.722 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SKIPPED
>>
>> [INFO] Ambari Web ......................................... SKIPPED
>>
>> [INFO] Ambari Views ....................................... SKIPPED
>>
>> [INFO] Ambari Admin View .................................. SKIPPED
>>
>> [INFO] ambari-metrics ..................................... SKIPPED
>>
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>
>> [INFO] Ambari Server ...................................... SKIPPED
>>
>> [INFO] Ambari Agent ....................................... SKIPPED
>>
>> [INFO] Ambari Client ...................................... SKIPPED
>>
>> [INFO] Ambari Python Client ............................... SKIPPED
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Total time: 2.071 s
>>
>> [INFO] Finished at: 2016-08-07T13:33:26+00:00
>>
>> [INFO] Final Memory: 28M/702M
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4:install
>> (default-install) on project ambari: Failed to install artifact
>> org.apache.ambari:ambari:pom:2.2.2.0.0: /home/build/.m2/repository/org
>> /apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom (Permission denied)
>> -> [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/conflu
>> ence/display/MAVEN/MojoExecutionException
>>
>>
>>
>>
>>
>> as already run as root, not sure why still got
>>  /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
>> (Permission denied)
>>
>>
>>
>>
>>
>> On Sun, Aug 7, 2016 at 9:22 PM, Ascot Moss <as...@gmail.com> wrote:
>>
>>> HI,
>>>
>>> Tried again.
>>>
>>>
>>> Added:
>>> echo $MAVEN_HOME
>>>
>>> /opt/apache-maven-3.3.9
>>>
>>>
>>>
>>> (command)
>>>
>>> mvn -B -e clean install package -DskipTests=true
>>>
>>>
>>> (log)
>>>
>>> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>>>
>>> npm WARN notsup Not compatible with your operating system or
>>> architecture: fsevents@0.2.1
>>>
>>> npm WARN Ambari@2.1.3 No license field.
>>>
>>> [INFO]
>>>
>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>>>
>>> /usr/lib/node_modules/brunch/lib/watch.js:433
>>>
>>>             throw new Error("You probably need to execute `npm install`
>>> to install brunch plugins. " + error);
>>>
>>>             ^
>>>
>>>
>>> Error: You probably need to execute `npm install` to install brunch
>>> plugins. SyntaxError: Setter must have exactly one formal parameter.
>>>
>>>   at /usr/lib/node_modules/brunch/lib/watch.js:433:19
>>>
>>>   at Array.map (native)
>>>
>>>   at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)
>>>
>>>   at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)
>>>
>>>   at /usr/lib/node_modules/brunch/lib/watch.js:458:19
>>>
>>>   at /usr/lib/node_modules/brunch/lib/helpers.js:529:16
>>>
>>>   at /usr/lib/node_modules/brunch/lib/helpers.js:485:14
>>>
>>>   at /usr/lib/node_modules/brunch/node_modules/read-components/in
>>> dex.js:263:16
>>>
>>>   at /usr/lib/node_modules/brunch/node_modules/read-components/in
>>> dex.js:72:14
>>>
>>>   at FSReqWrap.cb [as oncomplete] (fs.js:257:19)
>>>
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] Reactor Summary:
>>>
>>> [INFO]
>>>
>>> [INFO] Ambari Main ........................................ SUCCESS [
>>> 2.577 s]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>> 0.036 s]
>>>
>>> [INFO] Ambari Web ......................................... FAILURE [
>>> 22.124 s]
>>>
>>> [INFO] Ambari Views ....................................... SKIPPED
>>>
>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>
>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>
>>> [INFO] Ambari Server ...................................... SKIPPED
>>>
>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>
>>> [INFO] Ambari Client ...................................... SKIPPED
>>>
>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>
>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>
>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] Total time: 25.063 s
>>>
>>> [INFO] Finished at: 2016-08-07T21:13:30+08:00
>>>
>>> [INFO] Final Memory: 32M/991M
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:212)
>>>
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:153)
>>>
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:145)
>>>
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>>> uildProject(LifecycleModuleBuilder.java:116)
>>>
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>>> uildProject(LifecycleModuleBuilder.java:80)
>>>
>>> at org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>>> ingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>>> (LifecycleStarter.java:128)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>>
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>>
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnha
>>> nced(Launcher.java:289)
>>>
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Lau
>>> ncher.java:229)
>>>
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>>> itCode(Launcher.java:415)
>>>
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launc
>>> her.java:356)
>>>
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>> execution failed.
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>
>>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>>> o(DefaultBuildPluginManager.java:134)
>>>
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:207)
>>>
>>> ... 20 more
>>>
>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>> with an error: 1 (Exit value: 1)
>>>
>>> at org.apache.commons.exec.DefaultExecutor.executeInternal(Defa
>>> ultExecutor.java:377)
>>>
>>> at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecu
>>> tor.java:160)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>
>>> ... 22 more
>>>
>>> [ERROR]
>>>
>>> [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/conflu
>>> ence/display/MAVEN/MojoExecutionException
>>>
>>> [ERROR]
>>>
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>>
>>> [ERROR]   mvn <goals> -rf :ambari-web
>>>
>>>
>>>
>>>
>>> On Mon, Aug 1, 2016 at 11:21 PM, Amanda Moran <am...@esgyn.com>
>>> wrote:
>>>
>>>> Sorry if you already answered this.
>>>>
>>>> Is maven in your path?
>>>>
>>>> Thanks.
>>>>
>>>> On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:
>>>>
>>>> HI,
>>>>
>>>> Still have compilation error:
>>>>
>>>> sudo yum install -y python-setuptools
>>>>
>>>> sudo pip install psutil
>>>>
>>>> *sudo npm install -g brunch@1.7.20*
>>>>
>>>> *sudo pip install psutil*
>>>>
>>>> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>>>> -Dpython.ver='python >= 2.6' *
>>>>
>>>> [INFO] RPM build errors:
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [INFO] Reactor Summary:
>>>>
>>>> [INFO]
>>>>
>>>> [INFO] Ambari Main ........................................ SUCCESS [
>>>> 3.305 s]
>>>>
>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>>> 0.489 s]
>>>>
>>>> [INFO] Ambari Web ......................................... SUCCESS
>>>> [04:30 min]
>>>>
>>>> [INFO] Ambari Views ....................................... SUCCESS [
>>>> 1.530 s]
>>>>
>>>> [INFO] Ambari Admin View .................................. SUCCESS [
>>>> 17.835 s]
>>>>
>>>> [INFO] ambari-metrics ..................................... SUCCESS [
>>>> 1.036 s]
>>>>
>>>> [INFO] Ambari Metrics Common .............................. SUCCESS [
>>>> 1.104 s]
>>>>
>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
>>>> 1.936 s]
>>>>
>>>> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
>>>> 1.398 s]
>>>>
>>>> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
>>>> 0.990 s]
>>>>
>>>> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
>>>> 2.385 s]
>>>>
>>>> [INFO] Ambari Metrics Collector ........................... SUCCESS
>>>> [01:41 min]
>>>>
>>>> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
>>>> 1.501 s]
>>>>
>>>> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
>>>> 15.498 s]
>>>>
>>>> [INFO] Ambari Metrics Assembly ............................ SUCCESS
>>>> [04:55 min]
>>>>
>>>> [INFO] Ambari Server ...................................... SUCCESS
>>>> [33:51 min]
>>>>
>>>> [INFO] Ambari Agent ....................................... SUCCESS [
>>>> 32.124 s]
>>>>
>>>> [INFO] Ambari Client ...................................... SUCCESS [
>>>> 15.318 s]
>>>>
>>>> [INFO] Ambari Python Client ............................... FAILURE [
>>>> 13.884 s]
>>>>
>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [INFO] BUILD FAILURE
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [INFO] Total time: 46:49 min
>>>>
>>>> [INFO] Finished at: 2016-08-01T16:32:25+08:00
>>>>
>>>> [INFO] Final Memory: 325M/2743M
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
>>>> (default-cli) on project python-client: RPM build execution returned: '1'
>>>> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2
>>>> -src/ambari-client/python-client/target/rpm/python-client/SPECS &&
>>>> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2
>>>> -src/ambari-client/python-client/target/rpm/python-client/buildroot
>>>> --define '_topdir /usr/local/apache-ambari-2.2.2
>>>> -src/ambari-client/python-client/target/rpm/python-client' --target
>>>> x86_64-redhat-linux python-client.spec' -> [Help 1]
>>>>
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
>>>> (default-cli) on project python-client: RPM build execution returned: '1'
>>>> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2
>>>> -src/ambari-client/python-client/target/rpm/python-client/SPECS &&
>>>> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2
>>>> -src/ambari-client/python-client/target/rpm/python-client/buildroot
>>>> --define '_topdir /usr/local/apache-ambari-2.2.2
>>>> -src/ambari-client/python-client/target/rpm/python-client' --target
>>>> x86_64-redhat-linux python-client.spec'
>>>>
>>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>>> oExecutor.java:212)
>>>>
>>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>>> oExecutor.java:153)
>>>>
>>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>>> oExecutor.java:145)
>>>>
>>>>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>>>> uildProject(LifecycleModuleBuilder.java:116)
>>>>
>>>>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>>>> uildProject(LifecycleModuleBuilder.java:80)
>>>>
>>>>         at org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>>>> ingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>
>>>>         at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>>>> (LifecycleStarter.java:128)
>>>>
>>>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:30
>>>> 7)
>>>>
>>>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:19
>>>> 3)
>>>>
>>>>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>
>>>>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>
>>>>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>
>>>>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>
>>>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>
>>>>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>>> ssorImpl.java:62)
>>>>
>>>>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>>> thodAccessorImpl.java:43)
>>>>
>>>>         at java.lang.reflect.Method.invoke(Method.java:498)
>>>>
>>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnha
>>>> nced(Launcher.java:289)
>>>>
>>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Lau
>>>> ncher.java:229)
>>>>
>>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>>>> itCode(Launcher.java:415)
>>>>
>>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launc
>>>> her.java:356)
>>>>
>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
>>>> execution returned: '1' executing '/bin/sh -c cd
>>>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-clie
>>>> nt/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot
>>>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-clie
>>>> nt/target/rpm/python-client/buildroot --define '_topdir
>>>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
>>>> --target x86_64-redhat-linux python-client.spec'
>>>>
>>>>         at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:
>>>> 150)
>>>>
>>>>         at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMoj
>>>> o.java:792)
>>>>
>>>>         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>>>> o(DefaultBuildPluginManager.java:134)
>>>>
>>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>>> oExecutor.java:207)
>>>>
>>>>         ... 20 more
>>>>
>>>> [ERROR]
>>>>
>>>> [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/conflu
>>>> ence/display/MAVEN/MojoExecutionException
>>>>
>>>> [ERROR]
>>>>
>>>> [ERROR] After correcting the problems, you can resume the build with
>>>> the command
>>>>
>>>> [ERROR]   mvn <goals> -rf :python-client
>>>>
>>>> On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org>
>>>> wrote:
>>>>
>>>>> I was able to reproduce your issue. It seems, the build user I am
>>>>> creating didn’t have the permission to write to the local folder. I have
>>>>> updated the script to create the build user with the same UID from the host
>>>>> user. I have also using CentOS 6 image to build (as per the documentation).
>>>>>
>>>>>
>>>>>
>>>>> I have updated the JIRA with the updated script.
>>>>> https://issues.apache.org/jira/browse/AMBARI-17944
>>>>>
>>>>>
>>>>>
>>>>> Please do the following:
>>>>>
>>>>>
>>>>>
>>>>> 1.       docker rmi ambari_dev
>>>>>
>>>>> 2.       Go to root folder of your Ambari source
>>>>>
>>>>> 3.       $YOUR_PATH/build_ambari_using_docker.sh
>>>>>
>>>>>
>>>>>
>>>>> Let me know how it goes.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Bosco
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>> *Date: *Thursday, July 28, 2016 at 4:11 PM
>>>>> *To: *<us...@ambari.apache.org>
>>>>> *Subject: *Re: Build Error
>>>>>
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> yum install -y python-setuptools
>>>>>
>>>>> Loaded plugins: fastestmirror
>>>>>
>>>>> Loading mirror speeds from cached hostfile
>>>>>
>>>>>  * base: mirror.vpshosting.com.hk
>>>>>
>>>>>  * epel: ftp.cuhk.edu.hk
>>>>>
>>>>>  * extras: mirror.vpshosting.com.hk
>>>>>
>>>>>  * updates: mirror.vpshosting.com.hk
>>>>>
>>>>> Package python-setuptools-0.9.8-4.el7.noarch already installed and
>>>>> latest version
>>>>>
>>>>> Nothing to do
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "My script should have done the complete build. What is the error you
>>>>> are getting?"
>>>>>
>>>>> The error as follows:
>>>>>
>>>>> [INFO] ------------------------------------------------------------
>>>>> ------------
>>>>>
>>>>> [INFO] Reactor Summary:
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [INFO] Ambari Main ........................................ FAILURE
>>>>> [  2.135 s]
>>>>>
>>>>> [INFO] Apache Ambari Project POM .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Web ......................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>
>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>
>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>
>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>
>>>>> [INFO] ------------------------------------------------------------
>>>>> ------------
>>>>>
>>>>> [INFO] BUILD FAILURE
>>>>>
>>>>> [INFO] ------------------------------------------------------------
>>>>> ------------
>>>>>
>>>>> [INFO] Total time: 3.035 s
>>>>>
>>>>> [INFO] Finished at: 2016-07-28T23:09:34+00:00
>>>>>
>>>>> [INFO] Final Memory: 17M/479M
>>>>>
>>>>> [INFO] ------------------------------------------------------------
>>>>> ------------
>>>>>
>>>>> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
>>>>> (default) on project ambari: Could not create report parent directory
>>>>> /ambari/target -> [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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org>
>>>>> wrote:
>>>>>
>>>>> > Step 1: run your script
>>>>>
>>>>> > [INFO] Ambari Main ........................................ FAILURE
>>>>> [  0.521 s]
>>>>>
>>>>> My script should have done the complete build. What is the error you
>>>>> are getting?
>>>>>
>>>>>
>>>>>
>>>>> > Is "mvn clean install package -DskipTests"  correct command to
>>>>> build Ambari?
>>>>>
>>>>> Depends what do you want to do? For released versions, Apache Ambari
>>>>> already gives you the final binary bits, including RPM. So shouldn’t be
>>>>> needing to build.
>>>>>
>>>>>
>>>>>
>>>>> (From your very recent build)…
>>>>>
>>>>> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>>>>> -Dpython.ver='python >= 2.6' –DskipTests
>>>>>
>>>>> If you are compiling outside Docker, then try installing “yum install
>>>>> -y python-setuptools”. My script might not be able to take the space in the
>>>>> “python >= 2.6”. But if you want, I can look into it.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Bosco
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
from  "ambari-web/npm-debug.log", found the following


50491 silly gunzTarPerm extractEntry index.js

50492 error Error: ENOENT, lstat
'/home/ambari/tmp/npm-20999-fPHBBMwA/1470578512826-0.6402329006232321/package/.npmignore'

50493 error If you need help, you may report this log at:

50493 error     <http://github.com/isaacs/npm/issues>

50493 error or email it to:

50493 error     <np...@googlegroups.com>

50494 error System Linux 3.10.0-327.22.2.el7.x86_64

50495 error command "node" "/bin/npm" "install"

50496 error cwd /user/local/apache-ambari-2.2.2-src/ambari-web

50497 error node -v v0.10.42

50498 error npm -v 1.3.6

50499 error path
/home/ambari/tmp/npm-20999-fPHBBMwA/1470578512826-0.6402329006232321/package/.npmignore

50500 error fstream_path
/home/ambari/tmp/npm-20999-fPHBBMwA/1470578512826-0.6402329006232321/package/.npmignore

50501 error fstream_type File

50502 error fstream_class FileWriter

50503 error code ENOENT

50504 error errno 34

50505 error fstream_stack /usr/lib/node_modules/fstream/lib/writer.js:284:26

50505 error fstream_stack Object.oncomplete (fs.js:108:15)

50506 verbose exit [ 34, true ]



On Sun, Aug 7, 2016 at 9:35 PM, Ascot Moss <as...@gmail.com> wrote:

> and tried the following:
>
> (run as root)
>
> docker rmi ambari_dev
>
> /build_ambari_using_docker.sh
>
>
> [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
> approved: 1274 licence.
>
> [INFO]
>
> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @
> ambari ---
>
> [INFO] Reading assembly descriptor: /ambari/ambari-project/src/
> main/assemblies/empty.xml
>
> [INFO]
>
> [INFO] --- maven-install-plugin:2.4:install (default-install) @ ambari ---
>
> [INFO] Installing /ambari/pom.xml to /home/build/.m2/repository/
> org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ FAILURE [
> 1.722 s]
>
> [INFO] Apache Ambari Project POM .......................... SKIPPED
>
> [INFO] Ambari Web ......................................... SKIPPED
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Total time: 2.071 s
>
> [INFO] Finished at: 2016-08-07T13:33:26+00:00
>
> [INFO] Final Memory: 28M/702M
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-install-plugin:2.4:install (default-install) on project ambari:
> Failed to install artifact org.apache.ambari:ambari:pom:2.2.2.0.0:
> /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
> (Permission denied) -> [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
>
>
>
>
>
> as already run as root, not sure why still got
>  /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
> (Permission denied)
>
>
>
>
>
> On Sun, Aug 7, 2016 at 9:22 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> HI,
>>
>> Tried again.
>>
>>
>> Added:
>> echo $MAVEN_HOME
>>
>> /opt/apache-maven-3.3.9
>>
>>
>>
>> (command)
>>
>> mvn -B -e clean install package -DskipTests=true
>>
>>
>> (log)
>>
>> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>>
>> npm WARN notsup Not compatible with your operating system or
>> architecture: fsevents@0.2.1
>>
>> npm WARN Ambari@2.1.3 No license field.
>>
>> [INFO]
>>
>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>>
>> /usr/lib/node_modules/brunch/lib/watch.js:433
>>
>>             throw new Error("You probably need to execute `npm install`
>> to install brunch plugins. " + error);
>>
>>             ^
>>
>>
>> Error: You probably need to execute `npm install` to install brunch
>> plugins. SyntaxError: Setter must have exactly one formal parameter.
>>
>>   at /usr/lib/node_modules/brunch/lib/watch.js:433:19
>>
>>   at Array.map (native)
>>
>>   at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)
>>
>>   at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)
>>
>>   at /usr/lib/node_modules/brunch/lib/watch.js:458:19
>>
>>   at /usr/lib/node_modules/brunch/lib/helpers.js:529:16
>>
>>   at /usr/lib/node_modules/brunch/lib/helpers.js:485:14
>>
>>   at /usr/lib/node_modules/brunch/node_modules/read-components/in
>> dex.js:263:16
>>
>>   at /usr/lib/node_modules/brunch/node_modules/read-components/in
>> dex.js:72:14
>>
>>   at FSReqWrap.cb [as oncomplete] (fs.js:257:19)
>>
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ SUCCESS [
>> 2.577 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 0.036 s]
>>
>> [INFO] Ambari Web ......................................... FAILURE [
>> 22.124 s]
>>
>> [INFO] Ambari Views ....................................... SKIPPED
>>
>> [INFO] Ambari Admin View .................................. SKIPPED
>>
>> [INFO] ambari-metrics ..................................... SKIPPED
>>
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>
>> [INFO] Ambari Server ...................................... SKIPPED
>>
>> [INFO] Ambari Agent ....................................... SKIPPED
>>
>> [INFO] Ambari Client ...................................... SKIPPED
>>
>> [INFO] Ambari Python Client ............................... SKIPPED
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Total time: 25.063 s
>>
>> [INFO] Finished at: 2016-08-07T21:13:30+08:00
>>
>> [INFO] Final Memory: 32M/991M
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>> (compile-brunch) on project ambari-web: Command execution failed. Process
>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>> (compile-brunch) on project ambari-web: Command execution failed.
>>
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:212)
>>
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:153)
>>
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:145)
>>
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>> uildProject(LifecycleModuleBuilder.java:116)
>>
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>> uildProject(LifecycleModuleBuilder.java:80)
>>
>> at org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>> ingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>> (LifecycleStarter.java:128)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>>
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnha
>> nced(Launcher.java:289)
>>
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
>> Launcher.java:229)
>>
>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>> itCode(Launcher.java:415)
>>
>> at org.codehaus.plexus.classworlds.launcher.Launcher.main(
>> Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>> execution failed.
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>
>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>> o(DefaultBuildPluginManager.java:134)
>>
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:207)
>>
>> ... 20 more
>>
>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>> an error: 1 (Exit value: 1)
>>
>> at org.apache.commons.exec.DefaultExecutor.executeInternal(Defa
>> ultExecutor.java:377)
>>
>> at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecu
>> tor.java:160)
>>
>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>
>> ... 22 more
>>
>> [ERROR]
>>
>> [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/conflu
>> ence/display/MAVEN/MojoExecutionException
>>
>> [ERROR]
>>
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>>
>> [ERROR]   mvn <goals> -rf :ambari-web
>>
>>
>>
>>
>> On Mon, Aug 1, 2016 at 11:21 PM, Amanda Moran <am...@esgyn.com>
>> wrote:
>>
>>> Sorry if you already answered this.
>>>
>>> Is maven in your path?
>>>
>>> Thanks.
>>>
>>> On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:
>>>
>>> HI,
>>>
>>> Still have compilation error:
>>>
>>> sudo yum install -y python-setuptools
>>>
>>> sudo pip install psutil
>>>
>>> *sudo npm install -g brunch@1.7.20*
>>>
>>> *sudo pip install psutil*
>>>
>>> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>>> -Dpython.ver='python >= 2.6' *
>>>
>>> [INFO] RPM build errors:
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] Reactor Summary:
>>>
>>> [INFO]
>>>
>>> [INFO] Ambari Main ........................................ SUCCESS [
>>> 3.305 s]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>> 0.489 s]
>>>
>>> [INFO] Ambari Web ......................................... SUCCESS
>>> [04:30 min]
>>>
>>> [INFO] Ambari Views ....................................... SUCCESS [
>>> 1.530 s]
>>>
>>> [INFO] Ambari Admin View .................................. SUCCESS [
>>> 17.835 s]
>>>
>>> [INFO] ambari-metrics ..................................... SUCCESS [
>>> 1.036 s]
>>>
>>> [INFO] Ambari Metrics Common .............................. SUCCESS [
>>> 1.104 s]
>>>
>>> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
>>> 1.936 s]
>>>
>>> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
>>> 1.398 s]
>>>
>>> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
>>> 0.990 s]
>>>
>>> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
>>> 2.385 s]
>>>
>>> [INFO] Ambari Metrics Collector ........................... SUCCESS
>>> [01:41 min]
>>>
>>> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
>>> 1.501 s]
>>>
>>> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
>>> 15.498 s]
>>>
>>> [INFO] Ambari Metrics Assembly ............................ SUCCESS
>>> [04:55 min]
>>>
>>> [INFO] Ambari Server ...................................... SUCCESS
>>> [33:51 min]
>>>
>>> [INFO] Ambari Agent ....................................... SUCCESS [
>>> 32.124 s]
>>>
>>> [INFO] Ambari Client ...................................... SUCCESS [
>>> 15.318 s]
>>>
>>> [INFO] Ambari Python Client ............................... FAILURE [
>>> 13.884 s]
>>>
>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>
>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>
>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] Total time: 46:49 min
>>>
>>> [INFO] Finished at: 2016-08-01T16:32:25+08:00
>>>
>>> [INFO] Final Memory: 325M/2743M
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
>>> (default-cli) on project python-client: RPM build execution returned: '1'
>>> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2
>>> -src/ambari-client/python-client/target/rpm/python-client/SPECS &&
>>> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2
>>> -src/ambari-client/python-client/target/rpm/python-client/buildroot
>>> --define '_topdir /usr/local/apache-ambari-2.2.2
>>> -src/ambari-client/python-client/target/rpm/python-client' --target
>>> x86_64-redhat-linux python-client.spec' -> [Help 1]
>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
>>> (default-cli) on project python-client: RPM build execution returned: '1'
>>> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2
>>> -src/ambari-client/python-client/target/rpm/python-client/SPECS &&
>>> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2
>>> -src/ambari-client/python-client/target/rpm/python-client/buildroot
>>> --define '_topdir /usr/local/apache-ambari-2.2.2
>>> -src/ambari-client/python-client/target/rpm/python-client' --target
>>> x86_64-redhat-linux python-client.spec'
>>>
>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:212)
>>>
>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:153)
>>>
>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:145)
>>>
>>>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>>> uildProject(LifecycleModuleBuilder.java:116)
>>>
>>>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>>> uildProject(LifecycleModuleBuilder.java:80)
>>>
>>>         at org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>>> ingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>
>>>         at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>>> (LifecycleStarter.java:128)
>>>
>>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:30
>>> 7)
>>>
>>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:19
>>> 3)
>>>
>>>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>
>>>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>
>>>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>
>>>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>
>>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>>
>>>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>>
>>>         at java.lang.reflect.Method.invoke(Method.java:498)
>>>
>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnha
>>> nced(Launcher.java:289)
>>>
>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Lau
>>> ncher.java:229)
>>>
>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>>> itCode(Launcher.java:415)
>>>
>>>         at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launc
>>> her.java:356)
>>>
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
>>> execution returned: '1' executing '/bin/sh -c cd
>>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-clie
>>> nt/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot
>>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-clie
>>> nt/target/rpm/python-client/buildroot --define '_topdir
>>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
>>> --target x86_64-redhat-linux python-client.spec'
>>>
>>>         at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:
>>> 150)
>>>
>>>         at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMoj
>>> o.java:792)
>>>
>>>         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>>> o(DefaultBuildPluginManager.java:134)
>>>
>>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>>> oExecutor.java:207)
>>>
>>>         ... 20 more
>>>
>>> [ERROR]
>>>
>>> [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/conflu
>>> ence/display/MAVEN/MojoExecutionException
>>>
>>> [ERROR]
>>>
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>>
>>> [ERROR]   mvn <goals> -rf :python-client
>>>
>>> On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org>
>>> wrote:
>>>
>>>> I was able to reproduce your issue. It seems, the build user I am
>>>> creating didn’t have the permission to write to the local folder. I have
>>>> updated the script to create the build user with the same UID from the host
>>>> user. I have also using CentOS 6 image to build (as per the documentation).
>>>>
>>>>
>>>>
>>>> I have updated the JIRA with the updated script.
>>>> https://issues.apache.org/jira/browse/AMBARI-17944
>>>>
>>>>
>>>>
>>>> Please do the following:
>>>>
>>>>
>>>>
>>>> 1.       docker rmi ambari_dev
>>>>
>>>> 2.       Go to root folder of your Ambari source
>>>>
>>>> 3.       $YOUR_PATH/build_ambari_using_docker.sh
>>>>
>>>>
>>>>
>>>> Let me know how it goes.
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Bosco
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From: *Ascot Moss <as...@gmail.com>
>>>> *Reply-To: *<us...@ambari.apache.org>
>>>> *Date: *Thursday, July 28, 2016 at 4:11 PM
>>>> *To: *<us...@ambari.apache.org>
>>>> *Subject: *Re: Build Error
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> yum install -y python-setuptools
>>>>
>>>> Loaded plugins: fastestmirror
>>>>
>>>> Loading mirror speeds from cached hostfile
>>>>
>>>>  * base: mirror.vpshosting.com.hk
>>>>
>>>>  * epel: ftp.cuhk.edu.hk
>>>>
>>>>  * extras: mirror.vpshosting.com.hk
>>>>
>>>>  * updates: mirror.vpshosting.com.hk
>>>>
>>>> Package python-setuptools-0.9.8-4.el7.noarch already installed and
>>>> latest version
>>>>
>>>> Nothing to do
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> "My script should have done the complete build. What is the error you
>>>> are getting?"
>>>>
>>>> The error as follows:
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [INFO] Reactor Summary:
>>>>
>>>> [INFO]
>>>>
>>>> [INFO] Ambari Main ........................................ FAILURE [
>>>> 2.135 s]
>>>>
>>>> [INFO] Apache Ambari Project POM .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Web ......................................... SKIPPED
>>>>
>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>
>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>
>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [INFO] BUILD FAILURE
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [INFO] Total time: 3.035 s
>>>>
>>>> [INFO] Finished at: 2016-07-28T23:09:34+00:00
>>>>
>>>> [INFO] Final Memory: 17M/479M
>>>>
>>>> [INFO] ------------------------------------------------------------
>>>> ------------
>>>>
>>>> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
>>>> (default) on project ambari: Could not create report parent directory
>>>> /ambari/target -> [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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org>
>>>> wrote:
>>>>
>>>> > Step 1: run your script
>>>>
>>>> > [INFO] Ambari Main ........................................ FAILURE
>>>> [  0.521 s]
>>>>
>>>> My script should have done the complete build. What is the error you
>>>> are getting?
>>>>
>>>>
>>>>
>>>> > Is "mvn clean install package -DskipTests"  correct command to build
>>>> Ambari?
>>>>
>>>> Depends what do you want to do? For released versions, Apache Ambari
>>>> already gives you the final binary bits, including RPM. So shouldn’t be
>>>> needing to build.
>>>>
>>>>
>>>>
>>>> (From your very recent build)…
>>>>
>>>> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>>>> -Dpython.ver='python >= 2.6' –DskipTests
>>>>
>>>> If you are compiling outside Docker, then try installing “yum install
>>>> -y python-setuptools”. My script might not be able to take the space in the
>>>> “python >= 2.6”. But if you want, I can look into it.
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Bosco
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
and tried the following:

(run as root)

docker rmi ambari_dev

/build_ambari_using_docker.sh


[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 1274 licence.

[INFO]

[INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ ambari
---

[INFO] Reading assembly descriptor:
/ambari/ambari-project/src/main/assemblies/empty.xml

[INFO]

[INFO] --- maven-install-plugin:2.4:install (default-install) @ ambari ---

[INFO] Installing /ambari/pom.xml to
/home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ FAILURE [
1.722 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 2.071 s

[INFO] Finished at: 2016-08-07T13:33:26+00:00

[INFO] Final Memory: 28M/702M

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install)
on project ambari: Failed to install artifact
org.apache.ambari:ambari:pom:2.2.2.0.0:
/home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
(Permission denied) -> [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





as already run as root, not sure why still got
 /home/build/.m2/repository/org/apache/ambari/ambari/2.2.2.0.0/ambari-2.2.2.0.0.pom
(Permission denied)





On Sun, Aug 7, 2016 at 9:22 PM, Ascot Moss <as...@gmail.com> wrote:

> HI,
>
> Tried again.
>
>
> Added:
> echo $MAVEN_HOME
>
> /opt/apache-maven-3.3.9
>
>
>
> (command)
>
> mvn -B -e clean install package -DskipTests=true
>
>
> (log)
>
> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@0.2.1
>
> npm WARN Ambari@2.1.3 No license field.
>
> [INFO]
>
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>
> /usr/lib/node_modules/brunch/lib/watch.js:433
>
>             throw new Error("You probably need to execute `npm install` to
> install brunch plugins. " + error);
>
>             ^
>
>
> Error: You probably need to execute `npm install` to install brunch
> plugins. SyntaxError: Setter must have exactly one formal parameter.
>
>   at /usr/lib/node_modules/brunch/lib/watch.js:433:19
>
>   at Array.map (native)
>
>   at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)
>
>   at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)
>
>   at /usr/lib/node_modules/brunch/lib/watch.js:458:19
>
>   at /usr/lib/node_modules/brunch/lib/helpers.js:529:16
>
>   at /usr/lib/node_modules/brunch/lib/helpers.js:485:14
>
>   at /usr/lib/node_modules/brunch/node_modules/read-components/
> index.js:263:16
>
>   at /usr/lib/node_modules/brunch/node_modules/read-components/
> index.js:72:14
>
>   at FSReqWrap.cb [as oncomplete] (fs.js:257:19)
>
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 2.577 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.036 s]
>
> [INFO] Ambari Web ......................................... FAILURE [
> 22.124 s]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Total time: 25.063 s
>
> [INFO] Finished at: 2016-08-07T21:13:30+08:00
>
> [INFO] Final Memory: 32M/991M
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (compile-brunch) on project ambari-web: Command execution failed. Process
> exited with an error: 1 (Exit value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:212)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:153)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:145)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:116)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:80)
>
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.
> SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at org.apache.maven.lifecycle.internal.LifecycleStarter.
> execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:289)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:229)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:415)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
> DefaultBuildPluginManager.java:134)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at org.apache.commons.exec.DefaultExecutor.executeInternal(
> DefaultExecutor.java:377)
>
> at org.apache.commons.exec.DefaultExecutor.execute(
> DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
> [ERROR]
>
> [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 <goals> -rf :ambari-web
>
>
>
>
> On Mon, Aug 1, 2016 at 11:21 PM, Amanda Moran <am...@esgyn.com>
> wrote:
>
>> Sorry if you already answered this.
>>
>> Is maven in your path?
>>
>> Thanks.
>>
>> On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:
>>
>> HI,
>>
>> Still have compilation error:
>>
>> sudo yum install -y python-setuptools
>>
>> sudo pip install psutil
>>
>> *sudo npm install -g brunch@1.7.20*
>>
>> *sudo pip install psutil*
>>
>> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
>> >= 2.6' *
>>
>> [INFO] RPM build errors:
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ SUCCESS [
>> 3.305 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 0.489 s]
>>
>> [INFO] Ambari Web ......................................... SUCCESS
>> [04:30 min]
>>
>> [INFO] Ambari Views ....................................... SUCCESS [
>> 1.530 s]
>>
>> [INFO] Ambari Admin View .................................. SUCCESS [
>> 17.835 s]
>>
>> [INFO] ambari-metrics ..................................... SUCCESS [
>> 1.036 s]
>>
>> [INFO] Ambari Metrics Common .............................. SUCCESS [
>> 1.104 s]
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
>> 1.936 s]
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
>> 1.398 s]
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
>> 0.990 s]
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
>> 2.385 s]
>>
>> [INFO] Ambari Metrics Collector ........................... SUCCESS
>> [01:41 min]
>>
>> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
>> 1.501 s]
>>
>> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
>> 15.498 s]
>>
>> [INFO] Ambari Metrics Assembly ............................ SUCCESS
>> [04:55 min]
>>
>> [INFO] Ambari Server ...................................... SUCCESS
>> [33:51 min]
>>
>> [INFO] Ambari Agent ....................................... SUCCESS [
>> 32.124 s]
>>
>> [INFO] Ambari Client ...................................... SUCCESS [
>> 15.318 s]
>>
>> [INFO] Ambari Python Client ............................... FAILURE [
>> 13.884 s]
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Total time: 46:49 min
>>
>> [INFO] Finished at: 2016-08-01T16:32:25+08:00
>>
>> [INFO] Final Memory: 325M/2743M
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
>> (default-cli) on project python-client: RPM build execution returned: '1'
>> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2
>> -src/ambari-client/python-client/target/rpm/python-client/SPECS &&
>> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2
>> -src/ambari-client/python-client/target/rpm/python-client/buildroot
>> --define '_topdir /usr/local/apache-ambari-2.2.2
>> -src/ambari-client/python-client/target/rpm/python-client' --target
>> x86_64-redhat-linux python-client.spec' -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
>> (default-cli) on project python-client: RPM build execution returned: '1'
>> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2
>> -src/ambari-client/python-client/target/rpm/python-client/SPECS &&
>> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2
>> -src/ambari-client/python-client/target/rpm/python-client/buildroot
>> --define '_topdir /usr/local/apache-ambari-2.2.2
>> -src/ambari-client/python-client/target/rpm/python-client' --target
>> x86_64-redhat-linux python-client.spec'
>>
>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:212)
>>
>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:153)
>>
>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:145)
>>
>>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>> uildProject(LifecycleModuleBuilder.java:116)
>>
>>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.b
>> uildProject(LifecycleModuleBuilder.java:80)
>>
>>         at org.apache.maven.lifecycle.internal.builder.singlethreaded.S
>> ingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>
>>         at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
>> (LifecycleStarter.java:128)
>>
>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>
>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>
>>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>
>>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>
>>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>
>>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>>
>>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>>
>>         at java.lang.reflect.Method.invoke(Method.java:498)
>>
>>         at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnha
>> nced(Launcher.java:289)
>>
>>         at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
>> Launcher.java:229)
>>
>>         at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithEx
>> itCode(Launcher.java:415)
>>
>>         at org.codehaus.plexus.classworlds.launcher.Launcher.main(
>> Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
>> execution returned: '1' executing '/bin/sh -c cd
>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-clie
>> nt/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot
>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-clie
>> nt/target/rpm/python-client/buildroot --define '_topdir
>> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
>> --target x86_64-redhat-linux python-client.spec'
>>
>>         at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:
>> 150)
>>
>>         at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMoj
>> o.java:792)
>>
>>         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMoj
>> o(DefaultBuildPluginManager.java:134)
>>
>>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
>> oExecutor.java:207)
>>
>>         ... 20 more
>>
>> [ERROR]
>>
>> [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/conflu
>> ence/display/MAVEN/MojoExecutionException
>>
>> [ERROR]
>>
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>>
>> [ERROR]   mvn <goals> -rf :python-client
>>
>> On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org>
>> wrote:
>>
>>> I was able to reproduce your issue. It seems, the build user I am
>>> creating didn’t have the permission to write to the local folder. I have
>>> updated the script to create the build user with the same UID from the host
>>> user. I have also using CentOS 6 image to build (as per the documentation).
>>>
>>>
>>>
>>> I have updated the JIRA with the updated script.
>>> https://issues.apache.org/jira/browse/AMBARI-17944
>>>
>>>
>>>
>>> Please do the following:
>>>
>>>
>>>
>>> 1.       docker rmi ambari_dev
>>>
>>> 2.       Go to root folder of your Ambari source
>>>
>>> 3.       $YOUR_PATH/build_ambari_using_docker.sh
>>>
>>>
>>>
>>> Let me know how it goes.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Bosco
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From: *Ascot Moss <as...@gmail.com>
>>> *Reply-To: *<us...@ambari.apache.org>
>>> *Date: *Thursday, July 28, 2016 at 4:11 PM
>>> *To: *<us...@ambari.apache.org>
>>> *Subject: *Re: Build Error
>>>
>>>
>>>
>>> Hi,
>>>
>>> yum install -y python-setuptools
>>>
>>> Loaded plugins: fastestmirror
>>>
>>> Loading mirror speeds from cached hostfile
>>>
>>>  * base: mirror.vpshosting.com.hk
>>>
>>>  * epel: ftp.cuhk.edu.hk
>>>
>>>  * extras: mirror.vpshosting.com.hk
>>>
>>>  * updates: mirror.vpshosting.com.hk
>>>
>>> Package python-setuptools-0.9.8-4.el7.noarch already installed and
>>> latest version
>>>
>>> Nothing to do
>>>
>>>
>>>
>>>
>>>
>>> "My script should have done the complete build. What is the error you
>>> are getting?"
>>>
>>> The error as follows:
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] Reactor Summary:
>>>
>>> [INFO]
>>>
>>> [INFO] Ambari Main ........................................ FAILURE [
>>> 2.135 s]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SKIPPED
>>>
>>> [INFO] Ambari Web ......................................... SKIPPED
>>>
>>> [INFO] Ambari Views ....................................... SKIPPED
>>>
>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>
>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>
>>> [INFO] Ambari Server ...................................... SKIPPED
>>>
>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>
>>> [INFO] Ambari Client ...................................... SKIPPED
>>>
>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>
>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>
>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [INFO] Total time: 3.035 s
>>>
>>> [INFO] Finished at: 2016-07-28T23:09:34+00:00
>>>
>>> [INFO] Final Memory: 17M/479M
>>>
>>> [INFO] ------------------------------------------------------------
>>> ------------
>>>
>>> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
>>> (default) on project ambari: Could not create report parent directory
>>> /ambari/target -> [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
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org>
>>> wrote:
>>>
>>> > Step 1: run your script
>>>
>>> > [INFO] Ambari Main ........................................ FAILURE
>>> [  0.521 s]
>>>
>>> My script should have done the complete build. What is the error you are
>>> getting?
>>>
>>>
>>>
>>> > Is "mvn clean install package -DskipTests"  correct command to build
>>> Ambari?
>>>
>>> Depends what do you want to do? For released versions, Apache Ambari
>>> already gives you the final binary bits, including RPM. So shouldn’t be
>>> needing to build.
>>>
>>>
>>>
>>> (From your very recent build)…
>>>
>>> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>>> -Dpython.ver='python >= 2.6' –DskipTests
>>>
>>> If you are compiling outside Docker, then try installing “yum install -y
>>> python-setuptools”. My script might not be able to take the space in the
>>> “python >= 2.6”. But if you want, I can look into it.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Bosco
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
HI,

Tried again.


Added:
echo $MAVEN_HOME

/opt/apache-maven-3.3.9



(command)

mvn -B -e clean install package -DskipTests=true


(log)

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:

npm WARN notsup Not compatible with your operating system or architecture:
fsevents@0.2.1

npm WARN Ambari@2.1.3 No license field.

[INFO]

[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---

/usr/lib/node_modules/brunch/lib/watch.js:433

            throw new Error("You probably need to execute `npm install` to
install brunch plugins. " + error);

            ^


Error: You probably need to execute `npm install` to install brunch
plugins. SyntaxError: Setter must have exactly one formal parameter.

  at /usr/lib/node_modules/brunch/lib/watch.js:433:19

  at Array.map (native)

  at loadDeps (/usr/lib/node_modules/brunch/lib/watch.js:418:10)

  at loadPackages (/usr/lib/node_modules/brunch/lib/watch.js:438:15)

  at /usr/lib/node_modules/brunch/lib/watch.js:458:19

  at /usr/lib/node_modules/brunch/lib/helpers.js:529:16

  at /usr/lib/node_modules/brunch/lib/helpers.js:485:14

  at
/usr/lib/node_modules/brunch/node_modules/read-components/index.js:263:16

  at
/usr/lib/node_modules/brunch/node_modules/read-components/index.js:72:14

  at FSReqWrap.cb [as oncomplete] (fs.js:257:19)


[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [
2.577 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.036 s]

[INFO] Ambari Web ......................................... FAILURE [
22.124 s]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 25.063 s

[INFO] Finished at: 2016-08-07T21:13:30+08:00

[INFO] Final Memory: 32M/991M

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
ambari-web: Command execution failed. Process exited with an error: 1 (Exit
value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
project ambari-web: Command execution failed.

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command
execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an
error: 1 (Exit value: 1)

at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

[ERROR]

[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 <goals> -rf :ambari-web




On Mon, Aug 1, 2016 at 11:21 PM, Amanda Moran <am...@esgyn.com>
wrote:

> Sorry if you already answered this.
>
> Is maven in your path?
>
> Thanks.
>
> On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:
>
> HI,
>
> Still have compilation error:
>
> sudo yum install -y python-setuptools
>
> sudo pip install psutil
>
> *sudo npm install -g brunch@1.7.20*
>
> *sudo pip install psutil*
>
> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
> >= 2.6' *
>
> [INFO] RPM build errors:
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 3.305 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.489 s]
>
> [INFO] Ambari Web ......................................... SUCCESS
> [04:30 min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 1.530 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [
> 17.835 s]
>
> [INFO] ambari-metrics ..................................... SUCCESS [
> 1.036 s]
>
> [INFO] Ambari Metrics Common .............................. SUCCESS [
> 1.104 s]
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
> 1.936 s]
>
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
> 1.398 s]
>
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
> 0.990 s]
>
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
> 2.385 s]
>
> [INFO] Ambari Metrics Collector ........................... SUCCESS [01:41
> min]
>
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
> 1.501 s]
>
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
> 15.498 s]
>
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [04:55
> min]
>
> [INFO] Ambari Server ...................................... SUCCESS
> [33:51 min]
>
> [INFO] Ambari Agent ....................................... SUCCESS [
> 32.124 s]
>
> [INFO] Ambari Client ...................................... SUCCESS [
> 15.318 s]
>
> [INFO] Ambari Python Client ............................... FAILURE [
> 13.884 s]
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [INFO] Total time: 46:49 min
>
> [INFO] Finished at: 2016-08-01T16:32:25+08:00
>
> [INFO] Final Memory: 325M/2743M
>
> [INFO] ------------------------------------------------------------
> ------------
>
> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm
> (default-cli) on project python-client: RPM build execution returned: '1'
> executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.
> 2-src/ambari-client/python-client/target/rpm/python-client/SPECS &&
> rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.
> 2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client' --target x86_64-redhat-linux
> python-client.spec' -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
> project python-client: RPM build execution returned: '1' executing '/bin/sh
> -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/buildroot --define '_topdir
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client' --target x86_64-redhat-linux
> python-client.spec'
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:212)
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:153)
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:145)
>
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:116)
>
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:80)
>
>         at org.apache.maven.lifecycle.internal.builder.singlethreaded.
> SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
>         at org.apache.maven.lifecycle.internal.LifecycleStarter.
> execute(LifecycleStarter.java:128)
>
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
>
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
>
>         at java.lang.reflect.Method.invoke(Method.java:498)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:289)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:229)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:415)
>
>         at org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
> execution returned: '1' executing '/bin/sh -c cd
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client/buildroot --define '_topdir
> /usr/local/apache-ambari-2.2.2-src/ambari-client/python-
> client/target/rpm/python-client' --target x86_64-redhat-linux
> python-client.spec'
>
>         at org.codehaus.mojo.rpm.RPMHelper.buildPackage(
> RPMHelper.java:150)
>
>         at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(
> AbstractRPMMojo.java:792)
>
>         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
> DefaultBuildPluginManager.java:134)
>
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:207)
>
>         ... 20 more
>
> [ERROR]
>
> [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 <goals> -rf :python-client
>
> On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org> wrote:
>
>> I was able to reproduce your issue. It seems, the build user I am
>> creating didn’t have the permission to write to the local folder. I have
>> updated the script to create the build user with the same UID from the host
>> user. I have also using CentOS 6 image to build (as per the documentation).
>>
>>
>>
>> I have updated the JIRA with the updated script.
>> https://issues.apache.org/jira/browse/AMBARI-17944
>>
>>
>>
>> Please do the following:
>>
>>
>>
>> 1.       docker rmi ambari_dev
>>
>> 2.       Go to root folder of your Ambari source
>>
>> 3.       $YOUR_PATH/build_ambari_using_docker.sh
>>
>>
>>
>> Let me know how it goes.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Bosco
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *Ascot Moss <as...@gmail.com>
>> *Reply-To: *<us...@ambari.apache.org>
>> *Date: *Thursday, July 28, 2016 at 4:11 PM
>> *To: *<us...@ambari.apache.org>
>> *Subject: *Re: Build Error
>>
>>
>>
>> Hi,
>>
>> yum install -y python-setuptools
>>
>> Loaded plugins: fastestmirror
>>
>> Loading mirror speeds from cached hostfile
>>
>>  * base: mirror.vpshosting.com.hk
>>
>>  * epel: ftp.cuhk.edu.hk
>>
>>  * extras: mirror.vpshosting.com.hk
>>
>>  * updates: mirror.vpshosting.com.hk
>>
>> Package python-setuptools-0.9.8-4.el7.noarch already installed and
>> latest version
>>
>> Nothing to do
>>
>>
>>
>>
>>
>> "My script should have done the complete build. What is the error you are
>> getting?"
>>
>> The error as follows:
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ FAILURE [
>> 2.135 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SKIPPED
>>
>> [INFO] Ambari Web ......................................... SKIPPED
>>
>> [INFO] Ambari Views ....................................... SKIPPED
>>
>> [INFO] Ambari Admin View .................................. SKIPPED
>>
>> [INFO] ambari-metrics ..................................... SKIPPED
>>
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>
>> [INFO] Ambari Server ...................................... SKIPPED
>>
>> [INFO] Ambari Agent ....................................... SKIPPED
>>
>> [INFO] Ambari Client ...................................... SKIPPED
>>
>> [INFO] Ambari Python Client ............................... SKIPPED
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [INFO] Total time: 3.035 s
>>
>> [INFO] Finished at: 2016-07-28T23:09:34+00:00
>>
>> [INFO] Final Memory: 17M/479M
>>
>> [INFO] ------------------------------------------------------------
>> ------------
>>
>> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
>> (default) on project ambari: Could not create report parent directory
>> /ambari/target -> [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
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org>
>> wrote:
>>
>> > Step 1: run your script
>>
>> > [INFO] Ambari Main ........................................ FAILURE [
>> 0.521 s]
>>
>> My script should have done the complete build. What is the error you are
>> getting?
>>
>>
>>
>> > Is "mvn clean install package -DskipTests"  correct command to build
>> Ambari?
>>
>> Depends what do you want to do? For released versions, Apache Ambari
>> already gives you the final binary bits, including RPM. So shouldn’t be
>> needing to build.
>>
>>
>>
>> (From your very recent build)…
>>
>> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>> -Dpython.ver='python >= 2.6' –DskipTests
>>
>> If you are compiling outside Docker, then try installing “yum install -y
>> python-setuptools”. My script might not be able to take the space in the
>> “python >= 2.6”. But if you want, I can look into it.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Bosco
>>
>>
>>
>>
>>
>>
>>
>
>

Re: Build Error

Posted by Amanda Moran <am...@esgyn.com>.
Sorry if you already answered this. 

Is maven in your path? 

Thanks. 

> On Aug 1, 2016, at 7:18 AM, Ascot Moss <as...@gmail.com> wrote:
> 
> HI,
> 
> Still have compilation error:
> 
> sudo yum install -y python-setuptools
> 
> sudo pip install psutil
> 
> sudo npm install -g brunch@1.7.20
> 
> sudo pip install psutil
> 
> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' 
> 
> [INFO] RPM build errors:
> 
> [INFO] ------------------------------------------------------------------------
> 
> [INFO] Reactor Summary:
> 
> [INFO]
> 
> [INFO] Ambari Main ........................................ SUCCESS [  3.305 s]
> 
> [INFO] Apache Ambari Project POM .......................... SUCCESS [  0.489 s]
> 
> [INFO] Ambari Web ......................................... SUCCESS [04:30 min]
> 
> [INFO] Ambari Views ....................................... SUCCESS [  1.530 s]
> 
> [INFO] Ambari Admin View .................................. SUCCESS [ 17.835 s]
> 
> [INFO] ambari-metrics ..................................... SUCCESS [  1.036 s]
> 
> [INFO] Ambari Metrics Common .............................. SUCCESS [  1.104 s]
> 
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  1.936 s]
> 
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  1.398 s]
> 
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  0.990 s]
> 
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.385 s]
> 
> [INFO] Ambari Metrics Collector ........................... SUCCESS [01:41 min]
> 
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.501 s]
> 
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [ 15.498 s]
> 
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [04:55 min]
> 
> [INFO] Ambari Server ...................................... SUCCESS [33:51 min]
> 
> [INFO] Ambari Agent ....................................... SUCCESS [ 32.124 s]
> 
> [INFO] Ambari Client ...................................... SUCCESS [ 15.318 s]
> 
> [INFO] Ambari Python Client ............................... FAILURE [ 13.884 s]
> 
> [INFO] Ambari Groovy Client ............................... SKIPPED
> 
> [INFO] Ambari Shell ....................................... SKIPPED
> 
> [INFO] Ambari Python Shell ................................ SKIPPED
> 
> [INFO] Ambari Groovy Shell ................................ SKIPPED
> 
> [INFO] ------------------------------------------------------------------------
> 
> [INFO] BUILD FAILURE
> 
> [INFO] ------------------------------------------------------------------------
> 
> [INFO] Total time: 46:49 min
> 
> [INFO] Finished at: 2016-08-01T16:32:25+08:00
> 
> [INFO] Final Memory: 325M/2743M
> 
> [INFO] ------------------------------------------------------------------------
> 
> [ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec' -> [Help 1]
> 
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'
> 
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> 
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 
>         at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 
>         at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> 
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> 
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> 
>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> 
>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> 
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 
>         at java.lang.reflect.Method.invoke(Method.java:498)
> 
>         at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 
>         at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 
>         at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 
>         at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build execution returned: '1' executing '/bin/sh -c cd /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'
> 
>         at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)
> 
>         at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)
> 
>         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> 
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 
>         ... 20 more
> 
> [ERROR]
> 
> [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 <goals> -rf :python-client
> 
> 
>> On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org> wrote:
>> I was able to reproduce your issue. It seems, the build user I am creating didn’t have the permission to write to the local folder. I have updated the script to create the build user with the same UID from the host user. I have also using CentOS 6 image to build (as per the documentation).
>> 
>>  
>> 
>> I have updated the JIRA with the updated script. https://issues.apache.org/jira/browse/AMBARI-17944
>> 
>>  
>> 
>> Please do the following:
>> 
>>  
>> 
>> 1.       docker rmi ambari_dev
>> 
>> 2.       Go to root folder of your Ambari source
>> 
>> 3.       $YOUR_PATH/build_ambari_using_docker.sh
>> 
>>  
>> 
>> Let me know how it goes.
>> 
>>  
>> 
>> Thanks
>> 
>>  
>> 
>> Bosco
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> From: Ascot Moss <as...@gmail.com>
>> Reply-To: <us...@ambari.apache.org>
>> Date: Thursday, July 28, 2016 at 4:11 PM
>> To: <us...@ambari.apache.org>
>> Subject: Re: Build Error
>> 
>>  
>> 
>> Hi,
>> 
>> yum install -y python-setuptools
>> 
>> Loaded plugins: fastestmirror
>> 
>> Loading mirror speeds from cached hostfile
>> 
>>  * base: mirror.vpshosting.com.hk
>> 
>>  * epel: ftp.cuhk.edu.hk
>> 
>>  * extras: mirror.vpshosting.com.hk
>> 
>>  * updates: mirror.vpshosting.com.hk
>> 
>> Package python-setuptools-0.9.8-4.el7.noarch already installed and latest version
>> 
>> Nothing to do
>> 
>>  
>> 
>>  
>> 
>> "My script should have done the complete build. What is the error you are getting?"
>> The error as follows:
>> [INFO] ------------------------------------------------------------------------
>> 
>> [INFO] Reactor Summary:
>> 
>> [INFO] 
>> 
>> [INFO] Ambari Main ........................................ FAILURE [  2.135 s]
>> 
>> [INFO] Apache Ambari Project POM .......................... SKIPPED
>> 
>> [INFO] Ambari Web ......................................... SKIPPED
>> 
>> [INFO] Ambari Views ....................................... SKIPPED
>> 
>> [INFO] Ambari Admin View .................................. SKIPPED
>> 
>> [INFO] ambari-metrics ..................................... SKIPPED
>> 
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>> 
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>> 
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>> 
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>> 
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>> 
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>> 
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>> 
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>> 
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>> 
>> [INFO] Ambari Server ...................................... SKIPPED
>> 
>> [INFO] Ambari Agent ....................................... SKIPPED
>> 
>> [INFO] Ambari Client ...................................... SKIPPED
>> 
>> [INFO] Ambari Python Client ............................... SKIPPED
>> 
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>> 
>> [INFO] Ambari Shell ....................................... SKIPPED
>> 
>> [INFO] Ambari Python Shell ................................ SKIPPED
>> 
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>> 
>> [INFO] ------------------------------------------------------------------------
>> 
>> [INFO] BUILD FAILURE
>> 
>> [INFO] ------------------------------------------------------------------------
>> 
>> [INFO] Total time: 3.035 s
>> 
>> [INFO] Finished at: 2016-07-28T23:09:34+00:00
>> 
>> [INFO] Final Memory: 17M/479M
>> 
>> [INFO] ------------------------------------------------------------------------
>> 
>> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari: Could not create report parent directory /ambari/target -> [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
>> 
>>  
>> 
>>  
>> 
>>  
>>  
>>  
>>  
>> 
>> On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org> wrote:
>> 
>> > Step 1: run your script
>> 
>> > [INFO] Ambari Main ........................................ FAILURE [  0.521 s]
>> 
>> My script should have done the complete build. What is the error you are getting?
>> 
>>  
>> 
>> > Is "mvn clean install package -DskipTests"  correct command to build Ambari?
>> 
>> Depends what do you want to do? For released versions, Apache Ambari already gives you the final binary bits, including RPM. So shouldn’t be needing to build.
>> 
>>  
>> 
>> (From your very recent build)…
>> 
>> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' –DskipTests
>> 
>> If you are compiling outside Docker, then try installing “yum install -y python-setuptools”. My script might not be able to take the space in the “python >= 2.6”. But if you want, I can look into it.
>> 
>>  
>> 
>> Thanks
>> 
>>  
>> 
>> Bosco
>> 
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
HI,

Still have compilation error:

sudo yum install -y python-setuptools

sudo pip install psutil

*sudo npm install -g brunch@1.7.20*

*sudo pip install psutil*

*mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
>= 2.6' *

[INFO] RPM build errors:

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [
3.305 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.489 s]

[INFO] Ambari Web ......................................... SUCCESS [04:30
min]

[INFO] Ambari Views ....................................... SUCCESS [
1.530 s]

[INFO] Ambari Admin View .................................. SUCCESS [
17.835 s]

[INFO] ambari-metrics ..................................... SUCCESS [
1.036 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [
1.104 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
1.936 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
1.398 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
0.990 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
2.385 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [01:41
min]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [
1.501 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [
15.498 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [04:55
min]

[INFO] Ambari Server ...................................... SUCCESS [33:51
min]

[INFO] Ambari Agent ....................................... SUCCESS [
32.124 s]

[INFO] Ambari Client ...................................... SUCCESS [
15.318 s]

[INFO] Ambari Python Client ............................... FAILURE [
13.884 s]

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 46:49 min

[INFO] Finished at: 2016-08-01T16:32:25+08:00

[INFO] Final Memory: 325M/2743M

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project
python-client: RPM build execution returned: '1' executing '/bin/sh -c cd
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec' -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
project python-client: RPM build execution returned: '1' executing '/bin/sh
-c cd
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec'

        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

        at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

        at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

        at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

        at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

        at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
execution returned: '1' executing '/bin/sh -c cd
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/usr/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec'

        at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)

        at
org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)

        at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

        ... 20 more

[ERROR]

[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 <goals> -rf :python-client

On Sat, Jul 30, 2016 at 3:35 PM, Don Bosco Durai <bo...@apache.org> wrote:

> I was able to reproduce your issue. It seems, the build user I am creating
> didn’t have the permission to write to the local folder. I have updated the
> script to create the build user with the same UID from the host user. I
> have also using CentOS 6 image to build (as per the documentation).
>
>
>
> I have updated the JIRA with the updated script.
> https://issues.apache.org/jira/browse/AMBARI-17944
>
>
>
> Please do the following:
>
>
>
> 1.       docker rmi ambari_dev
>
> 2.       Go to root folder of your Ambari source
>
> 3.       $YOUR_PATH/build_ambari_using_docker.sh
>
>
>
> Let me know how it goes.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Thursday, July 28, 2016 at 4:11 PM
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> Hi,
>
> yum install -y python-setuptools
>
> Loaded plugins: fastestmirror
>
> Loading mirror speeds from cached hostfile
>
>  * base: mirror.vpshosting.com.hk
>
>  * epel: ftp.cuhk.edu.hk
>
>  * extras: mirror.vpshosting.com.hk
>
>  * updates: mirror.vpshosting.com.hk
>
> Package python-setuptools-0.9.8-4.el7.noarch already installed and latest
> version
>
> Nothing to do
>
>
>
>
>
> "My script should have done the complete build. What is the error you are
> getting?"
>
> The error as follows:
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ FAILURE [
> 2.135 s]
>
> [INFO] Apache Ambari Project POM .......................... SKIPPED
>
> [INFO] Ambari Web ......................................... SKIPPED
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 3.035 s
>
> [INFO] Finished at: 2016-07-28T23:09:34+00:00
>
> [INFO] Final Memory: 17M/479M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (default) on project ambari: Could not create report parent directory
> /ambari/target -> [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
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org>
> wrote:
>
> > Step 1: run your script
>
> > [INFO] Ambari Main ........................................ FAILURE [
> 0.521 s]
>
> My script should have done the complete build. What is the error you are
> getting?
>
>
>
> > Is "mvn clean install package -DskipTests"  correct command to build
> Ambari?
>
> Depends what do you want to do? For released versions, Apache Ambari
> already gives you the final binary bits, including RPM. So shouldn’t be
> needing to build.
>
>
>
> (From your very recent build)…
>
> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm
> -Dpython.ver='python >= 2.6' –DskipTests
>
> If you are compiling outside Docker, then try installing “yum install -y
> python-setuptools”. My script might not be able to take the space in the
> “python >= 2.6”. But if you want, I can look into it.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
>
>

Re: Build Error

Posted by Don Bosco Durai <bo...@apache.org>.
I was able to reproduce your issue. It seems, the build user I am creating didn’t have the permission to write to the local folder. I have updated the script to create the build user with the same UID from the host user. I have also using CentOS 6 image to build (as per the documentation).

 

I have updated the JIRA with the updated script. https://issues.apache.org/jira/browse/AMBARI-17944

 

Please do the following:

 

1.       docker rmi ambari_dev

2.       Go to root folder of your Ambari source

3.       $YOUR_PATH/build_ambari_using_docker.sh

 

Let me know how it goes.

 

Thanks

 

Bosco

 

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Thursday, July 28, 2016 at 4:11 PM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi,

yum install -y python-setuptools

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

 * base: mirror.vpshosting.com.hk

 * epel: ftp.cuhk.edu.hk

 * extras: mirror.vpshosting.com.hk

 * updates: mirror.vpshosting.com.hk

Package python-setuptools-0.9.8-4.el7.noarch already installed and latest version

Nothing to do

 

 

"My script should have done the complete build. What is the error you are getting?"

The error as follows:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ FAILURE [  2.135 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 3.035 s

[INFO] Finished at: 2016-07-28T23:09:34+00:00

[INFO] Final Memory: 17M/479M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari: Could not create report parent directory /ambari/target -> [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

 

 

 

 

 

 

On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org> wrote:

> Step 1: run your script

> [INFO] Ambari Main ........................................ FAILURE [  0.521 s]

My script should have done the complete build. What is the error you are getting?

 

> Is "mvn clean install package -DskipTests"  correct command to build Ambari?

Depends what do you want to do? For released versions, Apache Ambari already gives you the final binary bits, including RPM. So shouldn’t be needing to build.

 

(From your very recent build)…

> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' –DskipTests

If you are compiling outside Docker, then try installing “yum install -y python-setuptools”. My script might not be able to take the space in the “python >= 2.6”. But if you want, I can look into it.

 

Thanks

 

Bosco

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
Hi,

yum install -y python-setuptools

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

 * base: mirror.vpshosting.com.hk

 * epel: ftp.cuhk.edu.hk

 * extras: mirror.vpshosting.com.hk

 * updates: mirror.vpshosting.com.hk

Package python-setuptools-0.9.8-4.el7.noarch already installed and latest
version

Nothing to do



"My script should have done the complete build. What is the error you are
getting?"

The error as follows:

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ FAILURE [
2.135 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 3.035 s

[INFO] Finished at: 2016-07-28T23:09:34+00:00

[INFO] Final Memory: 17M/479M

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
(default) on project ambari: Could not create report parent directory
/ambari/target -> [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







On Fri, Jul 29, 2016 at 12:49 AM, Don Bosco Durai <bo...@apache.org> wrote:

> > Step 1: run your script
>
> > [INFO] Ambari Main ........................................ FAILURE [
> 0.521 s]
>
> My script should have done the complete build. What is the error you are
> getting?
>
>
>
> > Is "mvn clean install package -DskipTests"  correct command to build
> Ambari?
>
> Depends what do you want to do? For released versions, Apache Ambari
> already gives you the final binary bits, including RPM. So shouldn’t be
> needing to build.
>
>
>
> (From your very recent build)…
>
> > mvn -B -e clean install package rpm:rpm -Dbuild-rpm
> -Dpython.ver='python >= 2.6' –DskipTests
>
> If you are compiling outside Docker, then try installing “yum install -y
> python-setuptools”. My script might not be able to take the space in the
> “python >= 2.6”. But if you want, I can look into it.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Thursday, July 28, 2016 at 8:54 AM
>
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> Hi Bosco,
>
>
>
> Thanks for your reply!
>
>
>
> Your script did resolve the pre-requisite package issue.
>
>
>
> Step 1: run your script
>
> [INFO] Ambari Main ........................................ FAILURE [
> 0.521 s]
>
> [INFO] Apache Ambari Project POM .......................... SKIPPED
>
> [INFO] Ambari Web ......................................... SKIPPED
>
>
>
> Step 2:
> After running your script, then I ran "mvn clean install package
> -DskipTests"
>
>
>
> [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
> approved: 41 licence.
>
> [INFO]
>
> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (build-tarball) @
> ambari-groovy-shell ---
>
> [INFO] Assemblies have been skipped per configuration of the skipAssembly
> parameter.
>
> [INFO]
>
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ ambari-groovy-shell ---
>
> [INFO] Building jar:
> /edh_all_sources/edh_2.6.0/apache-ambari-2.2.2-src/ambari-shell/ambari-groovy-shell/target/ambari-groovy-shell-2.2.2.0.0.jar
>
> [INFO]
>
> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @
> ambari-groovy-shell ---
>
> [INFO] Assemblies have been skipped per configuration of the skipAssembly
> parameter.
>
> [INFO]
>
> [INFO] --- spring-boot-maven-plugin:1.0.2.RELEASE:repackage (default) @
> ambari-groovy-shell ---
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 2.093 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.070 s]
>
> [INFO] Ambari Web ......................................... SUCCESS [04:34
> min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 1.108 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [05:33
> min]
>
> [INFO] ambari-metrics ..................................... SUCCESS [
> 0.455 s]
>
> [INFO] Ambari Metrics Common .............................. SUCCESS [
> 1.205 s]
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
> 1.972 s]
>
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
> 1.061 s]
>
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
> 1.699 s]
>
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
> 2.077 s]
>
> [INFO] Ambari Metrics Collector ........................... SUCCESS [
> 17.234 s]
>
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
> 8.011 s]
>
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
> 8.841 s]
>
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [01:36
> min]
>
> [INFO] Ambari Server ...................................... SUCCESS [02:40
> min]
>
> [INFO] Ambari Agent ....................................... SUCCESS [
> 1.988 s]
>
> [INFO] Ambari Client ...................................... SUCCESS [
> 0.030 s]
>
> [INFO] Ambari Python Client ............................... SUCCESS [
> 0.923 s]
>
> [INFO] Ambari Groovy Client ............................... SUCCESS [01:32
> min]
>
> [INFO] Ambari Shell ....................................... SUCCESS [
> 0.035 s]
>
> [INFO] Ambari Python Shell ................................ SUCCESS [
> 0.361 s]
>
> [INFO] Ambari Groovy Shell ................................ SUCCESS [02:26
> min]
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 19:11 min
>
> [INFO] Finished at: 2016-07-28T23:46:04+08:00
>
> [INFO] Final Memory: 358M/3392M
>
> [INFO]
> ------------------------------------------------------------------------
>
>
>
> Its result looks good!
>
>
>
> Is "mvn clean install package -DskipTests"  correct command to build
> Ambari?
>
>
>
> Regards
>
>
>
>
>
>
>
>
>
> On Thu, Jul 28, 2016 at 10:29 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Hi,
>
>
>
> Thanks!
>
>
>
>
>
> My current status as follows:
>
> *mvn clean && mvn -B -e clean install package rpm:rpm -Dbuild-rpm
> -Dpython.ver='python >= 2.6' -DskipTests*
>
>
>
> [INFO] RPM build errors:
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 3.747 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.345 s]
>
> [INFO] Ambari Web ......................................... SUCCESS [04:33
> min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 1.672 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [
> 19.573 s]
>
> [INFO] ambari-metrics ..................................... SUCCESS [
> 1.075 s]
>
> [INFO] Ambari Metrics Common .............................. SUCCESS [
> 1.200 s]
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
> 2.021 s]
>
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
> 1.500 s]
>
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
> 1.162 s]
>
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
> 2.073 s]
>
> [INFO] Ambari Metrics Collector ........................... SUCCESS [01:48
> min]
>
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
> 1.588 s]
>
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
> 9.783 s]
>
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [05:18
> min]
>
> [INFO] Ambari Server ...................................... SUCCESS [03:22
> min]
>
> [INFO] Ambari Agent ....................................... SUCCESS [
> 16.770 s]
>
> [INFO] Ambari Client ...................................... SUCCESS [
> 0.496 s]
>
> [INFO] Ambari Python Client ............................... FAILURE [
> 1.067 s]
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 16:06 min
>
> [INFO] Finished at: 2016-07-28T22:23:55+08:00
>
> [INFO] Final Memory: 335M/3132M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project
> python-client: RPM build execution returned: '1' executing '/bin/sh -c cd
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
> && rpmbuild -bb --buildroot
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
> --target x86_64-redhat-linux python-client.spec' -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
> project python-client: RPM build execution returned: '1' executing '/bin/sh
> -c cd
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
> && rpmbuild -bb --buildroot
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
> --target x86_64-redhat-linux python-client.spec'
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
> execution returned: '1' executing '/bin/sh -c cd
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
> && rpmbuild -bb --buildroot
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
> --target x86_64-redhat-linux python-client.spec'
>
> at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)
>
> at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> [ERROR]
>
> [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 <goals> -rf :python-client
>
>
>
>
>
>
>
> On Thu, Jul 28, 2016 at 8:42 PM, Don Bosco Durai <bo...@apache.org> wrote:
>
> Ascot
>
>
>
> Would you be able to use Dockers to build Ambari? I have uploaded a script
> to this JIRA https://issues.apache.org/jira/browse/AMBARI-17944
>
>
>
> If you are using CentOS, then you would have to install Dockers. And then
> copy the script from the JIRA to the root folder of your Ambari source. You
> might need to chmod a+x to the script.
>
>
>
> When the first time you run the script, it will create the build the image
> and run it. Next time onwards, it will just run it.
>
>
>
> Give a try and let me know if it works for you.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Thursday, July 28, 2016 at 3:29 AM
>
>
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> *Hi,*
>
>
>
> *Thanks for your reply!!*
>
> *Just tried ur command, can get thru *[INFO] Ambari Web
> ......................................... SUCCESS [04:52 min]
>
>
>
> *Looks like " -Dstack.distribution" must be specified.Moving on *ambari-metrics
> now.
>
> Regards
>
>
>
> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
> >= 2.6' -Dstack.distribution=HDP*
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 7.205 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.297 s]
>
> [INFO] Ambari Web ......................................... SUCCESS [04:52
> min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 2.297 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [
> 19.035 s]
>
> [INFO] ambari-metrics ..................................... FAILURE [
> 0.174 s]
>
>
>
> On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <mi...@gmail.com> wrote:
>
> This is what I run on my machine:
>
>
>
> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
> >= 2.6' -Dstack.distribution=HDP
>
>
>
> Your error seems to be something related to npm since I see an error on
> lstat package.json
>
>
>
> May be try cleaning the npm cache under ambari-web:
>
> Go to ambari-src-folder/ambari-web and run the command npm cache clean
>
> Go back to ambari-src-folder and run the build command again?
>
>
>
> On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Found error in log
>
> 50462 silly gunzTarPerm extractEntry .npmignore
>
> 50463 silly gunzTarPerm extractEntry index.js
>
> 50464 silly gunzTarPerm extractEntry .npmignore
>
> 50465 silly gunzTarPerm extractEntry index.js
>
> 50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>
> 50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>
> 50468 verbose about to build
> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>
> 50469
> info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
> unbuild
>
> 50470 info preuninstall connect@2.12.0
>
> 50471 error Error: ENOENT, lstat
> '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'
>
> 50472 error If you need help, you may report this log at:
>
> 50472 error     <http://github.com/isaacs/npm/issues>
>
> 50472 error or email it to:
>
> 50472 error     <np...@googlegroups.com>
>
> 50473 error System Linux 3.10.0-327.4.4.el7.x86_64
>
> 50474 error command "node" "/usr/bin/npm" "install"
>
> 50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web
>
> 50476 error node -v v0.10.42
>
> 50477 error npm -v 1.3.6
>
> 50478 error path
> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>
> 50479 error fstream_path
> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>
> 50480 error fstream_type File
>
> 50481 error fstream_class FileWriter
>
> 50482 error code ENOENT
>
> 50483 error errno 34
>
> 50484 error fstream_stack
> /usr/lib/node_modules/fstream/lib/writer.js:284:26
>
> 50484 error fstream_stack Object.oncomplete (fs.js:108:15)
>
> 50485 verbose exit [ 34, true ]
>
>
>
>
>
>
>
> On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com> wrote:
>
> By the way, below are my steps:
>
> Please let me know if correct or not, many thanks!
>
> ---------------
>
> tar xfvz apache-ambari-2.2.2-src.tar.gz
>
> cd apache-ambari-2.2.2-src
>
> *mvn clean  *
>
> *pushd ambari-metrics  *
>
> *mvn versions:set -DnewVersion=2.2.2.1 *
>
> *popd  *
>
> *mvn versions:set -DnewVersion=2.2.2.1  *
>
>
> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl -e*---------------
>
>
>
> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com> wrote:
>
> My OS is CentOS 7:
>
>
> $node --version
>
> v6.3.0
>
>
>
> $ npm --version
>
> 3.10.5
>
>
>
> $ brunch --version
>
> 2.8.2
>
>
>
> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
> wrote:
>
> I would assume mvn to install the required version of node, npm and brunch.
>
>
>
> This is what I have on my environment (which does mvn builds without any
> issues):
>
> bash-3.2$ node --version
>
> v0.10.39
>
> bash-3.2$ npm --version
>
> 1.4.28
>
> bash-3.2$ brunch --version
>
> 1.8.5
>
>
>
> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:
>
>
> Hi,
>
>
>
> Thanks for your reply!
>
>
>
> Tried the following:
>
> (step 1)
> npm install -g brunch
>
> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>
> /usr/lib
>
> └─┬ brunch@2.8.2
>
>   ├─┬ check-dependencies@0.12.0
>
>   │ └─┬ bower-config@1.4.0
>
>   │   └── graceful-fs@4.1.5
>
>   └─┬ deppack@0.6.1
>
>     └─┬ node-browser-modules@0.1.0
>
>       └── process@0.11.6
> npm WARN optional Skipping failed optional dependency
> /brunch/chokidar/fsevents:
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@1.0.14
>
>
>
> (step 2)
>
> tar xfvz apache-ambari-2.2.2-src.tar.gz
>
> cd apache-ambari-2.2.2-src
>
> *mvn clean*
>
> *mvn versions:set -DnewVersion=2.2.2.1*
>
> *pushd ambari-metrics*
>
> *mvn versions:set -DnewVersion=2.2.2.1*
>
> *popd*
>
> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>
>
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
> [ERROR]
>
> [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 <goals> -rf :ambari-web
>
>
>
> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com> wrote:
>
> See if *npm install -g brunch* would fix the issue?
>
>
>
> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Hi
> thanks for your reply!
>
> Added -e
>
>
>
>
>
> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@0.2.1
>
> npm WARN Ambari@2.1.3 No license field.
>
> [INFO]
>
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>
> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
> order
>
> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
> execute `npm install` to install brunch plugins. SyntaxError: Setter must
> have exactly one formal parameter.
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 6.635 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.371 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:46
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 02:53 min
>
> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>
> [INFO] Final Memory: 33M/1036M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
>
>
> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
> wrote:
>
> Hi there-
>
>
>
> Adding -e to the mvn command will give you more output on your error.
>
>
>
> Thanks.
>
>
>
> Amanda
>
>
>
> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com> wrote:
>
> as root (also tried as ordinary user)
>
>
>
> Refer to the error below, is it about some default settings must be
> adjusted in pom?
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
>
>
>
>
> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
> wrote:
>
> As which user are you running this build? I was having issues when I ran
> the build as user “root”.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Tuesday, July 26, 2016 at 6:07 AM
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> my mvn is 3.3.9,  will this be an issue?
>
>
>
>
>
> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Hi,
>
>
>
>
>
> Please help!
>
> I am trying to build Ambari 2.2.2, got the following error as follows:
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [04:51
> min]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 4.361 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:55
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [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 <goals> -rf :ambari-web
>
>
>
> Any ideas how to resolve it?
>
> Regards
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Thanks,
>
>
>
> Amanda Moran
>
>
>
>
>
>
>
> --
>
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>
>
>
>
>
>
> --
>
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>
>
>
>
>
>
>
>
>
>
> --
>
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>
>
>
>
>
>

Re: Build Error

Posted by Don Bosco Durai <bo...@apache.org>.
> Step 1: run your script

> [INFO] Ambari Main ........................................ FAILURE [  0.521 s]

My script should have done the complete build. What is the error you are getting?

 

> Is "mvn clean install package -DskipTests"  correct command to build Ambari?

Depends what do you want to do? For released versions, Apache Ambari already gives you the final binary bits, including RPM. So shouldn’t be needing to build.

 

(From your very recent build)…

> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' –DskipTests

If you are compiling outside Docker, then try installing “yum install -y python-setuptools”. My script might not be able to take the space in the “python >= 2.6”. But if you want, I can look into it.

 

Thanks

 

Bosco

 

 

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Thursday, July 28, 2016 at 8:54 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi Bosco,

 

Thanks for your reply!

 

Your script did resolve the pre-requisite package issue.

 

Step 1: run your script

[INFO] Ambari Main ........................................ FAILURE [  0.521 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED

 

Step 2: 
After running your script, then I ran "mvn clean install package -DskipTests"

 

[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 41 licence.

[INFO] 

[INFO] --- maven-assembly-plugin:2.2-beta-5:single (build-tarball) @ ambari-groovy-shell ---

[INFO] Assemblies have been skipped per configuration of the skipAssembly parameter.

[INFO] 

[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ ambari-groovy-shell ---

[INFO] Building jar: /edh_all_sources/edh_2.6.0/apache-ambari-2.2.2-src/ambari-shell/ambari-groovy-shell/target/ambari-groovy-shell-2.2.2.0.0.jar

[INFO] 

[INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ ambari-groovy-shell ---

[INFO] Assemblies have been skipped per configuration of the skipAssembly parameter.

[INFO] 

[INFO] --- spring-boot-maven-plugin:1.0.2.RELEASE:repackage (default) @ ambari-groovy-shell ---

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [  2.093 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.070 s]

[INFO] Ambari Web ......................................... SUCCESS [04:34 min]

[INFO] Ambari Views ....................................... SUCCESS [  1.108 s]

[INFO] Ambari Admin View .................................. SUCCESS [05:33 min]

[INFO] ambari-metrics ..................................... SUCCESS [  0.455 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [  1.205 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  1.972 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  1.061 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  1.699 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.077 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [ 17.234 s]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [  8.011 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [  8.841 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [01:36 min]

[INFO] Ambari Server ...................................... SUCCESS [02:40 min]

[INFO] Ambari Agent ....................................... SUCCESS [  1.988 s]

[INFO] Ambari Client ...................................... SUCCESS [  0.030 s]

[INFO] Ambari Python Client ............................... SUCCESS [  0.923 s]

[INFO] Ambari Groovy Client ............................... SUCCESS [01:32 min]

[INFO] Ambari Shell ....................................... SUCCESS [  0.035 s]

[INFO] Ambari Python Shell ................................ SUCCESS [  0.361 s]

[INFO] Ambari Groovy Shell ................................ SUCCESS [02:26 min]

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 19:11 min

[INFO] Finished at: 2016-07-28T23:46:04+08:00

[INFO] Final Memory: 358M/3392M

[INFO] ------------------------------------------------------------------------

 

Its result looks good!

 

Is "mvn clean install package -DskipTests"  correct command to build Ambari?

 

Regards

 

 

 

 

On Thu, Jul 28, 2016 at 10:29 PM, Ascot Moss <as...@gmail.com> wrote:

Hi,

 

Thanks!

 

 

My current status as follows:

mvn clean && mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' -DskipTests

 

[INFO] RPM build errors:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [  3.747 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.345 s]

[INFO] Ambari Web ......................................... SUCCESS [04:33 min]

[INFO] Ambari Views ....................................... SUCCESS [  1.672 s]

[INFO] Ambari Admin View .................................. SUCCESS [ 19.573 s]

[INFO] ambari-metrics ..................................... SUCCESS [  1.075 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [  1.200 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  2.021 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  1.500 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  1.162 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.073 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [01:48 min]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.588 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [  9.783 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [05:18 min]

[INFO] Ambari Server ...................................... SUCCESS [03:22 min]

[INFO] Ambari Agent ....................................... SUCCESS [ 16.770 s]

[INFO] Ambari Client ...................................... SUCCESS [  0.496 s]

[INFO] Ambari Python Client ............................... FAILURE [  1.067 s]

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 16:06 min

[INFO] Finished at: 2016-07-28T22:23:55+08:00

[INFO] Final Memory: 335M/3132M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec' -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project python-client: RPM build execution returned: '1' executing '/bin/sh -c cd /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build execution returned: '1' executing '/bin/sh -c cd /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS && rpmbuild -bb --buildroot /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot --define '_topdir /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client' --target x86_64-redhat-linux python-client.spec'

at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)

at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

[ERROR] 

[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 <goals> -rf :python-client

 

 

 

On Thu, Jul 28, 2016 at 8:42 PM, Don Bosco Durai <bo...@apache.org> wrote:

Ascot

 

Would you be able to use Dockers to build Ambari? I have uploaded a script to this JIRA https://issues.apache.org/jira/browse/AMBARI-17944

 

If you are using CentOS, then you would have to install Dockers. And then copy the script from the JIRA to the root folder of your Ambari source. You might need to chmod a+x to the script.

 

When the first time you run the script, it will create the build the image and run it. Next time onwards, it will just run it.

 

Give a try and let me know if it works for you.

 

Thanks

 

Bosco

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Thursday, July 28, 2016 at 3:29 AM


To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi,

 

Thanks for your reply!!

Just tried ur command, can get thru [INFO] Ambari Web ......................................... SUCCESS [04:52 min]

Looks like " -Dstack.distribution" must be specified.

Moving on ambari-metrics now.

Regards



mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' -Dstack.distribution=HDP

[INFO] Ambari Main ........................................ SUCCESS [  7.205 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.297 s]

[INFO] Ambari Web ......................................... SUCCESS [04:52 min]

[INFO] Ambari Views ....................................... SUCCESS [  2.297 s]

[INFO] Ambari Admin View .................................. SUCCESS [ 19.035 s]

[INFO] ambari-metrics ..................................... FAILURE [  0.174 s]

 

On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <mi...@gmail.com> wrote:

This is what I run on my machine:

 

mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' -Dstack.distribution=HDP

 

Your error seems to be something related to npm since I see an error on lstat package.json

 

May be try cleaning the npm cache under ambari-web:

Go to ambari-src-folder/ambari-web and run the command npm cache clean

Go back to ambari-src-folder and run the build command again?

 

On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com> wrote:

Found error in log

50462 silly gunzTarPerm extractEntry .npmignore

50463 silly gunzTarPerm extractEntry index.js

50464 silly gunzTarPerm extractEntry .npmignore

50465 silly gunzTarPerm extractEntry index.js

50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0

50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0

50468 verbose about to build /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect

50469 info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect unbuild

50470 info preuninstall connect@2.12.0

50471 error Error: ENOENT, lstat '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'

50472 error If you need help, you may report this log at:

50472 error     <http://github.com/isaacs/npm/issues>

50472 error or email it to:

50472 error     <np...@googlegroups.com>

50473 error System Linux 3.10.0-327.4.4.el7.x86_64

50474 error command "node" "/usr/bin/npm" "install"

50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web

50476 error node -v v0.10.42

50477 error npm -v 1.3.6

50478 error path /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json

50479 error fstream_path /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json

50480 error fstream_type File

50481 error fstream_class FileWriter

50482 error code ENOENT

50483 error errno 34

50484 error fstream_stack /usr/lib/node_modules/fstream/lib/writer.js:284:26

50484 error fstream_stack Object.oncomplete (fs.js:108:15)

50485 verbose exit [ 34, true ]

 

 

 

On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com> wrote:

By the way, below are my steps:

Please let me know if correct or not, many thanks!

---------------

tar xfvz apache-ambari-2.2.2-src.tar.gz

cd apache-ambari-2.2.2-src

mvn clean  

pushd ambari-metrics  

mvn versions:set -DnewVersion=2.2.2.1 

popd  

mvn versions:set -DnewVersion=2.2.2.1  

mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e
---------------

 

On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com> wrote:

My OS is CentOS 7:


$node --version

v6.3.0

 

$ npm --version

3.10.5

 

$ brunch --version

2.8.2

 

On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com> wrote:

I would assume mvn to install the required version of node, npm and brunch.

 

This is what I have on my environment (which does mvn builds without any issues):

bash-3.2$ node --version

v0.10.39

bash-3.2$ npm --version

1.4.28

bash-3.2$ brunch --version

1.8.5

 

On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:


Hi,

 

Thanks for your reply!

 

Tried the following:

(step 1)
npm install -g brunch

/usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch

/usr/lib

└─┬ brunch@2.8.2 

  ├─┬ check-dependencies@0.12.0

  │ └─┬ bower-config@1.4.0

  │   └── graceful-fs@4.1.5 

  └─┬ deppack@0.6.1

    └─┬ node-browser-modules@0.1.0

      └── process@0.11.6 
npm WARN optional Skipping failed optional dependency /brunch/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14

 

(step 2)

tar xfvz apache-ambari-2.2.2-src.tar.gz

cd apache-ambari-2.2.2-src

mvn clean

mvn versions:set -DnewVersion=2.2.2.1

pushd ambari-metrics

mvn versions:set -DnewVersion=2.2.2.1

popd

mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e

 

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

[ERROR] 

[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 <goals> -rf :ambari-web

 

On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com> wrote:

See if npm install -g brunch would fix the issue?

 

On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:

Hi 
thanks for your reply!

Added -e

 

 

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:

npm WARN notsup Not compatible with your operating system or architecture: fsevents@0.2.1

npm WARN Ambari@2.1.3 No license field.

[INFO] 

[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---

28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: perhaps you meant defaultExtensions

28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps you meant defaultExtensions

28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant order

28 Jul 07:46:20 - error: Initialization error -  You probably need to execute `npm install` to install brunch plugins. SyntaxError: Setter must have exactly one formal parameter. 

Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [  6.635 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.371 s]

[INFO] Ambari Web ......................................... FAILURE [02:46 min]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 02:53 min

[INFO] Finished at: 2016-07-28T07:46:20+08:00

[INFO] Final Memory: 33M/1036M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

 

On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com> wrote:

Hi there-

 

Adding -e to the mvn command will give you more output on your error. 

 

Thanks. 

 

Amanda 

 

On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com> wrote:

as root (also tried as ordinary user)

 

Refer to the error below, is it about some default settings must be adjusted in pom?

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

 

 

On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org> wrote:

As which user are you running this build? I was having issues when I ran the build as user “root”.

 

Thanks

 

Bosco

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Tuesday, July 26, 2016 at 6:07 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

my mvn is 3.3.9,  will this be an issue?

 

 

On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:

Hi,

 

 

Please help!

I am trying to build Ambari 2.2.2, got the following error as follows:

Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [04:51 min]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  4.361 s]

[INFO] Ambari Web ......................................... FAILURE [02:55 min]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [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 <goals> -rf :ambari-web

 

Any ideas how to resolve it?

Regards

 

 

 

 

 



 

-- 

Thanks, 

 

Amanda Moran

 



 

-- 

Mithun Mathew (Matt)

www.linkedin.com/in/mithunmatt/
 

 

-- 

Mithun Mathew (Matt)

www.linkedin.com/in/mithunmatt/
 

 

 

 

-- 

Mithun Mathew (Matt)

www.linkedin.com/in/mithunmatt/

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
if I run

mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >=
2.6' -DskipTests
still have error as follows:

[INFO]

[INFO] RPM build errors:

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [
2.845 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.312 s]

[INFO] Ambari Web ......................................... SUCCESS [04:32
min]

[INFO] Ambari Views ....................................... SUCCESS [
1.276 s]

[INFO] Ambari Admin View .................................. SUCCESS [05:20
min]

[INFO] ambari-metrics ..................................... SUCCESS [
15.517 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [
16.003 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
17.095 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
16.327 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
15.789 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
17.211 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [01:57
min]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [
2.277 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [
9.874 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [11:15
min]

[INFO] Ambari Server ...................................... SUCCESS [05:09
min]

[INFO] Ambari Agent ....................................... SUCCESS [
17.034 s]

[INFO] Ambari Client ...................................... SUCCESS [
0.373 s]

[INFO] Ambari Python Client ............................... FAILURE [
1.939 s]

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 30:29 min

[INFO] Finished at: 2016-07-29T00:23:50+08:00

[INFO] Final Memory: 338M/3392M

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project
python-client: RPM build execution returned: '1' executing '/bin/sh -c cd
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec' -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
project python-client: RPM build execution returned: '1' executing '/bin/sh
-c cd
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec'

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
execution returned: '1' executing '/bin/sh -c cd
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec'

at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)

at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)

at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

[ERROR]

[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 <goals> -rf :python-client



On Thu, Jul 28, 2016 at 11:54 PM, Ascot Moss <as...@gmail.com> wrote:

> Hi Bosco,
>
> Thanks for your reply!
>
> Your script did resolve the pre-requisite package issue.
>
> Step 1: run your script
>
> [INFO] Ambari Main ........................................ FAILURE [
> 0.521 s]
>
> [INFO] Apache Ambari Project POM .......................... SKIPPED
>
> [INFO] Ambari Web ......................................... SKIPPED
>
>
> Step 2:
> After running your script, then I ran "mvn clean install package
> -DskipTests"
>
>
> [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
> approved: 41 licence.
>
> [INFO]
>
> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (build-tarball) @
> ambari-groovy-shell ---
>
> [INFO] Assemblies have been skipped per configuration of the skipAssembly
> parameter.
>
> [INFO]
>
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ ambari-groovy-shell ---
>
> [INFO] Building jar:
> /edh_all_sources/edh_2.6.0/apache-ambari-2.2.2-src/ambari-shell/ambari-groovy-shell/target/ambari-groovy-shell-2.2.2.0.0.jar
>
> [INFO]
>
> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @
> ambari-groovy-shell ---
>
> [INFO] Assemblies have been skipped per configuration of the skipAssembly
> parameter.
>
> [INFO]
>
> [INFO] --- spring-boot-maven-plugin:1.0.2.RELEASE:repackage (default) @
> ambari-groovy-shell ---
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 2.093 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.070 s]
>
> [INFO] Ambari Web ......................................... SUCCESS [04:34
> min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 1.108 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [05:33
> min]
>
> [INFO] ambari-metrics ..................................... SUCCESS [
> 0.455 s]
>
> [INFO] Ambari Metrics Common .............................. SUCCESS [
> 1.205 s]
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
> 1.972 s]
>
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
> 1.061 s]
>
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
> 1.699 s]
>
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
> 2.077 s]
>
> [INFO] Ambari Metrics Collector ........................... SUCCESS [
> 17.234 s]
>
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
> 8.011 s]
>
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
> 8.841 s]
>
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [01:36
> min]
>
> [INFO] Ambari Server ...................................... SUCCESS [02:40
> min]
>
> [INFO] Ambari Agent ....................................... SUCCESS [
> 1.988 s]
>
> [INFO] Ambari Client ...................................... SUCCESS [
> 0.030 s]
>
> [INFO] Ambari Python Client ............................... SUCCESS [
> 0.923 s]
>
> [INFO] Ambari Groovy Client ............................... SUCCESS [01:32
> min]
>
> [INFO] Ambari Shell ....................................... SUCCESS [
> 0.035 s]
>
> [INFO] Ambari Python Shell ................................ SUCCESS [
> 0.361 s]
>
> [INFO] Ambari Groovy Shell ................................ SUCCESS [02:26
> min]
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 19:11 min
>
> [INFO] Finished at: 2016-07-28T23:46:04+08:00
>
> [INFO] Final Memory: 358M/3392M
>
> [INFO]
> ------------------------------------------------------------------------
>
>
> Its result looks good!
>
>
> Is "mvn clean install package -DskipTests"  correct command to build
> Ambari?
>
>
> Regards
>
>
>
>
>
> On Thu, Jul 28, 2016 at 10:29 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> Hi,
>>
>> Thanks!
>>
>>
>> My current status as follows:
>>
>> *mvn clean && mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>> -Dpython.ver='python >= 2.6' **-DskipTests*
>>
>> [INFO] RPM build errors:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ SUCCESS [
>> 3.747 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 0.345 s]
>>
>> [INFO] Ambari Web ......................................... SUCCESS
>> [04:33 min]
>>
>> [INFO] Ambari Views ....................................... SUCCESS [
>> 1.672 s]
>>
>> [INFO] Ambari Admin View .................................. SUCCESS [
>> 19.573 s]
>>
>> [INFO] ambari-metrics ..................................... SUCCESS [
>> 1.075 s]
>>
>> [INFO] Ambari Metrics Common .............................. SUCCESS [
>> 1.200 s]
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
>> 2.021 s]
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
>> 1.500 s]
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
>> 1.162 s]
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
>> 2.073 s]
>>
>> [INFO] Ambari Metrics Collector ........................... SUCCESS
>> [01:48 min]
>>
>> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
>> 1.588 s]
>>
>> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
>> 9.783 s]
>>
>> [INFO] Ambari Metrics Assembly ............................ SUCCESS
>> [05:18 min]
>>
>> [INFO] Ambari Server ...................................... SUCCESS
>> [03:22 min]
>>
>> [INFO] Ambari Agent ....................................... SUCCESS [
>> 16.770 s]
>>
>> [INFO] Ambari Client ...................................... SUCCESS [
>> 0.496 s]
>>
>> [INFO] Ambari Python Client ............................... FAILURE [
>> 1.067 s]
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Total time: 16:06 min
>>
>> [INFO] Finished at: 2016-07-28T22:23:55+08:00
>>
>> [INFO] Final Memory: 335M/3132M
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project
>> python-client: RPM build execution returned: '1' executing '/bin/sh -c cd
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
>> && rpmbuild -bb --buildroot
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
>> --define '_topdir
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
>> --target x86_64-redhat-linux python-client.spec' -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
>> project python-client: RPM build execution returned: '1' executing '/bin/sh
>> -c cd
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
>> && rpmbuild -bb --buildroot
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
>> --define '_topdir
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
>> --target x86_64-redhat-linux python-client.spec'
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>
>> at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:497)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
>> execution returned: '1' executing '/bin/sh -c cd
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
>> && rpmbuild -bb --buildroot
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
>> --define '_topdir
>> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
>> --target x86_64-redhat-linux python-client.spec'
>>
>> at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)
>>
>> at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)
>>
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>
>> ... 20 more
>>
>> [ERROR]
>>
>> [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 <goals> -rf :python-client
>>
>>
>>
>>
>> On Thu, Jul 28, 2016 at 8:42 PM, Don Bosco Durai <bo...@apache.org>
>> wrote:
>>
>>> Ascot
>>>
>>>
>>>
>>> Would you be able to use Dockers to build Ambari? I have uploaded a
>>> script to this JIRA https://issues.apache.org/jira/browse/AMBARI-17944
>>>
>>>
>>>
>>> If you are using CentOS, then you would have to install Dockers. And
>>> then copy the script from the JIRA to the root folder of your Ambari
>>> source. You might need to chmod a+x to the script.
>>>
>>>
>>>
>>> When the first time you run the script, it will create the build the
>>> image and run it. Next time onwards, it will just run it.
>>>
>>>
>>>
>>> Give a try and let me know if it works for you.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Bosco
>>>
>>>
>>>
>>>
>>>
>>> *From: *Ascot Moss <as...@gmail.com>
>>> *Reply-To: *<us...@ambari.apache.org>
>>> *Date: *Thursday, July 28, 2016 at 3:29 AM
>>>
>>> *To: *<us...@ambari.apache.org>
>>> *Subject: *Re: Build Error
>>>
>>>
>>>
>>> *Hi,*
>>>
>>>
>>>
>>> *Thanks for your reply!!*
>>>
>>> *Just tried ur command, can get thru *[INFO] Ambari Web
>>> ......................................... SUCCESS [04:52 min]
>>>
>>>
>>>
>>> *Looks like " -Dstack.distribution" must be specified.Moving on *ambari-metrics
>>> now.
>>>
>>> Regards
>>>
>>>
>>>
>>> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm
>>> -Dpython.ver='python >= 2.6' -Dstack.distribution=HDP*
>>>
>>> [INFO] Ambari Main ........................................ SUCCESS [
>>> 7.205 s]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>> 0.297 s]
>>>
>>> [INFO] Ambari Web ......................................... SUCCESS
>>> [04:52 min]
>>>
>>> [INFO] Ambari Views ....................................... SUCCESS [
>>> 2.297 s]
>>>
>>> [INFO] Ambari Admin View .................................. SUCCESS [
>>> 19.035 s]
>>>
>>> [INFO] ambari-metrics ..................................... FAILURE [
>>> 0.174 s]
>>>
>>>
>>>
>>> On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <mi...@gmail.com>
>>> wrote:
>>>
>>> This is what I run on my machine:
>>>
>>>
>>>
>>> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
>>> >= 2.6' -Dstack.distribution=HDP
>>>
>>>
>>>
>>> Your error seems to be something related to npm since I see an error on
>>> lstat package.json
>>>
>>>
>>>
>>> May be try cleaning the npm cache under ambari-web:
>>>
>>> Go to ambari-src-folder/ambari-web and run the command npm cache clean
>>>
>>> Go back to ambari-src-folder and run the build command again?
>>>
>>>
>>>
>>> On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>> Found error in log
>>>
>>> 50462 silly gunzTarPerm extractEntry .npmignore
>>>
>>> 50463 silly gunzTarPerm extractEntry index.js
>>>
>>> 50464 silly gunzTarPerm extractEntry .npmignore
>>>
>>> 50465 silly gunzTarPerm extractEntry index.js
>>>
>>> 50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>>>
>>> 50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>>>
>>> 50468 verbose about to build
>>> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>>>
>>> 50469
>>> info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>>> unbuild
>>>
>>> 50470 info preuninstall connect@2.12.0
>>>
>>> 50471 error Error: ENOENT, lstat
>>> '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'
>>>
>>> 50472 error If you need help, you may report this log at:
>>>
>>> 50472 error     <http://github.com/isaacs/npm/issues>
>>>
>>> 50472 error or email it to:
>>>
>>> 50472 error     <np...@googlegroups.com>
>>>
>>> 50473 error System Linux 3.10.0-327.4.4.el7.x86_64
>>>
>>> 50474 error command "node" "/usr/bin/npm" "install"
>>>
>>> 50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web
>>>
>>> 50476 error node -v v0.10.42
>>>
>>> 50477 error npm -v 1.3.6
>>>
>>> 50478 error path
>>> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>>>
>>> 50479 error fstream_path
>>> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>>>
>>> 50480 error fstream_type File
>>>
>>> 50481 error fstream_class FileWriter
>>>
>>> 50482 error code ENOENT
>>>
>>> 50483 error errno 34
>>>
>>> 50484 error fstream_stack
>>> /usr/lib/node_modules/fstream/lib/writer.js:284:26
>>>
>>> 50484 error fstream_stack Object.oncomplete (fs.js:108:15)
>>>
>>> 50485 verbose exit [ 34, true ]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>> By the way, below are my steps:
>>>
>>> Please let me know if correct or not, many thanks!
>>>
>>> ---------------
>>>
>>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>>
>>> cd apache-ambari-2.2.2-src
>>>
>>> *mvn clean  *
>>>
>>> *pushd ambari-metrics  *
>>>
>>> *mvn versions:set -DnewVersion=2.2.2.1 *
>>>
>>> *popd  *
>>>
>>> *mvn versions:set -DnewVersion=2.2.2.1  *
>>>
>>>
>>> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
>>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*---------------
>>>
>>>
>>>
>>> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>> My OS is CentOS 7:
>>>
>>>
>>> $node --version
>>>
>>> v6.3.0
>>>
>>>
>>>
>>> $ npm --version
>>>
>>> 3.10.5
>>>
>>>
>>>
>>> $ brunch --version
>>>
>>> 2.8.2
>>>
>>>
>>>
>>> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
>>> wrote:
>>>
>>> I would assume mvn to install the required version of node, npm and
>>> brunch.
>>>
>>>
>>>
>>> This is what I have on my environment (which does mvn builds without any
>>> issues):
>>>
>>> bash-3.2$ node --version
>>>
>>> v0.10.39
>>>
>>> bash-3.2$ npm --version
>>>
>>> 1.4.28
>>>
>>> bash-3.2$ brunch --version
>>>
>>> 1.8.5
>>>
>>>
>>>
>>> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>>
>>> Hi,
>>>
>>>
>>>
>>> Thanks for your reply!
>>>
>>>
>>>
>>> Tried the following:
>>>
>>> (step 1)
>>> npm install -g brunch
>>>
>>> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>>>
>>> /usr/lib
>>>
>>> └─┬ brunch@2.8.2
>>>
>>>   ├─┬ check-dependencies@0.12.0
>>>
>>>   │ └─┬ bower-config@1.4.0
>>>
>>>   │   └── graceful-fs@4.1.5
>>>
>>>   └─┬ deppack@0.6.1
>>>
>>>     └─┬ node-browser-modules@0.1.0
>>>
>>>       └── process@0.11.6
>>> npm WARN optional Skipping failed optional dependency
>>> /brunch/chokidar/fsevents:
>>> npm WARN notsup Not compatible with your operating system or
>>> architecture: fsevents@1.0.14
>>>
>>>
>>>
>>> (step 2)
>>>
>>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>>
>>> cd apache-ambari-2.2.2-src
>>>
>>> *mvn clean*
>>>
>>> *mvn versions:set -DnewVersion=2.2.2.1*
>>>
>>> *pushd ambari-metrics*
>>>
>>> *mvn versions:set -DnewVersion=2.2.2.1*
>>>
>>> *popd*
>>>
>>> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
>>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>>
>>>
>>>
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>> value: 1) -> [Help 1]
>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>> execution failed.
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>
>>> ... 20 more
>>>
>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>>> an error: 1 (Exit value: 1)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>
>>> ... 22 more
>>>
>>> [ERROR]
>>>
>>> [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 <goals> -rf :ambari-web
>>>
>>>
>>>
>>> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com>
>>> wrote:
>>>
>>> See if *npm install -g brunch* would fix the issue?
>>>
>>>
>>>
>>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>> Hi
>>> thanks for your reply!
>>>
>>> Added -e
>>>
>>>
>>>
>>>
>>>
>>> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>>>
>>> npm WARN notsup Not compatible with your operating system or
>>> architecture: fsevents@0.2.1
>>>
>>> npm WARN Ambari@2.1.3 No license field.
>>>
>>> [INFO]
>>>
>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>>>
>>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>>> perhaps you meant defaultExtensions
>>>
>>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
>>> you meant defaultExtensions
>>>
>>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
>>> order
>>>
>>> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
>>> execute `npm install` to install brunch plugins. SyntaxError: Setter must
>>> have exactly one formal parameter.
>>>
>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>> trace.
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Reactor Summary:
>>>
>>> [INFO]
>>>
>>> [INFO] Ambari Main ........................................ SUCCESS [
>>> 6.635 s]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>> 0.371 s]
>>>
>>> [INFO] Ambari Web ......................................... FAILURE
>>> [02:46 min]
>>>
>>> [INFO] Ambari Views ....................................... SKIPPED
>>>
>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>
>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>
>>> [INFO] Ambari Server ...................................... SKIPPED
>>>
>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>
>>> [INFO] Ambari Client ...................................... SKIPPED
>>>
>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>
>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>
>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Total time: 02:53 min
>>>
>>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>>
>>> [INFO] Final Memory: 33M/1036M
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>> value: 1) -> [Help 1]
>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>> execution failed.
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>
>>> ... 20 more
>>>
>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>>> an error: 1 (Exit value: 1)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>
>>> ... 22 more
>>>
>>>
>>>
>>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
>>> wrote:
>>>
>>> Hi there-
>>>
>>>
>>>
>>> Adding -e to the mvn command will give you more output on your error.
>>>
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> Amanda
>>>
>>>
>>>
>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>> as root (also tried as ordinary user)
>>>
>>>
>>>
>>> Refer to the error below, is it about some default settings must be
>>> adjusted in pom?
>>>
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>> value: 1) -> [Help 1]
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>>> wrote:
>>>
>>> As which user are you running this build? I was having issues when I ran
>>> the build as user “root”.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Bosco
>>>
>>>
>>>
>>>
>>>
>>> *From: *Ascot Moss <as...@gmail.com>
>>> *Reply-To: *<us...@ambari.apache.org>
>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>> *To: *<us...@ambari.apache.org>
>>> *Subject: *Re: Build Error
>>>
>>>
>>>
>>> my mvn is 3.3.9,  will this be an issue?
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>>
>>>
>>> Please help!
>>>
>>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>>
>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>> trace.
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Reactor Summary:
>>>
>>> [INFO]
>>>
>>> [INFO] Ambari Main ........................................ SUCCESS
>>> [04:51 min]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>> 4.361 s]
>>>
>>> [INFO] Ambari Web ......................................... FAILURE
>>> [02:55 min]
>>>
>>> [INFO] Ambari Views ....................................... SKIPPED
>>>
>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>
>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>
>>> [INFO] Ambari Server ...................................... SKIPPED
>>>
>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>
>>> [INFO] Ambari Client ...................................... SKIPPED
>>>
>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>
>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>
>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>
>>>
>>>
>>> Any ideas how to resolve it?
>>>
>>> Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Amanda Moran
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Mithun Mathew* (Matt)
>>>
>>>    - www.linkedin.com/in/mithunmatt/
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Mithun Mathew* (Matt)
>>>
>>>    - www.linkedin.com/in/mithunmatt/
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Mithun Mathew* (Matt)
>>>
>>>    - www.linkedin.com/in/mithunmatt/
>>>
>>>
>>>
>>
>>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
Hi Bosco,

Thanks for your reply!

Your script did resolve the pre-requisite package issue.

Step 1: run your script

[INFO] Ambari Main ........................................ FAILURE [
0.521 s]

[INFO] Apache Ambari Project POM .......................... SKIPPED

[INFO] Ambari Web ......................................... SKIPPED


Step 2:
After running your script, then I ran "mvn clean install package
-DskipTests"


[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 41 licence.

[INFO]

[INFO] --- maven-assembly-plugin:2.2-beta-5:single (build-tarball) @
ambari-groovy-shell ---

[INFO] Assemblies have been skipped per configuration of the skipAssembly
parameter.

[INFO]

[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ ambari-groovy-shell ---

[INFO] Building jar:
/edh_all_sources/edh_2.6.0/apache-ambari-2.2.2-src/ambari-shell/ambari-groovy-shell/target/ambari-groovy-shell-2.2.2.0.0.jar

[INFO]

[INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @
ambari-groovy-shell ---

[INFO] Assemblies have been skipped per configuration of the skipAssembly
parameter.

[INFO]

[INFO] --- spring-boot-maven-plugin:1.0.2.RELEASE:repackage (default) @
ambari-groovy-shell ---

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [
2.093 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.070 s]

[INFO] Ambari Web ......................................... SUCCESS [04:34
min]

[INFO] Ambari Views ....................................... SUCCESS [
1.108 s]

[INFO] Ambari Admin View .................................. SUCCESS [05:33
min]

[INFO] ambari-metrics ..................................... SUCCESS [
0.455 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [
1.205 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
1.972 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
1.061 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
1.699 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
2.077 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [
17.234 s]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [
8.011 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [
8.841 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [01:36
min]

[INFO] Ambari Server ...................................... SUCCESS [02:40
min]

[INFO] Ambari Agent ....................................... SUCCESS [
1.988 s]

[INFO] Ambari Client ...................................... SUCCESS [
0.030 s]

[INFO] Ambari Python Client ............................... SUCCESS [
0.923 s]

[INFO] Ambari Groovy Client ............................... SUCCESS [01:32
min]

[INFO] Ambari Shell ....................................... SUCCESS [
0.035 s]

[INFO] Ambari Python Shell ................................ SUCCESS [
0.361 s]

[INFO] Ambari Groovy Shell ................................ SUCCESS [02:26
min]

[INFO]
------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 19:11 min

[INFO] Finished at: 2016-07-28T23:46:04+08:00

[INFO] Final Memory: 358M/3392M

[INFO]
------------------------------------------------------------------------


Its result looks good!


Is "mvn clean install package -DskipTests"  correct command to build Ambari?


Regards





On Thu, Jul 28, 2016 at 10:29 PM, Ascot Moss <as...@gmail.com> wrote:

> Hi,
>
> Thanks!
>
>
> My current status as follows:
>
> *mvn clean && mvn -B -e clean install package rpm:rpm -Dbuild-rpm
> -Dpython.ver='python >= 2.6' **-DskipTests*
>
> [INFO] RPM build errors:
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 3.747 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.345 s]
>
> [INFO] Ambari Web ......................................... SUCCESS [04:33
> min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 1.672 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [
> 19.573 s]
>
> [INFO] ambari-metrics ..................................... SUCCESS [
> 1.075 s]
>
> [INFO] Ambari Metrics Common .............................. SUCCESS [
> 1.200 s]
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
> 2.021 s]
>
> [INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
> 1.500 s]
>
> [INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
> 1.162 s]
>
> [INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
> 2.073 s]
>
> [INFO] Ambari Metrics Collector ........................... SUCCESS [01:48
> min]
>
> [INFO] Ambari Metrics Monitor ............................. SUCCESS [
> 1.588 s]
>
> [INFO] Ambari Metrics Grafana ............................. SUCCESS [
> 9.783 s]
>
> [INFO] Ambari Metrics Assembly ............................ SUCCESS [05:18
> min]
>
> [INFO] Ambari Server ...................................... SUCCESS [03:22
> min]
>
> [INFO] Ambari Agent ....................................... SUCCESS [
> 16.770 s]
>
> [INFO] Ambari Client ...................................... SUCCESS [
> 0.496 s]
>
> [INFO] Ambari Python Client ............................... FAILURE [
> 1.067 s]
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 16:06 min
>
> [INFO] Finished at: 2016-07-28T22:23:55+08:00
>
> [INFO] Final Memory: 335M/3132M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project
> python-client: RPM build execution returned: '1' executing '/bin/sh -c cd
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
> && rpmbuild -bb --buildroot
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
> --target x86_64-redhat-linux python-client.spec' -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
> project python-client: RPM build execution returned: '1' executing '/bin/sh
> -c cd
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
> && rpmbuild -bb --buildroot
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
> --target x86_64-redhat-linux python-client.spec'
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
> execution returned: '1' executing '/bin/sh -c cd
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
> && rpmbuild -bb --buildroot
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
> --define '_topdir
> /user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
> --target x86_64-redhat-linux python-client.spec'
>
> at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)
>
> at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> [ERROR]
>
> [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 <goals> -rf :python-client
>
>
>
>
> On Thu, Jul 28, 2016 at 8:42 PM, Don Bosco Durai <bo...@apache.org> wrote:
>
>> Ascot
>>
>>
>>
>> Would you be able to use Dockers to build Ambari? I have uploaded a
>> script to this JIRA https://issues.apache.org/jira/browse/AMBARI-17944
>>
>>
>>
>> If you are using CentOS, then you would have to install Dockers. And then
>> copy the script from the JIRA to the root folder of your Ambari source. You
>> might need to chmod a+x to the script.
>>
>>
>>
>> When the first time you run the script, it will create the build the
>> image and run it. Next time onwards, it will just run it.
>>
>>
>>
>> Give a try and let me know if it works for you.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Bosco
>>
>>
>>
>>
>>
>> *From: *Ascot Moss <as...@gmail.com>
>> *Reply-To: *<us...@ambari.apache.org>
>> *Date: *Thursday, July 28, 2016 at 3:29 AM
>>
>> *To: *<us...@ambari.apache.org>
>> *Subject: *Re: Build Error
>>
>>
>>
>> *Hi,*
>>
>>
>>
>> *Thanks for your reply!!*
>>
>> *Just tried ur command, can get thru *[INFO] Ambari Web
>> ......................................... SUCCESS [04:52 min]
>>
>>
>>
>> *Looks like " -Dstack.distribution" must be specified.Moving on *ambari-metrics
>> now.
>>
>> Regards
>>
>>
>>
>> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
>> >= 2.6' -Dstack.distribution=HDP*
>>
>> [INFO] Ambari Main ........................................ SUCCESS [
>> 7.205 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 0.297 s]
>>
>> [INFO] Ambari Web ......................................... SUCCESS
>> [04:52 min]
>>
>> [INFO] Ambari Views ....................................... SUCCESS [
>> 2.297 s]
>>
>> [INFO] Ambari Admin View .................................. SUCCESS [
>> 19.035 s]
>>
>> [INFO] ambari-metrics ..................................... FAILURE [
>> 0.174 s]
>>
>>
>>
>> On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <mi...@gmail.com>
>> wrote:
>>
>> This is what I run on my machine:
>>
>>
>>
>> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
>> >= 2.6' -Dstack.distribution=HDP
>>
>>
>>
>> Your error seems to be something related to npm since I see an error on
>> lstat package.json
>>
>>
>>
>> May be try cleaning the npm cache under ambari-web:
>>
>> Go to ambari-src-folder/ambari-web and run the command npm cache clean
>>
>> Go back to ambari-src-folder and run the build command again?
>>
>>
>>
>> On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>> Found error in log
>>
>> 50462 silly gunzTarPerm extractEntry .npmignore
>>
>> 50463 silly gunzTarPerm extractEntry index.js
>>
>> 50464 silly gunzTarPerm extractEntry .npmignore
>>
>> 50465 silly gunzTarPerm extractEntry index.js
>>
>> 50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>>
>> 50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>>
>> 50468 verbose about to build
>> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>>
>> 50469
>> info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>> unbuild
>>
>> 50470 info preuninstall connect@2.12.0
>>
>> 50471 error Error: ENOENT, lstat
>> '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'
>>
>> 50472 error If you need help, you may report this log at:
>>
>> 50472 error     <http://github.com/isaacs/npm/issues>
>>
>> 50472 error or email it to:
>>
>> 50472 error     <np...@googlegroups.com>
>>
>> 50473 error System Linux 3.10.0-327.4.4.el7.x86_64
>>
>> 50474 error command "node" "/usr/bin/npm" "install"
>>
>> 50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web
>>
>> 50476 error node -v v0.10.42
>>
>> 50477 error npm -v 1.3.6
>>
>> 50478 error path
>> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>>
>> 50479 error fstream_path
>> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>>
>> 50480 error fstream_type File
>>
>> 50481 error fstream_class FileWriter
>>
>> 50482 error code ENOENT
>>
>> 50483 error errno 34
>>
>> 50484 error fstream_stack
>> /usr/lib/node_modules/fstream/lib/writer.js:284:26
>>
>> 50484 error fstream_stack Object.oncomplete (fs.js:108:15)
>>
>> 50485 verbose exit [ 34, true ]
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>> By the way, below are my steps:
>>
>> Please let me know if correct or not, many thanks!
>>
>> ---------------
>>
>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>
>> cd apache-ambari-2.2.2-src
>>
>> *mvn clean  *
>>
>> *pushd ambari-metrics  *
>>
>> *mvn versions:set -DnewVersion=2.2.2.1 *
>>
>> *popd  *
>>
>> *mvn versions:set -DnewVersion=2.2.2.1  *
>>
>>
>> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*---------------
>>
>>
>>
>> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>> My OS is CentOS 7:
>>
>>
>> $node --version
>>
>> v6.3.0
>>
>>
>>
>> $ npm --version
>>
>> 3.10.5
>>
>>
>>
>> $ brunch --version
>>
>> 2.8.2
>>
>>
>>
>> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
>> wrote:
>>
>> I would assume mvn to install the required version of node, npm and
>> brunch.
>>
>>
>>
>> This is what I have on my environment (which does mvn builds without any
>> issues):
>>
>> bash-3.2$ node --version
>>
>> v0.10.39
>>
>> bash-3.2$ npm --version
>>
>> 1.4.28
>>
>> bash-3.2$ brunch --version
>>
>> 1.8.5
>>
>>
>>
>> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:
>>
>>
>> Hi,
>>
>>
>>
>> Thanks for your reply!
>>
>>
>>
>> Tried the following:
>>
>> (step 1)
>> npm install -g brunch
>>
>> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>>
>> /usr/lib
>>
>> └─┬ brunch@2.8.2
>>
>>   ├─┬ check-dependencies@0.12.0
>>
>>   │ └─┬ bower-config@1.4.0
>>
>>   │   └── graceful-fs@4.1.5
>>
>>   └─┬ deppack@0.6.1
>>
>>     └─┬ node-browser-modules@0.1.0
>>
>>       └── process@0.11.6
>> npm WARN optional Skipping failed optional dependency
>> /brunch/chokidar/fsevents:
>> npm WARN notsup Not compatible with your operating system or
>> architecture: fsevents@1.0.14
>>
>>
>>
>> (step 2)
>>
>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>
>> cd apache-ambari-2.2.2-src
>>
>> *mvn clean*
>>
>> *mvn versions:set -DnewVersion=2.2.2.1*
>>
>> *pushd ambari-metrics*
>>
>> *mvn versions:set -DnewVersion=2.2.2.1*
>>
>> *popd*
>>
>> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>
>>
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>> value: 1) -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
>> project ambari-web: Command execution failed.
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>
>> at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:497)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>> execution failed.
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>
>> ... 20 more
>>
>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>> an error: 1 (Exit value: 1)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>
>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>
>> ... 22 more
>>
>> [ERROR]
>>
>> [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 <goals> -rf :ambari-web
>>
>>
>>
>> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com>
>> wrote:
>>
>> See if *npm install -g brunch* would fix the issue?
>>
>>
>>
>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:
>>
>> Hi
>> thanks for your reply!
>>
>> Added -e
>>
>>
>>
>>
>>
>> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>>
>> npm WARN notsup Not compatible with your operating system or
>> architecture: fsevents@0.2.1
>>
>> npm WARN Ambari@2.1.3 No license field.
>>
>> [INFO]
>>
>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>>
>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>> perhaps you meant defaultExtensions
>>
>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
>> you meant defaultExtensions
>>
>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
>> order
>>
>> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
>> execute `npm install` to install brunch plugins. SyntaxError: Setter must
>> have exactly one formal parameter.
>>
>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ SUCCESS [
>> 6.635 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 0.371 s]
>>
>> [INFO] Ambari Web ......................................... FAILURE
>> [02:46 min]
>>
>> [INFO] Ambari Views ....................................... SKIPPED
>>
>> [INFO] Ambari Admin View .................................. SKIPPED
>>
>> [INFO] ambari-metrics ..................................... SKIPPED
>>
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>
>> [INFO] Ambari Server ...................................... SKIPPED
>>
>> [INFO] Ambari Agent ....................................... SKIPPED
>>
>> [INFO] Ambari Client ...................................... SKIPPED
>>
>> [INFO] Ambari Python Client ............................... SKIPPED
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Total time: 02:53 min
>>
>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>
>> [INFO] Final Memory: 33M/1036M
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>> value: 1) -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
>> project ambari-web: Command execution failed.
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>
>> at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:497)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>> execution failed.
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>
>> ... 20 more
>>
>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>> an error: 1 (Exit value: 1)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>
>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>
>> ... 22 more
>>
>>
>>
>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
>> wrote:
>>
>> Hi there-
>>
>>
>>
>> Adding -e to the mvn command will give you more output on your error.
>>
>>
>>
>> Thanks.
>>
>>
>>
>> Amanda
>>
>>
>>
>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>> as root (also tried as ordinary user)
>>
>>
>>
>> Refer to the error below, is it about some default settings must be
>> adjusted in pom?
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>> value: 1) -> [Help 1]
>>
>>
>>
>>
>>
>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>> wrote:
>>
>> As which user are you running this build? I was having issues when I ran
>> the build as user “root”.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Bosco
>>
>>
>>
>>
>>
>> *From: *Ascot Moss <as...@gmail.com>
>> *Reply-To: *<us...@ambari.apache.org>
>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>> *To: *<us...@ambari.apache.org>
>> *Subject: *Re: Build Error
>>
>>
>>
>> my mvn is 3.3.9,  will this be an issue?
>>
>>
>>
>>
>>
>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:
>>
>> Hi,
>>
>>
>>
>>
>>
>> Please help!
>>
>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>
>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ SUCCESS
>> [04:51 min]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 4.361 s]
>>
>> [INFO] Ambari Web ......................................... FAILURE
>> [02:55 min]
>>
>> [INFO] Ambari Views ....................................... SKIPPED
>>
>> [INFO] Ambari Admin View .................................. SKIPPED
>>
>> [INFO] ambari-metrics ..................................... SKIPPED
>>
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>
>> [INFO] Ambari Server ...................................... SKIPPED
>>
>> [INFO] Ambari Agent ....................................... SKIPPED
>>
>> [INFO] Ambari Client ...................................... SKIPPED
>>
>> [INFO] Ambari Python Client ............................... SKIPPED
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>> value: 1) -> [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 <goals> -rf :ambari-web
>>
>>
>>
>> Any ideas how to resolve it?
>>
>> Regards
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Thanks,
>>
>>
>>
>> Amanda Moran
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> *Mithun Mathew* (Matt)
>>
>>    - www.linkedin.com/in/mithunmatt/
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> *Mithun Mathew* (Matt)
>>
>>    - www.linkedin.com/in/mithunmatt/
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> *Mithun Mathew* (Matt)
>>
>>    - www.linkedin.com/in/mithunmatt/
>>
>>
>>
>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
Hi,

Thanks!


My current status as follows:

*mvn clean && mvn -B -e clean install package rpm:rpm -Dbuild-rpm
-Dpython.ver='python >= 2.6' **-DskipTests*

[INFO] RPM build errors:

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [
3.747 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.345 s]

[INFO] Ambari Web ......................................... SUCCESS [04:33
min]

[INFO] Ambari Views ....................................... SUCCESS [
1.672 s]

[INFO] Ambari Admin View .................................. SUCCESS [
19.573 s]

[INFO] ambari-metrics ..................................... SUCCESS [
1.075 s]

[INFO] Ambari Metrics Common .............................. SUCCESS [
1.200 s]

[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [
2.021 s]

[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [
1.500 s]

[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [
1.162 s]

[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [
2.073 s]

[INFO] Ambari Metrics Collector ........................... SUCCESS [01:48
min]

[INFO] Ambari Metrics Monitor ............................. SUCCESS [
1.588 s]

[INFO] Ambari Metrics Grafana ............................. SUCCESS [
9.783 s]

[INFO] Ambari Metrics Assembly ............................ SUCCESS [05:18
min]

[INFO] Ambari Server ...................................... SUCCESS [03:22
min]

[INFO] Ambari Agent ....................................... SUCCESS [
16.770 s]

[INFO] Ambari Client ...................................... SUCCESS [
0.496 s]

[INFO] Ambari Python Client ............................... FAILURE [
1.067 s]

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 16:06 min

[INFO] Finished at: 2016-07-28T22:23:55+08:00

[INFO] Final Memory: 335M/3132M

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on project
python-client: RPM build execution returned: '1' executing '/bin/sh -c cd
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec' -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:rpm-maven-plugin:2.1-alpha-2:rpm (default-cli) on
project python-client: RPM build execution returned: '1' executing '/bin/sh
-c cd
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec'

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: RPM build
execution returned: '1' executing '/bin/sh -c cd
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/SPECS
&& rpmbuild -bb --buildroot
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client/buildroot
--define '_topdir
/user/local/apache-ambari-2.2.2-src/ambari-client/python-client/target/rpm/python-client'
--target x86_64-redhat-linux python-client.spec'

at org.codehaus.mojo.rpm.RPMHelper.buildPackage(RPMHelper.java:150)

at org.codehaus.mojo.rpm.AbstractRPMMojo.execute(AbstractRPMMojo.java:792)

at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

[ERROR]

[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 <goals> -rf :python-client




On Thu, Jul 28, 2016 at 8:42 PM, Don Bosco Durai <bo...@apache.org> wrote:

> Ascot
>
>
>
> Would you be able to use Dockers to build Ambari? I have uploaded a script
> to this JIRA https://issues.apache.org/jira/browse/AMBARI-17944
>
>
>
> If you are using CentOS, then you would have to install Dockers. And then
> copy the script from the JIRA to the root folder of your Ambari source. You
> might need to chmod a+x to the script.
>
>
>
> When the first time you run the script, it will create the build the image
> and run it. Next time onwards, it will just run it.
>
>
>
> Give a try and let me know if it works for you.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Thursday, July 28, 2016 at 3:29 AM
>
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> *Hi,*
>
>
>
> *Thanks for your reply!!*
>
> *Just tried ur command, can get thru *[INFO] Ambari Web
> ......................................... SUCCESS [04:52 min]
>
>
>
> *Looks like " -Dstack.distribution" must be specified.Moving on *ambari-metrics
> now.
>
> Regards
>
>
>
> *mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
> >= 2.6' -Dstack.distribution=HDP*
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 7.205 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.297 s]
>
> [INFO] Ambari Web ......................................... SUCCESS [04:52
> min]
>
> [INFO] Ambari Views ....................................... SUCCESS [
> 2.297 s]
>
> [INFO] Ambari Admin View .................................. SUCCESS [
> 19.035 s]
>
> [INFO] ambari-metrics ..................................... FAILURE [
> 0.174 s]
>
>
>
> On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <mi...@gmail.com> wrote:
>
> This is what I run on my machine:
>
>
>
> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
> >= 2.6' -Dstack.distribution=HDP
>
>
>
> Your error seems to be something related to npm since I see an error on
> lstat package.json
>
>
>
> May be try cleaning the npm cache under ambari-web:
>
> Go to ambari-src-folder/ambari-web and run the command npm cache clean
>
> Go back to ambari-src-folder and run the build command again?
>
>
>
> On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Found error in log
>
> 50462 silly gunzTarPerm extractEntry .npmignore
>
> 50463 silly gunzTarPerm extractEntry index.js
>
> 50464 silly gunzTarPerm extractEntry .npmignore
>
> 50465 silly gunzTarPerm extractEntry index.js
>
> 50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>
> 50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>
> 50468 verbose about to build
> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>
> 50469
> info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
> unbuild
>
> 50470 info preuninstall connect@2.12.0
>
> 50471 error Error: ENOENT, lstat
> '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'
>
> 50472 error If you need help, you may report this log at:
>
> 50472 error     <http://github.com/isaacs/npm/issues>
>
> 50472 error or email it to:
>
> 50472 error     <np...@googlegroups.com>
>
> 50473 error System Linux 3.10.0-327.4.4.el7.x86_64
>
> 50474 error command "node" "/usr/bin/npm" "install"
>
> 50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web
>
> 50476 error node -v v0.10.42
>
> 50477 error npm -v 1.3.6
>
> 50478 error path
> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>
> 50479 error fstream_path
> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>
> 50480 error fstream_type File
>
> 50481 error fstream_class FileWriter
>
> 50482 error code ENOENT
>
> 50483 error errno 34
>
> 50484 error fstream_stack
> /usr/lib/node_modules/fstream/lib/writer.js:284:26
>
> 50484 error fstream_stack Object.oncomplete (fs.js:108:15)
>
> 50485 verbose exit [ 34, true ]
>
>
>
>
>
>
>
> On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com> wrote:
>
> By the way, below are my steps:
>
> Please let me know if correct or not, many thanks!
>
> ---------------
>
> tar xfvz apache-ambari-2.2.2-src.tar.gz
>
> cd apache-ambari-2.2.2-src
>
> *mvn clean  *
>
> *pushd ambari-metrics  *
>
> *mvn versions:set -DnewVersion=2.2.2.1 *
>
> *popd  *
>
> *mvn versions:set -DnewVersion=2.2.2.1  *
>
>
> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl -e*---------------
>
>
>
> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com> wrote:
>
> My OS is CentOS 7:
>
>
> $node --version
>
> v6.3.0
>
>
>
> $ npm --version
>
> 3.10.5
>
>
>
> $ brunch --version
>
> 2.8.2
>
>
>
> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
> wrote:
>
> I would assume mvn to install the required version of node, npm and brunch.
>
>
>
> This is what I have on my environment (which does mvn builds without any
> issues):
>
> bash-3.2$ node --version
>
> v0.10.39
>
> bash-3.2$ npm --version
>
> 1.4.28
>
> bash-3.2$ brunch --version
>
> 1.8.5
>
>
>
> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:
>
>
> Hi,
>
>
>
> Thanks for your reply!
>
>
>
> Tried the following:
>
> (step 1)
> npm install -g brunch
>
> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>
> /usr/lib
>
> └─┬ brunch@2.8.2
>
>   ├─┬ check-dependencies@0.12.0
>
>   │ └─┬ bower-config@1.4.0
>
>   │   └── graceful-fs@4.1.5
>
>   └─┬ deppack@0.6.1
>
>     └─┬ node-browser-modules@0.1.0
>
>       └── process@0.11.6
> npm WARN optional Skipping failed optional dependency
> /brunch/chokidar/fsevents:
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@1.0.14
>
>
>
> (step 2)
>
> tar xfvz apache-ambari-2.2.2-src.tar.gz
>
> cd apache-ambari-2.2.2-src
>
> *mvn clean*
>
> *mvn versions:set -DnewVersion=2.2.2.1*
>
> *pushd ambari-metrics*
>
> *mvn versions:set -DnewVersion=2.2.2.1*
>
> *popd*
>
> *mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>
>
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
> [ERROR]
>
> [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 <goals> -rf :ambari-web
>
>
>
> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com> wrote:
>
> See if *npm install -g brunch* would fix the issue?
>
>
>
> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Hi
> thanks for your reply!
>
> Added -e
>
>
>
>
>
> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@0.2.1
>
> npm WARN Ambari@2.1.3 No license field.
>
> [INFO]
>
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>
> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
> order
>
> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
> execute `npm install` to install brunch plugins. SyntaxError: Setter must
> have exactly one formal parameter.
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 6.635 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.371 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:46
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 02:53 min
>
> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>
> [INFO] Final Memory: 33M/1036M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
>
>
> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
> wrote:
>
> Hi there-
>
>
>
> Adding -e to the mvn command will give you more output on your error.
>
>
>
> Thanks.
>
>
>
> Amanda
>
>
>
> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com> wrote:
>
> as root (also tried as ordinary user)
>
>
>
> Refer to the error below, is it about some default settings must be
> adjusted in pom?
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
>
>
>
>
> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
> wrote:
>
> As which user are you running this build? I was having issues when I ran
> the build as user “root”.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Tuesday, July 26, 2016 at 6:07 AM
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> my mvn is 3.3.9,  will this be an issue?
>
>
>
>
>
> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Hi,
>
>
>
>
>
> Please help!
>
> I am trying to build Ambari 2.2.2, got the following error as follows:
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [04:51
> min]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 4.361 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:55
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [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 <goals> -rf :ambari-web
>
>
>
> Any ideas how to resolve it?
>
> Regards
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Thanks,
>
>
>
> Amanda Moran
>
>
>
>
>
>
>
> --
>
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>
>
>
>
>
>
> --
>
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>
>
>
>
>
>
>
>
>
>
> --
>
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>
>

Re: Build Error

Posted by Don Bosco Durai <bo...@apache.org>.
Ascot

 

Would you be able to use Dockers to build Ambari? I have uploaded a script to this JIRA https://issues.apache.org/jira/browse/AMBARI-17944

 

If you are using CentOS, then you would have to install Dockers. And then copy the script from the JIRA to the root folder of your Ambari source. You might need to chmod a+x to the script.

 

When the first time you run the script, it will create the build the image and run it. Next time onwards, it will just run it.

 

Give a try and let me know if it works for you.

 

Thanks

 

Bosco

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Thursday, July 28, 2016 at 3:29 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

Hi,

 

Thanks for your reply!!

Just tried ur command, can get thru [INFO] Ambari Web ......................................... SUCCESS [04:52 min]

Looks like " -Dstack.distribution" must be specified.

Moving on ambari-metrics now.

Regards



mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' -Dstack.distribution=HDP

[INFO] Ambari Main ........................................ SUCCESS [  7.205 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.297 s]

[INFO] Ambari Web ......................................... SUCCESS [04:52 min]

[INFO] Ambari Views ....................................... SUCCESS [  2.297 s]

[INFO] Ambari Admin View .................................. SUCCESS [ 19.035 s]

[INFO] ambari-metrics ..................................... FAILURE [  0.174 s]

 

On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <mi...@gmail.com> wrote:

This is what I run on my machine:

 

mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >= 2.6' -Dstack.distribution=HDP



Your error seems to be something related to npm since I see an error on lstat package.json

 

May be try cleaning the npm cache under ambari-web:

Go to ambari-src-folder/ambari-web and run the command npm cache clean

Go back to ambari-src-folder and run the build command again?

 

On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com> wrote:

Found error in log


50462 silly gunzTarPerm extractEntry .npmignore

50463 silly gunzTarPerm extractEntry index.js

50464 silly gunzTarPerm extractEntry .npmignore

50465 silly gunzTarPerm extractEntry index.js

50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0

50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0

50468 verbose about to build /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect

50469 info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect unbuild

50470 info preuninstall connect@2.12.0

50471 error Error: ENOENT, lstat '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'

50472 error If you need help, you may report this log at:

50472 error     <http://github.com/isaacs/npm/issues>

50472 error or email it to:

50472 error     <np...@googlegroups.com>

50473 error System Linux 3.10.0-327.4.4.el7.x86_64

50474 error command "node" "/usr/bin/npm" "install"

50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web

50476 error node -v v0.10.42

50477 error npm -v 1.3.6

50478 error path /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json

50479 error fstream_path /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json

50480 error fstream_type File

50481 error fstream_class FileWriter

50482 error code ENOENT

50483 error errno 34

50484 error fstream_stack /usr/lib/node_modules/fstream/lib/writer.js:284:26

50484 error fstream_stack Object.oncomplete (fs.js:108:15)

50485 verbose exit [ 34, true ]

 

 

 

On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com> wrote:

By the way, below are my steps:

Please let me know if correct or not, many thanks!

---------------

tar xfvz apache-ambari-2.2.2-src.tar.gz

cd apache-ambari-2.2.2-src

mvn clean  

pushd ambari-metrics  

mvn versions:set -DnewVersion=2.2.2.1 

popd  

mvn versions:set -DnewVersion=2.2.2.1  

mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e
---------------

 

On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com> wrote:

My OS is CentOS 7:


$node --version

v6.3.0

 

$ npm --version

3.10.5

 

$ brunch --version

2.8.2

 

On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com> wrote:

I would assume mvn to install the required version of node, npm and brunch.

 

This is what I have on my environment (which does mvn builds without any issues):

bash-3.2$ node --version

v0.10.39

bash-3.2$ npm --version

1.4.28

bash-3.2$ brunch --version

1.8.5

 

On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:


Hi,

 

Thanks for your reply!

 

Tried the following:

(step 1)
npm install -g brunch

/usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch

/usr/lib

└─┬ brunch@2.8.2 

  ├─┬ check-dependencies@0.12.0

  │ └─┬ bower-config@1.4.0

  │   └── graceful-fs@4.1.5 

  └─┬ deppack@0.6.1

    └─┬ node-browser-modules@0.1.0

      └── process@0.11.6 
npm WARN optional Skipping failed optional dependency /brunch/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14

 

(step 2)

tar xfvz apache-ambari-2.2.2-src.tar.gz

cd apache-ambari-2.2.2-src

mvn clean

mvn versions:set -DnewVersion=2.2.2.1

pushd ambari-metrics

mvn versions:set -DnewVersion=2.2.2.1

popd

mvn -B clean install package rpm:rpm -DnewVersion=2.2.2.1 -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e

 

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

[ERROR] 

[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 <goals> -rf :ambari-web

 

On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com> wrote:

See if npm install -g brunch would fix the issue?

 

On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:

Hi 
thanks for your reply!

Added -e

 

 

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:

npm WARN notsup Not compatible with your operating system or architecture: fsevents@0.2.1

npm WARN Ambari@2.1.3 No license field.

[INFO] 

[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---

28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: perhaps you meant defaultExtensions

28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps you meant defaultExtensions

28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant order

28 Jul 07:46:20 - error: Initialization error -  You probably need to execute `npm install` to install brunch plugins. SyntaxError: Setter must have exactly one formal parameter. 

Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [  6.635 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.371 s]

[INFO] Ambari Web ......................................... FAILURE [02:46 min]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 02:53 min

[INFO] Finished at: 2016-07-28T07:46:20+08:00

[INFO] Final Memory: 33M/1036M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed.

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

 

On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com> wrote:

Hi there-

 

Adding -e to the mvn command will give you more output on your error. 

 

Thanks. 

 

Amanda 

 

On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com> wrote:

as root (also tried as ordinary user)

 

Refer to the error below, is it about some default settings must be adjusted in pom?

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]

 

 

On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org> wrote:

As which user are you running this build? I was having issues when I ran the build as user “root”.

 

Thanks

 

Bosco

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Tuesday, July 26, 2016 at 6:07 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

my mvn is 3.3.9,  will this be an issue?

 

 

On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:

Hi,

 

 

Please help!

I am trying to build Ambari 2.2.2, got the following error as follows:

Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [04:51 min]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  4.361 s]

[INFO] Ambari Web ......................................... FAILURE [02:55 min]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [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 <goals> -rf :ambari-web

 

Any ideas how to resolve it?

Regards

 

 

 

 

 



 

-- 

Thanks, 

 

Amanda Moran

 



 

-- 

Mithun Mathew (Matt)

www.linkedin.com/in/mithunmatt/
 

 

-- 

Mithun Mathew (Matt)

www.linkedin.com/in/mithunmatt/
 

 

 

 

-- 

Mithun Mathew (Matt)

www.linkedin.com/in/mithunmatt/

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
*Hi,*


*Thanks for your reply!!*

*Just tried ur command, can get thru *[INFO] Ambari Web
......................................... SUCCESS [04:52 min]

*Looks like "*
* -Dstack.distribution" must be specified.*
*Moving on *ambari-metrics now.

Regards



*mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
>= 2.6' -Dstack.distribution=HDP*

[INFO] Ambari Main ........................................ SUCCESS [
7.205 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.297 s]

[INFO] Ambari Web ......................................... SUCCESS [04:52
min]

[INFO] Ambari Views ....................................... SUCCESS [
2.297 s]

[INFO] Ambari Admin View .................................. SUCCESS [
19.035 s]

[INFO] ambari-metrics ..................................... FAILURE [
0.174 s]

On Thu, Jul 28, 2016 at 4:25 PM, Mithun Mathew <mi...@gmail.com> wrote:

> This is what I run on my machine:
>
> mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python
> >= 2.6' -Dstack.distribution=HDP
>
> Your error seems to be something related to npm since I see an error on
> lstat package.json
>
> May be try cleaning the npm cache under ambari-web:
> Go to ambari-src-folder/ambari-web and run the command npm cache clean
> Go back to ambari-src-folder and run the build command again?
>
> On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> Found error in log
>>
>>
>> 50462 silly gunzTarPerm extractEntry .npmignore
>>
>> 50463 silly gunzTarPerm extractEntry index.js
>>
>> 50464 silly gunzTarPerm extractEntry .npmignore
>>
>> 50465 silly gunzTarPerm extractEntry index.js
>>
>> 50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>>
>> 50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>>
>> 50468 verbose about to build
>> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>>
>> 50469
>> info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>> unbuild
>>
>> 50470 info preuninstall connect@2.12.0
>>
>> 50471 error Error: ENOENT, lstat
>> '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'
>>
>> 50472 error If you need help, you may report this log at:
>>
>> 50472 error     <http://github.com/isaacs/npm/issues>
>>
>> 50472 error or email it to:
>>
>> 50472 error     <np...@googlegroups.com>
>>
>> 50473 error System Linux 3.10.0-327.4.4.el7.x86_64
>>
>> 50474 error command "node" "/usr/bin/npm" "install"
>>
>> 50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web
>>
>> 50476 error node -v v0.10.42
>>
>> 50477 error npm -v 1.3.6
>>
>> 50478 error path
>> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>>
>> 50479 error fstream_path
>> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>>
>> 50480 error fstream_type File
>>
>> 50481 error fstream_class FileWriter
>>
>> 50482 error code ENOENT
>>
>> 50483 error errno 34
>>
>> 50484 error fstream_stack
>> /usr/lib/node_modules/fstream/lib/writer.js:284:26
>>
>> 50484 error fstream_stack Object.oncomplete (fs.js:108:15)
>>
>> 50485 verbose exit [ 34, true ]
>>
>>
>>
>>
>> On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>>> By the way, below are my steps:
>>>
>>> Please let me know if correct or not, many thanks!
>>>
>>> ---------------
>>>
>>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>>
>>> cd apache-ambari-2.2.2-src
>>>
>>> *mvn clean  *
>>>
>>> *pushd ambari-metrics  *
>>>
>>> *mvn versions:set -DnewVersion=**2.2.2.1 *
>>>
>>> *popd  *
>>>
>>> *mvn versions:set -DnewVersion=**2.2.2.1  *
>>>
>>> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1*
>>> * -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>> ---------------
>>>
>>> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>>> My OS is CentOS 7:
>>>>
>>>>
>>>> $node --version
>>>>
>>>> v6.3.0
>>>>
>>>>
>>>> $ npm --version
>>>>
>>>> 3.10.5
>>>>
>>>>
>>>> $ brunch --version
>>>>
>>>> 2.8.2
>>>>
>>>> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
>>>> wrote:
>>>>
>>>>> I would assume mvn to install the required version of node, npm and
>>>>> brunch.
>>>>>
>>>>> This is what I have on my environment (which does mvn builds without
>>>>> any issues):
>>>>> bash-3.2$ node --version
>>>>> v0.10.39
>>>>> bash-3.2$ npm --version
>>>>> 1.4.28
>>>>> bash-3.2$ brunch --version
>>>>> 1.8.5
>>>>>
>>>>> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Thanks for your reply!
>>>>>>
>>>>>> Tried the following:
>>>>>>
>>>>>> (step 1)
>>>>>> npm install -g brunch
>>>>>>
>>>>>> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>>>>>>
>>>>>> /usr/lib
>>>>>>
>>>>>> └─┬ brunch@2.8.2
>>>>>>
>>>>>>   ├─┬ check-dependencies@0.12.0
>>>>>>
>>>>>>   │ └─┬ bower-config@1.4.0
>>>>>>
>>>>>>   │   └── graceful-fs@4.1.5
>>>>>>
>>>>>>   └─┬ deppack@0.6.1
>>>>>>
>>>>>>     └─┬ node-browser-modules@0.1.0
>>>>>>
>>>>>>       └── process@0.11.6
>>>>>> npm WARN optional Skipping failed optional dependency
>>>>>> /brunch/chokidar/fsevents:
>>>>>> npm WARN notsup Not compatible with your operating system or
>>>>>> architecture: fsevents@1.0.14
>>>>>>
>>>>>>
>>>>>> (step 2)
>>>>>>
>>>>>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>>>>>
>>>>>> cd apache-ambari-2.2.2-src
>>>>>>
>>>>>> *mvn clean*
>>>>>>
>>>>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>>>>
>>>>>> *pushd ambari-metrics*
>>>>>>
>>>>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>>>>
>>>>>> *popd*
>>>>>>
>>>>>> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1** -DskipTests
>>>>>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>>>>>
>>>>>>
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>> value: 1) -> [Help 1]
>>>>>>
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>>>
>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>>>
>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>>>
>>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>>>
>>>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>>>
>>>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>>>
>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>
>>>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>>>
>>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>>>> execution failed.
>>>>>>
>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>>>
>>>>>> ... 20 more
>>>>>>
>>>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>>>> with an error: 1 (Exit value: 1)
>>>>>>
>>>>>> at
>>>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>>>
>>>>>> at
>>>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>>>
>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>>>
>>>>>> ... 22 more
>>>>>>
>>>>>> [ERROR]
>>>>>>
>>>>>> [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 <goals> -rf :ambari-web
>>>>>>
>>>>>> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> See if *npm install -g brunch* would fix the issue?
>>>>>>>
>>>>>>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi
>>>>>>>> thanks for your reply!
>>>>>>>>
>>>>>>>> Added -e
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> npm WARN optional Skipping failed optional dependency
>>>>>>>> /chokidar/fsevents:
>>>>>>>>
>>>>>>>> npm WARN notsup Not compatible with your operating system or
>>>>>>>> architecture: fsevents@0.2.1
>>>>>>>>
>>>>>>>> npm WARN Ambari@2.1.3 No license field.
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>>
>>>>>>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @
>>>>>>>> ambari-web ---
>>>>>>>>
>>>>>>>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>>>>>>>> perhaps you meant defaultExtensions
>>>>>>>>
>>>>>>>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension:
>>>>>>>> perhaps you meant defaultExtensions
>>>>>>>>
>>>>>>>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you
>>>>>>>> meant order
>>>>>>>>
>>>>>>>> 28 Jul 07:46:20 - error: Initialization error -  You probably need
>>>>>>>> to execute `npm install` to install brunch plugins. SyntaxError: Setter
>>>>>>>> must have exactly one formal parameter.
>>>>>>>>
>>>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>>>>> trace.
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>>
>>>>>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>>>>>> [  6.635 s]
>>>>>>>>
>>>>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS
>>>>>>>> [  0.371 s]
>>>>>>>>
>>>>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>>>>> [02:46 min]
>>>>>>>>
>>>>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> [INFO] Total time: 02:53 min
>>>>>>>>
>>>>>>>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>>>>>>>
>>>>>>>> [INFO] Final Memory: 33M/1036M
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>>>> value: 1) -> [Help 1]
>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>>>>>
>>>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>>>>>
>>>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>>>>>
>>>>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>>>>>
>>>>>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>>>>>
>>>>>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>>>>>
>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>>>>>
>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>
>>>>>>>> at
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>>>>>
>>>>>>>> at
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>>>>>
>>>>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>>>>>> execution failed.
>>>>>>>>
>>>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>>>>>
>>>>>>>> ... 20 more
>>>>>>>>
>>>>>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>>>>>> with an error: 1 (Exit value: 1)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>>>>>
>>>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>>>>>
>>>>>>>> ... 22 more
>>>>>>>>
>>>>>>>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <
>>>>>>>> amanda.moran@esgyn.com> wrote:
>>>>>>>>
>>>>>>>>> Hi there-
>>>>>>>>>
>>>>>>>>> Adding -e to the mvn command will give you more output on your
>>>>>>>>> error.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> Amanda
>>>>>>>>>
>>>>>>>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <ascot.moss@gmail.com
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> as root (also tried as ordinary user)
>>>>>>>>>>
>>>>>>>>>> Refer to the error below, is it about some default settings must
>>>>>>>>>> be adjusted in pom?
>>>>>>>>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>>>>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>>>>>>>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <
>>>>>>>>>> bosco@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> As which user are you running this build? I was having issues
>>>>>>>>>>> when I ran the build as user “root”.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Bosco
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>>>>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>>>>>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>>>>>>>>> *To: *<us...@ambari.apache.org>
>>>>>>>>>>> *Subject: *Re: Build Error
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> my mvn is 3.3.9,  will this be an issue?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <
>>>>>>>>>>> ascot.moss@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Please help!
>>>>>>>>>>>
>>>>>>>>>>> I am trying to build Ambari 2.2.2, got the following error as
>>>>>>>>>>> follows:
>>>>>>>>>>>
>>>>>>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see
>>>>>>>>>>> the trace.
>>>>>>>>>>>
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>>
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Main ........................................
>>>>>>>>>>> SUCCESS [04:51 min]
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Apache Ambari Project POM ..........................
>>>>>>>>>>> SUCCESS [  4.361 s]
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Web .........................................
>>>>>>>>>>> FAILURE [02:55 min]
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Views .......................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Admin View ..................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] ambari-metrics .....................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Common ..............................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Hadoop Sink .........................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Flume Sink ..........................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Kafka Sink ..........................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Storm Sink ..........................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Collector ...........................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Monitor .............................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Grafana .............................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Metrics Assembly ............................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Server ......................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Agent .......................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Client ......................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Python Client ...............................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Groovy Client ...............................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Shell .......................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Python Shell ................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Ambari Groovy Shell ................................
>>>>>>>>>>> SKIPPED
>>>>>>>>>>>
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>>
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>>>>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Any ideas how to resolve it?
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Amanda Moran
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Mithun Mathew* (Matt)
>>>>>>>
>>>>>>>    - www.linkedin.com/in/mithunmatt/
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Mithun Mathew* (Matt)
>>>>>
>>>>>    - www.linkedin.com/in/mithunmatt/
>>>>>
>>>>>
>>>>
>>>
>>
>
>
> --
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>

Re: Build Error

Posted by Mithun Mathew <mi...@gmail.com>.
This is what I run on my machine:

mvn -B -e clean install package rpm:rpm -Dbuild-rpm -Dpython.ver='python >=
2.6' -Dstack.distribution=HDP

Your error seems to be something related to npm since I see an error on
lstat package.json

May be try cleaning the npm cache under ambari-web:
Go to ambari-src-folder/ambari-web and run the command npm cache clean
Go back to ambari-src-folder and run the build command again?

On Wed, Jul 27, 2016 at 10:26 PM, Ascot Moss <as...@gmail.com> wrote:

> Found error in log
>
>
> 50462 silly gunzTarPerm extractEntry .npmignore
>
> 50463 silly gunzTarPerm extractEntry index.js
>
> 50464 silly gunzTarPerm extractEntry .npmignore
>
> 50465 silly gunzTarPerm extractEntry index.js
>
> 50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>
> 50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0
>
> 50468 verbose about to build
> /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
>
> 50469
> info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
> unbuild
>
> 50470 info preuninstall connect@2.12.0
>
> 50471 error Error: ENOENT, lstat
> '/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'
>
> 50472 error If you need help, you may report this log at:
>
> 50472 error     <http://github.com/isaacs/npm/issues>
>
> 50472 error or email it to:
>
> 50472 error     <np...@googlegroups.com>
>
> 50473 error System Linux 3.10.0-327.4.4.el7.x86_64
>
> 50474 error command "node" "/usr/bin/npm" "install"
>
> 50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web
>
> 50476 error node -v v0.10.42
>
> 50477 error npm -v 1.3.6
>
> 50478 error path
> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>
> 50479 error fstream_path
> /root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json
>
> 50480 error fstream_type File
>
> 50481 error fstream_class FileWriter
>
> 50482 error code ENOENT
>
> 50483 error errno 34
>
> 50484 error fstream_stack
> /usr/lib/node_modules/fstream/lib/writer.js:284:26
>
> 50484 error fstream_stack Object.oncomplete (fs.js:108:15)
>
> 50485 verbose exit [ 34, true ]
>
>
>
>
> On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> By the way, below are my steps:
>>
>> Please let me know if correct or not, many thanks!
>>
>> ---------------
>>
>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>
>> cd apache-ambari-2.2.2-src
>>
>> *mvn clean  *
>>
>> *pushd ambari-metrics  *
>>
>> *mvn versions:set -DnewVersion=**2.2.2.1 *
>>
>> *popd  *
>>
>> *mvn versions:set -DnewVersion=**2.2.2.1  *
>>
>> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1*
>> * -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>> ---------------
>>
>> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>>> My OS is CentOS 7:
>>>
>>>
>>> $node --version
>>>
>>> v6.3.0
>>>
>>>
>>> $ npm --version
>>>
>>> 3.10.5
>>>
>>>
>>> $ brunch --version
>>>
>>> 2.8.2
>>>
>>> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
>>> wrote:
>>>
>>>> I would assume mvn to install the required version of node, npm and
>>>> brunch.
>>>>
>>>> This is what I have on my environment (which does mvn builds without
>>>> any issues):
>>>> bash-3.2$ node --version
>>>> v0.10.39
>>>> bash-3.2$ npm --version
>>>> 1.4.28
>>>> bash-3.2$ brunch --version
>>>> 1.8.5
>>>>
>>>> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks for your reply!
>>>>>
>>>>> Tried the following:
>>>>>
>>>>> (step 1)
>>>>> npm install -g brunch
>>>>>
>>>>> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>>>>>
>>>>> /usr/lib
>>>>>
>>>>> └─┬ brunch@2.8.2
>>>>>
>>>>>   ├─┬ check-dependencies@0.12.0
>>>>>
>>>>>   │ └─┬ bower-config@1.4.0
>>>>>
>>>>>   │   └── graceful-fs@4.1.5
>>>>>
>>>>>   └─┬ deppack@0.6.1
>>>>>
>>>>>     └─┬ node-browser-modules@0.1.0
>>>>>
>>>>>       └── process@0.11.6
>>>>> npm WARN optional Skipping failed optional dependency
>>>>> /brunch/chokidar/fsevents:
>>>>> npm WARN notsup Not compatible with your operating system or
>>>>> architecture: fsevents@1.0.14
>>>>>
>>>>>
>>>>> (step 2)
>>>>>
>>>>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>>>>
>>>>> cd apache-ambari-2.2.2-src
>>>>>
>>>>> *mvn clean*
>>>>>
>>>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>>>
>>>>> *pushd ambari-metrics*
>>>>>
>>>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>>>
>>>>> *popd*
>>>>>
>>>>> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1** -DskipTests
>>>>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>>>>
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>> value: 1) -> [Help 1]
>>>>>
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>>
>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>>
>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>>
>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>>
>>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>>
>>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>>
>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>>
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>
>>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>>
>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>>> execution failed.
>>>>>
>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>>
>>>>> at
>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>>
>>>>> ... 20 more
>>>>>
>>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>>> with an error: 1 (Exit value: 1)
>>>>>
>>>>> at
>>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>>
>>>>> at
>>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>>
>>>>> at
>>>>> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>>
>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>>
>>>>> ... 22 more
>>>>>
>>>>> [ERROR]
>>>>>
>>>>> [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 <goals> -rf :ambari-web
>>>>>
>>>>> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> See if *npm install -g brunch* would fix the issue?
>>>>>>
>>>>>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi
>>>>>>> thanks for your reply!
>>>>>>>
>>>>>>> Added -e
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> npm WARN optional Skipping failed optional dependency
>>>>>>> /chokidar/fsevents:
>>>>>>>
>>>>>>> npm WARN notsup Not compatible with your operating system or
>>>>>>> architecture: fsevents@0.2.1
>>>>>>>
>>>>>>> npm WARN Ambari@2.1.3 No license field.
>>>>>>>
>>>>>>> [INFO]
>>>>>>>
>>>>>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @
>>>>>>> ambari-web ---
>>>>>>>
>>>>>>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>>>>>>> perhaps you meant defaultExtensions
>>>>>>>
>>>>>>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension:
>>>>>>> perhaps you meant defaultExtensions
>>>>>>>
>>>>>>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you
>>>>>>> meant order
>>>>>>>
>>>>>>> 28 Jul 07:46:20 - error: Initialization error -  You probably need
>>>>>>> to execute `npm install` to install brunch plugins. SyntaxError: Setter
>>>>>>> must have exactly one formal parameter.
>>>>>>>
>>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>>>> trace.
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> [INFO] Reactor Summary:
>>>>>>>
>>>>>>> [INFO]
>>>>>>>
>>>>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>>>>> [  6.635 s]
>>>>>>>
>>>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS
>>>>>>> [  0.371 s]
>>>>>>>
>>>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>>>> [02:46 min]
>>>>>>>
>>>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>>>
>>>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> [INFO] BUILD FAILURE
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> [INFO] Total time: 02:53 min
>>>>>>>
>>>>>>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>>>>>>
>>>>>>> [INFO] Final Memory: 33M/1036M
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>>> value: 1) -> [Help 1]
>>>>>>>
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>>>>
>>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>>>>
>>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>>>>
>>>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>>>>
>>>>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>>>>
>>>>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>>>>
>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>>>>
>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>
>>>>>>> at
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>>>>
>>>>>>> at
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>>>>
>>>>>>> at
>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>>>>
>>>>>>> at
>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>>>>
>>>>>>> at
>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>>>>
>>>>>>> at
>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>>>>
>>>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>>>>> execution failed.
>>>>>>>
>>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>>>>
>>>>>>> ... 20 more
>>>>>>>
>>>>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>>>>> with an error: 1 (Exit value: 1)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>>>>
>>>>>>> at
>>>>>>> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>>>>
>>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>>>>
>>>>>>> ... 22 more
>>>>>>>
>>>>>>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <
>>>>>>> amanda.moran@esgyn.com> wrote:
>>>>>>>
>>>>>>>> Hi there-
>>>>>>>>
>>>>>>>> Adding -e to the mvn command will give you more output on your
>>>>>>>> error.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> Amanda
>>>>>>>>
>>>>>>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> as root (also tried as ordinary user)
>>>>>>>>>
>>>>>>>>> Refer to the error below, is it about some default settings must
>>>>>>>>> be adjusted in pom?
>>>>>>>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>>>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>>>>>>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <
>>>>>>>>> bosco@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>> As which user are you running this build? I was having issues
>>>>>>>>>> when I ran the build as user “root”.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Bosco
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>>>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>>>>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>>>>>>>> *To: *<us...@ambari.apache.org>
>>>>>>>>>> *Subject: *Re: Build Error
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> my mvn is 3.3.9,  will this be an issue?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Please help!
>>>>>>>>>>
>>>>>>>>>> I am trying to build Ambari 2.2.2, got the following error as
>>>>>>>>>> follows:
>>>>>>>>>>
>>>>>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see
>>>>>>>>>> the trace.
>>>>>>>>>>
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>>
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Main ........................................
>>>>>>>>>> SUCCESS [04:51 min]
>>>>>>>>>>
>>>>>>>>>> [INFO] Apache Ambari Project POM ..........................
>>>>>>>>>> SUCCESS [  4.361 s]
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Web .........................................
>>>>>>>>>> FAILURE [02:55 min]
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Views .......................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Admin View ..................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] ambari-metrics .....................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Common ..............................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Hadoop Sink .........................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Flume Sink ..........................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Kafka Sink ..........................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Storm Sink ..........................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Collector ...........................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Monitor .............................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Grafana .............................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Metrics Assembly ............................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Server ......................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Agent .......................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Client ......................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Python Client ...............................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Groovy Client ...............................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Shell .......................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Python Shell ................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO] Ambari Groovy Shell ................................
>>>>>>>>>> SKIPPED
>>>>>>>>>>
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>>
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>>>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Any ideas how to resolve it?
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Amanda Moran
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Mithun Mathew* (Matt)
>>>>>>
>>>>>>    - www.linkedin.com/in/mithunmatt/
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Mithun Mathew* (Matt)
>>>>
>>>>    - www.linkedin.com/in/mithunmatt/
>>>>
>>>>
>>>
>>
>


-- 
*Mithun Mathew* (Matt)

   - www.linkedin.com/in/mithunmatt/

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
Found error in log


50462 silly gunzTarPerm extractEntry .npmignore

50463 silly gunzTarPerm extractEntry index.js

50464 silly gunzTarPerm extractEntry .npmignore

50465 silly gunzTarPerm extractEntry index.js

50466 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0

50467 silly lockFile 1a4cf0d3-fresh-0-2-0 fresh@0.2.0

50468 verbose about to build
/usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect

50469
info /usr/local/apache-ambari-2.2.2-src/ambari-web/node_modules/karma/node_modules/connect
unbuild

50470 info preuninstall connect@2.12.0

50471 error Error: ENOENT, lstat
'/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json'

50472 error If you need help, you may report this log at:

50472 error     <http://github.com/isaacs/npm/issues>

50472 error or email it to:

50472 error     <np...@googlegroups.com>

50473 error System Linux 3.10.0-327.4.4.el7.x86_64

50474 error command "node" "/usr/bin/npm" "install"

50475 error cwd /usr/local/apache-ambari-2.2.2-src/ambari-web

50476 error node -v v0.10.42

50477 error npm -v 1.3.6

50478 error path
/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json

50479 error fstream_path
/root/tmp/npm-10392-lZuZvpyq/1469682943521-0.9882951530162245/package/package.json

50480 error fstream_type File

50481 error fstream_class FileWriter

50482 error code ENOENT

50483 error errno 34

50484 error fstream_stack /usr/lib/node_modules/fstream/lib/writer.js:284:26

50484 error fstream_stack Object.oncomplete (fs.js:108:15)

50485 verbose exit [ 34, true ]




On Thu, Jul 28, 2016 at 12:15 PM, Ascot Moss <as...@gmail.com> wrote:

> By the way, below are my steps:
>
> Please let me know if correct or not, many thanks!
>
> ---------------
>
> tar xfvz apache-ambari-2.2.2-src.tar.gz
>
> cd apache-ambari-2.2.2-src
>
> *mvn clean  *
>
> *pushd ambari-metrics  *
>
> *mvn versions:set -DnewVersion=**2.2.2.1 *
>
> *popd  *
>
> *mvn versions:set -DnewVersion=**2.2.2.1  *
>
> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1*
> * -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e*---------------
>
> On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> My OS is CentOS 7:
>>
>>
>> $node --version
>>
>> v6.3.0
>>
>>
>> $ npm --version
>>
>> 3.10.5
>>
>>
>> $ brunch --version
>>
>> 2.8.2
>>
>> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
>> wrote:
>>
>>> I would assume mvn to install the required version of node, npm and
>>> brunch.
>>>
>>> This is what I have on my environment (which does mvn builds without any
>>> issues):
>>> bash-3.2$ node --version
>>> v0.10.39
>>> bash-3.2$ npm --version
>>> 1.4.28
>>> bash-3.2$ brunch --version
>>> 1.8.5
>>>
>>> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> Thanks for your reply!
>>>>
>>>> Tried the following:
>>>>
>>>> (step 1)
>>>> npm install -g brunch
>>>>
>>>> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>>>>
>>>> /usr/lib
>>>>
>>>> └─┬ brunch@2.8.2
>>>>
>>>>   ├─┬ check-dependencies@0.12.0
>>>>
>>>>   │ └─┬ bower-config@1.4.0
>>>>
>>>>   │   └── graceful-fs@4.1.5
>>>>
>>>>   └─┬ deppack@0.6.1
>>>>
>>>>     └─┬ node-browser-modules@0.1.0
>>>>
>>>>       └── process@0.11.6
>>>> npm WARN optional Skipping failed optional dependency
>>>> /brunch/chokidar/fsevents:
>>>> npm WARN notsup Not compatible with your operating system or
>>>> architecture: fsevents@1.0.14
>>>>
>>>>
>>>> (step 2)
>>>>
>>>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>>>
>>>> cd apache-ambari-2.2.2-src
>>>>
>>>> *mvn clean*
>>>>
>>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>>
>>>> *pushd ambari-metrics*
>>>>
>>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>>
>>>> *popd*
>>>>
>>>> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1** -DskipTests
>>>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>>>
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>> value: 1) -> [Help 1]
>>>>
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>
>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>
>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>
>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>
>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>
>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>
>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>
>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>> execution failed.
>>>>
>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>
>>>> at
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>
>>>> ... 20 more
>>>>
>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>> with an error: 1 (Exit value: 1)
>>>>
>>>> at
>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>
>>>> at
>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>
>>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>
>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>
>>>> ... 22 more
>>>>
>>>> [ERROR]
>>>>
>>>> [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 <goals> -rf :ambari-web
>>>>
>>>> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com>
>>>> wrote:
>>>>
>>>>> See if *npm install -g brunch* would fix the issue?
>>>>>
>>>>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>> thanks for your reply!
>>>>>>
>>>>>> Added -e
>>>>>>
>>>>>>
>>>>>>
>>>>>> npm WARN optional Skipping failed optional dependency
>>>>>> /chokidar/fsevents:
>>>>>>
>>>>>> npm WARN notsup Not compatible with your operating system or
>>>>>> architecture: fsevents@0.2.1
>>>>>>
>>>>>> npm WARN Ambari@2.1.3 No license field.
>>>>>>
>>>>>> [INFO]
>>>>>>
>>>>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web
>>>>>> ---
>>>>>>
>>>>>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>>>>>> perhaps you meant defaultExtensions
>>>>>>
>>>>>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension:
>>>>>> perhaps you meant defaultExtensions
>>>>>>
>>>>>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you
>>>>>> meant order
>>>>>>
>>>>>> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
>>>>>> execute `npm install` to install brunch plugins. SyntaxError: Setter must
>>>>>> have exactly one formal parameter.
>>>>>>
>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>>> trace.
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> [INFO] Reactor Summary:
>>>>>>
>>>>>> [INFO]
>>>>>>
>>>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>>>> [  6.635 s]
>>>>>>
>>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS
>>>>>> [  0.371 s]
>>>>>>
>>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>>> [02:46 min]
>>>>>>
>>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>>
>>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> [INFO] BUILD FAILURE
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> [INFO] Total time: 02:53 min
>>>>>>
>>>>>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>>>>>
>>>>>> [INFO] Final Memory: 33M/1036M
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>> value: 1) -> [Help 1]
>>>>>>
>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>>>
>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>>>
>>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>>>
>>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>>>
>>>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>>>
>>>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>>>
>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>
>>>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>>>
>>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>>>> execution failed.
>>>>>>
>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>>
>>>>>> at
>>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>>>
>>>>>> ... 20 more
>>>>>>
>>>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>>>> with an error: 1 (Exit value: 1)
>>>>>>
>>>>>> at
>>>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>>>
>>>>>> at
>>>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>>>
>>>>>> at
>>>>>> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>>>
>>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>>>
>>>>>> ... 22 more
>>>>>>
>>>>>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <amanda.moran@esgyn.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi there-
>>>>>>>
>>>>>>> Adding -e to the mvn command will give you more output on your
>>>>>>> error.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> Amanda
>>>>>>>
>>>>>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> as root (also tried as ordinary user)
>>>>>>>>
>>>>>>>> Refer to the error below, is it about some default settings must be
>>>>>>>> adjusted in pom?
>>>>>>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>>>>>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bosco@apache.org
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> As which user are you running this build? I was having issues when
>>>>>>>>> I ran the build as user “root”.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Bosco
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>>>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>>>>>>> *To: *<us...@ambari.apache.org>
>>>>>>>>> *Subject: *Re: Build Error
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> my mvn is 3.3.9,  will this be an issue?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please help!
>>>>>>>>>
>>>>>>>>> I am trying to build Ambari 2.2.2, got the following error as
>>>>>>>>> follows:
>>>>>>>>>
>>>>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see
>>>>>>>>> the trace.
>>>>>>>>>
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>>
>>>>>>>>> [INFO]
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Main ........................................
>>>>>>>>> SUCCESS [04:51 min]
>>>>>>>>>
>>>>>>>>> [INFO] Apache Ambari Project POM ..........................
>>>>>>>>> SUCCESS [  4.361 s]
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Web .........................................
>>>>>>>>> FAILURE [02:55 min]
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>>>>>
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Any ideas how to resolve it?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Amanda Moran
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Mithun Mathew* (Matt)
>>>>>
>>>>>    - www.linkedin.com/in/mithunmatt/
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> *Mithun Mathew* (Matt)
>>>
>>>    - www.linkedin.com/in/mithunmatt/
>>>
>>>
>>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
By the way, below are my steps:

Please let me know if correct or not, many thanks!

---------------

tar xfvz apache-ambari-2.2.2-src.tar.gz

cd apache-ambari-2.2.2-src

*mvn clean  *

*pushd ambari-metrics  *

*mvn versions:set -DnewVersion=**2.2.2.1 *

*popd  *

*mvn versions:set -DnewVersion=**2.2.2.1  *

*mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1*
* -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl -e*---------------

On Thu, Jul 28, 2016 at 12:06 PM, Ascot Moss <as...@gmail.com> wrote:

> My OS is CentOS 7:
>
>
> $node --version
>
> v6.3.0
>
>
> $ npm --version
>
> 3.10.5
>
>
> $ brunch --version
>
> 2.8.2
>
> On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com>
> wrote:
>
>> I would assume mvn to install the required version of node, npm and
>> brunch.
>>
>> This is what I have on my environment (which does mvn builds without any
>> issues):
>> bash-3.2$ node --version
>> v0.10.39
>> bash-3.2$ npm --version
>> 1.4.28
>> bash-3.2$ brunch --version
>> 1.8.5
>>
>> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:
>>
>>>
>>> Hi,
>>>
>>> Thanks for your reply!
>>>
>>> Tried the following:
>>>
>>> (step 1)
>>> npm install -g brunch
>>>
>>> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>>>
>>> /usr/lib
>>>
>>> └─┬ brunch@2.8.2
>>>
>>>   ├─┬ check-dependencies@0.12.0
>>>
>>>   │ └─┬ bower-config@1.4.0
>>>
>>>   │   └── graceful-fs@4.1.5
>>>
>>>   └─┬ deppack@0.6.1
>>>
>>>     └─┬ node-browser-modules@0.1.0
>>>
>>>       └── process@0.11.6
>>> npm WARN optional Skipping failed optional dependency
>>> /brunch/chokidar/fsevents:
>>> npm WARN notsup Not compatible with your operating system or
>>> architecture: fsevents@1.0.14
>>>
>>>
>>> (step 2)
>>>
>>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>>
>>> cd apache-ambari-2.2.2-src
>>>
>>> *mvn clean*
>>>
>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>
>>> *pushd ambari-metrics*
>>>
>>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>>
>>> *popd*
>>>
>>> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1** -DskipTests
>>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>>
>>>
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>> value: 1) -> [Help 1]
>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>> execution failed.
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>
>>> ... 20 more
>>>
>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>>> an error: 1 (Exit value: 1)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>
>>> ... 22 more
>>>
>>> [ERROR]
>>>
>>> [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 <goals> -rf :ambari-web
>>>
>>> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com>
>>> wrote:
>>>
>>>> See if *npm install -g brunch* would fix the issue?
>>>>
>>>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>> thanks for your reply!
>>>>>
>>>>> Added -e
>>>>>
>>>>>
>>>>>
>>>>> npm WARN optional Skipping failed optional dependency
>>>>> /chokidar/fsevents:
>>>>>
>>>>> npm WARN notsup Not compatible with your operating system or
>>>>> architecture: fsevents@0.2.1
>>>>>
>>>>> npm WARN Ambari@2.1.3 No license field.
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web
>>>>> ---
>>>>>
>>>>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>>>>> perhaps you meant defaultExtensions
>>>>>
>>>>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension:
>>>>> perhaps you meant defaultExtensions
>>>>>
>>>>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you
>>>>> meant order
>>>>>
>>>>> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
>>>>> execute `npm install` to install brunch plugins. SyntaxError: Setter must
>>>>> have exactly one formal parameter.
>>>>>
>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>> trace.
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] Reactor Summary:
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [INFO] Ambari Main ........................................ SUCCESS [
>>>>> 6.635 s]
>>>>>
>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>>>> 0.371 s]
>>>>>
>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>> [02:46 min]
>>>>>
>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>
>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>
>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>
>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] BUILD FAILURE
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] Total time: 02:53 min
>>>>>
>>>>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>>>>
>>>>> [INFO] Final Memory: 33M/1036M
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>> value: 1) -> [Help 1]
>>>>>
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>>
>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>>
>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>>
>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>>
>>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>>
>>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>>
>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>>
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>
>>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>>
>>>>> at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>>
>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>>> execution failed.
>>>>>
>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>>
>>>>> at
>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>>
>>>>> ... 20 more
>>>>>
>>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>>> with an error: 1 (Exit value: 1)
>>>>>
>>>>> at
>>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>>
>>>>> at
>>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>>
>>>>> at
>>>>> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>>
>>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>>
>>>>> ... 22 more
>>>>>
>>>>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
>>>>> wrote:
>>>>>
>>>>>> Hi there-
>>>>>>
>>>>>> Adding -e to the mvn command will give you more output on your error.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Amanda
>>>>>>
>>>>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> as root (also tried as ordinary user)
>>>>>>>
>>>>>>> Refer to the error below, is it about some default settings must be
>>>>>>> adjusted in pom?
>>>>>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>>>>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> As which user are you running this build? I was having issues when
>>>>>>>> I ran the build as user “root”.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Bosco
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>>>>>> *To: *<us...@ambari.apache.org>
>>>>>>>> *Subject: *Re: Build Error
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> my mvn is 3.3.9,  will this be an issue?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Please help!
>>>>>>>>
>>>>>>>> I am trying to build Ambari 2.2.2, got the following error as
>>>>>>>> follows:
>>>>>>>>
>>>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>>>>> trace.
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> [INFO] Reactor Summary:
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>>
>>>>>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>>>>>> [04:51 min]
>>>>>>>>
>>>>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS
>>>>>>>> [  4.361 s]
>>>>>>>>
>>>>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>>>>> [02:55 min]
>>>>>>>>
>>>>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>>>>
>>>>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Any ideas how to resolve it?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks,
>>>>>>
>>>>>> Amanda Moran
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Mithun Mathew* (Matt)
>>>>
>>>>    - www.linkedin.com/in/mithunmatt/
>>>>
>>>>
>>>
>>
>>
>> --
>> *Mithun Mathew* (Matt)
>>
>>    - www.linkedin.com/in/mithunmatt/
>>
>>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
My OS is CentOS 7:


$node --version

v6.3.0


$ npm --version

3.10.5


$ brunch --version

2.8.2

On Thu, Jul 28, 2016 at 10:37 AM, Mithun Mathew <mi...@gmail.com> wrote:

> I would assume mvn to install the required version of node, npm and brunch.
>
> This is what I have on my environment (which does mvn builds without any
> issues):
> bash-3.2$ node --version
> v0.10.39
> bash-3.2$ npm --version
> 1.4.28
> bash-3.2$ brunch --version
> 1.8.5
>
> On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:
>
>>
>> Hi,
>>
>> Thanks for your reply!
>>
>> Tried the following:
>>
>> (step 1)
>> npm install -g brunch
>>
>> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>>
>> /usr/lib
>>
>> └─┬ brunch@2.8.2
>>
>>   ├─┬ check-dependencies@0.12.0
>>
>>   │ └─┬ bower-config@1.4.0
>>
>>   │   └── graceful-fs@4.1.5
>>
>>   └─┬ deppack@0.6.1
>>
>>     └─┬ node-browser-modules@0.1.0
>>
>>       └── process@0.11.6
>> npm WARN optional Skipping failed optional dependency
>> /brunch/chokidar/fsevents:
>> npm WARN notsup Not compatible with your operating system or
>> architecture: fsevents@1.0.14
>>
>>
>> (step 2)
>>
>> tar xfvz apache-ambari-2.2.2-src.tar.gz
>>
>> cd apache-ambari-2.2.2-src
>>
>> *mvn clean*
>>
>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>
>> *pushd ambari-metrics*
>>
>> *mvn versions:set -DnewVersion=**2.2.2.1*
>>
>> *popd*
>>
>> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1** -DskipTests
>> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>>
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>> value: 1) -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
>> project ambari-web: Command execution failed.
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>
>> at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:497)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>> execution failed.
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>
>> ... 20 more
>>
>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>> an error: 1 (Exit value: 1)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>
>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>
>> ... 22 more
>>
>> [ERROR]
>>
>> [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 <goals> -rf :ambari-web
>>
>> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com>
>> wrote:
>>
>>> See if *npm install -g brunch* would fix the issue?
>>>
>>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>> thanks for your reply!
>>>>
>>>> Added -e
>>>>
>>>>
>>>>
>>>> npm WARN optional Skipping failed optional dependency
>>>> /chokidar/fsevents:
>>>>
>>>> npm WARN notsup Not compatible with your operating system or
>>>> architecture: fsevents@0.2.1
>>>>
>>>> npm WARN Ambari@2.1.3 No license field.
>>>>
>>>> [INFO]
>>>>
>>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web
>>>> ---
>>>>
>>>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>>>> perhaps you meant defaultExtensions
>>>>
>>>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension:
>>>> perhaps you meant defaultExtensions
>>>>
>>>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
>>>> order
>>>>
>>>> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
>>>> execute `npm install` to install brunch plugins. SyntaxError: Setter must
>>>> have exactly one formal parameter.
>>>>
>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>> trace.
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] Reactor Summary:
>>>>
>>>> [INFO]
>>>>
>>>> [INFO] Ambari Main ........................................ SUCCESS [
>>>> 6.635 s]
>>>>
>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>>> 0.371 s]
>>>>
>>>> [INFO] Ambari Web ......................................... FAILURE
>>>> [02:46 min]
>>>>
>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>
>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>
>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] BUILD FAILURE
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] Total time: 02:53 min
>>>>
>>>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>>>
>>>> [INFO] Final Memory: 33M/1036M
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>> value: 1) -> [Help 1]
>>>>
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>>
>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>>
>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>>
>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>>
>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>>
>>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>>
>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>>
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>>
>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>>> execution failed.
>>>>
>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>>
>>>> at
>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>>
>>>> at
>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>>
>>>> ... 20 more
>>>>
>>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited
>>>> with an error: 1 (Exit value: 1)
>>>>
>>>> at
>>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>>
>>>> at
>>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>>
>>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>>
>>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>>
>>>> ... 22 more
>>>>
>>>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
>>>> wrote:
>>>>
>>>>> Hi there-
>>>>>
>>>>> Adding -e to the mvn command will give you more output on your error.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Amanda
>>>>>
>>>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> as root (also tried as ordinary user)
>>>>>>
>>>>>> Refer to the error below, is it about some default settings must be
>>>>>> adjusted in pom?
>>>>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>>>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> As which user are you running this build? I was having issues when I
>>>>>>> ran the build as user “root”.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Bosco
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>>>>> *To: *<us...@ambari.apache.org>
>>>>>>> *Subject: *Re: Build Error
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> my mvn is 3.3.9,  will this be an issue?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Please help!
>>>>>>>
>>>>>>> I am trying to build Ambari 2.2.2, got the following error as
>>>>>>> follows:
>>>>>>>
>>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>>>> trace.
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> [INFO] Reactor Summary:
>>>>>>>
>>>>>>> [INFO]
>>>>>>>
>>>>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>>>>> [04:51 min]
>>>>>>>
>>>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS
>>>>>>> [  4.361 s]
>>>>>>>
>>>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>>>> [02:55 min]
>>>>>>>
>>>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>>>
>>>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>>>
>>>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> [INFO] BUILD FAILURE
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>> [ERROR] Failed to execute goal
>>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Any ideas how to resolve it?
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks,
>>>>>
>>>>> Amanda Moran
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Mithun Mathew* (Matt)
>>>
>>>    - www.linkedin.com/in/mithunmatt/
>>>
>>>
>>
>
>
> --
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>

Re: Build Error

Posted by Mithun Mathew <mi...@gmail.com>.
I would assume mvn to install the required version of node, npm and brunch.

This is what I have on my environment (which does mvn builds without any
issues):
bash-3.2$ node --version
v0.10.39
bash-3.2$ npm --version
1.4.28
bash-3.2$ brunch --version
1.8.5

On Wed, Jul 27, 2016 at 6:15 PM, Ascot Moss <as...@gmail.com> wrote:

>
> Hi,
>
> Thanks for your reply!
>
> Tried the following:
>
> (step 1)
> npm install -g brunch
>
> /usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch
>
> /usr/lib
>
> └─┬ brunch@2.8.2
>
>   ├─┬ check-dependencies@0.12.0
>
>   │ └─┬ bower-config@1.4.0
>
>   │   └── graceful-fs@4.1.5
>
>   └─┬ deppack@0.6.1
>
>     └─┬ node-browser-modules@0.1.0
>
>       └── process@0.11.6
> npm WARN optional Skipping failed optional dependency
> /brunch/chokidar/fsevents:
> npm WARN notsup Not compatible with your operating system or
> architecture: fsevents@1.0.14
>
>
> (step 2)
>
> tar xfvz apache-ambari-2.2.2-src.tar.gz
>
> cd apache-ambari-2.2.2-src
>
> *mvn clean*
>
> *mvn versions:set -DnewVersion=**2.2.2.1*
>
> *pushd ambari-metrics*
>
> *mvn versions:set -DnewVersion=**2.2.2.1*
>
> *popd*
>
> *mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1** -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl -e*
>
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
> [ERROR]
>
> [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 <goals> -rf :ambari-web
>
> On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com> wrote:
>
>> See if *npm install -g brunch* would fix the issue?
>>
>> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:
>>
>>> Hi
>>> thanks for your reply!
>>>
>>> Added -e
>>>
>>>
>>>
>>> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>>>
>>> npm WARN notsup Not compatible with your operating system or
>>> architecture: fsevents@0.2.1
>>>
>>> npm WARN Ambari@2.1.3 No license field.
>>>
>>> [INFO]
>>>
>>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>>>
>>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>>> perhaps you meant defaultExtensions
>>>
>>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
>>> you meant defaultExtensions
>>>
>>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
>>> order
>>>
>>> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
>>> execute `npm install` to install brunch plugins. SyntaxError: Setter must
>>> have exactly one formal parameter.
>>>
>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>> trace.
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Reactor Summary:
>>>
>>> [INFO]
>>>
>>> [INFO] Ambari Main ........................................ SUCCESS [
>>> 6.635 s]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>> 0.371 s]
>>>
>>> [INFO] Ambari Web ......................................... FAILURE
>>> [02:46 min]
>>>
>>> [INFO] Ambari Views ....................................... SKIPPED
>>>
>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>
>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>
>>> [INFO] Ambari Server ...................................... SKIPPED
>>>
>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>
>>> [INFO] Ambari Client ...................................... SKIPPED
>>>
>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>
>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>
>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Total time: 02:53 min
>>>
>>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>>
>>> [INFO] Final Memory: 33M/1036M
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>> value: 1) -> [Help 1]
>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed.
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>>
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>>
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>>
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>>
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>>
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>>> execution failed.
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>>
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>>
>>> ... 20 more
>>>
>>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>>> an error: 1 (Exit value: 1)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>>
>>> at
>>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>>
>>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>>
>>> ... 22 more
>>>
>>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
>>> wrote:
>>>
>>>> Hi there-
>>>>
>>>> Adding -e to the mvn command will give you more output on your error.
>>>>
>>>> Thanks.
>>>>
>>>> Amanda
>>>>
>>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>>>> wrote:
>>>>
>>>>> as root (also tried as ordinary user)
>>>>>
>>>>> Refer to the error below, is it about some default settings must be
>>>>> adjusted in pom?
>>>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>>>
>>>>>
>>>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> As which user are you running this build? I was having issues when I
>>>>>> ran the build as user “root”.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>>
>>>>>> Bosco
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>>>> *To: *<us...@ambari.apache.org>
>>>>>> *Subject: *Re: Build Error
>>>>>>
>>>>>>
>>>>>>
>>>>>> my mvn is 3.3.9,  will this be an issue?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please help!
>>>>>>
>>>>>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>>>>>
>>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>>> trace.
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> [INFO] Reactor Summary:
>>>>>>
>>>>>> [INFO]
>>>>>>
>>>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>>>> [04:51 min]
>>>>>>
>>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS
>>>>>> [  4.361 s]
>>>>>>
>>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>>> [02:55 min]
>>>>>>
>>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>>
>>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>>
>>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> [INFO] BUILD FAILURE
>>>>>>
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>>>
>>>>>>
>>>>>>
>>>>>> Any ideas how to resolve it?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks,
>>>>
>>>> Amanda Moran
>>>>
>>>
>>>
>>
>>
>> --
>> *Mithun Mathew* (Matt)
>>
>>    - www.linkedin.com/in/mithunmatt/
>>
>>
>


-- 
*Mithun Mathew* (Matt)

   - www.linkedin.com/in/mithunmatt/

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
Hi,

Thanks for your reply!

Tried the following:

(step 1)
npm install -g brunch

/usr/bin/brunch -> /usr/lib/node_modules/brunch/bin/brunch

/usr/lib

└─┬ brunch@2.8.2

  ├─┬ check-dependencies@0.12.0

  │ └─┬ bower-config@1.4.0

  │   └── graceful-fs@4.1.5

  └─┬ deppack@0.6.1

    └─┬ node-browser-modules@0.1.0

      └── process@0.11.6
npm WARN optional Skipping failed optional dependency
/brunch/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture:
fsevents@1.0.14


(step 2)

tar xfvz apache-ambari-2.2.2-src.tar.gz

cd apache-ambari-2.2.2-src

*mvn clean*

*mvn versions:set -DnewVersion=**2.2.2.1*

*pushd ambari-metrics*

*mvn versions:set -DnewVersion=**2.2.2.1*

*popd*

*mvn -B clean install package rpm:rpm -DnewVersion=**2.2.2.1** -DskipTests
-Dpython.ver="python >= 2.6" -Preplaceurl -e*


[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
ambari-web: Command execution failed. Process exited with an error: 1 (Exit
value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
project ambari-web: Command execution failed.

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command
execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an
error: 1 (Exit value: 1)

at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

[ERROR]

[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 <goals> -rf :ambari-web

On Thu, Jul 28, 2016 at 8:55 AM, Mithun Mathew <mi...@gmail.com> wrote:

> See if *npm install -g brunch* would fix the issue?
>
> On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> Hi
>> thanks for your reply!
>>
>> Added -e
>>
>>
>>
>> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>>
>> npm WARN notsup Not compatible with your operating system or
>> architecture: fsevents@0.2.1
>>
>> npm WARN Ambari@2.1.3 No license field.
>>
>> [INFO]
>>
>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>>
>> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension:
>> perhaps you meant defaultExtensions
>>
>> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
>> you meant defaultExtensions
>>
>> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
>> order
>>
>> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
>> execute `npm install` to install brunch plugins. SyntaxError: Setter must
>> have exactly one formal parameter.
>>
>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ SUCCESS [
>> 6.635 s]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 0.371 s]
>>
>> [INFO] Ambari Web ......................................... FAILURE
>> [02:46 min]
>>
>> [INFO] Ambari Views ....................................... SKIPPED
>>
>> [INFO] Ambari Admin View .................................. SKIPPED
>>
>> [INFO] ambari-metrics ..................................... SKIPPED
>>
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>
>> [INFO] Ambari Server ...................................... SKIPPED
>>
>> [INFO] Ambari Agent ....................................... SKIPPED
>>
>> [INFO] Ambari Client ...................................... SKIPPED
>>
>> [INFO] Ambari Python Client ............................... SKIPPED
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Total time: 02:53 min
>>
>> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>>
>> [INFO] Final Memory: 33M/1036M
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>> value: 1) -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
>> project ambari-web: Command execution failed.
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>>
>> at
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>>
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>>
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:497)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>>
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
>> execution failed.
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>>
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>>
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>>
>> ... 20 more
>>
>> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
>> an error: 1 (Exit value: 1)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>>
>> at
>> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>>
>> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>>
>> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>>
>> ... 22 more
>>
>> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
>> wrote:
>>
>>> Hi there-
>>>
>>> Adding -e to the mvn command will give you more output on your error.
>>>
>>> Thanks.
>>>
>>> Amanda
>>>
>>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>>> as root (also tried as ordinary user)
>>>>
>>>> Refer to the error below, is it about some default settings must be
>>>> adjusted in pom?
>>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>>
>>>>
>>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>>>> wrote:
>>>>
>>>>> As which user are you running this build? I was having issues when I
>>>>> ran the build as user “root”.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Bosco
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *From: *Ascot Moss <as...@gmail.com>
>>>>> *Reply-To: *<us...@ambari.apache.org>
>>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>>> *To: *<us...@ambari.apache.org>
>>>>> *Subject: *Re: Build Error
>>>>>
>>>>>
>>>>>
>>>>> my mvn is 3.3.9,  will this be an issue?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Please help!
>>>>>
>>>>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>>>>
>>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>>> trace.
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] Reactor Summary:
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>>> [04:51 min]
>>>>>
>>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>>>> 4.361 s]
>>>>>
>>>>> [INFO] Ambari Web ......................................... FAILURE
>>>>> [02:55 min]
>>>>>
>>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>>
>>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>>
>>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>>
>>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>>
>>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>>
>>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] BUILD FAILURE
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [ERROR] Failed to execute goal
>>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>>
>>>>>
>>>>>
>>>>> Any ideas how to resolve it?
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks,
>>>
>>> Amanda Moran
>>>
>>
>>
>
>
> --
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>

Re: Build Error

Posted by Mithun Mathew <mi...@gmail.com>.
See if *npm install -g brunch* would fix the issue?

On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:

> Hi
> thanks for your reply!
>
> Added -e
>
>
>
> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@0.2.1
>
> npm WARN Ambari@2.1.3 No license field.
>
> [INFO]
>
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>
> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
> order
>
> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
> execute `npm install` to install brunch plugins. SyntaxError: Setter must
> have exactly one formal parameter.
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 6.635 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.371 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:46
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 02:53 min
>
> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>
> [INFO] Final Memory: 33M/1036M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
> wrote:
>
>> Hi there-
>>
>> Adding -e to the mvn command will give you more output on your error.
>>
>> Thanks.
>>
>> Amanda
>>
>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>>> as root (also tried as ordinary user)
>>>
>>> Refer to the error below, is it about some default settings must be
>>> adjusted in pom?
>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>
>>>
>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>>> wrote:
>>>
>>>> As which user are you running this build? I was having issues when I
>>>> ran the build as user “root”.
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Bosco
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From: *Ascot Moss <as...@gmail.com>
>>>> *Reply-To: *<us...@ambari.apache.org>
>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>> *To: *<us...@ambari.apache.org>
>>>> *Subject: *Re: Build Error
>>>>
>>>>
>>>>
>>>> my mvn is 3.3.9,  will this be an issue?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Please help!
>>>>
>>>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>>>
>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>> trace.
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] Reactor Summary:
>>>>
>>>> [INFO]
>>>>
>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>> [04:51 min]
>>>>
>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>>> 4.361 s]
>>>>
>>>> [INFO] Ambari Web ......................................... FAILURE
>>>> [02:55 min]
>>>>
>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>
>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>
>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] BUILD FAILURE
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>
>>>>
>>>>
>>>> Any ideas how to resolve it?
>>>>
>>>> Regards
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> Thanks,
>>
>> Amanda Moran
>>
>
>


-- 
*Mithun Mathew* (Matt)

   - www.linkedin.com/in/mithunmatt/

Re: Build Error

Posted by Amanda Moran <am...@esgyn.com>.
Make sure you do all the steps on this page:

https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development

On Wed, Jul 27, 2016 at 4:52 PM, Ascot Moss <as...@gmail.com> wrote:

> Hi
> thanks for your reply!
>
> Added -e
>
>
>
> npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
>
> npm WARN notsup Not compatible with your operating system or architecture:
> fsevents@0.2.1
>
> npm WARN Ambari@2.1.3 No license field.
>
> [INFO]
>
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
>
> 28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
> you meant defaultExtensions
>
> 28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
> order
>
> 28 Jul 07:46:20 - error: Initialization error -  You probably need to
> execute `npm install` to install brunch plugins. SyntaxError: Setter must
> have exactly one formal parameter.
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [
> 6.635 s]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 0.371 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:46
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 02:53 min
>
> [INFO] Finished at: 2016-07-28T07:46:20+08:00
>
> [INFO] Final Memory: 33M/1036M
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
> project ambari-web: Command execution failed.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command
> execution failed.
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>
> ... 20 more
>
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with
> an error: 1 (Exit value: 1)
>
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
>
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
>
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
>
> ... 22 more
>
> On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
> wrote:
>
>> Hi there-
>>
>> Adding -e to the mvn command will give you more output on your error.
>>
>> Thanks.
>>
>> Amanda
>>
>> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com>
>> wrote:
>>
>>> as root (also tried as ordinary user)
>>>
>>> Refer to the error below, is it about some default settings must be
>>> adjusted in pom?
>>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (compile-brunch) on project ambari-web: Command execution failed. Process
>>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>>
>>>
>>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>>> wrote:
>>>
>>>> As which user are you running this build? I was having issues when I
>>>> ran the build as user “root”.
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Bosco
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From: *Ascot Moss <as...@gmail.com>
>>>> *Reply-To: *<us...@ambari.apache.org>
>>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>>> *To: *<us...@ambari.apache.org>
>>>> *Subject: *Re: Build Error
>>>>
>>>>
>>>>
>>>> my mvn is 3.3.9,  will this be an issue?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Please help!
>>>>
>>>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>>>
>>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>>> trace.
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] Reactor Summary:
>>>>
>>>> [INFO]
>>>>
>>>> [INFO] Ambari Main ........................................ SUCCESS
>>>> [04:51 min]
>>>>
>>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>>> 4.361 s]
>>>>
>>>> [INFO] Ambari Web ......................................... FAILURE
>>>> [02:55 min]
>>>>
>>>> [INFO] Ambari Views ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>>
>>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>>
>>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>>
>>>> [INFO] Ambari Server ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Client ...................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>>
>>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>>
>>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>>
>>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [INFO] BUILD FAILURE
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>>
>>>>
>>>>
>>>> Any ideas how to resolve it?
>>>>
>>>> Regards
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> Thanks,
>>
>> Amanda Moran
>>
>
>


-- 
Thanks,

Amanda Moran

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
Hi
thanks for your reply!

Added -e



npm WARN optional Skipping failed optional dependency /chokidar/fsevents:

npm WARN notsup Not compatible with your operating system or architecture:
fsevents@0.2.1

npm WARN Ambari@2.1.3 No license field.

[INFO]

[INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---

28 Jul 07:46:19 - warn: config.files.stylesheets.defaultExtension: perhaps
you meant defaultExtensions

28 Jul 07:46:19 - warn: config.files.templates.defaultExtension: perhaps
you meant defaultExtensions

28 Jul 07:46:19 - warn: config.files.templates.paths: perhaps you meant
order

28 Jul 07:46:20 - error: Initialization error -  You probably need to
execute `npm install` to install brunch plugins. SyntaxError: Setter must
have exactly one formal parameter.

Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.

[INFO]
------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO]

[INFO] Ambari Main ........................................ SUCCESS [
6.635 s]

[INFO] Apache Ambari Project POM .......................... SUCCESS [
0.371 s]

[INFO] Ambari Web ......................................... FAILURE [02:46
min]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO]
------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
------------------------------------------------------------------------

[INFO] Total time: 02:53 min

[INFO] Finished at: 2016-07-28T07:46:20+08:00

[INFO] Final Memory: 33M/1036M

[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
ambari-web: Command execution failed. Process exited with an error: 1 (Exit
value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
project ambari-web: Command execution failed.

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command
execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an
error: 1 (Exit value: 1)

at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

On Thu, Jul 28, 2016 at 1:36 AM, Amanda Moran <am...@esgyn.com>
wrote:

> Hi there-
>
> Adding -e to the mvn command will give you more output on your error.
>
> Thanks.
>
> Amanda
>
> On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com> wrote:
>
>> as root (also tried as ordinary user)
>>
>> Refer to the error below, is it about some default settings must be
>> adjusted in pom?
>> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>> (compile-brunch) on project ambari-web: Command execution failed. Process
>> exited with an error: 1 (Exit value: 1) -> [Help 1]
>>
>>
>> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
>> wrote:
>>
>>> As which user are you running this build? I was having issues when I ran
>>> the build as user “root”.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Bosco
>>>
>>>
>>>
>>>
>>>
>>> *From: *Ascot Moss <as...@gmail.com>
>>> *Reply-To: *<us...@ambari.apache.org>
>>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>>> *To: *<us...@ambari.apache.org>
>>> *Subject: *Re: Build Error
>>>
>>>
>>>
>>> my mvn is 3.3.9,  will this be an issue?
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>>
>>>
>>> Please help!
>>>
>>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>>
>>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the
>>> trace.
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Reactor Summary:
>>>
>>> [INFO]
>>>
>>> [INFO] Ambari Main ........................................ SUCCESS
>>> [04:51 min]
>>>
>>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>>> 4.361 s]
>>>
>>> [INFO] Ambari Web ......................................... FAILURE
>>> [02:55 min]
>>>
>>> [INFO] Ambari Views ....................................... SKIPPED
>>>
>>> [INFO] Ambari Admin View .................................. SKIPPED
>>>
>>> [INFO] ambari-metrics ..................................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>>
>>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>>
>>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>>
>>> [INFO] Ambari Server ...................................... SKIPPED
>>>
>>> [INFO] Ambari Agent ....................................... SKIPPED
>>>
>>> [INFO] Ambari Client ...................................... SKIPPED
>>>
>>> [INFO] Ambari Python Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>>
>>> [INFO] Ambari Shell ....................................... SKIPPED
>>>
>>> [INFO] Ambari Python Shell ................................ SKIPPED
>>>
>>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>>> value: 1) -> [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 <goals> -rf :ambari-web
>>>
>>>
>>>
>>> Any ideas how to resolve it?
>>>
>>> Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
> --
> Thanks,
>
> Amanda Moran
>

Re: Build Error

Posted by Amanda Moran <am...@esgyn.com>.
Hi there-

Adding -e to the mvn command will give you more output on your error.

Thanks.

Amanda

On Tue, Jul 26, 2016 at 10:32 PM, Ascot Moss <as...@gmail.com> wrote:

> as root (also tried as ordinary user)
>
> Refer to the error below, is it about some default settings must be
> adjusted in pom?
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (compile-brunch) on project ambari-web: Command execution failed. Process
> exited with an error: 1 (Exit value: 1) -> [Help 1]
>
>
> On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org>
> wrote:
>
>> As which user are you running this build? I was having issues when I ran
>> the build as user “root”.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Bosco
>>
>>
>>
>>
>>
>> *From: *Ascot Moss <as...@gmail.com>
>> *Reply-To: *<us...@ambari.apache.org>
>> *Date: *Tuesday, July 26, 2016 at 6:07 AM
>> *To: *<us...@ambari.apache.org>
>> *Subject: *Re: Build Error
>>
>>
>>
>> my mvn is 3.3.9,  will this be an issue?
>>
>>
>>
>>
>>
>> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:
>>
>> Hi,
>>
>>
>>
>>
>>
>> Please help!
>>
>> I am trying to build Ambari 2.2.2, got the following error as follows:
>>
>> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] Reactor Summary:
>>
>> [INFO]
>>
>> [INFO] Ambari Main ........................................ SUCCESS
>> [04:51 min]
>>
>> [INFO] Apache Ambari Project POM .......................... SUCCESS [
>> 4.361 s]
>>
>> [INFO] Ambari Web ......................................... FAILURE
>> [02:55 min]
>>
>> [INFO] Ambari Views ....................................... SKIPPED
>>
>> [INFO] Ambari Admin View .................................. SKIPPED
>>
>> [INFO] ambari-metrics ..................................... SKIPPED
>>
>> [INFO] Ambari Metrics Common .............................. SKIPPED
>>
>> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>>
>> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>>
>> [INFO] Ambari Metrics Collector ........................... SKIPPED
>>
>> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>>
>> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>>
>> [INFO] Ambari Server ...................................... SKIPPED
>>
>> [INFO] Ambari Agent ....................................... SKIPPED
>>
>> [INFO] Ambari Client ...................................... SKIPPED
>>
>> [INFO] Ambari Python Client ............................... SKIPPED
>>
>> [INFO] Ambari Groovy Client ............................... SKIPPED
>>
>> [INFO] Ambari Shell ....................................... SKIPPED
>>
>> [INFO] Ambari Python Shell ................................ SKIPPED
>>
>> [INFO] Ambari Groovy Shell ................................ SKIPPED
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [INFO] BUILD FAILURE
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
>> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
>> value: 1) -> [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 <goals> -rf :ambari-web
>>
>>
>>
>> Any ideas how to resolve it?
>>
>> Regards
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>


-- 
Thanks,

Amanda Moran

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
as root (also tried as ordinary user)

Refer to the error below, is it about some default settings must be
adjusted in pom?
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
(compile-brunch) on project ambari-web: Command execution failed. Process
exited with an error: 1 (Exit value: 1) -> [Help 1]


On Tue, Jul 26, 2016 at 11:53 PM, Don Bosco Durai <bo...@apache.org> wrote:

> As which user are you running this build? I was having issues when I ran
> the build as user “root”.
>
>
>
> Thanks
>
>
>
> Bosco
>
>
>
>
>
> *From: *Ascot Moss <as...@gmail.com>
> *Reply-To: *<us...@ambari.apache.org>
> *Date: *Tuesday, July 26, 2016 at 6:07 AM
> *To: *<us...@ambari.apache.org>
> *Subject: *Re: Build Error
>
>
>
> my mvn is 3.3.9,  will this be an issue?
>
>
>
>
>
> On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:
>
> Hi,
>
>
>
>
>
> Please help!
>
> I am trying to build Ambari 2.2.2, got the following error as follows:
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [04:51
> min]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 4.361 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:55
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [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 <goals> -rf :ambari-web
>
>
>
> Any ideas how to resolve it?
>
> Regards
>
>
>
>
>
>
>
>
>

Re: Build Error

Posted by Don Bosco Durai <bo...@apache.org>.
As which user are you running this build? I was having issues when I ran the build as user “root”.

 

Thanks

 

Bosco

 

 

From: Ascot Moss <as...@gmail.com>
Reply-To: <us...@ambari.apache.org>
Date: Tuesday, July 26, 2016 at 6:07 AM
To: <us...@ambari.apache.org>
Subject: Re: Build Error

 

my mvn is 3.3.9,  will this be an issue?

 

 

On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:

Hi,

 

 

Please help!

I am trying to build Ambari 2.2.2, got the following error as follows:

Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] Ambari Main ........................................ SUCCESS [04:51 min]

[INFO] Apache Ambari Project POM .......................... SUCCESS [  4.361 s]

[INFO] Ambari Web ......................................... FAILURE [02:55 min]

[INFO] Ambari Views ....................................... SKIPPED

[INFO] Ambari Admin View .................................. SKIPPED

[INFO] ambari-metrics ..................................... SKIPPED

[INFO] Ambari Metrics Common .............................. SKIPPED

[INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED

[INFO] Ambari Metrics Flume Sink .......................... SKIPPED

[INFO] Ambari Metrics Kafka Sink .......................... SKIPPED

[INFO] Ambari Metrics Storm Sink .......................... SKIPPED

[INFO] Ambari Metrics Collector ........................... SKIPPED

[INFO] Ambari Metrics Monitor ............................. SKIPPED

[INFO] Ambari Metrics Grafana ............................. SKIPPED

[INFO] Ambari Metrics Assembly ............................ SKIPPED

[INFO] Ambari Server ...................................... SKIPPED

[INFO] Ambari Agent ....................................... SKIPPED

[INFO] Ambari Client ...................................... SKIPPED

[INFO] Ambari Python Client ............................... SKIPPED

[INFO] Ambari Groovy Client ............................... SKIPPED

[INFO] Ambari Shell ....................................... SKIPPED

[INFO] Ambari Python Shell ................................ SKIPPED

[INFO] Ambari Groovy Shell ................................ SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project ambari-web: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [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 <goals> -rf :ambari-web

 

Any ideas how to resolve it?

Regards

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
my mvn is 3.3.9,  will this be an issue?



On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:

> Hi,
>
>
> Please help!
> I am trying to build Ambari 2.2.2, got the following error as follows:
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [04:51
> min]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 4.361 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:55
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [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 <goals> -rf :ambari-web
>
>
> Any ideas how to resolve it?
>
> Regards
>
>
>
>
>

Re: Build Error

Posted by Ascot Moss <as...@gmail.com>.
Some error log:

[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
ambari-web: Command execution failed. Process exited with an error: 1 (Exit
value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on
project ambari-web: Command execution failed.

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.MojoExecutionException: Command
execution failed.

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)

at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

... 20 more

Caused by: org.apache.commons.exec.ExecuteException: Process exited with an
error: 1 (Exit value: 1)

at
org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)

at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)

at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)

... 22 more

[ERROR]

[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 <goals> -rf :ambari-web





On Tue, Jul 26, 2016 at 7:41 PM, Ascot Moss <as...@gmail.com> wrote:

> Hi,
>
>
> Please help!
> I am trying to build Ambari 2.2.2, got the following error as follows:
>
> Stack trace was suppressed. Run with `LOGGY_STACKS=true` to see the trace.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] Ambari Main ........................................ SUCCESS [04:51
> min]
>
> [INFO] Apache Ambari Project POM .......................... SUCCESS [
> 4.361 s]
>
> [INFO] Ambari Web ......................................... FAILURE [02:55
> min]
>
> [INFO] Ambari Views ....................................... SKIPPED
>
> [INFO] Ambari Admin View .................................. SKIPPED
>
> [INFO] ambari-metrics ..................................... SKIPPED
>
> [INFO] Ambari Metrics Common .............................. SKIPPED
>
> [INFO] Ambari Metrics Hadoop Sink ......................... SKIPPED
>
> [INFO] Ambari Metrics Flume Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Kafka Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Storm Sink .......................... SKIPPED
>
> [INFO] Ambari Metrics Collector ........................... SKIPPED
>
> [INFO] Ambari Metrics Monitor ............................. SKIPPED
>
> [INFO] Ambari Metrics Grafana ............................. SKIPPED
>
> [INFO] Ambari Metrics Assembly ............................ SKIPPED
>
> [INFO] Ambari Server ...................................... SKIPPED
>
> [INFO] Ambari Agent ....................................... SKIPPED
>
> [INFO] Ambari Client ...................................... SKIPPED
>
> [INFO] Ambari Python Client ............................... SKIPPED
>
> [INFO] Ambari Groovy Client ............................... SKIPPED
>
> [INFO] Ambari Shell ....................................... SKIPPED
>
> [INFO] Ambari Python Shell ................................ SKIPPED
>
> [INFO] Ambari Groovy Shell ................................ SKIPPED
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO]
> ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile-brunch) on project
> ambari-web: Command execution failed. Process exited with an error: 1 (Exit
> value: 1) -> [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 <goals> -rf :ambari-web
>
>
> Any ideas how to resolve it?
>
> Regards
>
>
>
>
>