Addon fails to start with caller=journaltarget.go:195 msg="unable to follow journal" err="Timeout expired"

[jinnko]

Describe the bug

Have installed the addon v2.2.0 into HassOS 2024.12.5 on a Pi4 and have my own pre-existing loki instance that is confirmed working with other Promtail clients.

Configured the addon URL and left everything else as default. Confirmed connectivity to Loki from the shell on the hass debug SSH port 22222.

In the logs promtail is unable to access the journal with the following error. There are no other errors shown.

level=error ts=2024-12-28T19:41:33.332167958Z caller=journaltarget.go:195 msg="unable to follow journal" err="Timeout expired"

Confirmed via SSH that the env var being passed to promtail is JOURNAL_PATH=/var/log/journal (via /proc/$PID/environ), and confirmed that in the container I can see files at that location.

To Reproduce

Steps to reproduce the behavior:

1. Installed addon as described in the README
2. Configured addon with a URL. Everything else left at defaults.
3. View the logs and see the above error emitted.

Expected behavior

Promtail should tail the logs and ship them to Loki.

Logs

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh

-----------------------------------------------------------
 Add-on: Promtail
 Promtail for Home Assistant
-----------------------------------------------------------
 Add-on version: 2.2.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.12.5
 Home Assistant Supervisor: 2024.12.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
Log level is set to INFO
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/02-set-timezone.sh
[19:38:00] INFO: Configuring timezone
cont-init: info: /etc/cont-init.d/02-set-timezone.sh exited 0
cont-init: info: running /etc/cont-init.d/promtail_setup.sh
[19:38:00] INFO: Setting base config for promtail...
cont-init: info: /etc/cont-init.d/promtail_setup.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun promtail (no readiness notification)
s6-rc: info: service legacy-services successfully started
[19:38:01] INFO: Starting Promtail...
[19:38:01] INFO: Promtail log level set to info
[19:38:01] INFO: Handing over control to Promtail...
level=info ts=2024-12-28T19:38:01.81407717Z caller=server.go:288 http=[::]:9080 grpc=[::]:39489 msg="server listening on addresses"
level=info ts=2024-12-28T19:38:01.814558571Z caller=main.go:121 msg="Starting Promtail" version="(version=2.6.1, branch=HEAD, revision=6bd05c9)"
s6-rc: info: service legacy-services: stopping
[19:41:33] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
level=info ts=2024-12-28T19:41:33.308143582Z caller=signals.go:55 msg="=== received SIGINT/SIGTERM ===\n*** exiting"
level=error ts=2024-12-28T19:41:33.331910534Z caller=journaltarget.go:192 msg="received error during sdjournal follow" err="Timeout expired"
level=error ts=2024-12-28T19:41:33.332167958Z caller=journaltarget.go:195 msg="unable to follow journal" err="Timeout expired"

Environment (please complete the following information):

• Add-on version: 2.2.0
• Supervisor version: 2024.12.0
• Operating system Home Assistant OS 14.1 (aarch64 / raspberrypi4-64)

Additional context

With the watchdog enabled the addon will be restarted and face the same issue.

Without the watchdog, when viewing the logs, Promtail exits and the logs page displays the error Failed to get 39bd2704_promtail logs, Error in input stream

[iUnstable0]

Getting the same error!