Grafana won't start after upgrade to 5.0!

All;
I just upgraded Grafana from 4.6.2 to 5.0.0-beta1 on a CentOS 6 server. It should of been a straight forward process but now I can’t get it to start. The only thing I am seeing in the log is the following:

t=2018-02-07T10:03:29-0500 lvl=dbug msg=Executing logger=migrator sql="CREATE UNIQUE INDEX UQE_dashboard_org_id_folder_id_title ON dashboard (org_id,folder_id,title);"
t=2018-02-07T10:03:29-0500 lvl=info msg=“Executing migration” logger=migrator id="Add unique index for dashboard_org_id_title_folder_id"
t=2018-02-07T10:03:29-0500 lvl=eror msg=“Executing migration failed” logger=migrator id=“Add unique index for dashboard_org_id_title_folder_id” error="Error 1071: Specified key was too long; max key length is 767 bytes"
t=2018-02-07T10:03:29-0500 lvl=eror msg=“Exec failed” logger=migrator error=“Error 1071: Specified key was too long; max key length is 767 bytes” sql="CREATE UNIQUE INDEX UQE_dashboard_org_id_folder_id_title ON dashboard (org_id,folder_id,title);"
t=2018-02-07T10:03:29-0500 lvl=eror msg=“Fail to initialize orm engine” logger=sqlstore error=“Sqlstore::Migration failed err: Error 1071: Specified key was too long; max key length is 767 bytes\n”

Honestly, I’m not sure what this means, if anything. Any insight at all would be greatly appreciated.
Thanks;
Frank

this has been fixed (will be available in beta2), but until then you can use the nightly build,

1 Like

Thank you very, very much for the quick response. Its strange, I have an Ubuntu server that I use for development and I upgraded that without any issues.
Regards;
Frank

I just downloaded the beta this morning and I’m getting that same issue. Is there a change that I can make on the DDL to fix this?

I downloaded the nightly build 5.0.0-11668beta1 and it installed and worked perfectly. I suggest giving that version a try.
Best Regards;
Frank

Hi Team,

When i tried to upgrade from grafana4.6 to grafana-5.0 ,
i dropped all tables and restarted the grafana.
then i got below error .

t=2018-03-30T08:55:26-0400 lvl=info msg=“Starting DB migration” logger=migrator
t=2018-03-30T08:55:27-0400 lvl=info msg=“Executing migration” logger=migrator id=“copy data account to org”
t=2018-03-30T08:55:27-0400 lvl=info msg=“Skipping migration condition not fulfilled” logger=migrator id=“copy data account to org”
t=2018-03-30T08:55:27-0400 lvl=info msg=“Executing migration” logger=migrator id=“copy data account_user to org_user”
t=2018-03-30T08:55:27-0400 lvl=info msg=“Skipping migration condition not fulfilled” logger=migrator id=“copy data account_user to org_user”
t=2018-03-30T08:55:28-0400 lvl=info msg=“Executing migration” logger=migrator id=“add index data_source.account_id”
t=2018-03-30T08:55:28-0400 lvl=eror msg=“Executing migration failed” logger=migrator id=“add index data_source.account_id” error=“Error 1072: Key column ‘account_id’ doesn’t exist in table”
t=2018-03-30T08:55:28-0400 lvl=eror msg=“Exec failed” logger=migrator error=“Error 1072: Key column ‘account_id’ doesn’t exist in table” sql=“CREATE INDEX IDX_data_source_account_id ON data_source (account_id);”
t=2018-03-30T08:55:28-0400 lvl=eror msg=“Fail to initialize orm engine” logger=sqlstore error=“Sqlstore::Migration failed err: Error 1072: Key column ‘account_id’ doesn’t exist in table\n”