Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
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
53 changes: 53 additions & 0 deletions content/blog/20260213_fluentd-v1.19.2-has-been-released.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# Fluentd v1.19.2 has been released

Hi users!

We have released v1.19.2 on 2026-02-13.
ChangeLog is [here](https://github.com/fluent/fluentd/blob/v1.19/CHANGELOG.md#release-v1192---20260213).

This release is a maintenance release of v1.19 series.

This release will be bundled for upcoming `fluent-package` LTS version v6.0.2!

## Bug Fixes

### Fixed duplicate configuration file loading in `config_include_dir`

Since Fluentd v1.19.0, the configuration files under`/etc/fluent/conf.d` were
changed to load automatically.

This feature was introduced to load builtin plugins and designed to work well with fluent-package.
But, as a side effect, there is a case that duplicated configuration files are
loaded if user already configured to include from `/etc/fluent/conf.d`.

In that case, it causes startup failures. Thus, user need to disable with `config_include_dir ""` explicitly as a workaround.

In this release, not to raise startup failure, we fixed duplicate configured file loading in `config_include_dir`.

### `in_tail`: fixed error when files without read permission are included in glob patterns

In the previous versions, if you enabled Linux capability feature with Fluentd,
there is a case that it causes an error.

It was caused when accessing uninitialized instance variable.

### `out_forward`: added timeout to prevent infinite loop under unstable network connection

In unstable network environments with proxy components,
if connection drops during handshake after TLS establishment, Fluentd gets stuck in infinite loop causing logs to stop being flushed.

In this release, fixed to uses existing [`hard_timeout`](https://docs.fluentd.org/output/forward#hard_timeout) configuration to break the loop,
then disable problematic nodes, and maintain log flow through healthy nodes.

This fixes improves stability of Fluentd.

Enjoy logging!

### Follow us on X

We have been posting information about Fluentd in Japanese on [@fluentd_jp](https://x.com/fluentd_jp).
We would appreciate it if you followed the X account.


TAG: Fluentd Announcement
AUTHOR: clearcode
3 changes: 2 additions & 1 deletion content/blog/tag/announcement
Original file line number Diff line number Diff line change
Expand Up @@ -157,4 +157,5 @@
/blog/20251111_fluent-package-v6.0.1-has-been-released
/blog/20251209_fluentd-v1.16.11-has-been-released
/blog/20251219_fluent-package-v5.0.9-has-been-released
/blog/20251225_schedule-for-fluent-package-5-eol
/blog/20251225_schedule-for-fluent-package-5-eol
/blog/20260213_fluentd-v1.19.2-has-been-released
3 changes: 2 additions & 1 deletion content/blog/tag/fluentd
Original file line number Diff line number Diff line change
Expand Up @@ -166,4 +166,5 @@
/blog/20251111_fluent-package-v6.0.1-has-been-released
/blog/20251209_fluentd-v1.16.11-has-been-released
/blog/20251219_fluent-package-v5.0.9-has-been-released
/blog/20251225_schedule-for-fluent-package-5-eol
/blog/20251225_schedule-for-fluent-package-5-eol
/blog/20260213_fluentd-v1.19.2-has-been-released