Open orgads opened 5 months ago
Not sure I follow the failing to start with two separate path entries, I'd expect it just to report it can't read one - same as if it did not have access for example. Unless it's to do with nesting or something strange.
Are you using two different tail inputs or specifying two paths in a single input?
I tried this:
[INPUT]
Name systemd
Tag systemd
Systemd_Filter _COMM=systemd
Path /run/log/journal
Lowercase On
Strip_Underscores On
DB /fluent-bit/db/cursor1.db
[INPUT]
Name systemd
Tag systemd
Systemd_Filter _COMM=systemd
Path /var/log/journal
Lowercase On
Strip_Underscores On
DB /fluent-bit/db/cursor2.db
and it failed with this error:
[2024/04/16 16:45:11] [ info] [input:systemd:systemd.0] initializing
[2024/04/16 16:45:11] [ info] [input:systemd:systemd.0] storage_strategy='memory' (memory only)
[2024/04/16 16:45:11] [error] [/src/fluent-bit/plugins/in_systemd/systemd_config.c:81 errno=2] No such file or directory
[2024/04/16 16:45:11] [error] [input:systemd:systemd.0] given path /run/log/journal is invalid
[2024/04/16 16:45:11] [error] [input:systemd:systemd.0] cannot initialize
[2024/04/16 16:45:11] [error] failed initialize input systemd.0
[2024/04/16 16:45:11] [error] [engine] input initialization failed
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale
label.
@patrick-stephens ping
Bug Report
Describe the bug If journald logs are stored as
volatile
(/run/log/journal
), systemd input plugin reads the logs correctly.But if
persistent
storage is used (/var/log/journal
), no logs are read.To Reproduce
/var/log/journal
.[OUTPUT] Name stdout Match *