Have a question or want live help from a DataStax engineer? Let's chat.

Jump to main content

Support
DataStax Home
Downloads

Learn
Drivers
Glossary
Get Live Help

Troubleshooting DataStax Enterprise
Troubleshooting DSE OpsCenter

Can't find what you're looking for? Try searching other guides

Troubleshooting

Troubleshooting DataStax Enterprise
Learn about issues experienced with DSE and solutions or workarounds.
Troubleshooting DSE OpsCenter
Learn about issues experienced with OpsCenter and solutions or workarounds.
- SSL issues
  Troubleshooting tips for typical SSL issues.
- Browser issues
  Troubleshoot browser issues that can prevent the OpsCenter UI from loading properly. Review currently supported browsers.
- SSTable issues
  Rectify issues encountered surrounding SSTables.
- Other troubleshooting
  Various troubleshooting topics regarding DSE OpsCenter.
  - DSE version not supported by LCM
    LCM indicates that the current version of DSE is unsupported.
  - High CPU usage by opscenterd
    Increasing the nodelist polling period or setting a sleep delay can reduce excessive CPU usage when starting or running opscenterd.
  - Collecting or displaying metrics
    Adjust configuration settings to manage and display metrics.
  - Restoring materialized views
    When restoring backups on clusters running DSE 6.0.0-6.0.2, materialized views might return no results when queried.
  - DataStax Agent port setting conflict
    Ensure there are no conflicts with port 7199 used by the DataStax Agent.
  - Java not installed or JAVA_HOME environment variable not set
    Error when Java is not installed or the path is not set.
  - Insufficient user resource limits errors
    Refer to the recommended settings for insufficient user resource limits errors.
  - Error getting version update information
    Disables the check for the latest versions of OpsCenter and DataStax Enterprise.
  - OpsCenter cannot start
    Steps to take when OpsCenter cannot start up due to improper directory permissions.

Other troubleshooting

Various troubleshooting topics regarding DSE OpsCenter.

The DSE OpsCenter Help Center also provides troubleshooting information.

DSE version not supported by LCM
LCM indicates that the current version of DSE is unsupported.
High CPU usage by opscenterd
Increasing the nodelist polling period or setting a sleep delay can reduce excessive CPU usage when starting or running opscenterd.
Troubleshooting collecting or displaying metrics
Adjust configuration settings to manage and display metrics.
Restoring materialized views
When restoring backups on clusters running DSE 6.0.0-6.0.2, materialized views might return no results when queried.
DataStax Agent port setting conflict
Ensure there are no conflicts with port 7199 used by the DataStax Agent.
Java not installed or JAVA_HOME environment variable not set
Error when Java is not installed or the path is not set.
Insufficient user resource limits errors
Refer to the recommended settings for insufficient user resource limits errors.
Error getting version update information
Disables the check for the latest versions of OpsCenter and DataStax Enterprise.
OpsCenter cannot start
Steps to take when OpsCenter cannot start up due to improper directory permissions.

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use | Updated: 18 February 2022

Build time: 2022-02-18 10:49:12.284

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

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.

dse-trblshoot troubleshooting