StackState Docs
StackState.comDownloadBlogsSupport
Search…
StackState version 4.1 (EOL)
Welcome to the StackState Docs!
🚀
Setup
Requirements
Installation
Kubernetes install
Linux install
StackState CLI
Troubleshooting
Authentication
Data management
Upgrade StackState
👤
Use
Introduction to StackState
Views
Analytics
Alerting
Anomaly Detection with Baselines
Glossary
🧩StackPacks
What is a StackPack?
Add-ons
Integrations
Develop your own StackPacks
🔧
Configure
Topology
Telemetry
Traces
Security
View state configuration
Identifiers
Logging
📖
Develop
Developer guides
Reference
Tutorials
Powered By GitBook
Troubleshooting
This page describes StackState version 4.1.
The StackState 4.1 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.1 version range to upgrade to a more recent release.
Go to the documentation for the latest StackState release.

Quick troubleshooting guide

Here is a quick guide for troubleshooting the startup of StackState on Kubernetes and Linux:
Kubernetes
Linux
  1. 1.
    Check that the install completed successfully and the release is listed:
    helm list --namespace stackstate
  2. 2.
    Check that all pods in the StackState namespace are running:
    kubectl get pods
  3. 3.
    ​Check the logs for errors.
  4. 4.
    Check the Knowledge base on the StackState Support site.
  1. 1.
    Check that the systemd services StackGraph and StackState are running:
    sudo systemctl status stackgraph
    sudo systemctl status stackstate
  2. 2.
    Check connection to StackState's user interface, default listening on TCP port 7070.
  3. 3.
    Check log files for errors, located at /opt/stackstate/var/log/
  4. 4.
    Check the Knowledge base on the StackState Support site.

Known issues

Check the StackState support Knowledge base to find troubleshooting steps for all known issues.

Reindex StackState

It is not advised to reindex StackState unless this was explicitly recommended by StackState support.
For search and querying purposes, StackState builds an index out of data in the graph database. It is possible to initiate a rebuild of this index from StackState's graph database. Note that under normal circumstances you will never need to do this.
  1. 1.
    Make sure that StackState is not running with the following command: systemctl stop stackstate
  2. 2.
    Make sure that StackGraph is running with the following command: systemctl start stackgraph
  3. 3.
    Execute the reindex command: sudo -u stackstate /opt/stackstate/bin/sts-standalone.sh reindex --graph default
Do not kill the reindex process while it is running. The reindex process will take some time to complete. You can monitor progress in the StackState logs.
Previous
StackState CLI
Next - Setup
Authentication
Last modified 1yr ago
Copy link
Outline
Quick troubleshooting guide
Known issues
Reindex StackState