question Re: Knox 0.6 log file issue in Archives of Support Questions (Read Only)

Knox 0.6 log file issue

cspolisetty — Fri, 13 May 2016 01:16:40 GMT

Hi, the gateway.log & gateway-audit.log is not getting updated after a while, however the log file timestamp is updated.

I had to manually start the gateway and run the following command to get the logging, starting from Ambari didn't work.

java -jar bin/gateway.jar > gateway.log

Let me know what is causing this issue.

Re: Knox 0.6 log file issue

lmccay — Fri, 13 May 2016 01:19:41 GMT

This seems really odd. Would you happen to have multiple instances of Knox gateway running behind a load-balancer?

Re: Knox 0.6 log file issue

cspolisetty — Fri, 13 May 2016 03:32:45 GMT

No, I am running 5 node basic cluster with only one instance of gateway. Here are more details about the issue

# ls -ltr total 8

-rw-r----- 1 knox hadoop 4096 May 12 13:23 gateway.log

-rw-r----- 1 knox hadoop 4096 May 12 13:23 gateway-audit.log

tail -2 gateway-audit.log

16/05/12 11:08:10 ||8c0e145f-a495-470b-918a-9ca1da7228ab|audit|HIVE|guest|knox||access|uri|/gateway/default/hive|success|Response status: 200 16/05/12 11:08:10 ||aa48685f-c5bf-4340-bc53-50cf332b

gateway-audit.log timestamp updated (13:23), however log file stopped updating after 11:08:10 (the log statement cut off as well). Same issue with gateway.log

# tail -2 gateway.log (log statement cut off: certificate is valid between: 4/)

2016-05-12 09:14:37,205 INFO hadoop.gateway (JettySSLService.java:logAndValidateCertificate(125)) - The Gateway SSL certificate is issued to hostname: XXXXX. 2016-05-12 09:14:37,207 INFO hadoop.gateway (JettySSLService.java:logAndValidateCertificate(128)) - The Gateway SSL certificate is valid between: 4/

Re: Knox 0.6 log file issue

cspolisetty — Sat, 14 May 2016 01:16:13 GMT

Hi Lmccay, I added more details about the issue below. This morning too the log statement was cut off and then stopped updating the log.

Re: Knox 0.6 log file issue

cspolisetty — Tue, 17 May 2016 20:40:39 GMT

The issue is resolved after freeing up the disk space.