Joe, we are on version 1.1 (Very old I know but we are planning to upgrade in the near future). Just need a way to avoid having to go in and restart controllers individually and instead start them all automatically after the NiFi service gets restarted. Thanks -- tc
Tom Cassidy JMLFDC Operations Manager Clinical Support Branch, Solution Delivery Division (SDD), Health Information Technology (HIT), Defense Health Agency (DHA) JMLFDC - DXC - CTR 1674 Nelson Street, Ste. #121 Fort Detrick, MD 21702 301-619-8744 (work) 301-471-4559 (cell) [email protected] From: Cassidy, Thomas G (Tom) JR CTR USARMY MEDCOM JMLFDC (US) Sent: Thursday, May 03, 2018 4:17 PM To: [email protected] Subject: RE: [Non-DoD Source] Re: Starting controller services Nagios XI. How do I determine which version? I suspect its recent but not the latest. Here are a couple of the controllers in use at the Process Group Configuration level. [cid:[email protected]] Tom Cassidy -----Original Message----- From: Joe Witt [mailto:[email protected]] Sent: Thursday, May 03, 2018 4:13 PM To: [email protected] Subject: [Non-DoD Source] Re: Starting controller services Hello What version of NiFi are you on? Can you share more about the controller services/specific processor combinations where you're seeing this? Thanks On Thu, May 3, 2018 at 4:05 PM, Cassidy, Thomas G (Tom) JR CTR USARMY MEDCOM JMLFDC (US) <[email protected]> wrote: > We are relatively new users of NiFi and think there might be a better way of > recovery than what we do now. > > Occasionally a flow will hang and the best way to recover is to bounce the > NiFi service. > > This is where the problem comes in: > We then go into the flows and find each controller service and enable it to > get the flow running again. Is there a setting or command that can be used to > automatically restart the controller services? > > Thanks for any help > Tom Cassidy > >
