We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--inline-config -
Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.
fluentd or td-agent version. v1.0.x and v0.14.x
How to confirm it.
Add puts "#{ENV['SERVERENGINE_WORKER_ID'] || 'sup'}: #{@config_data}" between L740 and L741: https://github.com/fluent/fluentd/blob/v1.0.2/lib/fluent/supervisor.rb#L736-L741
puts "#{ENV['SERVERENGINE_WORKER_ID'] || 'sup'}: #{@config_data}"
$ touch empty.conf $ echo abc | bundle exec bin/fluentd -c empty.conf --inline-config - sup: abc 2018-01-15 15:08:42 +0900 [info]: parsing config file is succeeded path="empty.conf" 2018-01-15 15:08:42 +0900 [info]: using configuration file: <ROOT> abc </ROOT> 2018-01-15 15:08:42 +0900 [info]: starting fluentd-1.0.2 pid=36926 ruby="2.4.1" 2018-01-15 15:08:42 +0900 [info]: spawn command to main: cmdline=["/Users/yito/.rbenv/versions/2.4.1/bin/ruby", "-Eascii-8bit:ascii-8bit", "-rbundler/setup", "bin/fluentd", "-c", "empty.conf", "--inline-config", "-", "--under-supervisor"] 0: 2018-01-15 15:08:43 +0900 [info]: gem 'fluentd' version '1.0.2' ...
The text was updated successfully, but these errors were encountered:
#2708 fixed this issue.
Sorry, something went wrong.
No branches or pull requests
Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.
fluentd or td-agent version.
v1.0.x and v0.14.x
How to confirm it.
Add
puts "#{ENV['SERVERENGINE_WORKER_ID'] || 'sup'}: #{@config_data}"
between L740 and L741:https://github.com/fluent/fluentd/blob/v1.0.2/lib/fluent/supervisor.rb#L736-L741
The text was updated successfully, but these errors were encountered: