NEW ISSUE : unexpected event 'mapping-start-event' (9) in state 'plugin-values' (17)

[P-pri]

Bug Report

Describe the bug

To Reproduce

• Rubular link if applicable:
• Example log message if applicable:

[2024/06/20 15:30:57] [error] [config] forward: unknown configuration property 'tls_verify'. The following properties are allowed: time_as_integer, retain_metadata_in_forward_mode, shared_key, self_hostname, empty_shared_key, send_options, require_ack_response, username, password, unix_path, upstream, tag, compress, fluentd_compat, and add_option.
[2024/06/20 15:30:57] [ help] try the command: /usr/local/bin/stsfaoci/fluent-bit -o forward -h

[2024/06/20 15:30:57] [error] [engine] output initialization failed


**Your Environment**
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used: Linux Server 7.8
* Configuration: 
* Environment name and version (e.g. Kubernetes? What version?): 
* Server type and version: VM
* Operating System and version: Linux 4.14.35-2025.400.9.el7uek.x86_64
* Filters and plugins:
      Kernel: Linux 4.14.35-2025.400.9.el7uek.x86_64
      Architecture: x86-64


_**Complete Error **_  

Fluent Bit v2.2.1
* Copyright (C) 2015-2023 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

       \ || /
       = ** =
        /__\ 
       /____\
      /______\
     /________\
    /__________\
   /____________\
  /__Fluent Bit__\
 /__|__v2.2.1_|___\
/___\_________/____\
        |||
        |||
       =====

[2024/06/20 14:41:10] [error] [/tmp/src/fluent-bit.git/src/config_format/flb_cf_yaml.c:1996 errno=2] No such file or directory
[2024/06/20 14:41:10] [error] [config] including file '/usr/local/bin/sts-faoci-fluent-bit/faoci/input.yaml' at /usr/local/etc/sts-faoci-fluent-bit/env.yaml:4
[2024/06/20 14:41:10] [error] yaml error
[2024/06/20 14:41:10] [error] configuration file contains errors, aborting.


_**Just help me in figuring out this bug.**_ 

[mattmooree]

@P-pri please share the contents for your fluent-bit config.

[patrick-stephens]

It looks like you're using YAML in quite an old version of Fluent Bit, I would step up to the latest to verify it is still an issue. The other thing it could be is unable to find an include file.

[edsiper]

 [config] forward: unknown configuration property 'tls_verify'

try tls.verify (with a dot)

[P-pri]

Thanks @patrick-stephens , I found out the issue it is pathing .

[P-pri]

Hi @edsiper , @patrick-stephens ,

Facing some other issue : [config] YAML error found in file "/usr/local/bin/sts-faoci-fluent-bit/faoci/ohs/ohs_input.yaml", line 39, column 10: unexpected event 'mapping-start-event' (9) in state 'plugin-values' (17).

Complete log : [root@fbim-dev1lldrdz9n-ohs1 sts-faoci-fluent-bit]# /usr/local/bin/stsfaoci/fluent-bit -c /usr/local/etc/sts-faoci-fluent-bit/fluent-bit.yaml Fluent Bit v2.2.1

• Copyright (C) 2015-2023 The Fluent Bit Authors

• Fluent Bit is a CNCF sub-project under the umbrella of Fluentd

• https://fluentbit.io

   \ || /
   = ** =
    /__\ 
   /____\
  /______\
  

  /
  /
  /
  /Fluent Bit
  /|v2.2.1|
  /________/____
  ||| ||| =====

[2024/06/25 13:54:11] [error] [config] YAML error found in file "/usr/local/bin/sts-faoci-fluent-bit/faoci/ohs/ohs_input.yaml", line 39, column 10: unexpected event 'mapping-start-event' (9) in state 'plugin-values' (17). [2024/06/25 13:54:11] [error] yaml error [2024/06/25 13:54:11] [error] configuration file contains errors, aborting.

[patrick-stephens]

Please step up version, 2.2.1 is very old and has different YAML syntax.

[P-pri]

How do we do it @patrick-stephens , steps please !

[P-pri]

[root@fbim-dev1lldrd~]# fluent-bit --version Fluent Bit v1.6.10 [root@fbim-dev1lldrd ~]# The version which is already present in my machine

[patrick-stephens]

Installation guides are here: https://docs.fluentbit.io/manual/installation/getting-started-with-fluent-bit

If it's Linux then the repositories can upgrade it for you like any other package.

1.6 will definitely not work for YAML :)

[github-actions[bot]]

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[bot]]

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