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

Unable to login after memcached has restarted #1385

Open
jsirex opened this issue Apr 9, 2020 · 6 comments
Open

Unable to login after memcached has restarted #1385

jsirex opened this issue Apr 9, 2020 · 6 comments

Comments

@jsirex
Copy link
Contributor

jsirex commented Apr 9, 2020

I have on-prem builder (4 nodes) in clustered setup with 4 memcached servers.
After memcached restart I noticed that I'm unable to login anymore.
Navigation still works.

Apr 09 15:42:48 host-1 hab[23022]: builder-api.default(O): [2020-04-09T15:42:48Z WARN  habitat_builder_api::server::services::memcache] Failed to reset namespace channel:project/stable to 17430049293516192964: Broken pipe (os error 32)

I will try to upgrade to the very latest version and reproduce the issue.

Aha! Link: https://chef.aha.io/features/APPDL-17

@jsirex jsirex added the Type:Bug label Apr 9, 2020
@jsirex
Copy link
Contributor Author

jsirex commented Apr 10, 2020

Confirmed. User unable to login again if builder-memcached had been restarted

@jeremymv2
Copy link
Contributor

@jsirex thanks for bringing this to our attention. Sorry for the inconvenience.
If you restart builder-api we believe you should be able to reconnect to memcached.

In the meantime, we will begin work on a bug fix.

@jsirex
Copy link
Contributor Author

jsirex commented Apr 10, 2020

@jeremymv2 yep. I can confirm - restarting the builder-api helps.

@stale
Copy link

stale bot commented Apr 11, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

@stale stale bot added the Stale label Apr 11, 2021
@stale stale bot removed the Stale label May 24, 2021
@stale
Copy link

stale bot commented Jul 31, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

1 similar comment
@stale
Copy link

stale bot commented Sep 17, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

@stale stale bot added the Stale label Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants