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

in_tail: follow symlink target change #1118

Open
bmalynovytch opened this issue Feb 18, 2019 · 1 comment

Comments

@bmalynovytch
Copy link

commented Feb 18, 2019

Bug Report

Summary
in_tail doesn't follow target symlink changes

To Reproduce

  • Configure INPUT:
[INPUT]
    Name        tail
    Path        /opt/my_app/releases/current/var/log/exceptions.log
  • Configure /opt/my_app/releases/current to be a symlink of /opt/my_app/releases/v1.2.3
  • Start agent
  • Rotate symlink to point to somewhere else (but still valid target) /opt/my_app/releases/v1.2.4
  • No more logs will be processed as file descriptor still points to initial target of symlink

Expected behavior
in_tail should probe regularly (or listen for event) to check if rotation occurred and reload it's FD to point to the right file.

Your Environment

  • Version used: Fluent Bit v1.0.4
  • Configuration: N/A
  • Server type and version: N/A
  • Operating System and version: Linux Ubuntu 16.04
  • Filters and plugins: N/A

Additional context
Using symlinks to handle running version of an application with its logs stored in a subfolder prevents the log collection to continue working after release a new version without restarting agent, which could cause privilege troubles as the releasing user may not have enough privileges to trigger a restart of the agent.

@wulfgar93

This comment has been minimized.

Copy link

commented Aug 12, 2019

Hello! Got the same issue with 1.2.2 on CentOS 7. Is there any chance to fix this?

As workaround I use cron for restart td-agent-bit every 15 minutes...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.