Hi All,
I am receiving this error on my nifi cluster setup
Error -ERROR [NiFi Web Server-16] o.a.nifi.web.security.jwt.JwtService
There was an error validating the JWT
io.jsonwebtoken.JwtException: Unable to validate the access token.
WARN [NiFi Web Server-16] o.a.n.w.s.NiFiAuthenticationFilter
Classification\_- INTERNAL & PARTNERS
Hello.
By any chance, did you take thread dumps?
If it happens again, take thread dumps of the java nifi process (with jstack:
jstack -l >> threaddumps.log). Take 3 or 4 every 10/15 seconds .
Regards.
From: Jean-Sebastien Vachon
Sent: lundi 23
Have you looked into this error ? It seems a bit concerning to me.
Executable command /usr/bin/python3 ended in an error:
/usr/local/lib/python3.7/site-packages/requests/__init__.py:80:
RequestsDependencyWarning: urllib3 (1.23) or chardet (3.0.4) doesn't match
a supported version!
I could if the Nifi was up and running but when I loose the node, the Nifi
process itself dies so I can hardly take a heap dump of something that is not
running
It happened twice before I sent my first email...nothing since then.
From: DEHAY Aurelien
Sent:
1) You can only have one parent NAR, and it creates a hierarchy, so if
you need hadoop libraries you would want your parent NAR to be
nifi-hadoop-libraries-nar, which already has a parent of
nifi-standard-services-api-nar, so then you have both in your parent
hierarchy.
2) This is really up to
Trying to figure out what's causing this issue. In a simple test of
UpdateRecord I'm getting an exception. This is on NiFi 1.9.2
2019-09-25 11:59:55,462 ERROR [Timer-Driven Process Thread-10]
o.a.n.processors.standard.UpdateRecord
UpdateRecord[id=692c3fdc-016d-1000-1d1a-3f2c2a1a99bb] Failed to
Hello, Shawn.
It seems to be related to the syntax of your custom fields.
Check below the form that I use to perform such operations:
[image: image.png]
Em qua, 25 de set de 2019 às 14:14, Shawn Weeks
escreveu:
> Trying to figure out what's causing this issue. In a simple test of
>
Not sure if this is reason but I believe record path would be
/log_date instead of //log_date
On Wed, Sep 25, 2019 at 1:14 PM Shawn Weeks wrote:
>
> Trying to figure out what's causing this issue. In a simple test of
> UpdateRecord I'm getting an exception. This is on NiFi 1.9.2
>
> 2019-09-25
Hi,
I have developed some custom processors within single Maven project (lets
call this project custom-processors). These processors need Hadoop
dependencies (nifi-hadoop-nar), record-serde related dependencies
(nifi-record-serialization-service-api) and Kerberos dependencies apart
from usual
Dweep,
Sorry you're having trouble with this. Can you please confirm the URL you
direct your browser to initially and compare that to the address you are
returned to following successful authentication? Would also be interested
in seeing if the value in the redirect_uri query parameter when
Maybe something interesting nifi-bootstrap.log when this happens?
On Wed, Sep 25, 2019 at 11:51 AM Jean-Sebastien Vachon <
jsvac...@brizodata.com> wrote:
> I could if the Nifi was up and running but when I loose the node, the Nifi
> process itself dies so I can hardly take a heap dump of
Thanks Bryan, will try it out.
Sent from my iPhone
> On 25 Sep 2019, at 7:15 pm, Bryan Bende wrote:
>
> 1) You can only have one parent NAR, and it creates a hierarchy, so if
> you need hadoop libraries you would want your parent NAR to be
> nifi-hadoop-libraries-nar, which already has a
Hopefully I missing something really trivial. I've got a new 1.9.2 install with
HTTPS enabled. I've added my initial user to the data provenance policy and I'm
able to click on the data provenance menu but it's always empty despite seeing
files getting modifed in the ./provenance_repository
Well nevermind on this. I had to both add a policy for View Provenance and add
a policy on the default flow. Now I see events.
Thanks
Shawn
From: Shawn Weeks
Sent: Wednesday, September 25, 2019 5:29 PM
To: users@nifi.apache.org
Subject: NiFi 1.9.2 Data
I copied the //log_date from the NiFi Documentation so if your only supposed to
use single slashes we might have a bug there. Turns out the EOF error is
because I was Record Path mode instead of Literal Value. Something I missed
from the documentation.
Thanks
Shawn Weeks
15 matches
Mail list logo
