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

[Bug] Loki service fails to start after installation on aarch64 #15421

Open
sunwupark opened this issue Dec 15, 2024 · 2 comments · May be fixed by #15535
Open

[Bug] Loki service fails to start after installation on aarch64 #15421

sunwupark opened this issue Dec 15, 2024 · 2 comments · May be fixed by #15535
Labels
type/bug Somehing is not working as expected

Comments

@sunwupark
Copy link

sunwupark commented Dec 15, 2024

Describe the bug
There is an error when installing Loki as mentioned in the official documentation using apt. After following the installation steps, the Loki service fails to start.

bash apt-get update apt-get install loki promtail

When checking the Loki service status, it reports a failure:

loki.service - Loki service
Loaded: loaded (/etc/systemd/system/loki.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2024-12-15 15:12:35 KST; 651ms ago
Process: 1090824 ExecStart=/usr/bin/loki -config.file /etc/loki/config.yml (code=exited, status=1/FAILURE)
Main PID: 1090824 (code=exited, status=1/FAILURE)
CPU: 97ms

To Reproduce

Steps to reproduce the behavior:

  1. Run the following commands:

apt-get update apt-get install loki promtail

  1. Check the status of the Loki service:

sudo systemctl status loki

  1. Observe the error:

loki.service - Loki service
Loaded: loaded (/etc/systemd/system/loki.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since ...
Process: 1090824 ExecStart=/usr/bin/loki -config.file /etc/loki/config.yml (code=exited, status=1/FAILURE)
Main PID: 1090824 (code=exited, status=1/FAILURE)

Expected behavior

The Loki service should start successfully and its status should indicate that it is active and running.

For example:

loki.service - Loki service
Loaded: loaded (/etc/systemd/system/loki.service; enabled; preset: enabled)
Active: active (running) since Sun 2024-12-15 15:27:59 KST; 23s ago
Main PID: 1094130 (loki)
Tasks: 10 (limit: 9252)
CPU: 230ms
CGroup: /system.slice/loki.service
└─1094130 /usr/bin/loki -config.file /etc/loki/config.yml

Environment

  • Infrastructure: Raspberry pi 5
  • Operating System: Debian GNU/Linux 12 (bookworm)

Screenshots or Logs
Image

Additional Context
- The service fails even when attempting to run Loki manually:
/usr/bin/loki -config.file=/etc/loki/config.yml
- The error log reports:

failed parsing config: /etc/loki/config.yml: yaml: unmarshal errors:
line 41: field enabled not found in type aggregation.Config

Please let me know if I need to provide additional details or configurations!

@JStickler JStickler added the type/bug Somehing is not working as expected label Dec 16, 2024
@pbjhelmert
Copy link

I can reproduce but I can also get around the error by removing line 41 in the default configuration (enabled: true under pattern_ingester.metric_aggregation). Looks like that field was removed with c1fde26, removed from the configuration with #15059, then the configuration was fixed again with #15302. And fortunately it looks like this was backported to 3.3 and will be in 3.3.2 with #15326.

@lvqq
Copy link

lvqq commented Dec 21, 2024

Same error with 3.3.2 after installing via apt on Debian GNU/Linux 10. It works after remove the pattern_ingester.metric_aggregation.enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Somehing is not working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants