-
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
Nomad can't use in windows7/2012r2 from version 0.7.3to0.8.3 #4309
Comments
I have tried many versions, only the version 0.7.0 can work in windows7. |
@molin0000 Can you display |
yes.Windows IP 配置 以太网适配器 本地连接: 连接特定的 DNS 后缀 . . . . . . . : localdomain 隧道适配器 isatap.localdomain: 媒体状态 . . . . . . . . . . . . : 媒体已断开 隧道适配器 Teredo Tunneling Pseudo-Interface: 媒体状态 . . . . . . . . . . . . : 媒体已断开 And for English: Windows IP Configuration Ethernet adapter 本地连接: Connection-specific DNS Suffix . : localdomain Tunnel adapter isatap.localdomain: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected |
I found it can be run on my windows, just add a net adapter config, like this: |
@molin0000 Currently nomad selects the network interface for fingerprinting based on the client's default gateway. Your client doesn't seem to have a default gateway thus you need to set the You will either need a host with the default route or configuring it as you've been using either the CLI option or a configuration file |
Ok! Thank you. |
This works for me on Windows.
|
base on windows 7 Chinese character and nomad 0.10.3, run client agent still exist this question, need to add thanks molin0000! |
Alternatively you can create nomad.config file:
and run it like this |
The approach from @belesev and @hubugui worked for me. The problem is still present on 11.2, but only on some hosts. I have yet to positively identify exactly what is causing it, but the machines are running German versions of Windows Server 2019 set to use ENG-US, and the network interface name is "NIC1" - no special characters. As a note, the nic has a default gateway manually defined (based on earlier comments here, that seemed to be a possible cause if there was no default gateway). There are 2 NICs on this host, only one of which has a cable plugged in. I've tried disabling the unused nic, but there's no difference in the fingerprinting issue. I have my nomad agent using "-config='c:\nomad-client\config'", and I just add an additional hcl file in that directory for those hosts that need a little extra help due to this fingerprinting not finding a nic with the specified IP. Contents of that additional file are: client { |
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. |
If you have a question, prepend your issue with
[question]
or preferably use the nomad mailing list.If filing a bug please include the following:
Nomad version
Output from
nomad version
�[0mNomad v0.8.3 (c85483d)�[0m
Operating system and Environment details
Windows 7 and Windows Server 2012 R2
Issue
Nomad can't use in windows7/2012r2 from version 0.7.3to0.8.3
Reproduction steps
Just try the command:
nomad agent -dev
and it will exit after a few seconds.
Nomad Server logs (if appropriate)
error log is:
==> Error starting agent: client setup failed: fingerprinting failed: Error while detecting network interface during fingerprinting: No default interface found with matching IP
std log is:
==> No configuration files loaded
==> Starting Nomad agent...
2018/05/19 23:26:32 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]
2018/05/19 23:26:32 [INFO] raft: Node at 127.0.0.1:4647 [Follower] entering Follower state (Leader: "")
2018/05/19 23:26:32 [INFO] serf: EventMemberJoin: 27FB.global 127.0.0.1
2018/05/19 23:26:32.894337 [INFO] nomad: starting 2 scheduling worker(s) for [service batch system _core]
2018/05/19 23:26:32.911299 [DEBUG] server.nomad: lost contact with Nomad quorum, falling back to Consul for server list
2018/05/19 23:26:32.928235 [INFO] nomad: adding server 27FB.global (Addr: 127.0.0.1:4647) (DC: dc1)
2018/05/19 23:26:32.965218 [INFO] client: using state directory C:\Users\molin\AppData\Local\Temp\NomadClient676797939
2018/05/19 23:26:32.976288 [INFO] client: using alloc directory C:\Users\molin\AppData\Local\Temp\NomadClient951381174
2018/05/19 23:26:33.053359 [DEBUG] client.fingerprint_manager: built-in fingerprints: [arch consul cpu host memory network nomad signal storage vault env_gce env_aws]
2018/05/19 23:26:33 [WARN] raft: Heartbeat timeout from "" reached, starting election
2018/05/19 23:26:33 [INFO] raft: Node at 127.0.0.1:4647 [Candidate] entering Candidate state in term 2
2018/05/19 23:26:33 [DEBUG] raft: Votes needed: 1
2018/05/19 23:26:33 [DEBUG] raft: Vote granted from 127.0.0.1:4647 in term 2. Tally: 1
2018/05/19 23:26:33 [INFO] raft: Election won. Tally: 1
2018/05/19 23:26:33 [INFO] raft: Node at 127.0.0.1:4647 [Leader] entering Leader state
2018/05/19 23:26:33.893688 [INFO] nomad: cluster leadership acquired
2018/05/19 23:26:33.964685 [ERR] consul: error looking up Nomad servers: server.nomad: unable to query Consul datacenters: Get http://127.0.0.1:8500/v1/catalog/datacenters: dial tcp 127.0.0.1:8500: connectex: No connection could be made because the target machine actively refused it.
2018/05/19 23:26:34.086689 [DEBUG] client.fingerprint_manager: fingerprinting consul every 15s
2018/05/19 23:26:34.132498 [DEBUG] leader: reconciling job summaries at index: 0
2018/05/19 23:26:35.087360 [DEBUG] fingerprint.cpu: frequency: 2600 MHz
2018/05/19 23:26:35.087360 [DEBUG] fingerprint.cpu: core count: 2
Nomad Client logs (if appropriate)
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: