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
turnin
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 for wire via:
> log
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
+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 must update the log4j se