search

PaloAltoNetworks / SafeNetworking

Read only mirror. To contribute or submit issues, please go to the website link --->
https://gitlab.com/panw-gse/as/SafeNetworking/
Apache License 2.0
12 stars 10 forks source link

Need to catch timeout exceptions from Elasticsearch #89 #17

Closed punisherVX closed 5 years ago

punisherVX commented 6 years ago

Expected behavior and actual behavior.

Expect code to catch read/write errors for sfn-dns-event documents and continue processing.
Actual behavior is that the error is caught and shown, but processing stops, eventually, because all documents fail once we hit this error.

Steps to reproduce the problem.

This is random, but we do have several logs that contain the information from separate instances (customer and demo) 2018-03-27 17:58:59,046 - runner:searchDomain[170] - 140467375175424 - [ERROR] -- Unable to work with event doc 9ixTKmIB5lInishqeTxy - ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host='localhost', port=9200): Read timed out. (read timeout=10))

Specifications like the version of the project, operating system, or hardware.

This is in v2.0.3 and is not fixed in v2.1.0. Ubuntu 16.04 AWS server(s).

https://github.com/PaloAltoNetworks/safe-networking-sp/issues/89

zube[bot] commented 5 years ago

sdndude said: This started again in v3.5 on a larger scale. This will be fixed as part of SFNv4.0 There are several places where this will be put into a try/except block and will be documented in the commit message as to which areas will be fixed.