too long for unix domain socket

Not specified by the original author.

TL;DR

What fixed it This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path.

Steps

1. What was going on

Ansible ssh connections failed with SSH Error: unix_listener: "[HOME]/..." too long for Unix domain socket, typically against hosts with long names such as EC2 public DNS names. The ControlPath socket path exceeded the OS limit for unix socket paths. The error message printed the full socket path, which made the overlong hostname portion obvious.

2. What fixed it

This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path. If you still see the error on 2.3 or newer, it is because a custom controlpath is set in ansible.cfg; remove the custom setting (leave it blank) so the hashed default applies. On older versions the workaround is to shorten the path in ansible.cfg with controlpath = %(directory)s/%%h-%%p-%%r under [ssh_connection].

When to use

You are seeing this: What was going on Ansible ssh connections failed with SSH Error: unixlistener: "[HOME]/..." too long for Unix domain socket, typically against hosts with long names such as EC2 public DNS names. Use this skill when you run into "SSH Error: unixlistener too long for Unix domain socket on hosts with long names".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the thread, the question was: Ansible ssh connections failed with SSH Error: unixlistener: "[HOME]/..." too long for Unix domain socket, typically against hosts with long names such as EC2 public DNS names. The ControlPath socket path exceeded the OS limit for unix socket paths. The error message printed the full socket path, which made the overlong hostname portion obvious. The verified resolution: This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path. If you still see the error on 2.3 or newer, it is because a custom controlpath is set in ansible.cfg; remove the custom setting (leave it blank) so the hashed default applies. On older versions the workaround is to shorten the path in ansible.cfg with controlpath = %(directory)s/%%h-%%p-%%r under [sshconnection]. Thread: https://vectle.com/threads/thr_0BMtQ1f7hzHe57LSyVv9Zw

Not specified by the original author.

TL;DR

This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path.

Steps

1. This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path. If you still see the error on 2.3 or newer, it is because a custom controlpath is set in ansible.cfg; remove the custom setting (leave it blank) so the hashed default applies. On older versions the workaround is to shorten the path in ansible.cfg with controlpath = %(directory)s/%%h-%%p-%%r under [ssh_connection].

When to use

You are seeing this: Ansible ssh connections failed with SSH Error: unixlistener: "[HOME]/..." too long for Unix domain socket, typically against hosts with long names such as EC2 public DNS names. Use this skill when you run into "SSH Error: unixlistener too long for Unix domain socket on hosts with long names".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Question from the thread: Ansible ssh connections failed with SSH Error: unixlistener: "[HOME]/..." too long for Unix domain socket, typically against hosts with long names such as EC2 public DNS names. The ControlPath socket path exceeded the OS limit for unix socket paths. The error message printed the full socket path, which made the overlong hostname portion obvious. Verified answer: This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path. If you still see the error on 2.3 or newer, it is because a custom controlpath is set in ansible.cfg; remove the custom setting (leave it blank) so the hashed default applies. On older versions the workaround is to shorten the path in ansible.cfg with controlpath = %(directory)s/%%h-%%p-%%r under [sshconnection]. Full thread: https://vectle.com/threads/thr_0BMtQ1f7hzHe57LSyVv9Zw

Not specified by the original author.

TL;DR

Search with large (+100) includedomains/excludedomains lists returns empty results; shrinking the list brings results back. No documented limit found.

Steps

1. Collaborator maitarasher: Tavily imposes no hard limit, but very long domain lists can lead to suboptimal or empty results - keep the lists as short as possible. For exclude_domains, a 150-domain deny list can also simply leave no relevant results for the query. Lesson: prefer short, targeted domain lists.

When to use

You are seeing this: Search with large (+100) includedomains/excludedomains lists returns empty results; shrinking the list brings results back. Use this skill when you run into "Empty results for search with large (+100) includedomains/excludedomains lists".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In gh:tavily-ai/tavily-python#83 (https://github.com/tavily-ai/tavily-python/issues/83), the question was: Search with large (+100) includedomains/excludedomains lists returns empty results; shrinking the list brings results back. No documented limit found. The verified resolution: Collaborator maitarasher: Tavily imposes no hard limit, but very long domain lists can lead to suboptimal or empty results - keep the lists as short as possible. For exclude_domains, a 150-domain deny list can also simply leave no relevant results for the query.