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

consul-dataplane 1.23 and 1.3.1 keep crashing with "Too many open files" on EKS #378

Closed
remiphilippe opened this issue Dec 27, 2023 · 2 comments

Comments

@remiphilippe
Copy link

Hello,
We use EKS 1.24 (containerd) configured with:

# Having non-zero Limit*s causes performance problems due to accounting overhead
# in the kernel. We recommend using cgroups to do container-local accounting.
LimitNPROC=infinity
LimitCORE=infinity
LimitNOFILE=infinity

But our consul-dataplane containers keep dying with the following error:

2023-12-27T15:42:31.825Z+00:00 [critical] envoy.assert(23) assert failure: SOCKET_VALID(result.return_value_). Details: socket(2) failed, got error: Too many open files
2023-12-27T15:42:31.825Z+00:00 [critical] envoy.backtrace(23) Caught Aborted, suspect faulting address 0x176b00000010
2023-12-27T15:42:31.825Z+00:00 [critical] envoy.backtrace(23) Backtrace (use tools/stack_decode.py to get line numbers):
2023-12-27T15:42:31.825Z+00:00 [critical] envoy.backtrace(23) Envoy version: c2919e90b0e63ad78602122d6c2c3e2c0df1e0fc/1.26.6/Clean/RELEASE/BoringSSL
[symbolize_elf.inc : 1000] RAW: /proc/self/task/16/maps: errno=24

we can't find any reasons for this, even our elastics work on these nodes (which are usually the fd problem child). Any pointers would be great!

Thanks

@remiphilippe
Copy link
Author

probably going to self reply, but looks a lot like this: awslabs/amazon-eks-ami#1551

@remiphilippe
Copy link
Author

confirmed that was the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant