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

Connections to vault still in CLOSE_WAIT status #59

Open
Thorsieger opened this issue Oct 26, 2023 · 0 comments
Open

Connections to vault still in CLOSE_WAIT status #59

Thorsieger opened this issue Oct 26, 2023 · 0 comments

Comments

@Thorsieger
Copy link

foreman version : 3.7.0
foreman_vault version : 1.2.0

Hello, we are using foreman_vault to get secret from our vault. But since we upgrade to foreman version 3.7.0 we have connections to vault that do not close, stack and reach the limit of connections. We then only found that restarting foreman close the connections and allow use to regenerate puppet configuration.

production.log :

2023-09-25T03:41:21 [I|app|5eae260a] Backtrace for 'Failed to generate external nodes for [node]' error (Errno::EADDRNOTAVAIL): Failed to open TCP connection to vault.xxx:443 (Cannot assign requested address - connect(2) for "vault.xxx" port 443)
 5eae260a | /usr/share/ruby/net/http.rb:960:in `initialize'

[root@katello~]# netstat -a | grep "service-internal.:https CLOSE_WAIT" | wc -l
28232

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