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.

Sign up for GitHub

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

Jump to bottom

meta-mimir-ruler-for-dashboards crashes on startup #148

Open
wesbrownfavor opened this issue Aug 20, 2024 · 1 comment · May be fixed by #154
Open

meta-mimir-ruler-for-dashboards crashes on startup #148

wesbrownfavor opened this issue Aug 20, 2024 · 1 comment · May be fixed by #154

Comments

@wesbrownfavor
Copy link

First off, wow configuring this has been a experience. Secondly I have most of the kinks worked out except that when the meta-mimir-ruler-for-dashboards pod starts up it immediately fails with the following error:

ts=2024-08-20T21:51:06.65869097Z caller=mimir.go:800 level=info msg="Application stopped"

ts=2024-08-20T21:51:06.658757648Z caller=log.go:65 level=error msg="error running application" err="failed services\ngithub.com/grafana/mimir/pkg/mimir.(*Mimir).Run\n\t/__w/mimir/mimir/pkg/mimir/mimir.go:854\nmain.main\n\t/__w/mimir/mimir/cmd/mimir/main.go:215\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1598"

I am referencing this chart via a dependency on my main chart and here is my config. Maybe I am missing something that needs to be configured.

meta-monitoring:

  fullnameOverride: meta
  nameOverride: meta

  namespacesToMonitor:
  - loki

  loki:
    fullnameOverride: loki
    nameOverride: loki
    loki:
      structuredConfig:
        common:
          storage:
            s3:
              endpoint: "minio.meta.svc:9000"

  tempo-distributed:
    fullnameOverride: tempo
    nameOverride: tempo
    tempo:
      structuredConfig:
        storage:
          trace:
            backend: s3
            s3:
              endpoint: "minio.meta.svc:9000"

  mimir-distributed:
    fullnameOverride: meta-mimir
    nameOverride: meta-mimir
    mimir:
      structuredConfig:
        common:
          storage:
            s3:
              endpoint: "minio.meta.svc:9000"

  alloy:
    fullnameOverride: alloy
    nameOverride: alloy

  minio:
    fullnameOverride: minio
    nameOverride: minio
    postJob:
      annotations:
        argocd.argoproj.io/hook: Sync

  grafana:
    ingress:
      enabled: false

  cloud:
    logs:
      enabled: false
    metrics:
      enabled: false
    traces:
      enabled: false

  local:
    grafana:
      enabled: true
    logs:
      enabled: true
    metrics:
      enabled: true
    traces:
      enabled: true
    minio:
      enabled: true
@tchabit
Copy link

tchabit commented Sep 2, 2024 •
edited
Loading

Hi @wesbrownfavor,

I had an issue with this pod aswell, but it was due to a volume bad reference, if your reference and project's name arent the same.
Mine were meta & meta-monitoring, therefore configmaps used by most of the mimir pods are 'project'-mimir-config & 'project'-mimir-runtime, while the deployment configuration for the ruler pod is 'namespace'-mimir-config & 'namespace'-mimir-runtime.

@andrejshapal andrejshapal linked a pull request Sep 23, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Align resources names within chart andrejshapal/meta-monitoring-chart
2 participants
@wesbrownfavor @tchabit