Skip to content
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

Error creating task api socket: bind: invalid argument #24295

Open
Himura2la opened this issue Oct 25, 2024 · 2 comments
Open

Error creating task api socket: bind: invalid argument #24295

Himura2la opened this issue Oct 25, 2024 · 2 comments

Comments

@Himura2la
Copy link

Versions

  • Nomad: v1.8.2
  • CNI Plugins: v1.1.1

Operating system and Environment details

Debian 12, amd64

Issue

Clients logs are flooded with messages like that:

[WARN] client.alloc_runner.task_runner.task_hook.api: error creating task api socket: alloc_id=d2c89842-2332-9471-f996-a041e5e41e00 task=foo path=/opt/nomad/alloc/d2c89842-2332-9471-f996-a041e5e41e00/foo/secrets/api.sock error="listen unix /opt/nomad/alloc/d2c89842-2332-9471-f996-a041e5e41e00/foo/secrets/api.sock: bind: invalid argument"

[WARN] client.alloc_runner.task_runner.task_hook.api: error creating task api socket: alloc_id=e93c99d3-78c0-a3f7-5f06-03bd262e743d task=foo path=/opt/nomad/alloc/e93c99d3-78c0-a3f7-5f06-03bd262e743d/foo/secrets/api.sock error="listen unix /opt/nomad/alloc/e93c99d3-78c0-a3f7-5f06-03bd262e743d/foo/secrets/api.sock: bind: invalid argument"

Affected tasks seem random...

Reproduction steps

IDK, we did not catch the moment when these messages starts appearing. Looks like they appear only in those clusters where we have CSI volumes configured with RBD (Ceph).

Expected Result

no warnings

Actual Result

warnings

@jrasell
Copy link
Member

jrasell commented Nov 4, 2024

Hi @Himura2la and thanks for raising this issue.

I have not been able to reproduce this using Nomad v1.8.2 and checked that the UNIX socket path length is not exceeding the maximum limit. You mention they only appear on certain clusters with certain jobs; could you therefore provide more information about this or even steps for a reproduction?

$ nomad alloc exec f9e6de8c ls -ltr /secrets/
total 4
-rw-r--r-- 1 root root 827 Nov  4 09:19 nomad_token
srw-rw-rw- 1 root root   0 Nov  4 09:19 api.sock

I'll mark this issue for further investigation and await your reply. It is worth noting, this is a warning and doesn't impact the running on the allocations on the cluster itself. The impact is that they will not have the API socket available.

@Himura2la
Copy link
Author

I looked closer at the affected tasks, and they all are batch jobs, or connect-proxy- of batch jobs. Hope this helps.

@jrasell jrasell moved this from Needs Triage to Needs Roadmapping in Nomad - Community Issues Triage Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs Roadmapping
Development

No branches or pull requests

2 participants