You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if distributed TLS requests to --distributed_tls_read_endpoint and --distributed_tls_write_endpoint fail on the TCP/IP or TLS layer, or if the JSON in the response could not be parsed, osquery shows nothing and retries (even when running with --verbose).
E.g. if osquery is configured with --distributed_tls_max_attempts=3 and the server is down or not returning a JSON response you just get:
265887 I0430 11:55:03.687932 29520 tls.cpp:263] TLS/HTTPS POST request to URI: https://example.com/api/v1/osquery/distributed/write
265891 I0430 11:55:05.651844 29520 tls.cpp:263] TLS/HTTPS POST request to URI: https://example.com/api/v1/osquery/distributed/write
265892 I0430 11:55:10.595957 29520 tls.cpp:263] TLS/HTTPS POST request to URI: https://example.com/api/v1/osquery/distributed/write
Which does not help for troubleshooting.
We should add some error logs when running with --verbose.
The text was updated successfully, but these errors were encountered:
Bug report
What version of osquery are you using?
osquery 5.12.1
Currently, if distributed TLS requests to
--distributed_tls_read_endpoint
and--distributed_tls_write_endpoint
fail on the TCP/IP or TLS layer, or if the JSON in the response could not be parsed, osquery shows nothing and retries (even when running with--verbose
).E.g. if osquery is configured with
--distributed_tls_max_attempts=3
and the server is down or not returning a JSON response you just get:Which does not help for troubleshooting.
We should add some error logs when running with
--verbose
.The text was updated successfully, but these errors were encountered: