You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Pierre Villard <pi...@gmail.com> on 2016/03/22 15:03:59 UTC
Error at startup
Hi,
I updated my local checkout to current master and did a successful maven
build. When trying to start generated binaries, I have a bunch of errors
and NIFI does not start. See attached logs.
Does someone experience the same issue?
Thanks,
Pierre
Re: Error at startup
Posted by Pierre Villard <pi...@gmail.com>.
Thanks Matt,
Logs in Maven build are all OK (SUCCESS for each module at the end). I did
a new full build and I got a similar error (not exactly the same but
related to compilation). I tried once again and this is now OK. This is
really strange that Maven is not complaining about compilation issues...
Next time I'll try to keep Maven build logs in case it appears again to
have a deeper look...
Pierre
2016-03-22 19:05 GMT+01:00 Matt Gilman <ma...@gmail.com>:
> Pierre,
>
> The error message is really strange. It appears that a number of classes
> did not compile correctly. Was there any unexpected output during the maven
> build? I just verified the build locally on OSX and Windows 10. In Windows
> 10 I copied the zip, extracted, and executed run-nifi.bat without
> additionally configuration.
>
> Matt
>
> On Tue, Mar 22, 2016 at 10:47 AM, Pierre Villard <
> pierre.villard.fr@gmail.com> wrote:
>
> > I did a full build with Maven, took the generated zip
> > (nifi-0.6.0-SNAPSHOT-bin.zip), unzipped it, and executed the
> run-nifi.bat.
> > So it is a clean instance. As you said, the local-provider is correctly
> > set:
> >
> > <local-provider>
> > <id>local-provider</id>
> >
> >
> >
> <class>org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider</class>
> > <property name="Directory">./state/local</property>
> > </local-provider>
> >
> >
> > 2016-03-22 15:38 GMT+01:00 Matt Gilman <ma...@gmail.com>:
> >
> > > Pierre,
> > >
> > > Are you attempting to upgrade an existing instance? If so, what version
> > are
> > > you coming from? I'm wondering if there is some configuration missing
> > after
> > > the upgrade. Are you able to start up the built assembly using default
> > > configuration?
> > >
> > > In your <NIFI_HOME>/conf/state-management.xml can you verify the
> > > configuration of the local-provider? By default, it's configured to
> > > use
> > >
> >
> org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider
> > > with a Directory property that points to ./state/local.
> > >
> > > I think the error in the logs is having trouble with that property.
> > >
> > > Matt
> > >
> > >
> > > On Tue, Mar 22, 2016 at 10:16 AM, Pierre Villard <
> > > pierre.villard.fr@gmail.com> wrote:
> > >
> > > > OK. Logs are here:
> > > >
> https://raw.githubusercontent.com/pvillard31/share/master/nifi-app.log
> > > >
> > > > 2016-03-22 15:12 GMT+01:00 Matt Burgess <ma...@gmail.com>:
> > > >
> > > > > I can't see them, perhaps the attachment is being removed. Can you
> > > paste
> > > > > the text from the logs into the email?
> > > > >
> > > > > Thanks,
> > > > > Matt
> > > > >
> > > > > On Tue, Mar 22, 2016 at 10:10 AM, Pierre Villard <
> > > > > pierre.villard.fr@gmail.com> wrote:
> > > > >
> > > > > > Erf that's strange, I do see logs from my side.
> > > > > > Is it better?
> > > > > >
> > > > > > 2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky <
> > > > > ozhurakousky@hortonworks.com>
> > > > > > :
> > > > > >
> > > > > >> Pierre, no logs ;)
> > > > > >>
> > > > > >> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
> > > > > >> pierre.villard.fr@gmail.com> wrote:
> > > > > >> >
> > > > > >> > Hi,
> > > > > >> >
> > > > > >> > I updated my local checkout to current master and did a
> > successful
> > > > > >> maven build. When trying to start generated binaries, I have a
> > bunch
> > > > of
> > > > > >> errors and NIFI does not start. See attached logs.
> > > > > >> >
> > > > > >> > Does someone experience the same issue?
> > > > > >> >
> > > > > >> > Thanks,
> > > > > >> > Pierre
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Error at startup
Posted by Matt Gilman <ma...@gmail.com>.
Pierre,
The error message is really strange. It appears that a number of classes
did not compile correctly. Was there any unexpected output during the maven
build? I just verified the build locally on OSX and Windows 10. In Windows
10 I copied the zip, extracted, and executed run-nifi.bat without
additionally configuration.
Matt
On Tue, Mar 22, 2016 at 10:47 AM, Pierre Villard <
pierre.villard.fr@gmail.com> wrote:
> I did a full build with Maven, took the generated zip
> (nifi-0.6.0-SNAPSHOT-bin.zip), unzipped it, and executed the run-nifi.bat.
> So it is a clean instance. As you said, the local-provider is correctly
> set:
>
> <local-provider>
> <id>local-provider</id>
>
>
> <class>org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider</class>
> <property name="Directory">./state/local</property>
> </local-provider>
>
>
> 2016-03-22 15:38 GMT+01:00 Matt Gilman <ma...@gmail.com>:
>
> > Pierre,
> >
> > Are you attempting to upgrade an existing instance? If so, what version
> are
> > you coming from? I'm wondering if there is some configuration missing
> after
> > the upgrade. Are you able to start up the built assembly using default
> > configuration?
> >
> > In your <NIFI_HOME>/conf/state-management.xml can you verify the
> > configuration of the local-provider? By default, it's configured to
> > use
> >
> org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider
> > with a Directory property that points to ./state/local.
> >
> > I think the error in the logs is having trouble with that property.
> >
> > Matt
> >
> >
> > On Tue, Mar 22, 2016 at 10:16 AM, Pierre Villard <
> > pierre.villard.fr@gmail.com> wrote:
> >
> > > OK. Logs are here:
> > > https://raw.githubusercontent.com/pvillard31/share/master/nifi-app.log
> > >
> > > 2016-03-22 15:12 GMT+01:00 Matt Burgess <ma...@gmail.com>:
> > >
> > > > I can't see them, perhaps the attachment is being removed. Can you
> > paste
> > > > the text from the logs into the email?
> > > >
> > > > Thanks,
> > > > Matt
> > > >
> > > > On Tue, Mar 22, 2016 at 10:10 AM, Pierre Villard <
> > > > pierre.villard.fr@gmail.com> wrote:
> > > >
> > > > > Erf that's strange, I do see logs from my side.
> > > > > Is it better?
> > > > >
> > > > > 2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky <
> > > > ozhurakousky@hortonworks.com>
> > > > > :
> > > > >
> > > > >> Pierre, no logs ;)
> > > > >>
> > > > >> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
> > > > >> pierre.villard.fr@gmail.com> wrote:
> > > > >> >
> > > > >> > Hi,
> > > > >> >
> > > > >> > I updated my local checkout to current master and did a
> successful
> > > > >> maven build. When trying to start generated binaries, I have a
> bunch
> > > of
> > > > >> errors and NIFI does not start. See attached logs.
> > > > >> >
> > > > >> > Does someone experience the same issue?
> > > > >> >
> > > > >> > Thanks,
> > > > >> > Pierre
> > > > >> >
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: Error at startup
Posted by Pierre Villard <pi...@gmail.com>.
I did a full build with Maven, took the generated zip
(nifi-0.6.0-SNAPSHOT-bin.zip), unzipped it, and executed the run-nifi.bat.
So it is a clean instance. As you said, the local-provider is correctly set:
<local-provider>
<id>local-provider</id>
<class>org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider</class>
<property name="Directory">./state/local</property>
</local-provider>
2016-03-22 15:38 GMT+01:00 Matt Gilman <ma...@gmail.com>:
> Pierre,
>
> Are you attempting to upgrade an existing instance? If so, what version are
> you coming from? I'm wondering if there is some configuration missing after
> the upgrade. Are you able to start up the built assembly using default
> configuration?
>
> In your <NIFI_HOME>/conf/state-management.xml can you verify the
> configuration of the local-provider? By default, it's configured to
> use
> org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider
> with a Directory property that points to ./state/local.
>
> I think the error in the logs is having trouble with that property.
>
> Matt
>
>
> On Tue, Mar 22, 2016 at 10:16 AM, Pierre Villard <
> pierre.villard.fr@gmail.com> wrote:
>
> > OK. Logs are here:
> > https://raw.githubusercontent.com/pvillard31/share/master/nifi-app.log
> >
> > 2016-03-22 15:12 GMT+01:00 Matt Burgess <ma...@gmail.com>:
> >
> > > I can't see them, perhaps the attachment is being removed. Can you
> paste
> > > the text from the logs into the email?
> > >
> > > Thanks,
> > > Matt
> > >
> > > On Tue, Mar 22, 2016 at 10:10 AM, Pierre Villard <
> > > pierre.villard.fr@gmail.com> wrote:
> > >
> > > > Erf that's strange, I do see logs from my side.
> > > > Is it better?
> > > >
> > > > 2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky <
> > > ozhurakousky@hortonworks.com>
> > > > :
> > > >
> > > >> Pierre, no logs ;)
> > > >>
> > > >> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
> > > >> pierre.villard.fr@gmail.com> wrote:
> > > >> >
> > > >> > Hi,
> > > >> >
> > > >> > I updated my local checkout to current master and did a successful
> > > >> maven build. When trying to start generated binaries, I have a bunch
> > of
> > > >> errors and NIFI does not start. See attached logs.
> > > >> >
> > > >> > Does someone experience the same issue?
> > > >> >
> > > >> > Thanks,
> > > >> > Pierre
> > > >> >
> > > >>
> > > >>
> > > >
> > >
> >
>
Re: Error at startup
Posted by Matt Gilman <ma...@gmail.com>.
Pierre,
Are you attempting to upgrade an existing instance? If so, what version are
you coming from? I'm wondering if there is some configuration missing after
the upgrade. Are you able to start up the built assembly using default
configuration?
In your <NIFI_HOME>/conf/state-management.xml can you verify the
configuration of the local-provider? By default, it's configured to
use org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider
with a Directory property that points to ./state/local.
I think the error in the logs is having trouble with that property.
Matt
On Tue, Mar 22, 2016 at 10:16 AM, Pierre Villard <
pierre.villard.fr@gmail.com> wrote:
> OK. Logs are here:
> https://raw.githubusercontent.com/pvillard31/share/master/nifi-app.log
>
> 2016-03-22 15:12 GMT+01:00 Matt Burgess <ma...@gmail.com>:
>
> > I can't see them, perhaps the attachment is being removed. Can you paste
> > the text from the logs into the email?
> >
> > Thanks,
> > Matt
> >
> > On Tue, Mar 22, 2016 at 10:10 AM, Pierre Villard <
> > pierre.villard.fr@gmail.com> wrote:
> >
> > > Erf that's strange, I do see logs from my side.
> > > Is it better?
> > >
> > > 2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky <
> > ozhurakousky@hortonworks.com>
> > > :
> > >
> > >> Pierre, no logs ;)
> > >>
> > >> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
> > >> pierre.villard.fr@gmail.com> wrote:
> > >> >
> > >> > Hi,
> > >> >
> > >> > I updated my local checkout to current master and did a successful
> > >> maven build. When trying to start generated binaries, I have a bunch
> of
> > >> errors and NIFI does not start. See attached logs.
> > >> >
> > >> > Does someone experience the same issue?
> > >> >
> > >> > Thanks,
> > >> > Pierre
> > >> >
> > >>
> > >>
> > >
> >
>
Re: Error at startup
Posted by Pierre Villard <pi...@gmail.com>.
OK. Logs are here:
https://raw.githubusercontent.com/pvillard31/share/master/nifi-app.log
2016-03-22 15:12 GMT+01:00 Matt Burgess <ma...@gmail.com>:
> I can't see them, perhaps the attachment is being removed. Can you paste
> the text from the logs into the email?
>
> Thanks,
> Matt
>
> On Tue, Mar 22, 2016 at 10:10 AM, Pierre Villard <
> pierre.villard.fr@gmail.com> wrote:
>
> > Erf that's strange, I do see logs from my side.
> > Is it better?
> >
> > 2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky <
> ozhurakousky@hortonworks.com>
> > :
> >
> >> Pierre, no logs ;)
> >>
> >> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
> >> pierre.villard.fr@gmail.com> wrote:
> >> >
> >> > Hi,
> >> >
> >> > I updated my local checkout to current master and did a successful
> >> maven build. When trying to start generated binaries, I have a bunch of
> >> errors and NIFI does not start. See attached logs.
> >> >
> >> > Does someone experience the same issue?
> >> >
> >> > Thanks,
> >> > Pierre
> >> >
> >>
> >>
> >
>
Re: Error at startup
Posted by Matt Burgess <ma...@gmail.com>.
I can't see them, perhaps the attachment is being removed. Can you paste
the text from the logs into the email?
Thanks,
Matt
On Tue, Mar 22, 2016 at 10:10 AM, Pierre Villard <
pierre.villard.fr@gmail.com> wrote:
> Erf that's strange, I do see logs from my side.
> Is it better?
>
> 2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky <oz...@hortonworks.com>
> :
>
>> Pierre, no logs ;)
>>
>> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
>> pierre.villard.fr@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I updated my local checkout to current master and did a successful
>> maven build. When trying to start generated binaries, I have a bunch of
>> errors and NIFI does not start. See attached logs.
>> >
>> > Does someone experience the same issue?
>> >
>> > Thanks,
>> > Pierre
>> >
>>
>>
>
Re: Error at startup
Posted by Pierre Villard <pi...@gmail.com>.
Erf that's strange, I do see logs from my side.
Is it better?
2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky <oz...@hortonworks.com>:
> Pierre, no logs ;)
>
> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
> pierre.villard.fr@gmail.com> wrote:
> >
> > Hi,
> >
> > I updated my local checkout to current master and did a successful maven
> build. When trying to start generated binaries, I have a bunch of errors
> and NIFI does not start. See attached logs.
> >
> > Does someone experience the same issue?
> >
> > Thanks,
> > Pierre
> >
>
>
Re: Error at startup
Posted by Oleg Zhurakousky <oz...@hortonworks.com>.
Pierre, no logs ;)
> On Mar 22, 2016, at 10:03 AM, Pierre Villard <pi...@gmail.com> wrote:
>
> Hi,
>
> I updated my local checkout to current master and did a successful maven build. When trying to start generated binaries, I have a bunch of errors and NIFI does not start. See attached logs.
>
> Does someone experience the same issue?
>
> Thanks,
> Pierre
>