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.

Sign up for GitHub

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

[DOC] Add firewall as possible troubleshooting issue #21743

Merged
merged 6 commits into from
Oct 21, 2020
Merged

[DOC] Add firewall as possible troubleshooting issue #21743

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c9bd1bd
[DOC] Add firewall as possible troubleshooting issue
lucabelluccini Oct 13, 2020
42c5ea4
Update shared-faq.asciidoc
lucabelluccini Oct 13, 2020
a59a050
Update libbeat/docs/shared-faq.asciidoc
lucabelluccini Oct 16, 2020
b01cb73
Update libbeat/docs/shared-faq.asciidoc
lucabelluccini Oct 16, 2020
faed80f
Update libbeat/docs/shared-faq.asciidoc
lucabelluccini Oct 16, 2020
5cdaf5b
Make title more descriptive
dedemorton Oct 17, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions libbeat/docs/shared-faq.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,27 @@ connect to the Lumberjack input plugin. To learn how to install and update
plugins, see {logstash-ref}/working-with-plugins.html[Working with plugins].
endif::[]

ifndef::no-output-logstash[]
[[disconnections-problem]]
=== {beatname_uc} reports connections being reset by {ls}
dedemorton marked this conversation as resolved.
Show resolved Hide resolved
dedemorton marked this conversation as resolved.
Show resolved Hide resolved

{beatname_uc} requires a persistent TCP connection to {ls}. If a firewall interferes
with the connection, you might see errors like this:

[source,shell]
----------------------------------------------------------------------
Failed to publish events caused by: write tcp ... write: connection reset by peer
----------------------------------------------------------------------


To solve the problem:

* make sure the firewall is not closing connections between {beatname_uc} and {ls}, or
* set the `ttl` value in the <<logstash-output,{ls} output>> to a value that's
lower than the maximum time allowed by the firewall, and set `pipelining` to 0
(pipelining cannot be enabled when `ttl` is used).
endif::[]

ifndef::no-output-logstash[]
[[metadata-missing]]
=== @metadata is missing in {ls}
Expand Down