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

Logstash stops consuming input after journald-remote log rotation #21

Open
wraithm opened this issue Jan 31, 2017 · 5 comments
Open

Logstash stops consuming input after journald-remote log rotation #21

wraithm opened this issue Jan 31, 2017 · 5 comments

Comments

@wraithm
Copy link

wraithm commented Jan 31, 2017

I have several journal-upload services sending logs to a central server running journald-remote, where I have logstash consuming the journald output. After the remote logs rotate, logstash stops consuming those remote logs. The sincedb cursor location halts at the end of the rotated file, so when logstash is restarted, it starts consuming the new logs. It would be great if I didn't have to restart logstash every time the remote logs rotate.

  • Version: logstash 2.4.1, up to date logstash-input-journald
  • Operating System: Ubuntu Xenial
  • Config File:
input {
    # local logs
    journald {
        lowercase => true
        seekto => "head"
        thisboot => true
        type => "journald"
    }

    # remote logs
    journald {
        lowercase => true
        seekto => "head"
        thisboot => false
        type => "journald"
        sincedb_path => "/var/lib/logstash/.remote_sincedb_journal"
        path => "/var/log/journal/remote"
    }
}
  • Steps to Reproduce:
  1. Run journald-remote
  2. Use journald input plugin to consume remote logs
  3. Wait for journald-remote logs to rotate
  4. Logstash stops consuming input
@mdunnio
Copy link

mdunnio commented Jan 31, 2017

+1

@MeanderingCode
Copy link

I have what I believe is the same problem. I have not confirmed the timing of when the logs stop processing, however.

I have noticed that they will begin processing again after some time. I am not sure of the trigger for that, either.

Has anyone taken a look at this? Have either of you noticed that processing will resume after a window?

@octopusx
Copy link

octopusx commented Apr 7, 2017

+1

2 similar comments
@vnadgir-ef
Copy link

+1

@vx3r
Copy link

vx3r commented Aug 21, 2018

+1

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

6 participants