diff options
Diffstat (limited to 'lib/chef/formatters/error_inspectors/api_error_formatting.rb')
| -rw-r--r-- | lib/chef/formatters/error_inspectors/api_error_formatting.rb | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/lib/chef/formatters/error_inspectors/api_error_formatting.rb b/lib/chef/formatters/error_inspectors/api_error_formatting.rb index f306a5a5f1..954eebafdb 100644 --- a/lib/chef/formatters/error_inspectors/api_error_formatting.rb +++ b/lib/chef/formatters/error_inspectors/api_error_formatting.rb @@ -28,7 +28,7 @@ class Chef def describe_network_errors(error_description) error_description.section("Networking Error:", <<~E) #{exception.message} - + Your chef_server_url may be misconfigured, or the network could be down. E error_description.section("Relevant Config Settings:", <<~E) @@ -40,25 +40,25 @@ E error_description.section("Authentication Error:", <<~E) Received an EOF on transport socket. This almost always indicates a network error external to chef-client. Some causes include: - + - Blocking ICMP Dest Unreachable (breaking Path MTU Discovery) - IPsec or VPN tunnelling / TCP Encapsulation MTU issues - Jumbo frames configured only on one side (breaking Path MTU) - Jumbo frames configured on a LAN that does not support them - Proxies or Load Balancers breaking large POSTs - Broken TCP offload in network drivers/hardware - + Try sending large pings to the destination: - + windows: ping server.example.com -f -l 9999 unix: ping server.example.com -s 9999 - + Try sending large POSTs to the destination (any HTTP code returned is success): - + e.g.: curl http://server.example.com/`printf '%*s' 9999 '' | tr ' ' 'a'` - + Try disabling TCP Offload Engines (TOE) in your ethernet drivers. - + windows: Disable-NetAdapterChecksumOffload * -TcpIPv4 -UdpIPv4 -IpIPv4 -NoRestart Disable-NetAdapterLso * -IPv4 -NoRestart @@ -66,7 +66,7 @@ E Restart-NetAdapter * unix(bash): for i in rx tx sg tso ufo gso gro lro rxvlan txvlan rxhash; do /sbin/ethtool -K eth0 $i off; done - + In some cases the underlying virtualization layer (Xen, VMware, KVM, Hyper-V, etc) may have broken virtual networking code. E @@ -89,7 +89,7 @@ E chef_server_url "#{server_url}" node_name "#{username}" client_key "#{api_key}" - + If these settings are correct, your client_key may be invalid, or you may have a chef user with the same client name as this node. E |