petibonvm,   I also had this issue in CDH 5.1.x.  My advice would be to upgrade to CM/CDH 5.3 and use Spark on YARN.  If that is not currently possible, the following work around is posted in the CM 5.1.x Release Notes:   The Spark History Server does not start when Kerberos authentication is enabled. The Spark History Server does not start when managed by a Cloudera Manager 5.1 instance when Kerberos authentication is enabled. Workaround: Go to the Spark service. Expand the History Server Default Group > Advanced category. Add the following configuration to the History Server Environment Advanced Configuration Snippet property: SPARK_HISTORY_OPTS=-Dspark.history.kerberos.enabled=true \ -Dspark.history.kerberos.principal=principal \ -Dspark.history.kerberos.keytab=keytab where principal is the name of the Kerberos principal to use for the History Server, and keytab is the path to the principal's keytab file on the local filesystem of the host running the History Server.   Regards, Chad ... View more

Please refer to the following page as part of the Kerberos setup:  http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_sg_s7_prepare_cluster.html   By default, the mapred, hdfs, and bin user accounts are kept from submitting and executing jobs. ... View more

I also ran into this issue on a Kerberos secured CDH5.1 cluster.  After making the following changes to the Oozie configuration via Cloudera Manager, I am able to bring the browser up (may not be suitable for production):   Property: Oozie Server Advanced Configuration Snippet (Safety Valve) for oozie-site.xml    <property>   <name>oozie.authentication.type</name>   <value>simple</value> </property> <property>   <name>oozie.authentication.token.validity</name>   <value>36000</value> </property> <property>   <name>oozie.authentication.cookie.domain</name>   <value>example.com</value> </property> ... View more