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

Promtail journal scraper fails silently for permissions issues #7836

Closed
timw6n opened this issue Dec 2, 2022 · 2 comments · Fixed by #16027
Closed

Promtail journal scraper fails silently for permissions issues #7836

timw6n opened this issue Dec 2, 2022 · 2 comments · Fixed by #16027

Comments

@timw6n
Copy link

timw6n commented Dec 2, 2022

When configuring promtail to scrape journal logs, it appears to fail silently if filesystem permissions prevent reading the configured journal directory. E.g. because the promtail user had not been added to the systemd-journal group.

It would be helpful in troubleshooting if an error message were logged in this case.

      scrape_configs:
        - job_name: journal
          journal:
            json: false
            max_age: 12h
            path: /var/log/journal
            labels:
              job: systemd-journal
          relabel_configs:
            # etc
$ promtail --version
promtail, version HEAD-1b627d8 (branch: HEAD, revision: 1b627d880)
  build user:       root@079d888186e6
  build date:       2022-11-10T23:52:44Z
  go version:       go1.19.2
  platform:         linux/amd64

(This is the using latest package in the official repository, on Ubuntu 20.04.)

@skibbipl
Copy link

skibbipl commented Jan 4, 2025

I was debugging why logs weren't processed on my machine and stumbled on this bug. The issue is still valid in 2025 :(

@axi92
Copy link
Contributor

axi92 commented Jan 30, 2025

What permission is needed for the promtail user to be able to access journal logs?

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

Successfully merging a pull request may close this issue.

3 participants