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 alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jan 11, 2017, at 11:38 AM, Joe Gresock <jgres...@gmail.com> 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 <alopre...@apache.org > <mailto:alopre...@apache.org>> 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 >> alopre...@apache.org >> *alopresto.apa...@gmail.com <mailto:alopresto.apa...@gmail.com> >> <alopresto.apa...@gmail.com <mailto:alopresto.apa...@gmail.com>>* >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >> >> On Jan 11, 2017, at 9:48 AM, Joe Gresock <jgres...@gmail.com> 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*
signature.asc
Description: Message signed with OpenPGP using GPGMail
