Grafana 10.2.0 upgrade failure using mysql database

nickidw · November 29, 2023, 7:17am

I’m having this same issue upgrading from 10.1.1 to 10.2.0, running mysql

nickidw · November 29, 2023, 7:34am

github.com/grafana/grafana

Grafana 10.2.0: Upgrading from 10.1.5 failure with MariaDB as database on other machine

opened 04:25AM - 27 Oct 23 UTC

closed 01:30PM - 15 Nov 23 UTC

fadjar340

area/backend/db triage/needs-confirmation

### What happened? Upgrading from 10.1.5 to 10.2.0 with MariaDB as database. F…ailure when database migration with this message: ``` Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464549501+07:00 level=info msg="Config loaded from" file=/usr/share/grafana/conf/defaults.ini Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464742164+07:00 level=info msg="Config loaded from" file=/etc/grafana/grafana.ini Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464766338+07:00 level=info msg="Config overridden from command line" arg="default.paths.data=/var/lib/grafana" Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464779899+07:00 level=info msg="Config overridden from command line" arg="default.paths.logs=/var/log/grafana" Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464791009+07:00 level=info msg="Config overridden from command line" arg="default.paths.plugins=/var/lib/grafana/plugins" Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464802086+07:00 level=info msg="Config overridden from command line" arg="default.paths.provisioning=/etc/grafana/provisioning" Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464820071+07:00 level=info msg=Target target=[all] Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464869116+07:00 level=info msg="Path Home" path=/usr/share/grafana Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.46488246+07:00 level=info msg="Path Data" path=/var/lib/grafana Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464893514+07:00 level=info msg="Path Logs" path=/var/log/grafana Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.464908835+07:00 level=info msg="Path Plugins" path=/var/lib/grafana/plugins Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.465015914+07:00 level=info msg="Path Provisioning" path=/etc/grafana/provisioning Oct 26 12:53:30 monitoring02 grafana: logger=settings t=2023-10-26T12:53:30.465037051+07:00 level=info msg="App mode production" Oct 26 12:53:30 monitoring02 grafana: logger=sqlstore t=2023-10-26T12:53:30.468758507+07:00 level=info msg="Connecting to DB" dbtype=mysql Oct 26 12:53:30 monitoring02 grafana: logger=migrator t=2023-10-26T12:53:30.47788942+07:00 level=info msg="Starting DB migrations" Oct 26 12:53:30 monitoring02 grafana: logger=migrator t=2023-10-26T12:53:30.498018871+07:00 level=info msg="Executing migration" id="add unique index signing_key.key_id" Oct 26 12:53:30 monitoring02 grafana: logger=migrator t=2023-10-26T12:53:30.503698308+07:00 level=error msg="Executing migration failed" id="add unique index signing_key.key_id" error="Error 1071 (42000): Specified key was too long; max key length is 767 bytes" duration=5.657264ms Oct 26 12:53:30 monitoring02 grafana: logger=migrator t=2023-10-26T12:53:30.503783865+07:00 level=error msg="Exec failed" error="Error 1071 (42000): Specified key was too long; max key length is 767 bytes" sql="CREATE UNIQUE INDEX `UQE_signing_key_key_id` ON `signing_key` (`key_id`);" Oct 26 12:53:30 monitoring02 grafana: Error: ✗ migration failed (id = add unique index signing_key.key_id): Error 1071 (42000): Specified key was too long; max key length is 767 bytes Oct 26 12:53:30 monitoring02 systemd: grafana-server.service: main process exited, code=exited, status=1/FAILURE ``` The table signing_key have issue with varchar length. MariaDB version: `mysql Ver 15.1 Distrib 5.5.68-MariaDB` This also happened when fresh install with new database, the solution only downgrade to Grafana 10.1.5 again. Info: Both version have empty spining_key table ### What did you expect to happen? The db migration was working and Grafana 10.2.0 spinning up. ### Did this work before? I did migration from Grafana 9.x to 10.1.5 without problem with same configuration database ### How do we reproduce it? 1. yum upgrade grafana (failed) 2. systemctl restart grafana-server (failed) 3. yum downgrade grafana-10.5.1-1 (running) 4. Create new database for new grafana 5. Modify grafana.ini to new empty database 6. yum upgrade grafana (failed with same error message and empty signing_key table) 7. mysql: `ALTER TABLE grafana.signing_key MODIFY COLUMN key_id varchar(15000) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL; 8. systemctl restart grafana-server (failed with same error message)` 9. Revert back grafana.ini to old database 10. yum downgrade grafana-10.5.1-1 (running) Node 1 Node 2 ________ _________ | Grafana | --------> | mariadb | -------------- --------------- ### Is the bug inside a dashboard panel? _No response_ ### Environment (with versions)? Grafana: 10.1.5 to 10.2.0 OS: Centos 7 (both) Browser: Chrome Linux ### Grafana platform? A package manager (APT, YUM, BREW, etc.) ### Datasource(s)? _No response_

Topic		Replies	Views
Need help :Grafana not start after update database (mysql) setting in .ini file Grafana	0	685	August 31, 2020
Issues after upgrade Installation	3	461	August 21, 2023
Grafana stucks on Starting DB migrations Configuration datasource	2	516	March 27, 2024
Can't connect grafana to MYSQL database Configuration	6	252	May 8, 2024
After upgrade of Grafana service stopped running Configuration	0	27	November 14, 2024

Grafana 10.2.0 upgrade failure using mysql database

Related topics