Fix handling of exceptions when osquery goes away #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves an issue where the extension does not shut down if osquery
goes away unexpectedly (without sending a shutdown signal via Thrift).
The scenario could be reliably reproduced by running
osqueryi
,connecting an extension, and then sending a
SIGKILL
toosqueryi
. Theexception thrown in the
start_watcher
function would be of typethrift.transport.TTransport.TTransportException
, and would cause thewatcher thread to exit without exiting the rest of the program.
This is a possible fix for issues that users have experienced with
extensions reconnecting after the Watchdog kills osquery.