Skip to content
New issue

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

out_forest stalls on Ruby-2.0.0-p353 #14

Closed
kiyoto opened this issue Apr 20, 2014 · 5 comments
Closed

out_forest stalls on Ruby-2.0.0-p353 #14

kiyoto opened this issue Apr 20, 2014 · 5 comments

Comments

@kiyoto
Copy link
Contributor

kiyoto commented Apr 20, 2014

Environment

  • Ubuntu precise 64-bit (inside Docker container)
  • Ruby-2.0.0-p353

Steps to reproduce

Configuration

$ cat fluent.conf
<source>
  type forward
</source>

<match nodelog.*>
  type forest
  subtype file
  <template>
    path /home/fluentd/test/nodelog.__TAG__
    flush_interval 3s
  </template>
</match>

Command

$ fluentd -c fluent.conf --daemon pid.log -o debug.log -vv
$ echo '{"hello":"world"}' | fluent-cat nodelog.hogehoge

(...and the file buffer never gets created UPDATE minor edits to make the above commands correct)

It looks like it stalls here (not 100% sure)

Caveat

The above configuration worked with ruby 2.2.0dev (2014-04-20 trunk 45641) [x86_64-linux]

@kiyoto kiyoto changed the title out_forest stalled on Ruby-2.0.0-p353 out_forest stalls on Ruby-2.0.0-p353 Apr 20, 2014
@tagomoris
Copy link
Owner

Please check this list below.

  • With ruby 2.1.1?
  • With buffered_stdout? (fluent-plugin-buffered-stdout)
<match nodelog.*>
  type forest
  subtype buffered_stdout
  <template>
    buf_type file
    buffer_path /home/fluentd/test/stdout_buffer.__TAG__
    flush_interval 3s
  </template>
</match>

@kiyoto
Copy link
Contributor Author

kiyoto commented Apr 20, 2014

  • With 2.0.0-p353, it also stalled (no "test/..." directory created) with buffered_stdout.
  • With 2.1.1-p76, the original configuration worked (did NOT stall).

@tagomoris
Copy link
Owner

Thanks! I'll try to reproduce it later.

@tagomoris
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants