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

Grafana/log-analyser not working after fresh setup with docker on Ubuntu24 #1956

Open
pzystorm opened this issue Oct 28, 2024 · 0 comments
Open

Comments

@pzystorm
Copy link

Hi,
to install I have followed these instructions: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-log-analyser/

My system:

# docker -v
Docker version 27.3.1, build ce12230
# docker compose version
Docker Compose version v2.29.7
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.1 LTS
Release:        24.04
Codename:       noble

After starting I first had the problem, that Grafana complained about not having permissions to write to /var/lib/grafana. But after chmod -R a+w log-analyser this problem is gone. I have realized that grafana is not runnning under root in the docker container but rather under a local user with the id 472.

Now it starts, but after doing a lot of migration and import stuff with the output of "Migration successfully executed" it stated, that there is some error with the admin user and some dashboards and a database lock:

grafana-1  | logger=ngalert.migration t=2024-10-28T01:47:51.448727439Z level=info msg=Starting
grafana-1  | logger=ngalert.migration t=2024-10-28T01:47:51.449037184Z level=info msg="Starting legacy migration"
grafana-1  | logger=ngalert.migration orgID=1 t=2024-10-28T01:47:51.449198965Z level=info msg="Migrating alerts for organisation"
grafana-1  | logger=ngalert.migration orgID=1 t=2024-10-28T01:47:51.449499582Z level=info msg="Alerts found to migrate" alerts=0
grafana-1  | logger=ngalert.migration orgID=1 t=2024-10-28T01:47:51.449852528Z level=warn msg="No available receivers"
grafana-1  | logger=dashboard-service t=2024-10-28T01:47:51.451198337Z level=error msg="Could not make user admin" dashboard="Jitsi Web Dashboard" namespaceID=user userID=0 error="identifier is not initialized"
grafana-1  | logger=dashboard-service t=2024-10-28T01:47:51.452762025Z level=error msg="Could not make user admin" dashboard="JVB Dashboard" namespaceID=user userID=0 error="identifier is not initialized"
grafana-1  | logger=dashboard-service t=2024-10-28T01:47:51.454722487Z level=error msg="Could not make user admin" dashboard="Prosody Dashboard" namespaceID=user userID=0 error="identifier is not initialized"
grafana-1  | logger=dashboard-service t=2024-10-28T01:47:51.457034977Z level=error msg="Could not make user admin" dashboard="Docker Statistics" namespaceID=user userID=0 error="identifier is not initialized"
grafana-1  | logger=dashboard-service t=2024-10-28T01:47:51.458611722Z level=error msg="Could not make user admin" dashboard="Jicofo Dashboard" namespaceID=user userID=0 error="identifier is not initialized"
grafana-1  | logger=dashboard-service t=2024-10-28T01:47:51.45991985Z level=error msg="Could not make user admin" dashboard="Jitsi All Components Dashboard" namespaceID=user userID=0 error="identifier is not initialized"
grafana-1  | logger=grafana.update.checker t=2024-10-28T01:47:51.51175419Z level=info msg="Update check succeeded" duration=84.619297ms
grafana-1  | logger=sqlstore.transactions t=2024-10-28T01:47:51.518900925Z level=info msg="Database locked, sleeping then retrying" error="executing migration: database is locked" retry=0 code="database is locked"

Do you have any ideas on that? Is it a bug or version incompability or am I doing something wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant