Troubleshooting Kerberos in OpsCenter

About this task

Troubleshoot OpsCenter Kerberos connections with debug options.


  1. Locate the cluster_name.conf file. The location of this file depends on the type of installation:

    • Package installations: /etc/opscenter/clusters/cluster_name.conf

    • Tarball installations: install_location/conf/clusters/cluster_name.conf

  2. Open the cluster-specific configuration file, cluster_name.conf for editing. Replace cluster_name with the name of your cluster.

  3. Add the following to the [kerberos] section to output debug messages during Kerberos connections attempts from OpsCenter:

    debug = True

    The debug option outputs the contents of the server section from the jaas-krb5.conf file, informing you of the settings in use that you can verify against your configuration settings.

  4. Restart OpsCenter.

  5. If deeper debugging is necessary, add to $OPSC_JVM_OPTS. The JVM parameter outputs verbose information about reasons why Kerberos connections attempts are failing, such as not authenticating due to key expiration, or no keys present in keytab, or cannot find keytab, for example.

    For more information about JVM, see Configuring the OpsCenter JVM.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,