Re: turn off debug logging from org.apache.http.wire

Ok guys, I finally figure out the reason. It's because we introduced logback from one of our internal packages, so Knox was using logback instead of log4j underlying, and that's why no matter how we modify gateway-log4j.properties, nothing changed. By simply removing that package, Knox is using

Re: turn off debug logging from org.apache.http.wire

Change it back to this and see what happens. Another thing to check is that - if you are in a kerberized environment is whether any of the kerberos DEBUG settings are set via environment variables or krb5.conf, etc. Lastly, make sure that you are actually using the log4j.propoerties file that you

Re: turn off debug logging from org.apache.http.wire

Hi Larry, Here is my gateway-log4j.properties. *app.log.dir=/var/log/knox* *app.log.file=${launcher.name }.log* *app.audit.file=${launcher.name }-audit.log* *log4j.rootLogger=ERROR* *log4j.logger.org.apache.knox.gateway=ERROR*

Re: turn off debug logging from org.apache.http.wire

Hi Guang - This certainly sounds frustrating. I have never had trouble turning it off. Can you share your gatway-log4j.properties file - just make sure there isn't anything sensitive in there? thanks, --larry On Wed, Sep 5, 2018 at 1:40 PM Guang Yang wrote: > And we're not using Ambari. We

Re: turn off debug logging from org.apache.http.wire

And we're not using Ambari. We just deploy manually. On Tue, Sep 4, 2018 at 11:02 PM, Guang Yang wrote: > Hi guys, > > I'm working with Wei and we still don't figure it out. Let me clarify the > question. > > Currently, we're seeing lots of DEBUG logs in file *gateway.out*, which > is from here

Re: turn off debug logging from org.apache.http.wire

Hi guys, I'm working with Wei and we still don't figure it out. Let me clarify the question. Currently, we're seeing lots of DEBUG logs in file *gateway.out*, which is from here https://github.com/apache/knox/blob/master/gateway-release/home/bin/gateway.sh#L127. On the one hand, it prints the

Re: turn off debug logging from org.apache.http.wire

+1 to Kevin's point. Ambari rewrites all configs on server restart. On Sun, Apr 15, 2018 at 1:16 PM, Kevin Risden wrote: > Are you using Ambari or deploying Knox manually? > > If you using Ambari, then Ambari will force overwrite the log4j configs > during a restart. You

Re: turn off debug logging from org.apache.http.wire

Are you using Ambari or deploying Knox manually? If you using Ambari, then Ambari will force overwrite the log4j configs during a restart. You must update the log4j settings in Ambari. Another option if using Ambari is to find the debug setting and set it to false (I don't have a cluster in front

Re: turn off debug logging from org.apache.http.wire

Interesting. Thanks Larry. I'll dig more on my side. On Sun, Apr 15, 2018 at 4:54 AM, larry mccay wrote: > No, I cannot reproduce it. > If you are modifying the correct gateway-log4j.properties and restarting > the server you should not see that. > > In fact, turning on DEBUG

Re: turn off debug logging from org.apache.http.wire

No, I cannot reproduce it. If you are modifying the correct gateway-log4j.properties and restarting the server you should not see that. In fact, turning on DEBUG for wire via: log4j.logger.org.apache.http.wire=DEBUG Doesn't result in output in gateway.out for me but instead gateway.log and

Re: turn off debug logging from org.apache.http.wire

Hi Larry - Thanks a lot for getting back to me. Yes I made sure all DEBUG level is turned off in my gateway-log4j.properties file, but that doesn't seem to be working. I also tried to explicitly set log4j.logger.httpclient.wire.header to WARN (as suggested in post

Re: turn off debug logging from org.apache.http.wire

Hi Wei - If you look at your gateway-log4j.properties file, you should see something like the following near the top: app.log.dir=${launcher.dir}/../logs app.log.file=${launcher.name}.log app.audit.file=${launcher.name}-audit.log log4j.rootLogger=ERROR, drfa