Push/Pull Error
653 views
Skip to first unread message
Robert Hartman
May 24, 2017, 1:33:01 AM5/24/17
to Consul
I'm getting this message in the consul log on a periodic basis. Everything seems to be working fine. The message appears only for a small subset of all nodes, but those nodes and services on them are registered fine. Should I be concerned? Any idea on why this might be happening?
2017/05/23 23:34:16 [ERR] memberlist: Push/Pull with <host_name> failed: dial tcp <ip>:8301: i/o timeout
James Phillips
May 31, 2017, 5:54:22 PM5/31/17
to consu...@googlegroups.com
Hi that generally indicates a networking issue between the host
showing that log and the target host, or this can also happen if one
of the hosts is CPU starved (out of CPU credits in EC2, for example),
and experiencing packet loss. It can also happen if there's a firewall
blocking the traffic between that pair of hosts. Because Consul agents
randomly probe each other as part of the gossip protocol, a pair with
a firewall problem may not encounter each other very often, so this
can seem sporadic.
On Tue, May 23, 2017 at 10:33 PM, Robert Hartman <hart...@gmail.com> wrote:
> I'm getting this message in the consul log on a periodic basis. Everything seems to be working fine. The message appears only for a small subset of all nodes, but those nodes and services on them are registered fine. Should I be concerned? Any idea on why this might be happening?
>
> 2017/05/23 23:34:16 [ERR] memberlist: Push/Pull with <host_name> failed: dial tcp <ip>:8301: i/o timeout
>
> --
> 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/consul/issues
> IRC: #consul on Freenode
> ---
> You received this message because you are subscribed to the Google Groups "Consul" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to consul-tool...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/consul-tool/2203711a-ae51-4445-a89c-67e9bff9f02c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
showing that log and the target host, or this can also happen if one
of the hosts is CPU starved (out of CPU credits in EC2, for example),
and experiencing packet loss. It can also happen if there's a firewall
blocking the traffic between that pair of hosts. Because Consul agents
randomly probe each other as part of the gossip protocol, a pair with
a firewall problem may not encounter each other very often, so this
can seem sporadic.
On Tue, May 23, 2017 at 10:33 PM, Robert Hartman <hart...@gmail.com> wrote:
> I'm getting this message in the consul log on a periodic basis. Everything seems to be working fine. The message appears only for a small subset of all nodes, but those nodes and services on them are registered fine. Should I be concerned? Any idea on why this might be happening?
>
> 2017/05/23 23:34:16 [ERR] memberlist: Push/Pull with <host_name> failed: dial tcp <ip>:8301: i/o timeout
>
> 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/consul/issues
> IRC: #consul on Freenode
> ---
> You received this message because you are subscribed to the Google Groups "Consul" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to consul-tool...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/consul-tool/2203711a-ae51-4445-a89c-67e9bff9f02c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages