Scheduled support lifecycle announcement about Fluent Package v7

Hi users!

We had launched fluent-package v6 series last year, recently shipped v6.0.4 in LTS release channel.

In this blog article, we explains the planned next major updates - v7.0.0.

When the next LTS (Long Term Support) version available?

In short, we will ship fluent-package v7 in Aug, 2027.

We keeps two release channels as follows:

  • Normal release
  • LTS (Long Term Support)

Here is the difference of these channels.

  • Normal release (7.x series)
    • Recommended for early adopters (eager to try new features of Fluentd)
    • Rapid release development (planned semi-annually releases, but it may vary. Regular releases are not guaranteed.)
    • Fluentd will be upgraded occasionally
      • Minor upgrade will be applied. e.g. 1.20 => 1.21 and so on.
      • e.g. v7.0.1 (Fluentd v1.20.1), v7.0.2 (Fluentd v1.20.2), ... v7.1.0 (Fluentd v1.21.0)
    • The only latest version will be supported
  • LTS (Long Term Support, 7.0.x series)
    • Recommended for enterprise services
    • Security and bug fix release only
    • Fluentd will be upgraded only in the teeny version and will stick to 1.20.x series. (T.B.D.)
      • Thus, the version number will be 7.0.x. (7.1 series will not be shipped for LTS channel)
      • e.g. v7.0.1 (Fluentd v1.20.1), v7.0.2 (Fluentd v1.20.2), v7.0.3 (Fluentd v1.20.3) ... v7.0.x (Fluentd v1.20.x) and so on.
    • Next major version will be fluent-package v8.0.0, and will be shipped in 2029 (T.B.D.).

As for fluent-package v7,

  • fluent-package v6 LTS will be supported until Dec, 2027.
    • We expect users upgrade from v6 to v7 during the grace period.
  • Until 7.1.0 is released, normal release channel and LTS channel are the same package.
  • Upgrade from v4 or older version is not supported. Upgrade to v5 or v6 first, then upgrade it to v7.

Current releases and future plans:

Release Version Release Date End of life
v6.0.x (LTS) Aug, 2025 Dec, 2027
v7.0.0 (LTS) Aug, 2027 Dec, 2029 (T.B.D.)
v8.0.0 (LTS) Aug, 2029 (T.B.D.) T.B.D.

Happy logging!

Read More

fluent-package v6.0.3 has been released

Hi users!

We have released fluent-package v6.0.3 on 2026-03-27. Fluent Package is a stable distribution package of Fluentd. (successor of td-agent)

This is a maintenance release of v6.0.x LTS series.

Fluent Package v6.0.3

Fluent Package v6.0.3 includes the following improvements:

  • Fixed a severe memory leak issue in the bundled cool.io v1.9.3 under specific conditions
  • Updated bundled Ruby to 3.4.9
  • Updated bundled Nokogiri to v1.19.2 (Windows only) for vulnerability fix

This article explains the changes in Fluent Package v6.0.3.

Changes

Fixed a severe memory leak issue in the bundled cool.io v1.9.3

In fluent-package v6.0.2, a critical issue was discovered where memory usage continuously increases over time. This release completely resolves this problem.

  • Affected Environments
    • This issue occurs in environments where TCP connections are frequently connected and disconnected.
    • It is easily reproducible when using the out_forward plugin with the keepalive false setting (which is the default value).
  • Root cause
    • The asynchronous I/O library cool.io (v1.9.2 and v1.9.3) bundled in fluent-package v6.0.2 had a bug in its detachment process.
    • When a TCP connection was detached, the internal watcher objects were not properly garbage collected, leaving "garbage" data accumulated in the memory.
  • Resolution
    • We have released cool.io v1.9.4 which fixes this bug, and it is now bundled by default in fluent-package v6.0.3.

If operated for a long period, this memory leak will exhaust system memory resources, eventually causing the Fluentd process to be terminated unexpectedly by the OOM (Out of Memory) Killer. We strongly recommend users who are using out_forward on v6.0.2 to update to this version immediately.

Note: Users on fluent-package v6.0.1 or earlier are not affected by this specific issue.

Updated bundled Ruby to 3.4.9

Ruby 3.4.9 includes multiple bug and security fixes. Specifically, it addresses the following vulnerability:

For details, please see the Ruby 3.4.9 release notes.

Updated bundled Nokogiri (Windows only) for vulnerability fix

We have updated the bundled Nokogiri from v1.18.10 to v1.19.2 for the Windows version to address the following vulnerability:

Download

Please visit the download page.

Announcement

About next LTS schedule

We plan to release the next LTS version of fluent-package v6.0.4 at June 2026. The content of updates are still TBD.

Follow us on X

We have been posting information about Fluentd in Japanese on @fluentd_jp. We would appreciate it if you followed the X account.

Read More

fluent-package v6.0.2 has been released

Hi users!

We have released fluent-package v6.0.2 on 2026-02-27. Fluent Package is a stable distribution package of Fluentd. (successor of td-agent)

This is a maintenance release of v6.0.x LTS series.

Fluent Package v6.0.2

Fluent Package v6.0.2 includes the following improvements:

  • Updated bundled Ruby to 3.4.8
  • Updated bundled Fluentd from v1.19.1 to v1.19.2
  • rpm: fixed update error if working directory was removed
  • Fixed CVEs about bundled gems: CVE-2025-14762, CVE-2026-25765
    • When using with fluentd, usually it will not be affected by these vulnerability, but bundled fixed versions with keeping compatibility.
  • msi: fixed installation rollback issue when executing maintenance script

This article explains the changes in Fluent Package v6.0.2.

Changes

Updated bundled Ruby to 3.4.8

Ruby 3.4.8 includes multiple bug and security fixes. For details, please see the Ruby 3.4.8 release notes.

Updated bundled Fluentd from v1.19.1 to v1.19.2

Fluentd v1.19.2 includes the following fixes:

  • Fixed duplicate configuration file loading in config_include_dir
  • in_tail: fixed error when files without read permission are included in glob patterns
  • out_forward: added timeout to prevent infinite loop under unstable network connection
  • gem: use latest net-http to solve IPv6 addr error
  • warn when backed-up conf file will be included

For details, please see the Fluentd v1.19.2 has been released.

rpm: fixed update error if working directory was removed

In this release, it was fixed update error if temporary working directory was removed.

In the previous versions, if temporary working directory was removed by tmpfiles.d, there was a case that updating to v6 (up to v6.0.1) causes fatal error while rpm processes transaction.

Now, with changing temporary working directory handling, it was fixed in v6.0.2.

msi: fixed installation rollback issue when executing maintenance script

Since v6.0.0, installation maintenance script (powershell) was partially introduced for Windows. But in some environments, there is a case that the execution of powershell was prohibited in your policy. In such a case, installation process will be failed unexpectedly.

In this release, added fallback not to terminate installation process accidentally.

Download

Please visit the download page.

Announcement

About next LTS schedule

We plan to release the next LTS version of fluent-package v6.0.3 at June 2026. The content of updates are still TBD.

Follow us on X

We have been posting information about Fluentd in Japanese on @fluentd_jp. We would appreciate it if you followed the X account.

Read More

Fluentd v1.19.2 has been released

Hi users!

We have released v1.19.2 on 2026-02-13. ChangeLog is here.

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 configuration to break the loop, then disable problematic nodes, and maintain log flow through healthy nodes.

This fixes improves stability of Fluentd.

gem: use latest net-http to solve IPv6 addr error

net-http gem had a bug in handling IPv6 addresses, and updating the uri gem would trigger strict checking, thus causing errors.

It was affected when you installed via gem command.

warn when backed-up conf file will be included

There is a case that unintentionally backed-up conf file will be loaded by wild card @include.

It will help to detect such a careless mistakes by warning.

For example, if you include configuration file by @include conf/*.conf, and there are unintentionally backed-up file exists (conf/dummy.bak.conf), usually it causes startup failures.

In this release, it detects such a case as a warning.

$ fluentd -c wildcard_include.conf --dry-run
2026-02-12 17:41:39 +0900 [info]: init supervisor logger path=nil rotate_age=nil rotate_size=nil
2026-02-12 17:41:39 +0900 [warn]: There is a possibility that '@include conf/*.conf' includes duplicated backed-up config file such as <dummy.bak.conf>
2026-02-12 17:41:39 +0900 [info]: parsing config file is succeeded path="wildcard_include.conf"
2026-02-12 17:41:39 +0900 [info]: configuration include directory is disabled
2026-02-12 17:41:39 +0900 [info]: gem 'fluentd' version '1.19.0'
2026-02-12 17:41:39 +0900 [info]: starting fluentd-1.19.0 as dry run mode ruby="3.4.8"
2026-02-12 17:41:39 +0900 [info]: using configuration file: <ROOT>
  <system>
    config_include_dir ""
  </system>
  <source>
    @type forward
  </source>
  <source>
    @type forward
  </source>
</ROOT>
2026-02-12 17:41:39 +0900 [info]: finished dry run mode

Enjoy logging!

Follow us on X

We have been posting information about Fluentd in Japanese on @fluentd_jp. We would appreciate it if you followed the X account.

Read More

Drop schedule announcement about EOL of Fluent Package (fluent-package) 5

Hi users and developers!

As already planned before, we announce the dropping schedule for Fluent Package 5 (LTS) development.

About Fluent Package v5

Since fluent-package 5.0.0 was released in 2023, fluent-package 5 has been maintained for a long time.

As new major version of fluent-package 6 was released in August 2025, we decided to stop maintaining fluent-package 5 in Dec 31, 2025.

LTS version of fluent-package v6 will be planned support until Dec, 2027. It will meet for your enterprise services.

Scheduled end of life - Dec 2025

As you know, already stepping down maintenance activity, new minor update for fluent-package 5 will not be shipped anymore. fluent-package v5.0.9 should be the last release of this series, it was shipped in Dec 19, 2025.

Thus, we recommend using fluent-package v6 for new deployment :)

How to migrate to Fluent Package v6

There is a good article to do it.

Follow the above instructions.

Follow us on X

We have been posting information about Fluentd in Japanese on @fluentd_jp. We would appreciate it if you followed the X account.

Read More


About Fluentd

Fluentd is an open source data collector to simplify log management.

Learn

Want to learn the basics of Fluentd? Check out these pages.

Ask the Community

Couldn't find enough information? Let's ask the community!

Ask the Experts

You need commercial-grade support from Fluentd committers and experts?

Follow Us!