msg="received error during sdjournal follow" err="received error event: -24"

[wkshare]

Describe the issue err log found, how to fix it?

To Reproduce Steps to reproduce the behavior:

1. Started Loki (SHA or version) loki, version 2.5.0 (branch: HEAD, revision: 2d9d0ee23) build user: root@4779f4b48f3a build date: 2022-04-07T21:50:00Z go version: go1.17.6 platform: linux/amd64

2. Started Promtail (SHA or version) to tail '...' agent, version v0.24.1 (branch: HEAD, revision: 35015aa4) build user: root@4500bb0cda4b build date: 2022-04-14T15:27:31Z go version: go1.17.6 platform: linux/amd64

Expected behavior

Environment: LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: OracleServer Description: Oracle Linux Server release 7.8 Release: 7.8 Linux ech-10-157-130-81 3.10.0-1127.el7.x86_64 #1 SMP Wed Apr 1 10:20:09 PDT 2020 x86_64 x86_64 x86_64 GNU/Linux

Screenshots, Promtail config, or terminal output May 25 21:57:53 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:53.515375963Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:53 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:53.616333419Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:53 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:53.716490798Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:53 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:53.817518732Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:53 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:53.918798663Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:54 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:54.023809994Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:54 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:54.124330729Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:54 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:54.224839418Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24" May 25 21:57:54 ech-10-168-130-22 grafana_agent[3018]: ts=2022-05-25T13:57:54.32670046Z caller=journaltarget.go:187 level=error component=logs logs_config=loki msg="received error during sdjournal follow" err="received error event: -24"

[wkshare]

I have multiple Grafana Agents running on one machine at the same time, using the same configuration, is there impact?：

      - job_name: journal
        journal:
          json: false
          max_age: 12h
          path: /run/log/journal
          labels:
            type: journal
        relabel_configs:
        - source_labels:
          - __journal__systemd_unit
          target_label: systemd_unit
        - source_labels:
          - __journal__hostname
          target_label: nodename
        - source_labels:
          - __journal_syslog_identifier
          target_label: syslog_identifier

[stale[bot]]

Hi! This issue has been automatically marked as stale because it has not had any activity in the past 30 days.

We use a stalebot among other tools to help manage the state of issues in this project. A stalebot can be very useful in closing issues in a number of cases; the most common is closing issues or PRs where the original reporter has not responded.

Stalebots are also emotionless and cruel and can close issues which are still very relevant.

If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.

We regularly sort for closed issues which have a stale label sorted by thumbs up.

We may also:

• Mark issues as revivable if we think it's a valid issue but isn't something we are likely to prioritize in the future (the issue will still remain closed).
• Add a keepalive label to silence the stalebot if the issue is very common/popular/important.

We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task, our sincere apologies if you find yourself at the mercy of the stalebot.

[cstyan]

@wkshare are you still experiencing this issue? if you're using the agent I would suggest opening an issue there