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

Conflicts of acmnodemanager and hpcnodemanager on the same machine #13

Open
coin8086 opened this issue Mar 22, 2019 · 2 comments
Open
Assignees
Labels

Comments

@coin8086
Copy link
Member

acmnodemanager on Linux nodes may not start due to conflict with hpcnodemanager after adding HPC Pack cluster to ACM cluster

@chezhang
Copy link
Contributor

chezhang commented Apr 18, 2019

This should be due to Linux node manager listening port conflict.
Need to be fixed by modifying config in ACM Linux nodemanager, ACM Node Agent and HpcNodeAgent.

  1. ACM Linux nodemanager
    config when installing:
- "ListeningUri":"http://0.0.0.0:40000"
+ "ListeningUri":"http://0.0.0.0:40010"
  1. ACM Node Agent
    code change in file hpc-acm.git\src\Services\NodeAgent\NodeCommunicatorOptions.cs:
- public string NodeManagerUriBase { get; set; } = "http://localhost:40000/api";
+ public string NodeManagerUriBase { get; set; } = "http://localhost:40010/api";
  1. HpcNodeAgent
    code change in file One\Azure\hpc\src\Scheduler\NodeManager\RemotingCommunicator\AgentConfig.cs:
- public string ListeningUri { get => ConfigurationManager.AppSettings["ListeningUri"] ?? "http://*:40000"; }
+ public string ListeningUri { get => ConfigurationManager.AppSettings["ListeningUri"] ?? "http://*:40010"; }

@coin8086
Copy link
Member Author

Cool! Please make a Pull Request for code change and associate it with the issue. @chezhang

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

No branches or pull requests

2 participants