Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1D01C200C03 for ; Fri, 6 Jan 2017 19:48:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1B978160B39; Fri, 6 Jan 2017 18:48:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9C499160B37 for ; Fri, 6 Jan 2017 19:48:44 +0100 (CET) Received: (qmail 5349 invoked by uid 500); 6 Jan 2017 18:48:43 -0000 Mailing-List: contact users-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@nifi.apache.org Delivered-To: mailing list users@nifi.apache.org Received: (qmail 5339 invoked by uid 99); 6 Jan 2017 18:48:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2017 18:48:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 0ADB01800B7 for ; Fri, 6 Jan 2017 18:48:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.409 X-Spam-Level: ** X-Spam-Status: No, score=2.409 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, T_MIME_MALF=0.01, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id tvhRtWZAAJEG for ; Fri, 6 Jan 2017 18:48:40 +0000 (UTC) Received: from mail-qk0-f176.google.com (mail-qk0-f176.google.com [209.85.220.176]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E19B85F1B8 for ; Fri, 6 Jan 2017 18:48:39 +0000 (UTC) Received: by mail-qk0-f176.google.com with SMTP id s140so60632060qke.0 for ; Fri, 06 Jan 2017 10:48:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=BW3zzrYMVl3YZ0lkH5QLI88uqiglGXSWrnkLH6yAupU=; b=snnWfHt7m2zfHk2K6of8mN2PmV6g5jfdCMXu6HeO+ZUw+2Sv1h4bpmR1ekSjgIYPep f6G2L3nJ/hu+uIN5J6yG86hlobpwqekfhSkJtVdRg7p5PudAochD/fIi4QNP8YKGVxqi a2C6TfbMKCWR0r//nKnng2Ahx+0NzLekXPzvR0wP8Vdrw2KiTRJ0iwQxCyG4RoQF7VRt 9DNvrRkkzALOjBTZOYXo+fHRYAxfhjq1JyxxwbrXqYim56yNCPfJ3tfiQL7CDpzQU/wv FHDU/qKTmvlq6GC5QnFgqtKzPsxvOSy5FJQbrFSRtu54I/oZU6fc/4p3gK/col+IdTYP EefQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=BW3zzrYMVl3YZ0lkH5QLI88uqiglGXSWrnkLH6yAupU=; b=h+SojLL1LBGMMD5l+rTuc89dVC3eyAPQiDKpVTGFFUgh5i2VLA6STtVzre0tt57so2 ANAiz5dEQiGLtxDhaHFIGIiX8yxthG4QP+/ucaWkGYOgDsSg0ySjVKwfBRq+bjJfksXB De3uygk4LzsB3sBjRgXp3VBwGihPyEStXfLvmscdkf0AJhzXt05YdQuAeFvPPAPtpt7y aTyqSK8RFm9t9+g8P3rw7IPHQeQVD9dgWPUUtnRN56GKMRJPvHd6a4cCsK1MXPVTUWjt gh9b4CU/fu+9tnYo974zRADZvbNT2NHCl0CwJmkVZexhr/nsRoP1dLyA5oXFFHuvrSoV G/7w== X-Gm-Message-State: AIkVDXJOUCXfVMvzocb3sa2HRW9a6IxMuh5pjGWAl4WwCgcxzQy09NyxnZX6E7X5cGipSYvPXvaZMl/DresRtg== X-Received: by 10.55.49.7 with SMTP id x7mr70117057qkx.141.1483728516467; Fri, 06 Jan 2017 10:48:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.53.135 with HTTP; Fri, 6 Jan 2017 10:48:36 -0800 (PST) In-Reply-To: References: From: Matt Gilman Date: Fri, 6 Jan 2017 13:48:36 -0500 Message-ID: Subject: Re: NiFi UI fails to display Processor Group: NullPointerException To: users@nifi.apache.org Content-Type: multipart/alternative; boundary=001a114906f42ad04b05457177de archived-at: Fri, 06 Jan 2017 18:48:46 -0000 --001a114906f42ad04b05457177de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Can you check the app log for the stack trace? Being a cluster, if there was a bug in the response merging logic it may be logged outside the user log. Also, is it possible that all the nodes did not get upgraded? I'm pretty sure that GenerateFlowFile received some new properties in 1.1.0. I wonder if there is an issue when the different nodes have different sets of properties for the same component. Matt On Fri, Jan 6, 2017 at 1:25 PM, Kevin Verhoeven wrote: > I=E2=80=99ll enable DEBUG level logging and see if I can capture anything= . > > > > Navigating into the Processor Group still works in my 1.0.0 installation, > it is only when I updated a cluster to 1.1.1 that I started seeing this > behavior. I have two clusters, Dev and Prod and I updated Dev. Prod remai= ns > 1.0.0. > > > > The problem also happens on new Processor Groups. Here=E2=80=99s my test: > > > > 1. Create new Processor Group. > > 2. Browse into the Processor Group. > > 3. Add UpdateAttribute Processor, works. > > 4. Add GenerateFlowFile Processor, fails. (error is the same error as > above). > > > > At this point I cannot enter my new Processor Group. > > > > Strangely, my Processor Groups that do not have a GenerateFlowFile > Processor still work. So I might have just narrowed this down to one > Processor, GenerateFlowFile. > > > > Kevin > > > > *From:* Matt Gilman [mailto:matt.c.gilman@gmail.com] > *Sent:* Friday, January 6, 2017 10:18 AM > > *To:* users@nifi.apache.org > *Subject:* Re: NiFi UI fails to display Processor Group: > NullPointerException > > > > Thanks for the extra details. So it is the endpoint for loading the group > which contains the necessary configuration and statistics to generate the > graph. Can you try enabling DEBUG level logging for this package in your > conf/logback.xml? > > > > org.apache.nifi.web.api.config > > > > Does navigating into this Process Group still work in your 1.0.0 > installation? Do you know if there is anything unique about the contents = of > that group? I'm just trying to find something that might help point us in > the correct direction so we can figure out a work around and get the issu= e > addressed for upcoming releases. > > > > Thanks > > > > Matt > > > > On Fri, Jan 6, 2017 at 1:01 PM, Kevin Verhoeven > wrote: > > Thank you for your response, I really appreciate your help. I reviewed th= e > user log and did not see a stack trace after the NPE message. Looking > backward in the user log I see other log messages for the same thread and= I > found the endpoint being requested: > > > > 2017-01-06 17:45:44,338 INFO [NiFi Web Server-3798] > org.apache.nifi.web.filter.RequestLogger Attempting request for > (anonymous) GET http://servername:10000/nifi-api/flow/process-groups/ > e8a4ad16-1b4e-3afc-a8e0-0a2cdda95632 (source ip: ipaddress) > > =E2=80=A6 > > 2017-01-06 17:45:44,360 ERROR [NiFi Web Server-3798] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error > response.java.lang.NullPointerException: null > > > > Using Developer Tools in Chrome I compared the endpoint and it matches, > here=E2=80=99s what Chrome indicated: > > > > GET http://servername:10000/nifi-api/flow/process-groups/ > e8a4ad16-1b4e-3afc-a8e0-0a2cdda95632 500 (Internal Server Error) > > An unexpected error has occurred. Please check the logs for additional > details. > > > > > > send @ jquery-2.1.1.min.js:2 > > ajax @ jquery-2.1.1.min.js:2 > > u @ nf-canvas-all.js?1.1.1:45 > > (anonymous) @ nf-canvas-all.js?1.1.1:45 > > Deferred @ jquery-2.1.1.min.js:2 > > reload @ nf-canvas-all.js?1.1.1:45 > > enterGroup @ nf-canvas-all.js?1.1.1:4 > > (anonymous) @ nf-canvas-all.js?1.1.1:32 > > (anonymous) @ d3.min.js:1 > > > > > > Response Headers: > > HTTP/1.1 500 Internal Server Error > > Date: Fri, 06 Jan 2017 17:54:07 GMT > > Content-Type: text/plain > > Transfer-Encoding: chunked > > Server: Jetty(9.3.9.v20160517) > > > > > > Request Headers > > Accept: application/json, text/javascript, */*; q=3D0.01 > > Accept-Encoding: gzip, deflate, sdch > > Accept-Language: en-US,en;q=3D0.8 > > Connection: keep-alive > > Host: servername:10000 > > Referer: http://servername:10000/nifi/ > > User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 > (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 > > X-Requested-With: XMLHttpRequest > > > > > > There is one other error that Chrome points out to me, but it might not b= e > related. Kerberos returns an error: > > > > POST http://servername:10000/nifi-api/access/kerberos 409 > (Conflict) > > > > Probably not related, but otherwise I do not see any other error that > would explain what is going on with the Process Group. > > > > Regards, > > > > Kevin > > > > *From:* Matt Gilman [mailto:matt.c.gilman@gmail.com] > *Sent:* Thursday, January 5, 2017 5:14 PM > *To:* users@nifi.apache.org > *Subject:* Re: NiFi UI fails to display Processor Group: > NullPointerException > > > > Sorry for the inconvenience. Is there a stack trace listed in the user > log? A quick glance at the code and the error handler looks like it logs > the exception (which should include the stack trace) unconditionally. > > > > Also, you should be able to look backward from that line to look for othe= r > log messages for the same thread 'NiFi Web Server-299' to see which > endpoint was being invoked. Sounds like the endpoint is going to be the o= ne > that returns that nest Process Group but just to be sure. Additionally, y= ou > can verify that by checking the develop tools in your browser to see whic= h > requestion failed. > > > > If there is a stack trace following the NPE message, that would be > helpful. Thanks. > > > > Matt > > > > On Thu, Jan 5, 2017 at 7:47 PM, Kevin Verhoeven > wrote: > > After updating from NiFi 1.0 to 1.1.1, I am unable to browse into one or > more of my Processor Groups. The UI seems to work until I double click on= a > specific Processor Group, then the UI throws an error =E2=80=9CAn unexpec= ted error > has occurred=E2=80=9D and I find the following in the nifi-user.log log f= ile: > > > > 2017-01-05 22:29:15,886 INFO [NiFi Web Server-19] > org.apache.nifi.web.filter.RequestLogger Attempting request for > (anonymous) GET http://servername:10000/nifi-api/flow/process-groups/ > e8a4ad16-1b4e-3afc-a8e0-0a2cdda95632 (source ip: ipaddress) > > 2017-01-05 22:29:16,397 INFO [NiFi Web Server-305] > org.apache.nifi.web.filter.RequestLogger Attempting request for > (anonymous) GET http:// servername:10000/nifi-api/flow/current-user > (source ip: ipaddress) > > =E2=80=A6 > > 2017-01-05 22:29:16,402 ERROR [NiFi Web Server-299] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > > java.lang.NullPointerException: null > > =E2=80=A6 > > 2017-01-05 22:29:16,408 INFO [NiFi Web Server-305] > org.apache.nifi.web.filter.RequestLogger Attempting request for > (anonymous) GET http:// servername:10000/nifi-api/flow/controller/bulleti= ns > (source ip: 10 ipaddress) > > 2017-01-05 22:29:16,821 INFO [NiFi Web Server-19] > org.apache.nifi.web.filter.RequestLogger Attempting request for > (anonymous) GET http:// servername:10000/nifi-api/site-to-site (source > ip: ipaddress) > > > > Any advice on how to proceed? > > > Thanks, > > > > Kevin > > > > > --001a114906f42ad04b05457177de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Can you check the app log for the stack trace? Being = a cluster, if there was a bug in the response merging logic it may be logge= d outside the user log.

Also, is it possible t= hat all the nodes did not get upgraded? I'm pretty sure that GenerateFl= owFile received some new properties in 1.1.0. I wonder if there is an issue= when the different nodes have different sets of properties for the same co= mponent.

Matt

On Fri, Jan 6, 2017 at 1:25 PM, Kevin Verh= oeven <Kevin.Verhoeven@ds-iq.com> wrote:

I=E2=80=99ll enable DEBUG level loggi= ng and see if I can capture anything.

=C2=A0

Navigating into the Processor Group s= till works in my 1.0.0 installation, it is only when I updated a cluster to= 1.1.1 that I started seeing this behavior. I have two clusters, Dev and Prod and I updated Dev. Prod remains 1.0.0. =

=C2=A0

The problem also happens on new Proce= ssor Groups. Here=E2=80=99s my test:

=C2=A0

1. Create new Processor Group.

2. Browse into the Processor Group.

3. Add UpdateAttribute Processor, wor= ks.

4. Add GenerateFlowFile Processor, fa= ils. (error is the same error as above).

=C2=A0

At this point I cannot enter my new P= rocessor Group.

=C2=A0

Strangely, my Processor Groups that d= o not have a GenerateFlowFile Processor still work. So I might have just na= rrowed this down to one Processor, GenerateFlowFile.

=C2=A0

Kevin

=C2=A0

From: Matt Gilman [mailto:matt.c.gilman@gmail.com]
Sent: Friday, January 6, 2017 10:18 AM


To: users= @nifi.apache.org
Subject: Re: NiFi UI fails to display Processor Group: NullPointerEx= ception

=C2=A0

Thanks for the extra details. So it is the endpoint = for loading the group which contains the necessary configuration and statis= tics to generate the graph. Can you try enabling DEBUG level logging for th= is package in your conf/logback.xml?

=C2=A0

org.apache.nifi.web.api.config

=C2=A0

Does navigating into this Process Group still work i= n your 1.0.0 installation? Do you know if there is anything unique about th= e contents of that group? I'm just trying to find something that might = help point us in the correct direction so we can figure out a work around and get the issue addressed for upcomin= g releases.

=C2=A0

Thanks

=C2=A0

Matt=C2=A0

=C2=A0

On Fri, Jan 6, 2017 at 1:01 PM, Kevin Verhoeven <= Kevin.Verhoe= ven@ds-iq.com> wrote:

Thank you for your response, I really= appreciate your help. I reviewed the user log and did not see a stack trace after the NPE message. Looking backward in the user log I se= e other log messages for the same thread and I found the endpoint being req= uested:

=C2=A0

2017-01-06 17:45:44,338 INFO [NiFi We= b Server-3798] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://servername:10000/nifi-api/flow/process-groups/e8a4ad16-1b4= e-3afc-a8e0-0a2cdda95632 (source ip: ipaddress)

=E2=80=A6

2017-01-06 17:45:44,360 ERROR [NiFi W= eb Server-3798] o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: java.lang.NullPointerException. Returning Interna= l Server Error response.java.lang.NullPointerException: null=

=C2=A0

Using Developer Tools in Chrome I com= pared the endpoint and it matches, here=E2=80=99s what Chrome indicated:

=C2=A0

GET =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0http://servername:10000/nifi= -api/flow/process-groups/e8a4ad16-1b4e-3afc-a8e0-0a2cdda95632 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0500 (Internal Server Error)<= /u>

An unexpected error has occurred. Ple= ase check the logs for additional details.

=C2=A0

=C2=A0

send=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 jquery-2= .1.1.min.js:2

ajax=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 @=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 jquery-2.1.1.min.js:2

u=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 nf-canvas-all.js?1.1.1:45

(anonymous)=C2=A0=C2=A0=C2=A0=C2=A0 @= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 nf-canva= s-all.js?1.1.1:45

Deferred=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 @=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 jquery-2.1.1.min.js:2=

reload=C2=A0=C2=A0 @=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 nf-canvas-all.js?1.1.1:= 45

enterGroup=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 @=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 nf-canvas-all.js?1.1.1:4

(anonymous)=C2=A0=C2=A0=C2=A0=C2=A0 @= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 nf-canva= s-all.js?1.1.1:32

(anonymous)=C2=A0=C2=A0=C2=A0=C2=A0 @= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 d3.min.j= s:1

=C2=A0

=C2=A0

Response Headers:

HTTP/1.1 500 Internal Server Error

Date: Fri, 06 Jan 2017 17:54:07 GMT

Content-Type: text/plain

Transfer-Encoding: chunked<= /u>

Server: Jetty(9.3.9.v20160517)=

=C2=A0

=C2=A0

Request Headers<= /p>

Accept: application/json, text/javasc= ript, */*; q=3D0.01

Accept-Encoding: gzip, deflate, sdch<= /span>

Accept-Language: en-US,en;q=3D0.8

Connection: keep-alive<= u>

Host: servername:10000<= u>

Referer: http://serverna= me:10000/nifi/

User-Agent: Mozilla/5.0 (Windows NT 1= 0.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

X-Requested-With: XMLHttpRequest

=C2=A0

=C2=A0

There is one other error that Chrome = points out to me, but it might not be related. Kerberos returns an error:

=C2=A0

POST =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0http://servername:10000/nifi-api/access/kerberos =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0409 (Conflict)

=C2=A0

Probably not related, but otherwise I= do not see any other error that would explain what is going on with the Process Group.

=C2=A0

Regards,

=C2=A0

Kevin

=C2=A0

From: Matt Gilman [mailto:matt.c.gilman@gmail.com]
Sent: Thursday, January 5, 2017 5:14 PM
To: users= @nifi.apache.org
Subject: Re: NiFi UI fails to display Processor Group: NullPointerEx= ception

=C2=A0

Sorry for the inconvenience. Is there a stack trace = listed in the user log? A quick glance at the code and the error handler lo= oks like it logs the exception (which should include the stack trace) unconditionally.

=C2=A0

Also, you should be able to look backward from that = line to look for other log messages for the same thread 'NiFi Web Serve= r-299' to see which endpoint was being invoked. Sounds like the endpoint is going to be the one that returns that nest Process Gr= oup but just to be sure. Additionally, you can verify that by checking the = develop tools in your browser to see which requestion failed.=

=C2=A0

If there is a stack trace following the NPE message,= that would be helpful. Thanks.

=C2=A0

Matt

=C2=A0

On Thu, Jan 5, 2017 at 7:47 PM, Kevin Verhoeven <= Kevin.Verhoe= ven@ds-iq.com> wrote:

After updating from NiFi 1.0 to 1.1.1= , I am unable to browse into one or more of my Processor Groups. The UI seems to work until I double click on a specific Processor Group, t= hen the UI throws an error =E2=80=9CAn unexpected error has occurred=E2=80= =9D and I find the following in the nifi-user.log log file:

=C2=A0

2017-01-05 22:29:15,886 INFO [NiFi We= b Server-19] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://servername:10000/nifi-api/flow/process-groups/e8a4ad16-1b4= e-3afc-a8e0-0a2cdda95632 (source ip: ipaddress)

2017-01-05 22:29:16,397 INFO [NiFi We= b Server-305] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http:// servername:10000/nifi-api/flow/cu= rrent-user (source ip: ipaddress)

=E2=80=A6

2017-01-05 22:29:16,402 ERROR [NiFi W= eb Server-299] o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: java.lang.NullPointerException. Returning Interna= l Server Error response.

java.lang.NullPointerException: = null

=E2=80=A6

2017-01-05 22:29:16,408 INFO [NiFi We= b Server-305] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http:// servername:10000/nifi-api/flow/co= ntroller/bulletins (source ip: 10 ipaddress)

2017-01-05 22:29:16,821 INFO [NiFi We= b Server-19] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http:// servername:10000/nifi-api/site-to= -site (source ip: ipaddress)

=C2=A0

Any advice on how to proceed?<= u>


Thanks,

=C2=A0

Kevin

=C2=A0

=C2=A0


--001a114906f42ad04b05457177de--