For the record, you can enable debug logging by changing the log levels in a log4j.properties and starting the service via:
bin/sentry --log4jConf ./log4j.properties --command service --conffile sentry-site.xml Colm. On Thu, Sep 29, 2016 at 12:39 PM, Colm O hEigeartaigh <cohei...@apache.org> wrote: > Hi all, > > How do I enable debug logging for the Sentry Service? I couldn't find an > obvious way to do it. > > I'm experimenting with Kafka. On the broker side I see the following > request for permissions for the "admin" group, but none are returned from > the service: > > [2016-09-29 12:28:18,317] DEBUG Getting permissions for [admin] > (org.apache.sentry.policy.kafka.SimpleKafkaPolicyEngine) > [2016-09-29 12:28:18,325] DEBUG Successfully opened transport: > org.apache.thrift.transport.TSocket@39d76ac7 to localhost/127.0.0.1:8038 > (org.apache.sentry.provider.db.generic.service.thrift. > SentryGenericServiceClientDefaultImpl) > [2016-09-29 12:28:18,332] DEBUG Successfully created client > (org.apache.sentry.provider.db.generic.service.thrift. > SentryGenericServiceClientDefaultImpl) > [2016-09-29 12:28:18,611] DEBUG result = [] (org.apache.sentry.policy. > kafka.SimpleKafkaPolicyEngine) > > However, I can see the privileges via the command line: > > > bash bin/kafka-sentry.sh --config config/ -lr -g admin > admin_role > > bash bin/kafka-sentry.sh --config config/ -lp -r admin_role > HOST=*->CLUSTER=kafka-cluster->action=all > > Am I doing anything obviously wrong here? The sentry-site.xml for the > Sentry Service has "sentry.service.admin.group" set to "admin" as well. > > Colm. > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
