[Provider Audit] provider.medas-digital.io

[oxygene76]

Prerequisite Steps:

1. Make sure your provider has community provider attributes and your contact details (email, website):

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community
  info:
    email: "<your email>"
    website: "<your website>"

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

• More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

• If you are using a firewall, please follow this doc:
  https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/#step-11---firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:

1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")

2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.

3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.

4. Audit Issue will be closed by core team member.

Leave contact information (optional)

1. Eike Janssen
2. @xgn_MedasDigital
3. info@medas-digital.io

[shimpa1]

hi @oxygene76 ,

Your provider is not responding on status endpoint / port 8443:

curl -sk https://provider.medas-digital.io:8443/status | jq

returns an empty response

The GRPC endpoint is not working / port 8444:

grpcurl -insecure provider.medas-digital.io:8444 akash.provider.v1.ProviderRPC.GetStatus
Failed to dial target host "provider.medas-digital.io:8444": dial tcp 88.205.101.206:8444: connect: connection refused

Please fix those issues before we can continue.

thank you!

[oxygene76]

Hi, is running again, I got akash-provider-0 0/1 CrashLoopBackOff 1187 (21s ago) 15d Investigating the cause Freundliche Grüße Eike Janßen Medas Computers GmbH Im Ziegelhaus 13 63571 Gelnhausen Fon: 06051 / 91669-0 Fax: 06051 / 91669-29 http://www.medas-computers.de<http://www.medas-computers.de/> ***@***.*** Von: shimpa ***@***.***> Gesendet: Mittwoch, 8. Mai 2024 15:41 An: akash-network/community ***@***.***> Cc: Eike Janssen (medas Computers GmbH) ***@***.***>; Mention ***@***.***> Betreff: Re: [akash-network/community] [Provider Audit] provider.medas-digital.io (Issue #558) hi @oxygene76<https://github.com/oxygene76> , Your provider is not responding on status endpoint / port 8443: curl -sk https://provider.medas-digital.io:8443/status | jq returns an empty response The GRPC endpoint is not working / port 8444: grpcurl -insecure provider.medas-digital.io:8444 akash.provider.v1.ProviderRPC.GetStatus Failed to dial target host "provider.medas-digital.io:8444": dial tcp 88.205.101.206:8444: connect: connection refused Please fix those issues before we can continue. thank you! — Reply to this email directly, view it on GitHub<#558 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2T3XC3UL5X7GEL2UHQQQZTZBITQFAVCNFSM6AAAAABGSMGWIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGYYDMNRZGU>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[andy108369]

Hi @oxygene76
your provider won't bid to my deployment order:

profiles:
  compute:
    app:
      resources:
        cpu:
          units: 4
        memory:
          size: 8Gi
        storage:
          size: 20Gi

Please check your provider logs for dseq 16922520 to see if you have any relevant logs.
Example command to check the logs for that dseq:

kubectl -n akash-services logs akash-provider-0 --tail=10000000 | grep 16922520

Your provider should have enough capacity for my request though.

$ provider_info2.sh provider.medas-digital.io
PROVIDER INFO
BALANCE: 9.338558
"hostname"                   "address"
"provider.medas-digital.io"  "akash1rlkx7vef3h2jaz33ru0axhggmt6gyq35xevg5x"

Total/Available/Used (t/a/u) per node:
"name"   "cpu(t/a/u)"        "gpu(t/a/u)"  "mem(t/a/u GiB)"       "ephemeral(t/a/u GiB)"
"node1"  "16/13.33/2.67"     "0/0/0"       "31.24/27.7/3.54"      "43.13/43.13/0"
"node2"  "64/53.895/10.105"  "0/0/0"       "125.68/106.41/19.27"  "882.71/882.21/0.5"

ACTIVE TOTAL:
"cpu(cores)"  "gpu"  "mem(GiB)"  "ephemeral(GiB)"  "beta1(GiB)"  "beta2(GiB)"  "beta3(GiB)"
0.5           0      0.5         0.5               0             0             0

PERSISTENT STORAGE:
"storage class"  "available space(GiB)"

PENDING TOTAL:
"cpu(cores)"  "gpu"  "mem(GiB)"  "ephemeral(GiB)"  "beta1(GiB)"  "beta2(GiB)"  "beta3(GiB)"