@Include symblink config file is not supported

[zw963]

Reproduce

My config file is organized like following:

[root@10-8-130-243 td-agent-bit]# pwd
/etc/td-agent-bit
[root@10-8-130-243 td-agent-bit]# ls *.conf -alh
lrwxrwxrwx 1 root root 120 Jul 12 21:40 hardware_monitor.conf -> /home/deployer/apps/test_fluentd/test_fluentd_app2/current/config/containers/fluentbit/config/hardware_monitor_app2.conf
lrwxrwxrwx 1 root root 111 Jul 12 21:40 parsers.conf -> /home/deployer/apps/test_fluentd/test_fluentd_app2/current/config/containers/fluentbit/config/parsers_app2.conf
lrwxrwxrwx 1 root root 111 Jul 12 21:40 plugins.conf -> /home/deployer/apps/test_fluentd/test_fluentd_app2/current/config/containers/fluentbit/config/plugins_app2.conf
lrwxrwxrwx 1 root root 116 Jul 12 21:40 td-agent-bit.conf -> /home/deployer/apps/test_fluentd/test_fluentd_app2/current/config/containers/fluentbit/config/td-agent-bit_app2.conf
[root@10-8-130-243 td-agent-bit]# 

Symlink is not broken:

[root@10-8-130-243 td-agent-bit]# cat hardware_monitor.conf 
[INPUT]
    Name cpu
    Tag  stats.cpu.app2
    # Interval Sec
    # ====
    # Read interval (sec) Default: 1
    Interval_Sec 1

[INPUT]
    Name disk
    Tag  stats.disk.app2

[INPUT]
    Name mem
    Tag  stats.mem.app2

[INPUT]
    Name          netif
    Tag           stats.net.app2
    Interface     eth0

[OUTPUT]
    Name  influxdb
    Match stats.*
    Database stats[root@10-8-130-243 td-agent-bit]# 

When use include in main config:

@INCLUDE hardware_monitor.conf

Get following error in systemd (append a extra / in path config//hardware_monitor.conf)

Jul 12 21:58:30 10-8-130-243 td-agent-bit[14582]: [2019/07/12 21:58:30] [Warning] [config] I cannot open /home/deployer/apps/test_fluentd/test_fluentd_app2/releases/20190712133948/config/containers/fluentbit/config//hardware_monitor.conf file
Jul 12 21:58:30 10-8-130-243 td-agent-bit[14582]: Error: Configuration file contain errors. Aborting

i can reporoduce manually.

[root@10-8-130-243 /]# cd /home
[root@10-8-130-243 home]# td-agent-bit -c /etc/td-agent-bit/td-agent-bit.conf
Fluent Bit v1.2.1
Copyright (C) Treasure Data

[2019/07/12 21:59:07] [Warning] [config] I cannot open /home/deployer/apps/test_fluentd/test_fluentd_app2/releases/20190712133948/config/containers/fluentbit/config//hardware_monitor.conf file
Error: Configuration file contain errors. Aborting

[edsiper]

I tried to reproduce without success:

$ ls -l
total 4
-rw-r--r-- 1 edsiper edsiper 19 jul 23 11:31 fluent-bit.conf
lrwxrwxrwx 1 edsiper edsiper 42 jul 23 11:31 link.conf -> /tmp/data/conf/issues/1436/fluent-bit.conf

$ cat fluent-bit.conf 
@INCLUDE link.conf

$ cat link.conf 
[SERVICE]
    Flush        5
    Daemon       Off
    Log_Level    info

[INPUT]
    Name cpu
    Tag  cpu.local
    Interval_Sec 1

[OUTPUT]
    Name  stdout
    Match *

$ ../../build/bin/fluent-bit -c fluent-bit.conf 
Fluent Bit v1.3.0
Copyright (C) Treasure Data

[2019/07/23 11:33:05] [ info] [storage] initializing...
[2019/07/23 11:33:05] [ info] [storage] in-memory
[2019/07/23 11:33:05] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2019/07/23 11:33:05] [ info] [engine] started (pid=26005)
[2019/07/23 11:33:05] [ info] [sp] stream processor started
^C[engine] caught signal (SIGINT)
[2019/07/23 11:33:06] [ info] [input] pausing cpu.0

[zw963]

Thank you for reply.

$ cat link.conf 

Is link.conf is a symblink to /tmp/data/conf/issues/1436/link.conf too?

BTW: i am copy all config into /etc, so there is no issue now.

[edsiper]

yes, it's a symbolic link, no issues here.

[zw963]

For my case, fluent-bit.conf is a symblink too.

i consider config @INCLUDE link.conf in symblink version fluent-bit.conf is not same behavior as normal version.

Thank.

[krancour]

I stumbled into replicating this issue-- but, oddly, only in a Windows container. My fluent-bit.conf can be a symlink and it's no problem, but any of the files it includes cannot be. Everywhere else, I've observed this working as I expected.

[github-actions]

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.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.