Yeah, that's what I thought. I have rebuilt my NAR adding the GetFileAttributes processor back into it, and verified that it shows up in the work/nar... JAR file. So the class is there in the NAR and unpacked JAR, and I do not believe it is referenced in the latest graph...
I think I'm going to drop back to an earlier save and see if I can resolve it that way. Thanks Rick -----Original Message----- From: Michael Moser [mailto:[email protected]] Sent: Wednesday, September 09, 2015 5:21 PM To: [email protected] Subject: Re: NiFi service fails to start after removing processor from NAR Rick, If you had an instance of your GetFileAttributes processor on your graph then NiFi will fail to start if you remove the processor from your NAR. It still has the GetFileAttributes in your flow.xml.gz and NiFi is trying to instantiate it. If you can start NiFi with your old NAR, then remove GetFileAttributes from your graph, then you will be able to install your new NAR that doesn't contain GetFileAttributes. -- Mike On Wed, Sep 9, 2015 at 6:11 PM, Rick Braddy <[email protected]> wrote: > Hi, > > One of the processor files I deleted from my NAR project is > GetFileAttributes. Now the NiFi service fails to start with these > complaints below. I have deleted the library in the lib folder, > deleted work/nar folder, I even tried adding the file back into the > project to see if that might help... > > Now Nifi service simply won't start. > > Any idea how I can recover from this? > (I could fall back to an earlier tar file save if that's easiest) > > Rick > > > Excerpts from nifi-app.log: > > 2015-09-09 16:59:27,808 WARN [main] > o.a.nifi.fingerprint.FingerprintFactory Unable to create Processor of > type com.softnas.projectname.processors.files.GetFileAttributes due to > org.apache.nifi.controller.exception.ProcessorInstantiationException: > com.softnas.projectname.processors.files.GetFileAttributes; its > default properties will be fingerprinted instead of being ignored. > > ... > > 2015-09-09 16:59:28,066 WARN [main] > org.eclipse.jetty.webapp.WebAppContext > Failed startup of context o.e.j.w.WebAppContext@107aac4a > {/nifi-api,file:/root/nifi-0.3.0-SNAPSHOT/work/jetty/nifi-web-api-0.3. > 0-SNAPSHOT.war/webapp/,STARTING}{./work/nar/framework/nifi-framework-n > ar-0.3.0-SNAPSHOT.nar-unpacked/META-INF/bundled-dependencies/nifi-web- > api-0.3.0-SNAPSHOT.war} > org.apache.nifi.controller.FlowSynchronizationException: > org.apache.nifi.controller.exception.ProcessorInstantiationException: > com.softnas.projectname.processors.files.GetFileAttributes > at > org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowS > ynchronizer.java:317) > ~[nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.FlowController.synchronize(FlowController.j > ava:1160) ~[nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at org > ... > >
