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
(this message was edited after @repeatedly comment but the issue is still valid)
Describe the bug
The doc states that when using multi process workers and file buffers, path in the <buffer> section should be omitted in favour of root_dir in the <system> section and @id in the output section.
We tried to do it with a <buffer> section for the out_elasticsearch plugin like so:
and we got the following error when starting Fluentd:
2021-10-21 12:19:53 +0000 [error]: config error file="/etc/td-agent/td-agent.conf" error_class=Fluent::ConfigError error="buffer path is not configured. specify 'path' in <buffer>"
EDIT: as @repeatedly said, @id should go in the output configuration and not in the <buffer> configuration. So we tried this as well, and then Fluentd crashes without any error message (even with log_level trace):
Finally, we did the following, and not only it worked, but it also automatically created subfolders /var/lib/td-agent/worker0 and /var/lib/td-agent/worker1, which suggests that what the doc states is useless/outdated:
(this message was edited after @repeatedly comment but the issue is still valid)
Describe the bug
The doc states that when using multi process workers and file buffers,
path
in the<buffer>
section should be omitted in favour ofroot_dir
in the<system>
section and@id
in the output section.We tried to do it with a
<buffer>
section for theout_elasticsearch
plugin like so:and we got the following error when starting Fluentd:
EDIT: as @repeatedly said,
@id
should go in the output configuration and not in the<buffer>
configuration. So we tried this as well, and then Fluentd crashes without any error message (even withlog_level trace
):Finally we tried to put the
@id
in our<match>
block directly (not in<store>
), and we get the following:Finally, we did the following, and not only it worked, but it also automatically created subfolders
/var/lib/td-agent/worker0
and/var/lib/td-agent/worker1
, which suggests that what the doc states is useless/outdated:Link to the problematic documentation
https://docs.fluentd.org/deployment/multi-process-workers
Expected explanation
Not sure what is the right combination of settings, but clearly the current doc produces an error.
Additional context
No response
The text was updated successfully, but these errors were encountered: