Skip to content

Latest commit

 

History

History
31 lines (21 loc) · 1.37 KB

troubleshooting.md

File metadata and controls

31 lines (21 loc) · 1.37 KB
Raw

Troubleshooting

Possible Deployment Issues and Recommendations

Provider Slow or Over Utilized disks

Issue - Slow/over utilized disks OR networking issue impacting distributed storage system (Ceph)

Solution - always use providers with beta3 class fast storage and change to a new provider if you experience issues

Persistent Storage for Deployment Full

Issue - persistent storage allocated to the deployment reaches capacity

Solution - either use fast ephemeral storage so the pod will automatically restart once it gets full or allocate more disk space when for the persistent storage. Continue to watch and clean the disk or redeploy the pod once persistent storage gets full.

Hostname Conflict - May Cause Manifest Send Errors

If the hostname defined in the accept field is already in use within the Akash provider, a conflict occurs if another deployment attempts to launch with the same hostname. This could occur within our testnet environment if multiple people are attempting to use the same SDL and deploy to the same provider. Consider changing the accept field to a unique hostname (I.e. <myname>.locahost) if you receive an error in send of the manifest to the provider.

 grafana:
    image: grafana/grafana
    expose:
      - port: 3000
        as: 80
        to:
          - global: true
        accept:
          - webdistest.localhost