ight be because
authentication module isnt using the standard routines that
javax.net.debug effect.
I tried comparing it to the logs I get from a nifi 1.28.1 instance. But
that doesnt log anything at all. So must be using different code.
--
Robert Cohen
json file into minifi, we should convert
it with minifi toolkit. Related ticket for more details:
https://issues.apache.org/jira/browse/NIFI-12644
Regards,
Peter
Robert Cohen ezt írta (időpont: 2024.
dec. 12., Cs, 2:11):
Im having trouble getting code into minifi 2 from nifi 2.
The document
ins a minifi.properties file but not a
nifi.properties file.
So Im really not sure what is going on.
On 6/1/2025 4:40 pm, Robert Cohen wrote:
Ahh, it appears the functionality is there. Its just that the README
file hasnt been updated,
Theres now a transform-nifi command in addition t
Ahh, it appears the functionality is there. Its just that the README
file hasnt been updated,
Theres now a transform-nifi command in addition to the transform-yml
command.
On 6/1/2025 2:59 pm, Robert Cohen wrote:
[You don't often get email from robert.co...@anu.edu.au.invalid. Learn
.
|"maxTimerDrivenThreadCount":5 But when I do that minifi fails to start
as it says the flow file fails validation Does the flow file contain a
checksum? |
On 8/1/2025 1:27 pm, Robert Cohen wrote:
Thanks for that. It clears some things up.
Im not sure if the doco is supposed to be su
Just reporting a minor issue with the gui in nifi2.
In nifi 1, the buttons in the operate and navigate panels have mouseover
text.
in Nifi 2, while the main buttons in the top menu have mouseover text,
but the operate and navgate panel buttons don't.
Im having trouble getting code into minifi 2 from nifi 2.
The documentation here
https://github.com/apache/nifi/blob/main/minifi/minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md
says
# Export the dataflow in JSON format.
# Move your new .json file to |minifi/conf|.
# Rename your
Ive noticed a couple of errors showing up in the nifi 2.0.0 startup logs.
They dont appear to be breaking anything, but random errors and warnings
make me nervous.
So I just thought I'd report them.
The most serious looking is
java.lang.reflect.InaccessibleObjectException: Unable to make pu
uld ignore the GUI related attributes.
On 20/1/2025 5:25 pm, Robert Cohen wrote:
Actually, I suspect the export from nifi is supposed to be
scheduledState: Enabled.
I think its probably the job of the minifi-toolkit to change that from
Enabled to Running.
converter.
The problem is there in the exported file. So it appears to be a nifi
problem, not a toolkit problem.
On 16/1/2025 5:19 pm, Robert Cohen wrote:
Ive tried running the transform-yml. The output appears to be minifi
json. Not nifi json.
So I think that doco is misleading.
The code
Since upgrading from nifi 2.1.0 to nifi 2.2.0 I have noticed the
following stack dump appearing in my logs.
It isnt fatal, nifi appears to be working correctly.
2025-01-29 14:14:05,218 WARN [NiFi Web Server-127]
o.a.nifi.web.server.HostHeaderHandler Request URI
[https://odc-nifi-dev.nci.org.
OK, I think you can ignore this report, its being triggered by a nagios
probe of the server.
On 29/1/2025 2:25 pm, Robert Cohen wrote:
Since upgrading from nifi 2.1.0 to nifi 2.2.0 I have noticed the
following stack dump appearing in my logs.
It isnt fatal, nifi appears to be working
Actually, I suspect the export from nifi is supposed to be
scheduledState: Enabled.
I think its probably the job of the minifi-toolkit to change that from
Enabled to Running.
On 20/1/2025 5:07 pm, Robert Cohen wrote:
OK, I believe Ive spotted the problem with exporting code from nifi
Yes, Ive checked the logs.
There are no error messages of any kind or any indication that its
attempting to transmit anything at all.
Its as if the remote process group is either disconnected or disabled.
The nifi URL works when its in the originating source nifi. And Im
running the minifi
running.
I'll have to try and get the GUI working so I can log into it and see
whats going on.
On 13/1/2025 1:21 pm, Robert Cohen wrote:
Yes, Ive checked the logs.
There are no error messages of any kind or any indication that its
attempting to transmit anything at all.
Its as if the r
ike it fails (but dislike it fails silently or weirdly).
Kind regards,
On Tue, 14 Jan 2025, 16:23 Robert Cohen,
wrote:
Ive got no idea whats going on with this thing.
I thought it might have been a minifi issue or a converter issue, so Im
trying to export a process group from my source nifi
ifi flow JSON format
transform-yml: Transform MiNiFi config YAML into NiFi flow JSON format
So does that mean I need to use transform-yml to convert it to nifi flow
format.
Then use transform-nifi to convert it from nifi flow format to minifi
flow format
On 14/1/2025 9:25 pm, Robert Cohen wr
exported from nifi 2.1.0 and converted to minifi
json doesnt.
I'll start comparing the two and see if I can spot the problem.
On 16/1/2025 4:00 pm, Robert Cohen wrote:
Im coming at it a different way. Im trying to take the code from
minifi 1.28.1 and convert it to minifi 2.1.0.
No
rties file based on the
bootstrap.conf
- nifi.properties is the legacy configuration file of minifi
- config.yaml is the legacy flow configuration, now we have the json one
what you have tried to import previously
I hope it helps to set up your minfi agent.
Regards,
Peter
Robert Cohen ezt írt
e
following setting from 0.
|"maxTimerDrivenThreadCount":5 But when I do that minifi fails to
start as it says the flow file fails validation Does the flow file
contain a checksum? |
On 8/1/2025 1:27 pm, Robert Cohen wrote:
Thanks for that. It clears some things up.
Im not sure
20 matches
Mail list logo
