/gateway/default/static/... shouldn't exist, knox rewrites the /static/... from the namenode to /gateway/default/hdfs/static/... on the way to you and does the opposite transform on the way to the namenode. ... View more

I created a rule in ranger that allowed select access to @null and default. It seems like a hack but it also seems to work. ... View more

This is an expect script not a shell script. Your shell does not understand expect commands. ... View more

I now have a working livy running, at least sc.version works After trying everything I could find with livy 0.2.0 (the version in 2.5.0) I decided to give 0.3.0 a try. I believe that the problem is caused by a bug in spark 1.6.2 when connecting to the metadata store. After compiling livy 0.3.0 with hadoop 2.7.3 and spark 2.0.0, and installing it beside 0.2.0 I had problems creating credentials for the HTTP principal. I solved that by using the hadoop jars from livy 0.2.0 instead of those from the build. ... View more

The problem isn't in zeppelin, it is in livy. Check livy.out you may see a timeout connecting to hive. ... View more

I don't really have an answer but I do have some more information. I see that zeppelin contacts livy, authenticates successfully and that livy replies with a: Set-Cookie: hadoop.auth="u=zeppelin..."; HttpOnly However I don't ever see that cookie returned. As far as I can see the livy interpreter should send the cookie on every call to livy. It uses org.springframework.web.client.RestTemplate to handle communication between itself and the livy server and I can see that that framework can handle cookies but I also see that the cookie is missing. ... View more

The tokens aren't passed. zeppelin authenticates itself with livy and as it is a superuser (livy.superusers) livy takes the proxyUser sent by zeppelin and becomes that user. ... View more

I believe that the problem is that localhost is not a valid host for kerberos. I changed my livy interpreter settings to point out the actual host. ... View more