Thanks Matt . We edited the flow.xml file and removed the reference to 1.4 Update Attribute bundle from it and used the edited flow file to start Nifi and the issue got fixed. No more ghost Update Attribute Processors. Thanks alot for all your help and detailed explanation on this, ... View more

Thanks Matt. I had a look at the flow.xml file and could see some multiple bundled up versions of the update attribute processor . There was no mention of the custom processor though however we had multiple versions like 1.4 and 1.8. Is there a possibility that we could tweak the flow.xml file and remove these old instances and get the flow.xml uploaded ? ... View more

HI Matt , Thanks for your answer. I am attaching the screen shot below . You can see how just the " Update Attribute" seems to have those dashed lines and is in "invalid" state. I doubt think our developers made any custom change to the update attribute processor. Let me know what you think about this meanwhile I have looked at the app.log and can see this error You were bang on when you said about the 'Ghost' Implementation. What do you think should be the next steps -bash-4.2$ cat nifi-app-*.log |grep "Unable to find bundle for coordinate" Caused by: java.lang.IllegalStateException: Unable to find bundle for coordinate org.apache.nifi:nifi-update-attribute-nar:1.8.0 ERROR [main] o.a.nifi.controller.ExtensionBuilder Could not create Processor of type org.apache.nifi.processors.attributes.UpdateAttribute for ID 629d355f-0167-1000-ffff-ffffbc497b67; creating "Ghost" implementation ... View more

Hi Matt , for the existing flow , the "update attribute" processor was in an inconfigurable state i.e it had this dotted line all over it and when I clicked on it it wasnt showing anything. This has happened for all the "update attribute" processors in our flow. For now , we have had to delete this processor and add a new one and add configur it. We also realize that the new "update attribute" processor has an extra feature with version 1.9 which wasnt available in 1.8. However this should be taken care of automatically with an upgrade. ... View more

Hi Rishabh , did you try shutting down the nifi instances and start them one at a time ? ... View more

Hi Rishabh , Have a look at https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/ This one is really good . I have followed this although I am stuck . Waiting for Pierre Villard to respond ... View more

Is there any progress on this as we are in 2019 now and this post is almost 3 years back . Is there an easy way to install Minifi on an Android Phone and then use it to transmit data ... View more

@Vipin Chourasia I reckon this might be a firewall issue or something . I remember seeing something like this and then realized the firewall wasnt opened between the C2 server and the Minifi server ... View more

Hi @Vipin Chourasia . sorry mate . I know this is something that is very new and there is hardly any material out there . I also chased Abdelkrim 🙂 but didnt get any response. hahaha. Anyways .. sent you the document now. Have a read through ... View more

Hi @Vipin Chourasia ..apologies , for not being able to respond earlier . I have prepared a document to go through all this . Its a big document , can you give me your email id . I will flick it through .. I also went through the same issues but now our C2 is working very well. ... View more

thanks . My question is perhaps more on the compatibility between AIX and Linux . Could that be an issue ? ... View more

Hey @Raymond Honderdors .. all good mate. This issue is now fixed. I had to rename my template to have the suffix .v1. I ignored that which is why I wasnt getting the config.yml . Its all sorted now and its working fine. Thanks again for all your help ... View more

Hi @Raymond Honderdors. Actually I tried using the 10080 port before but it seems this port is already used in my case which is why I was getting an error address already used.I then used 8080 and put that in the c2.properties file as well. Please also note that my Nifi server is secured . The error that I am getting from my log file is as follows :- Server returned HTTP response code: 403 for URL: https://capltda23:8443/nifi-api/flow/templates DEBUG [qtp438135304-15] o.a.n.m.c2.provider.util.HttpConnector Connecting to endpoint: https://capltda23:8443/nifi-api/flow/templates WARN [qtp438135304-15] o.a.nifi.minifi.c2.service.ConfigService Unable to get configuration. org.apache.nifi.minifi.c2.api.ConfigurationProviderException: Unable to retrieve template list Didn't find any templates that matched \QFROM_CAPLTDA1E.v\E([0-9+])\Q\E the above error states that C2 server couldn't get hold of the template name. Not sure why this is occuring. Thanks again @Raymond Honderdors . I guess I am pretty close now . Let me know of your thoughts. ... View more

Hi @Raymond Honderdors I started the C2 server and tried to test the URL below but it keeps on giving me the error --> HTTP ERROR 500 http://C2Server:8080/c2/config?class=CAPLTDA1E where CAPLTDA1E is the name of the template on the nifi server. I have also updated minifi-c2-context.xml to ppint to the Nifi server. I am on version 0.4 for C2 and also removed the lib file javax.ws.rs-api-2.1.jar. is there anything I am missing here ? cheers Abhi ... View more

Thanks @Raymond Honderdors. I think i am now close. I want to first try to test the c2 server. I have already run the script c2.sh and it looks up and running . My template on the remote nifi server is called FROM_CAPLTDA1E. So , if I want the config.yml returned , then would my url look like this ===> http://C2SERVER:8080/c2/config?class=FROM_CAPLTDA1E . I guess this is the first step that needs to be sorted after which the minifi related settings can be tweaked. Can you please let me know if my approach is correct and also whether the URL mentioned above is right. Many Many thanks @Raymond Honderdors by the way . The idea is much much clear now ... View more

Thanks @Raymond Honderdors . Hey quick question . I think i need to also tweak the authorizations and authorizers.xml to add the CLASS. Do you have any details on that by any chance ... View more