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

A hanging extension with an open socket read prevents new shells from starting #3764

Closed
theopolis opened this issue Oct 4, 2017 · 0 comments
Labels
bug extensions Related to osquery extension SDK or to extensions themselves

Comments

@theopolis
Copy link
Member

The osqueryi shell may not start if hanging extensions are attempting a read from an extension socket that was not shutdown properly. When the new shell starts it will check if an existing socket path is still "active" by attempting a ping API call. No timeout is used so this may hang the initialization of the shell.

@theopolis theopolis added bug extensions Related to osquery extension SDK or to extensions themselves labels Oct 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug extensions Related to osquery extension SDK or to extensions themselves
Projects
None yet
Development

No branches or pull requests

1 participant