nomad 0.1.2 - problems launching client

253 views
Skip to first unread message

Matt Ho

unread,
Oct 29, 2015, 5:37:34 PM10/29/15
to Nomad
I'm attempting to launch a nomad client and am getting the following error:

# nomad agent -config nomad.conf
==> Starting Nomad agent...
==> Nomad agent configuration:

                 Atlas: <disabled>
                Client: true
             Log Level: DEBUG
                Region: global (DC: us-east-1)
                Server: false

==> Nomad agent started! Log data will stream in below:

    2015/10/29 21:34:34 [INFO] client: using state directory /root/data/client
    2015/10/29 21:34:34 [INFO] client: using alloc directory /root/data/alloc
    2015/10/29 21:34:34 [WARN] fingerprint.network: Unable to parse Speed in output of '/sbin/ethtool eth0'
    2015/10/29 21:34:34 [WARN] fingerprint.network: Unable to read link speed from /sys/class/net/eth0/speed
    2015/10/29 21:34:34 [DEBUG] fingerprint.network: Unable to read link speed; setting to default 100
    2015/10/29 21:34:34 [DEBUG] client: applied fingerprints [arch cpu host memory storage network env_aws]
    2015/10/29 21:34:34 [DEBUG] client: available drivers [docker exec]
    2015/10/29 21:34:34 [ERR] yamux: Invalid protocol version: 72
    2015/10/29 21:34:49 [ERR] yamux: Invalid protocol version: 72
    2015/10/29 21:34:49 [ERR] client: failed to register node: rpc error: EOF
    2015/10/29 21:35:13 [ERR] yamux: Invalid protocol version: 72
    2015/10/29 21:35:13 [ERR] client: failed to register node: rpc error: EOF

Here's the config file for the agent:

# Increase log verbosity
log_level = "DEBUG"

# Setup data dir
data_dir = "/root/data"

# list on all addresses
bind_addr = "xxx.xxx.xxx.xxx"

# datacenter location
datacenter = "us-east-1"

client {
  enabled = true

  servers = ["xxx.xxx.xxx.xxx:4646"]
}

Any thoughts as to what this error means?

M

Armon Dadgar

unread,
Oct 29, 2015, 7:31:47 PM10/29/15
to Matt Ho, Nomad
Hey Matt,

I think the issue is you are using port 4646 on the servers, that should be 4647.
The 4646 port serves HTTP, which explains why you are seeing so many protocol errors,
as the client is expecting to talk to the RPC port.

Best Regards,
Armon Dadgar

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/nomad/issues
IRC: #nomad-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Nomad" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nomad-tool+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nomad-tool/997c8cad-d5bf-4b70-8f0e-5085837ca27f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Matt Ho

unread,
Oct 29, 2015, 7:37:54 PM10/29/15
to Nomad
Sure enough, that was it.  Thanks!  I'm wondering if something needs to change with the documentation on:


In the section for ports, I read that as ports 4647 and 4648 are only used on server nodes.  Am I mis-interpreting something?

M

Armon Dadgar

unread,
Oct 29, 2015, 10:57:33 PM10/29/15
to Matt Ho, Nomad
The ports are only used by the servers to bind to, however the clients still connect to that port. I can see how it's a point of confusion, please open a ticket so that we can improve the documentation. Thanks!

Best Regards,

Armon Dadgar

Sent from my iPhone
Reply all
Reply to author
Forward
0 new messages