-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Can't schedule a job because "resources exhausted" #146
Comments
I think the problem here is that nomad assumes eth0 for all systems, which is not true for systemd. See the code here: https://github.com/hashicorp/nomad/blob/master/client/fingerprint/network_unix.go#L38 |
Cross-linking with #158 |
Thanks for your reply @kelseyhightower & @sethvargo Trying to test this hypothesis:
I choose this because:
After compiling the modified version of nomad and running, I still get this result:
Of course this is just a quick hack to test the hypothesis and not an actual fix. Are my steps above correct? If so, the problem might be different. |
+1 Nomad 0.1.0 docker images do not currently function on CentOS 7 or CoreOS stable (766.4.0), similar error (using example.nomad)
Installing net-tools (provides ifconfig) and setting net.ifnames 0 to rename the interface back to eth0 also does not make a difference on CentOS 7. Nomad server/agent log:
Interesting line
|
It seems I am getting the same issue on Debian:
|
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
I tried starting nomad on both CoreOS (local and GCE) and Debian (GCE) and running a cluster (both with -dev and with client/server. For installation, I follow the steps described in the Vagrantfile.
As soon as I try to run:
I get a message that my resources are exhausted:
Or this variant:
This is the first job I am scheduling so it is unlikely that the network resources are actually exhausted. Am I missing some kind of configuration telling nomad about the network?
The text was updated successfully, but these errors were encountered: