I got mine up and running!

Ubuntu 14.04
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T16:58:10-04:00)
Maven home: /opt/apache-maven/apache-maven-3.2.3
Java version: 1.7.0_71, vendor: Oracle Corporation
Java home: /opt/jdk1.7.0_71/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-37-generic", arch: "amd64", family:
"unix"


I'm hesitant to say there is an issue.. although, I was expecting the
"Enable" and "Disable" buttons to enable and disable the processors.  Seems
like this isn't working for me (or it's late and I'm doing something wrong).

Ryan


On Mon, Dec 8, 2014 at 11:59 PM, Tony Kurc <[email protected]> wrote:

> I have been running on openjdk without any notable issues. I'm based the
> docker image off java:7u65 (which is openjdk on debian, I believe)
>
> On Mon, Dec 8, 2014 at 11:16 PM, Chad Zobrisky <[email protected]>
> wrote:
>
> > Joe,
> >
> > I tried to rebuild with openjdk but skipping tests and it was successful.
> > I'm not sure if the product runs or what issues it may have running on
> > openjdk though.
> >
> > -Chad
> >
> > On Mon, Dec 8, 2014 at 11:07 PM, Joe Witt <[email protected]> wrote:
> >
> > > Thanks Chad.  Have added your observation to the Jira ticket for this:
> > > https://issues.apache.org/jira/browse/NIFI-8
> > >
> > > Joe
> > >
> > > On Mon, Dec 8, 2014 at 10:55 PM, Chad Zobrisky <[email protected]>
> > > wrote:
> > >
> > > > Hello,
> > > > In response to the OpenJDK comment, Nifi would not build for me with
> > > > openjdk 1.7.0_65 on ubuntu 14.04.  It gave the following error:
> > > >
> > > > ERROR org.apache.nifi.provenance.PersistentProvenanceRepository -
> > > > java.lang.AssertionError: On Linux and MacOSX fsyncing a directory
> > should
> > > > not throw IOException, we just don't want to rely on that in
> production
> > > > (undocumented).
> > > >
> > > > Chad
> > > >
> > > >
> > > > On Mon, Dec 8, 2014 at 10:47 PM, Drew Farris <[email protected]>
> wrote:
> > > >
> > > > > Nifi built fine for me on OSX Mavericks with jdk1.7.0_45 and maven
> > > 3.2.3
> > > > >
> > > > > Removing the 'readlink -f' from nifi.sh and setting NIFI_HOME
> > manually
> > > > > worked to the extent that I'm able to pull up the nifi flow UI on
> > > > > localhost:8080/nifi
> > > > >
> > > > > I was able to create a simple GetFile -> Base64EncodeContent ->
> > > > > PutFile flow and this worked wonderfully.
> > > > >
> > > > > I noticed that the version is 0.0.1-SNAPSHOT. Perhaps this should
> be
> > > > > 0.0.1-incubating-SNAPSHOT per the incubator release management
> > > > > guide[1]. This may not be strictly required for SNAPSHOT artifacts.
> > > > >
> > > > > [1]
> http://incubator.apache.org/guides/releasemanagement.html#naming
> > > > >
> > > > > Drew
> > > > >
> > > > > On Mon, Dec 8, 2014 at 9:40 PM, Josh Elser <[email protected]>
> > > wrote:
> > > > > > I think we use the following snippet to get around the readlink
> > issue
> > > > for
> > > > > > Accumulo:
> > > > > >
> > > > > >
> > > >
> > https://github.com/apache/accumulo/blob/master/assemble/bin/accumulo#L18
> > > > > >
> > > > > >
> > > > > > Matt Gilman wrote:
> > > > > >>
> > > > > >> Building on OSX wasn't an issue for me. However, the start
> script
> > > > > >> (bin/nifi.sh) currently does not have support for it. The only
> > issue
> > > > > >> preventing it is the usage of readlink. Anyways, until that is
> > > squared
> > > > > >> away
> > > > > >> there is a package that can be installed to provide GNU readlink
> > > > > >> capability...
> > > > > >>
> > > > > >> http://stackoverflow.com/a/4031502
> > > > > >>
> > > > > >> Matt
> > > > > >>
> > > > > >> On Mon, Dec 8, 2014 at 9:17 PM, Kelvin Rawls<
> > > [email protected]>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> builds and seems to run fine on Ubuntu 14.10
> > > > > >>>
> > > > > >>> On Mon, Dec 8, 2014 at 7:08 PM, Aldrin Piri<
> [email protected]
> > >
> > > > > wrote:
> > > > > >>>
> > > > > >>>> Joey,
> > > > > >>>>
> > > > > >>>> I filed a ticket:
> > https://issues.apache.org/jira/browse/NIFI-144
> > > > > >>>>
> > > > > >>>> Seems to be a test failure.  Didn't have time to do any more
> > > > > >>>
> > > > > >>> investigation
> > > > > >>>>
> > > > > >>>> at the moment, but I'll scope it out later if it's not
> something
> > > > that
> > > > > is
> > > > > >>>> immediately obvious.
> > > > > >>>>
> > > > > >>>> Tony,
> > > > > >>>> Thanks for the link.
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> On Mon, Dec 8, 2014 at 7:02 PM, Tony Kurc<[email protected]>
> > > wrote:
> > > > > >>>>
> > > > > >>>>> Aldrin,
> > > > > >>>>> I have my Dockerfile here -
> > > > > >>>>> https://github.com/trkurc/docker-nifi
> > > > > >>>>>
> > > > > >>>>> I built it with 'docker build -t tkurc/nifi .'
> > > > > >>>>>
> > > > > >>>>> Again, I'd appreciate comments on where it fits into the
> apache
> > > > nifi
> > > > > >>>>
> > > > > >>>> source
> > > > > >>>>>
> > > > > >>>>> tree!
> > > > > >>>>>
> > > > > >>>>> On Mon, Dec 8, 2014 at 5:48 PM, Aldrin Piri<
> > [email protected]
> > > >
> > > > > >>>>
> > > > > >>>> wrote:
> > > > > >>>>>>
> > > > > >>>>>> Tony,
> > > > > >>>>>>
> > > > > >>>>>> Do you have your Dockerfile for the build shared anywhere?
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>> On Mon, Dec 8, 2014 at 5:38 PM, Joey Echeverria<
> > > [email protected]
> > > > >
> > > > > >>>>>
> > > > > >>>>> wrote:
> > > > > >>>>>>>
> > > > > >>>>>>> Maven 3.2.1 didn't work for me. I upgraded to 3.2.3 and
> it's
> > > > > >>>
> > > > > >>> running
> > > > > >>>>>>>
> > > > > >>>>>>> now. I'll report back after the build finishes. I'm not
> sure
> > if
> > > > > >>>
> > > > > >>> Maven
> > > > > >>>>>>>
> > > > > >>>>>>> 3.2.2 works or not, but if you see this error:
> > > > > >>>>>>>
> > > > > >>>>>>> [ERROR] Failed to execute goal
> > > > > >>>>>>> org.apache.maven.plugins:maven-plugin-plugin:3.3:descriptor
> > > > > >>>>>>> (default-descriptor) on project nar-maven-plugin: Error
> > > > extracting
> > > > > >>>>>>> plugin descriptor: 'No mojo definitions were found for
> > plugin:
> > > > > >>>>>>> org.apache.nifi:nar-maven-plugin.' ->  [Help 1]
> > > > > >>>>>>>
> > > > > >>>>>>> Upgrading to Maven 3.2.3 will definitely fix it.
> > > > > >>>>>>>
> > > > > >>>>>>> -Joey
> > > > > >>>>>>>
> > > > > >>>>>>> On Mon, Dec 8, 2014 at 1:00 PM, Joe Witt<
> [email protected]>
> > > > > >>>
> > > > > >>> wrote:
> > > > > >>>>>>>>
> > > > > >>>>>>>> All
> > > > > >>>>>>>>
> > > > > >>>>>>>> We will obviously keep working on improving things and
> > > updating
> > > > > >>>>
> > > > > >>>> docs
> > > > > >>>>>>
> > > > > >>>>>> and
> > > > > >>>>>>>>
> > > > > >>>>>>>> such but for those playing along to build:
> > > > > >>>>>>>>
> > > > > >>>>>>>> 1) You need a recent Java 7
> > > > > >>>>>>>> 2) You need the latest Maven (or one that is 3.2.1 or
> newer
> > [
> > > i
> > > > > >>>>>
> > > > > >>>>> think])
> > > > > >>>>>>>>
> > > > > >>>>>>>> 3) In the root dir of the source tree run
> > > ./misc/build-order.sh
> > > > > >>>>>
> > > > > >>>>> (expect
> > > > > >>>>>>>>
> > > > > >>>>>>>> 20-30 mins build time)  -OR - if you like pain you can
> build
> > > > each
> > > > > >>>>>>>
> > > > > >>>>>>> component
> > > > > >>>>>>>>
> > > > > >>>>>>>> manually.  We understand we need to make this better.
> > > > > >>>>>>>>
> > > > > >>>>>>>> Once that is done you can go to the assemblies/nifi
> > directory
> > > > and
> > > > > >>>>
> > > > > >>>> run
> > > > > >>>>>>>>
> > > > > >>>>>>>> mvn assembly:assembly
> > > > > >>>>>>>>
> > > > > >>>>>>>> The result of that is the tar.gz of NiFi which you can
> > install
> > > > > >>>
> > > > > >>> and
> > > > > >>>>>
> > > > > >>>>> run.
> > > > > >>>>>>>>
> > > > > >>>>>>>> The current bin/nifi.sh should be enough to get you going
> on
> > > > many
> > > > > >>>>>
> > > > > >>>>> linux
> > > > > >>>>>>>>
> > > > > >>>>>>>> distros for now.  The application itself should run pretty
> > > find
> > > > > >>>>>>
> > > > > >>>>>> anywhere
> > > > > >>>>>>>>
> > > > > >>>>>>>> the JVM will run.  So we will be doing a lot of work to
> make
> > > > sure
> > > > > >>>>
> > > > > >>>> we
> > > > > >>>>>>
> > > > > >>>>>> can
> > > > > >>>>>>>>
> > > > > >>>>>>>> run on more platforms easily.  We had a nice service
> wrapper
> > > > > >>>
> > > > > >>> before
> > > > > >>>>>
> > > > > >>>>> but
> > > > > >>>>>>>
> > > > > >>>>>>> its
> > > > > >>>>>>>>
> > > > > >>>>>>>> license was a no-go so we're researching and figuring out
> > what
> > > > to
> > > > > >>>>
> > > > > >>>> do
> > > > > >>>>>>>
> > > > > >>>>>>> next.
> > > > > >>>>>>>>
> > > > > >>>>>>>> For those of you highly motivated in this area who'd love
> to
> > > > help
> > > > > >>>>>
> > > > > >>>>> solve
> > > > > >>>>>>>>
> > > > > >>>>>>>> this important problem - we need you!
> > > > > >>>>>>>>
> > > > > >>>>>>>> With the default settings you can go in a web browser to:
> > > > > >>>>>>>> http://ip-of-wherever-nifi-is:8080/nifi
> > > > > >>>>>>>>
> > > > > >>>>>>>> You can watch all the logging action in
> ./logs/nifi-app.log
> > > > > >>>>>>>>
> > > > > >>>>>>>> Very excited for us all to start taking our apache baby
> > steps
> > > > and
> > > > > >>>>
> > > > > >>>> get
> > > > > >>>>>>
> > > > > >>>>>> up
> > > > > >>>>>>>>
> > > > > >>>>>>>> and running.
> > > > > >>>>>>>>
> > > > > >>>>>>>> Thanks
> > > > > >>>>>>>> Joe
> > > > > >>>>>>>>
> > > > > >>>>>>>> On Mon, Dec 8, 2014 at 3:46 PM, Joe Witt<
> [email protected]
> > >
> > > > > >>>>
> > > > > >>>> wrote:
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> Doesn't look like it.  But by convention when we do it
> will
> > > be
> > > > > >>>>
> > > > > >>>> here:
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> https://github.com/apache/incubator-nifi
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> I'd assume that is just something that takes time to kick
> > in.
> > > > > >>>
> > > > > >>> Not
> > > > > >>>>>>>
> > > > > >>>>>>> another
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> request?
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> On Mon, Dec 8, 2014 at 3:43 PM, Benson Margulies<
> > > > > >>>>>>
> > > > > >>>>>> [email protected]
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> wrote:
> > > > > >>>>>>>>>
> > > > > >>>>>>>>>> Have we a mirror on github yet?
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>> On Mon, Dec 8, 2014 at 3:41 PM, Joe Witt<
> > [email protected]
> > > >
> > > > > >>>>>
> > > > > >>>>> wrote:
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Team,
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Very happy to finally point out that the code
> > contribution
> > > > > >>>
> > > > > >>> has
> > > > > >>>>>
> > > > > >>>>> been
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>> pushed
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> to the newly created nifi Git repo at the ASF.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> The url to browse the repo is here:
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>
> > > > > >>>
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf/incubator-nifi.git/?p=incubator-nifi.git;a=tree
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Getting started:
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> git clone
> > > > > >>>>>>
> > > > > >>>>>> https://git-wip-us.apache.org/repos/asf/incubator-nifi.git
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Very helpful documentation to get started is found
> here:
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> https://git-wip-us.apache.org/
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Tony Kurc is still wrestling with SVN issues affecting
> > the
> > > > > >>>>>
> > > > > >>>>> ability
> > > > > >>>>>>
> > > > > >>>>>> to
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> update the site but once sorted the website will point
> to
> > > our
> > > > > >>>>
> > > > > >>>> new
> > > > > >>>>>>>
> > > > > >>>>>>> Jira
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>> and
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Git instances and we can get on with business.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Thanks!
> > > > > >>>>>>>>>>> Joe
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>
> > > > > >>>>>>>
> > > > > >>>>>>>
> > > > > >>>>>>> --
> > > > > >>>>>>> Joey Echeverria
> > > > > >>>>>>>
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to