Joe, It doesn’t sound like a common deployment scenario, but it also doesn’t hurt to write up what you would like to have happen and submit a Jira. If it can be supported with minor changes, I wouldn’t be opposed to it. Either way, having it documented will help the next person who encounters that edge case.
Thanks. Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jan 12, 2017, at 4:48 AM, Joe Gresock <[email protected]> wrote: > > Ok, I narrowed it down and found that when I specify an external directory > as the conf directory, nifi-bootstrap.log isn't written to (though it is > created). In this scenario, the other log files work just fine, it's just > the nifi-bootstrap.log that doesn't work. > > To reproduce this, I replaced "./conf" with "/opt/nifi/data/conf" in > bootstrap.conf, and specified the same absolute path in the nifi.properties > file as well, for all properties that use the ./conf directory. > > In order to get this configuration to start up, you also apparently need > ${NIFI_HOME}/conf/bootstrap.conf to be a symbolic link to the actual > location of that file (in /opt/nifi/data/conf, in my case). > > I was able to work around this with my current configuration by simply > linking the entire ${NIFI_HOME}/conf directory to /opt/nifi/data/conf. > > The configuration I described definitely did work in the 0.x line. So, I'm > not sure if this is worth fixing, since we're using a non-standard setup > and there's a workaround. > > On Wed, Jan 11, 2017 at 7:54 PM, Joe Gresock <[email protected]> wrote: > >> No, we have not called setOut anywhere before now, and no customizations >> in logging.properties. I'll see if I can reproduce this with a vanilla >> installation of NiFi and I'll get back to you. >> >> On Wed, Jan 11, 2017 at 7:51 PM, Andy LoPresto <[email protected]> >> wrote: >> >>> Have you had to call System.setOut() anywhere else in the code base? >>> Anything in your custom processors that redirects output streams? Any >>> custom configurations in $JAVA_HOME/jre/lib/logging.properties? >>> >>> This isn’t something I’ve encountered before — we get questions about log >>> threshold, but I’ve never heard of the standard out/error streams not >>> writing correctly, or the entire nifi-bootstrap.log being empty. >>> >>> Andy LoPresto >>> [email protected] >>> *[email protected] <[email protected]>* >>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >>> >>> On Jan 11, 2017, at 11:38 AM, Joe Gresock <[email protected]> wrote: >>> >>> CentOS 6.8 with openjdk version "1.8.0_111". I did also try running nifi >>> directly using nifi.sh start, to the same effect. >>> >>> I was able to work around the issue by calling System.setOut(...) inside >>> one of my custom processors, so I at least have the debugging info I need. >>> However, it would still be nice to get the standard out working again. >>> >>> On Wed, Jan 11, 2017 at 7:19 PM, Andy LoPresto <[email protected]> >>> wrote: >>> >>> Joe, >>> >>> Sorry you are experiencing difficulty with this. SSL debugging is a >>> feature I use often. You should see this output in >>> logs/nifi-bootstrap.log. >>> Ensure you do not have another Java arg with a conflicting argument number >>> in bootstrap.conf (although as you have put it as 16, I think you should >>> be >>> safe against a default install). If it is not getting *any* output, I’d >>> toggle that Java arg and restart. If it’s still nothing, I’d try running >>> NiFi directly, rather than as a service. >>> >>> Can you please let us know what OS, hardware, and Java version you are >>> using? Thanks. >>> >>> >>> Andy LoPresto >>> [email protected] >>> *[email protected] <[email protected]>* >>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >>> >>> On Jan 11, 2017, at 9:48 AM, Joe Gresock <[email protected]> wrote: >>> >>> Hi folks, >>> >>> I'm trying to turn on SSL verbose logging using >>> java.arg.16=-Djavax.net.debug=ssl,handshake in my bootstrap.conf (nifi >>> version 1.1.0). As far as I can remember, this output goes to either >>> stdout or stderr (I forget which). >>> >>> As a result, I'm trying to find the output in my nifi-bootstrap.log file, >>> but this log file doesn't appear to be getting any output whatsoever (not >>> even at startup time). I am using the original logback.xml, with respect >>> to the BOOTSTRAP_FILE appender and related loggers. >>> >>> Does anyone know where the javax.net.debug logging should go? Also, >>> should >>> I see anything in my nifi-bootstrap.log file? >>> >>> I am starting nifi using "sudo service nifi start". >>> >>> -- >>> 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* >>> >>> >>> >>> >>> >>> -- >>> 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* >>> >>> >>> >> >> >> -- >> 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* >> > > > > -- > 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*
signature.asc
Description: Message signed with OpenPGP using GPGMail
