Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[provider.akashserverdaniel.nl] akash server #725

Open
Speld opened this issue Nov 12, 2024 · 1 comment
Open

[provider.akashserverdaniel.nl] akash server #725

Speld opened this issue Nov 12, 2024 · 1 comment
Assignees

Comments

@Speld
Copy link

Speld commented Nov 12, 2024

Prerequisite Steps:

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

Done


[Ref documentation:](https://akash.network/docs/providers/audited-attributes/#attribute-auditors).

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

host .ingress.


Example:
``
root@akash-1:/home/user# host aaa.ingress.akash.akashserverdaniel.nl
aaa.ingress.akash.colnetwork.com is an alias for akash.akashserverdaniel.nl.
akash.akashserverdaniel.nl has address 87.209.236.248

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

Confirmed, firewall is disabled

Leave contact information (optional)

Name: Daniel Spel
Discord: daniel_380805
Contact email address: [email protected]

@shimpa1
Copy link

shimpa1 commented Dec 5, 2024

hi @Speld ,

This is the status of the audit process:

Provider name: provider.akashserverdaniel.nl
Provider address: akash1yv80gw479dyqkpcu65lscnav73wugsrucenu82
Provider URI: provider.akashserverdaniel.nl
Provider URI name resolution works? yes
Ingress URI name resolution works? yes
Provider status endpoint works? yes
Provider grpc status endpoint works? yes
Provider responding to orders? no
Deployment works?
SSH works?
Network functional?
Attributes OK? no
Other remarks:

The provider only has 4 VCPU available total. Highly suggested to increase the number of VCPU to at least 32.
This is probably the reason the provider is not responding to orders.

provider-services query provider get akash1yv80gw479dyqkpcu65lscnav73wugsrucenu82
attributes:

  • key: organization
    value: Cloudprovider
  • key: arch
    value: intel
  • key: region
    value: eu-west
  • key: Capabilities/memory
    value: ddr4
  • key: Network-Speed
    value: 1GB
    host_uri: https://provider.akashserverdaniel.nl:8443
    info:
    email: ""
    website: ""
    owner: akash1yv80gw479dyqkpcu65lscnav73wugsrucenu82

Please set the

  • key: host
    value: akash
  • key: tier
    value: community

Also please set the info: section in your ~/provider/provider.yaml file

Apply those settings:

helm upgrade --install akash-provider akash/provider -n akash-services -f provider.yaml --set bidpricescript="$(cat ~/provider/price_script_generic.sh | openssl base64 -A)"

Please revisit after those issues have been fixed.

thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants