Skip to content
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.

Docker stack service grafana: Can't read alerting provisioning files from directory #521

Open
3 tasks
heldrida opened this issue Apr 24, 2023 · 0 comments
Open
3 tasks

Comments

@heldrida
Copy link
Member

Description

On Docker stack launch, fresh install, fresh VPS launch there's an error "Can't read alerting provisioning files from directory".

Environment

  • Ubuntu 22.04 LTS

Demo

full-node-grafana-1     | logger=migrator t=2023-04-24T10:35:09.253655644Z level=info msg="Executing migration" id="alter table query_history alter column created_by type to bigint"
full-node-grafana-1     | logger=migrator t=2023-04-24T10:35:09.259102213Z level=info msg="Executing migration" id="teams permissions migration"
full-node-grafana-1     | logger=migrator t=2023-04-24T10:35:09.266712958Z level=info msg="Executing migration" id="dashboard permissions"
full-node-grafana-1     | logger=migrator t=2023-04-24T10:35:09.274318078Z level=info msg="Executing migration" id="dashboard permissions uid scopes"
full-node-grafana-1     | logger=migrator t=2023-04-24T10:35:09.284814788Z level=info msg="Executing migration" id="drop managed folder create actions"
full-node-grafana-1     | logger=migrator t=2023-04-24T10:35:09.290150517Z level=info msg="Executing migration" id="alerting notification permissions"
full-node-grafana-1     | logger=migrator t=2023-04-24T10:35:09.294887829Z level=info msg="Executing migration" id="create query_history_star table v1"

...

full-node-grafana-1     | logger=query_data t=2023-04-24T10:35:24.458454106Z level=info msg="Query Service initialization"
full-node-grafana-1     | logger=live.push_http t=2023-04-24T10:35:24.461756569Z level=info msg="Live Push Gateway initialization"
full-node-grafana-1     | logger=infra.usagestats.collector t=2023-04-24T10:35:25.274019008Z level=info msg="registering usage stat providers" usageStatsProvidersLen=2
full-node-grafana-1     | logger=provisioning.plugins t=2023-04-24T10:35:25.370443713Z level=error msg="Failed to read plugin provisioning files from directory" path=/etc/grafana/provisioning/plugins error="open /etc/grafana/provisioning/plugins: no such file or directory"
full-node-grafana-1     | logger=provisioning.notifiers t=2023-04-24T10:35:25.370528878Z level=error msg="Can't read alert notification provisioning files from directory" path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory"
full-node-grafana-1     | logger=provisioning.alerting t=2023-04-24T10:35:25.370557277Z level=error msg="can't read alerting provisioning files from directory" path=/etc/grafana/provisioning/alerting error="open /etc/grafana/provisioning/alerting: no such file or directory"
full-node-grafana-1     | logger=provisioning.alerting t=2023-04-24T10:35:25.370566088Z level=info msg="starting to provision alerting"
full-node-grafana-1     | logger=provisioning.alerting t=2023-04-24T10:35:25.370575514Z level=info msg="finished to provision alerting"
full-node-grafana-1     | logger=ngalert.state.manager t=2023-04-24T10:35:25.371092404Z level=info msg="Warming state cache for startup"
full-node-grafana-1     | logger=grafanaStorageLogger t=2023-04-24T10:35:25.37119118Z level=info msg="storage starting"
full-node-grafana-1     | logger=http.server t=2023-04-24T10:35:25.375483264Z level=info msg="HTTP Server Listen" address=[::]:3000 protocol=http subUrl= socket=
full-node-grafana-1     | logger=ngalert.state.manager t=2023-04-24T10:35:25.392922858Z level=info msg="State cache has been initialized" states=0 duration=21.826805ms
full-node-grafana-1     | logger=ngalert.multiorg.alertmanager t=2023-04-24T10:35:25.393019516Z level=info msg="starting MultiOrg Alertmanager"
full-node-grafana-1     | logger=ticker t=2023-04-24T10:35:25.393487265Z level=info msg=starting first_tick=2023-04-24T10:35:30Z

Notes

Checklist

  • I have ensured that my version is up-to-date
  • I have ensured that my issue is reproducible
  • I have ensured that my issue is not a duplicate
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant