Thanks for the quick responses Mark, Andrew and Bryan! This is very helpful. I am now able to investigate the problem with my flow.
Olav Jordens Senior ETL Developer Two Degrees Mobile Limited =========================== (M) 022 620 2429 (P) 09 919 7000 www.2degreesmobile.co.nz<http://www.2degreesmobile.co.nz> [cid:[email protected]] Two Degrees Mobile Limited | 47-49 George Street | Newmarket | Auckland | New Zealand | PO Box 8355 | Symonds Street | Auckland 1150 | New Zealand | Fax +64 9 919 7001 [cid:[email protected]] [cid:[email protected]] [cid:[email protected]] [cid:[email protected]] ________________________________ Disclaimer The e-mail and any files transmitted with it are confidential and may contain privileged or copyright information. If you are not the intended recipient you must not copy, distribute, or use this e-mail or the information contained in it for any purpose other than to notify us of the error. If you have received this message in error, please notify the sender immediately, by email or phone (+64 9 919 7000) and delete this email from your system. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Two Degrees Mobile Limited. We do not guarantee that this material is free from viruses or any other defects although due care has been taken to minimize the risk From: Mark Payne [mailto:[email protected]] Sent: Wednesday, 30 November 2016 11:11 a.m. To: [email protected] Subject: Re: error with flow.xml.gz Olav, You can update nifi.properties and set the "nifi.flowcontroller.autoResumeState" property to false. This will cause NiFI to start with all processors, etc. stopped. A couple of things to remember, though: 1) You'll need to change the property back to "true" or else it will continue to start this way. 2) If you make any changes to the flow, you'll write out a new flow.xml.gz that has all of the components stopped. So then even if you set the property back to true, the state is stored as 'STOPPED' so you'll need to go start the components again. Does this give you what you need? Thanks -Mark On Nov 29, 2016, at 5:01 PM, Olav Jordens <[email protected]<mailto:[email protected]>> wrote: Hi, I have a flow.xml.gz that runs as soon as I start nifi (as expected). However, it appears to (almost) immediately cause an error which results in the UI hanging, and so I am not able to stop the processors to investigate what is going on. Is there a way to start nifi and force all existing processors to be in the ‘stopped’ state? The problem is definitely with the workflow as I have managed to start nifi with no problems using the initial blank flow.xml.gz. Any advice? Thanks, Olav Olav Jordens Senior ETL Developer Two Degrees Mobile Limited =========================== (M) 022 620 2429 (P) 09 919 7000 www.2degreesmobile.co.nz<http://www.2degreesmobile.co.nz/> <image52a84a.JPG> Two Degrees Mobile Limited | 47-49 George Street | Newmarket | Auckland | New Zealand | PO Box 8355 | Symonds Street | Auckland 1150 | New Zealand | Fax +64 9 919 7001 <image08a923.PNG> <image46e0e5.PNG> <image5067f5.PNG> <image0cee59.PNG> ________________________________ Disclaimer The e-mail and any files transmitted with it are confidential and may contain privileged or copyright information. If you are not the intended recipient you must not copy, distribute, or use this e-mail or the information contained in it for any purpose other than to notify us of the error. If you have received this message in error, please notify the sender immediately, by email or phone (+64 9 919 7000) and delete this email from your system. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Two Degrees Mobile Limited. We do not guarantee that this material is free from viruses or any other defects although due care has been taken to minimize the risk
