I ran into the issue of Grafana logging users out because the SQLite database was locked and tokens couldn't be looked up. This is discussed in #10727 on grafana/grafana. The solution is to migrate to a database that isn't the default one of SQLite.
You must already have an existing database in Postgres for Grafana.
Run CREATE DATABASE grafana
in psql
to make the database. Then, start up an instance of Grafana pointed to the new database. Grafana will automagically create all the tables that it will need. You can shut Grafana down once those tables are made. We need those tables to exist for the migration to work.
Tested on:
OS | SQLite Version | Postgres Version | Grafana Version |
---|---|---|---|
MacOS | 3.24.0 | 11.3 | 6.1.0+ |
CentOS 7/RHEL7 | 3.7.17 | 11.3 | 6.1.0+ |
usage: Grafana SQLite to Postgres Migrator [<flags>] <sqlite-file> <postgres-connection-string>
A command-line application to migrate Grafana data from SQLite to Postgres.
Flags:
--help Show context-sensitive help (also try --help-long and --help-man).
--dump=/tmp Directory path where the sqlite dump should be stored.
Args:
<sqlite-file> Path to SQLite file being imported.
<postgres-connection-string> URL-format database connection string to use in the URL format (postgres://USERNAME:PASSWORD@HOST/DATABASE).
This is the command I used to transfer my Grafana database:
./grafana-migrate grafana.db "postgres://postgres:PASSWORDHERE@localhost:5432/grafana?sslmode=disable"
Notice the ?sslmode=disable
parameter. The pq driver has sslmode turned on by default, so you may need to add a parameter to adjust it. You can see all the support connection string parameters here.
- Dumps SQLite database to /tmp
- Sanitize the dump so it can be imported to Postgres
- Import the dump to the Grafana database
Inspiration for this program was taken from