ข้ามไปยังเนื้อหา

This is the Experimental version (Latest). It is under active development and may change. For the most reliable documentation, use the version selector in the top-right to switch to Stable, or click here to go to the Stable version's homepage.

Health Checks Failed

อัพเดทล่าสุด:

เนื้อหานี้ยังไม่มีในภาษาของคุณ

Force Healthcheck for Opstella will refresh caches that Opstella stored for its operations and also perform priliminary checks for Opstella Dependency Services.

  1. Go to Opstella Core (Back-end) URL with Health Check Path https://opstella-backend.CHANGEME.com/healthcheck

    It should return a JSON with message OK

  1. Connect to 🟢 Management Kubernetes Cluster ; i.e w/ Kubeconfig File

    Terminal window
    export KUBECONFIG="$HOME/opstella-installation/kubeconfigs/management_cluster.yaml"
  2. Port-Forward of Opstella-Worker of Port 3000

    Choose one Worker, worker-XYZ. Where XYZ is the name of the worker.

    For example, Worker Kubernetes worker-kubernetes

    Terminal window
    kubectl port-forward -n opstella-system svc/worker-kubernetes 3000:3000

  3. Open new Terminal or Using Web Browser and go to http://localhost:3000/ and http://localhost:3000/healthcheck

    • IF the Worker is OK
      • http://localhost:3000/: Should return Worker-XYZ ; Where XYZ is the name of the worker.
      • http://localhost:3000/healthcheck: Should return OK

    • IF the Worker is NOT OK
      • http://localhost:3000/healthcheck: May return errors such as Middleware Failed or others.
      • Please investigate the coorresponding Worker connection to its Dependency Services.
      • Please investigate configuration of the devopstool in Opstella Core (Back-end) UI.
      • Please investigate the logs of the Worker Pod for more details.
      • For example, worker-kubernetes may have issues connecting to Kubernetes API Server or Token used to connect to Kubernetes Cluster is invalid/expired.

Finished?

Use the below navigation to proceed