Hi Joe, It does in fact appear to be an issue and I was able to reproduce. Going through git history, it looks like when this was initially solved via NIFI-2199 [1] it introduced other, undesirable behavior with errors getting lost as reported in NIFI-3112 [2].
3112 reverted the work of 2199 causing the behavior exhibited. I will re-open both issues so that we can track this down and solve both issues. [1] https://issues.apache.org/jira/browse/NIFI-2199 [2] https://issues.apache.org/jira/browse/NIFI-3112 On Thu, May 11, 2017 at 3:13 PM, Joe Gresock <[email protected]> wrote: > After upgrading our cluster to 1.2.0, the problem described in [1] appears > to be back. > > On a 1.1.1 cluster, I can issue the following command, which exits ssh > appropriately with a return code of 0: > ssh stage-nifi1 "sudo service nifi start" > > On 1.2.0, the same command correctly starts nifi, but the ssh command hangs > afterwards, and I have to Ctrl-C to continue using that terminal. > > Has anyone else encountered this, before I create a ticket? > > [1] https://issues.apache.org/jira/browse/NIFI-2199 > > -- > I know what it is to be in need, and I know what it is to have plenty. I > have learned the secret of being content in any and every situation, > whether well fed or hungry, whether living in plenty or in want. I can do > all this through him who gives me strength. *-Philippians 4:12-13* >
