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.

Sign up for GitHub

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

Jump to bottom

AKASH_CLUSTER_NODE_PORT_QUANTITY doesn't appear to take into effect #135

Open
andy108369 opened this issue Oct 20, 2023 · 0 comments
Open

AKASH_CLUSTER_NODE_PORT_QUANTITY doesn't appear to take into effect #135

andy108369 opened this issue Oct 20, 2023 · 0 comments
Labels
P2 repo/provider Akash provider-services repo issues

Comments

@andy108369
Copy link
Contributor

andy108369 commented Oct 20, 2023 •
edited
Loading

AKASH_CLUSTER_NODE_PORT_QUANTITY doesn't appear to take into effect.

Even when set to 0 or 1 by the provider, the provider still bids to the SDL with multiple node ports (two in total, and one extra HTTP 80)

dseq in the logs 13293092

provider logs that's been running with AKASH_CLUSTER_NODE_PORT_QUANTITY set to 0 => logs.txt

provider-services 0.4.6
akash network 0.26.1
@andy108369 andy108369 added repo/provider Akash provider-services repo issues awaiting-triage labels Oct 20, 2023
@troian troian added P2 and removed awaiting-triage labels Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P2 repo/provider Akash provider-services repo issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@troian @andy108369