[ 
https://issues.apache.org/jira/browse/RANGER-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213797#comment-16213797
 ] 

Ronald van de Kuil commented on RANGER-1847:
--------------------------------------------

Hi Don Bosco,

I have Kafka Server start up now with out errors. 

Also, I see Kafka sync the policies after I updated these in Ranger.

[2017-10-14 15:56:22,891] DEBUG ==> 
PolicyRefresher(serviceName=kafkadev).loadPolicy() 
(org.apache.ranger.plugin.util.PolicyRefresher)
[2017-10-14 15:56:22,891] DEBUG In-Use memory: 165081104, Free memory:908660720 
(org.apache.ranger.perf.policyengine.init)
[2017-10-14 15:56:22,891] DEBUG ==> 
PolicyRefresher(serviceName=kafkadev).loadPolicyfromPolicyAdmin() 
(org.apache.ranger.plugin.util.PolicyRefresher)
[2017-10-14 15:56:22,891] DEBUG ==> 
RangerAdminRESTClient.getServicePoliciesIfUpdated(4) 
(org.apache.ranger.admin.client.RangerAdminRESTClient)
[2017-10-14 15:56:22,891] DEBUG Checking Service policy if updated with old api 
call (org.apache.ranger.admin.client.RangerAdminRESTClient)
[2017-10-14 15:56:22,902] DEBUG <== 
RangerAdminRESTClient.getServicePoliciesIfUpdated(4): null 
(org.apache.ranger.admin.client.RangerAdminRESTClient)
[2017-10-14 15:56:22,903] DEBUG PolicyRefresher(serviceName=kafkadev).run(): no 
update found. lastKnownVersion=4 (org.apache.ranger.plugin.util.PolicyRefresher)
[2017-10-14 15:56:22,903] DEBUG [PERF] 
PolicyRefresher.loadPolicyFromPolicyAdmin(serviceName=kafkadev): 12 
(org.apache.ranger.perf.policyengine.init)
[2017-10-14 15:56:22,903] DEBUG <== 
PolicyRefresher(serviceName=kafkadev).loadPolicyfromPolicyAdmin() 
(org.apache.ranger.plugin.util.PolicyRefresher)
[2017-10-14 15:56:22,903] DEBUG [PERF] 
PolicyRefresher.loadPolicy(serviceName=kafkadev): 12 
(org.apache.ranger.perf.policyengine.init)
[2017-10-14 15:56:22,903] DEBUG In-Use memory: 165166120, Free memory:908575704 
(org.apache.ranger.perf.policyengine.init)
[2017-10-14 15:56:22,903] DEBUG <== 
PolicyRefresher(serviceName=kafkadev).loadPolicy() 
(org.apache.ranger.plugin.util.PolicyRefresher)

So far, all is looking well.

This morning I started my producer test, but the connection fails to establish.

On the producer:

[2017-10-14 15:56:52,819] DEBUG Completed connection to node -1 
(org.apache.kafka.clients.NetworkClient)
[2017-10-14 15:56:52,842] DEBUG Sending metadata request 
{topics=[ranger-topic]} to node -1 (org.apache.kafka.clients.NetworkClient)
[2017-10-14 15:56:52,847] DEBUG Connection with ronald-VirtualBox/127.0.1.1 
disconnected (org.apache.kafka.common.network.Selector)
java.io.EOFException
        at 
org.apache.kafka.common.network.NetworkReceive.readFromReadableChannel(NetworkReceive.java:83)
        at 
org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:71)
        at 
org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:154)
        at 
org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:135)
        at 
org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:323)
        at org.apache.kafka.common.network.Selector.poll(Selector.java:283)
        at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:260)
        at 
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:229)
        at 
org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:134)
        at java.lang.Thread.run(Thread.java:748)
[2017-10-14 15:56:52,851] DEBUG Node -1 disconnected. 
(org.apache.kafka.clients.NetworkClient)

On the kafka server:

[2017-10-14 15:56:52,576] DEBUG Got ping response for sessionid: 
0x15f1a9a349c0011 after 0ms (org.apache.zookeeper.ClientCnxn)
[2017-10-14 15:56:52,843] DEBUG Set SASL server state to HANDSHAKE_REQUEST 
(org.apache.kafka.common.security.authenticator.SaslServerAuthenticator)
[2017-10-14 15:56:52,844] DEBUG Handle Kafka request METADATA 
(org.apache.kafka.common.security.authenticator.SaslServerAuthenticator)
[2017-10-14 15:56:52,844] DEBUG Set SASL server state to FAILED 
(org.apache.kafka.common.security.authenticator.SaslServerAuthenticator)
[2017-10-14 15:56:52,844] DEBUG Connection with /127.0.0.1 disconnected 
(org.apache.kafka.common.network.Selector)
java.io.IOException: org.apache.kafka.common.errors.IllegalSaslStateException: 
Unexpected Kafka request of type METADATA during SASL handshake.
        at 
org.apache.kafka.common.security.authenticator.SaslServerAuthenticator.authenticate(SaslServerAuthenticator.java:243)
        at 
org.apache.kafka.common.network.KafkaChannel.prepare(KafkaChannel.java:64)
        at 
org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:318)
        at org.apache.kafka.common.network.Selector.poll(Selector.java:283)
        at kafka.network.Processor.poll(SocketServer.scala:472)
        at kafka.network.Processor.run(SocketServer.scala:412)
        at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.kafka.common.errors.IllegalSaslStateException: Unexpected 
Kafka request of type METADATA during SASL handshake.

It would be proud to help with an instruction if I get it working. 

> Ranger Kafka Plugin sasl.enabled.mechanisms=PLAIN
> -------------------------------------------------
>
>                 Key: RANGER-1847
>                 URL: https://issues.apache.org/jira/browse/RANGER-1847
>             Project: Ranger
>          Issue Type: Test
>          Components: plugins
>    Affects Versions: 0.6.3, 0.7.1
>         Environment: ubuntu stand-alone hobby environment
>            Reporter: Ronald van de Kuil
>            Priority: Minor
>
> I am such a NOOB hobby-ing away. And I like it. ;)
> I figured I would give it a try to setup Kafka to use the 
> sasl.enabled.mechanisms of type PLAIN with ranger to do the authorisation and 
> the auditing (instead of GSSAPI).
> I got it to work pretty far. KafkaServer gets into state SaslAuthenticated 
> with Zookeeper. 
> Next it loads the ranger kafka plugin. Then the RangerKafkaAuthorizer 
> complains about Kerberos. 
> I then updated the CLASSPATH and it complains about something else.
> I am not sure how to classify this issue. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to