LogoLogo
StackState.comDownloadSupportExplore playground
StackState v6.0
StackState v6.0
  • StackState docs!
  • Docs for all StackState products
  • 🚀Get started
    • Quick start guide
    • StackState walk-through
    • SUSE Rancher Prime
      • Air-gapped
      • Agent Air-gapped
  • 🦮Guided troubleshooting
    • What is guided troubleshooting?
    • YAML Configuration
    • Changes
    • Logs
  • 🚨Monitors and alerts
    • Monitors
    • Out of the box monitors for Kubernetes
    • Notifications
      • Configure notifications
      • Notification channels
        • Slack
        • Teams
        • Webhook
        • Opsgenie
      • Troubleshooting
    • Customize
      • Add a monitor using the CLI
      • Override monitor arguments
      • Write a remediation guide
  • 📈Metrics
    • Explore Metrics
    • Custom charts
      • Adding custom charts to components
      • Writing PromQL queries for representative charts
      • Troubleshooting custom charts
    • Advanced Metrics
      • Grafana Datasource
      • Prometheus remote_write
      • OpenMetrics
  • 📑Logs
    • Explore Logs
    • Log Shipping
  • 🔭Traces
    • Explore Traces
  • 📖Health
    • Health synchronization
    • Send health data over HTTP
      • Send health data
      • Repeat Snapshots JSON
      • Repeat States JSON
      • Transactional Increments JSON
    • Debug health synchronization
  • 🔍Views
    • Kubernetes views
    • Custom views
    • Component views
    • Explore views
    • View structure
      • Filters
      • Overview perspective
      • Highlights perspective
      • Topology perspective
      • Events perspective
      • Metrics perspective
      • Traces perspective
    • Timeline and time travel
  • 🕵️Agent
    • Network configuration
      • Proxy Configuration
    • Using a custom registry
    • Custom Secret Management
    • Request tracing
      • Certificates for sidecar injection
  • 🔭Open Telemetry
    • Getting started
    • Open telemetry collector
    • Languages
      • Generic Exporter configuration
      • Java
      • Node.js
      • .NET
      • Verify the results
    • Troubleshooting
  • CLI
    • StackState CLI
  • 🚀Self-hosted setup
    • Install StackState
      • Requirements
      • Kubernetes / OpenShift
        • Kubernetes install
        • OpenShift install
        • Required Permissions
        • Non-high availability setup
        • Small profile setup
        • Override default configuration
        • Configure storage
        • Exposing StackState outside of the cluster
      • Initial run guide
      • Troubleshooting
        • Logs
    • Configure StackState
      • Slack notifications
      • Stackpacks
    • Release Notes
      • v1.11.0 - 18/07/2024
      • v1.11.3 - 15/08/2024
      • v1.11.4 - 29/08/2024
      • v1.12.0 - 24/10/2024
      • v1.12.1 - 08/11/2024
    • Upgrade StackState
      • Steps to upgrade
      • Version-specific upgrade instructions
    • Uninstall StackState
    • Air-gapped
      • StackState air-gapped
      • StackState Kubernetes Agent air-gapped
    • Data management
      • Backup and Restore
        • Kubernetes backup
        • Configuration backup
      • Data retention
      • Clear stored data
    • Security
      • Authentication
        • Authentication options
        • File-based
        • LDAP
        • Open ID Connect (OIDC)
        • KeyCloak
        • Service tokens
      • RBAC
        • Role-based Access Control
        • Permissions
        • Roles
        • Scopes
      • Self-signed certificates
  • 🔐Security
    • Service Tokens
    • Ingestion API Keys
  • ☁️SaaS
    • User Management
  • Reference
    • StackState Query Language (STQL)
    • Chart units
Powered by GitBook
LogoLogo

Legal notices

  • Privacy
  • Cookies
  • Responsible disclosure
  • SOC 2/SOC 3
On this page
  • Quick troubleshooting guide
  • Known issues
  1. Self-hosted setup
  2. Install StackState

Troubleshooting

StackState Self-hosted

PreviousInitial run guideNextLogs

Last updated 10 months ago

Quick troubleshooting guide

Here is a quick guide for troubleshooting the startup of StackState:

  1. Check that the install completed successfully and the release is listed:

    helm list --namespace stackstate
  2. Check that all pods in the StackState namespace are running:

    kubectl get pods

    In a first deployment it can be that containers in several pods restart a few times, because they are waiting for other pods to start up and be in the ready state. This can be delayed due to scheduling and docker image pulling delays.

    Pods that are in pending state are usually an indication of a problem:

    • The pod is unschedulable due to lack of resources in the cluster. If a cluster auto-scaler is active it will often be able to resolve this automatically, otherwise manual intervention is needed to add more nodes to the cluster

    • The pod is unschedulable, there are nodes it would fit on, but those nodes have taints that the pod doesn not tolerate. To solve this more nodes can be added that don't have the taints, but StackState can also be to tolerate certain taints and run on the tainted nodes.

    • The pod is waiting for the Persistent Volumes (PVs) to be mounted. A cause can be that the StackState Helm chart doesn't specify a storageClassName but relies on the cluster having a default storage class. When there is no default for the cluster it's required to via the Helm values of StackState.

    For pods with state ImagePullBackOff also check the exact error message, common causes are:

    • An incorrect username/password used to pull the images

    • Connecting to the docker registry failed, this can be due to authentication issues or connectivity issues (firewalls, air-gapped installations)

    • A typo in the overriden docker image registry URL

    To find out a more detailed cause for the Pending, ImagePullBackOff or CrashLoopBackOff states use this command:

    kubectl describe pod<pod-name>

    The output contains an event section at the end which usually contains the problem. It also has a State section for each container that has more details for termination of the container.

  3. for errors.

  4. Check the Knowledge base on the .

Known issues

Check the to find troubleshooting steps for all known issues.

🚀
StackState support Knowledge base
specify a storage class
Check the logs
StackState Support site
configured