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 and push it into
another standalone nifi.
Since I dont care about the GUI, I havent bothered to set up
authentication or authorization.
I just took the the exported flow definition and renamed it to flow.json.raw
But the code doesnt appear to be running properly in the standalone nifi
either.
The app log doesnt show anything. Just the regular checkpoints.
None of the processors or the RPG appear to be 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 remote process group is either disconnected or disabled.
The nifi URL works when its in the originating source nifi. And Im
running the minifi on the same host as the source nifi. So things like
firewalls/routing arent an issue.
And https:odc-nifi-test.nci.org.au:444/nifi is the correct URL for the
destination remote NIFI.
Im going to try a flow file converted from the minifi 1 config.ynl, If
that works I;ll have sonething to compare.
I'll also try importing the exported flow into a new NIFI and see if
theres something wrong with the exported file.
On 10/1/2025 8:49 pm, Kedvessy Péter wrote:
[You don't often get email frompkedve...@gmail.com. Learn why this is
important athttps://aka.ms/LearnAboutSenderIdentification ]
Hi Robert,
Have you checked your minifi agent logs? Specifically the
minifi-app.log.
There should be an error describing the reason for the failed
connection/communication with the remote NiFi instance... Is
https:odc-nifi-test.nci.org.au:444/nifi the right URI of your remote
NiFi
instance where you are expecting flow files from the minifi agent?
Regards,
Peter
