最近試用了MeterSphere做接口測(cè)試平臺(tái),感覺(jué)使用起來(lái)非常方便谴仙,最重要的是開(kāi)源免費(fèi)迂求!官方文檔還是非常詳細(xì)的,這里我就不多介紹了晃跺,感興趣的同學(xué)可以參考:
https://metersphere.io/docs/v2.x/
經(jīng)過(guò)討論揩局,決定在測(cè)試團(tuán)隊(duì)推廣。由于公司數(shù)據(jù)庫(kù)管理策略哼审,數(shù)據(jù)庫(kù)必須通過(guò)dba 統(tǒng)一管理谐腰,所以需要MeterSphere連接外部mysql數(shù)據(jù)庫(kù)。數(shù)據(jù)庫(kù)遷移過(guò)程中主要遇到下面錯(cuò)誤:
Caused by: org.flywaydb.core.api.FlywayException: Schema `metersphere` contains a failed migration to version 5 !
接下來(lái)我就詳細(xì)講述一下涩盾,MeterSphere連接外部數(shù)據(jù)庫(kù)的操作過(guò)程十气,以及再此過(guò)程中解決遇到問(wèn)題的詳細(xì)步驟:
修改配置文件
根據(jù)官方提示 在/opt/metersphere/.env (該文件是隱藏文件)中修改如下配置,注意標(biāo)紅
# 數(shù)據(jù)庫(kù)配置
## 是否使用外部數(shù)據(jù)庫(kù)
MS_EXTERNAL_MYSQL=true
## 數(shù)據(jù)庫(kù)地址
MS_MYSQL_HOST=mysql
## 數(shù)據(jù)庫(kù)端口
MS_MYSQL_PORT=3306
## 數(shù)據(jù)庫(kù)庫(kù)名
MS_MYSQL_DB=metersphere
## 數(shù)據(jù)庫(kù)用戶名
MS_MYSQL_USER=root
## 數(shù)據(jù)庫(kù)密碼
MS_MYSQL_PASSWORD=Password123@mysql
然后運(yùn)行命令
msctl reload
msctl restart
錯(cuò)誤現(xiàn)象
自以為會(huì)是大功告成春霍,事實(shí)則是登錄無(wú)反應(yīng)砸西!
查看/opt/metersphere/logs/metersphere/info.log 日志發(fā)現(xiàn)問(wèn)題如下:
Caused by: org.flywaydb.core.api.FlywayException: Schema `metersphere` contains a failed migration to version 5 !
at org.flywaydb.core.internal.command.DbMigrate.migrateGroup(DbMigrate.java:217)
at org.flywaydb.core.internal.command.DbMigrate.lambda$migrateAll$0(DbMigrate.java:141)
at org.flywaydb.core.internal.database.mysql.MySQLNamedLockTemplate.execute(MySQLNamedLockTemplate.java:60)
at org.flywaydb.core.internal.database.mysql.MySQLConnection.lock(MySQLConnection.java:154)
at org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory.lock(JdbcTableSchemaHistory.java:141)
at org.flywaydb.core.internal.command.DbMigrate.migrateAll(DbMigrate.java:141)
at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:101)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:219)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:170)
at org.flywaydb.core.Flyway.execute(Flyway.java:586)
at org.flywaydb.core.Flyway.migrate(Flyway.java:170)
at org.springframework.boot.autoconfigure.flyway.FlywayMigrationInitializer.afterPropertiesSet(FlywayMigrationInitializer.java:66)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800)
... 34 common frames omitted
第一反應(yīng)是 — 怎么會(huì)?我明明按照官網(wǎng)鏈接一步一步執(zhí)行的爸啡濉芹枷!
https://metersphere.io/docs/v2.x/installation/offline_installation/
并協(xié)調(diào)dba搞了個(gè)MySQL5.7 ,怎么還會(huì)報(bào)db遷移到5的錯(cuò)誤呢莲趣?
Caused by: org.flywaydb.core.api.FlywayException: Schema `metersphere` contains a failed migration to version 5 !
尋求問(wèn)題解決方案
于是乎找了metersphere的技術(shù)支持鸳慈,解決方案如下:
首先執(zhí)行下面的腳本
https://raw.githubusercontent.com/metersphere/metersphere/master/backend/src/main/resources/db/migration/V5__schedule.sql
然后修改metersphere_version 表對(duì)應(yīng)版本的的success值為1,
最后執(zhí)行命令 msclt reload 重啟服務(wù)即可
1.這里需要注意的是:執(zhí)行V5__schedule.sql語(yǔ)句一定讓dba找一個(gè)最高權(quán)限的賬號(hào)來(lái)執(zhí)行喧伞,否者需要各種授權(quán)走芋,非常的麻煩!
2.如果執(zhí)行過(guò)程中有各種表已經(jīng)創(chuàng)建潘鲫,列已經(jīng)存在的相關(guān)消息翁逞,直接忽略即可
3. V5__schedule.sql 執(zhí)行之前已經(jīng)執(zhí)行了很多sql操作,這些語(yǔ)句是在執(zhí)行下面語(yǔ)句時(shí)就已經(jīng)完成了的溉仑!換句話說(shuō)挖函,V5__schedule.sql是基于下面的語(yǔ)句運(yùn)行之后再運(yùn)行的!
msctl reload
msctl restart
最后的總結(jié)
如果執(zhí)行sql語(yǔ)句過(guò)程中出現(xiàn)了意想不到的問(wèn)題浊竟。建議如下操作:
1. 刪掉庫(kù)metersphere怨喘,然后重新創(chuàng)建庫(kù)metersphere
2. 執(zhí)行msctl restart
3. 執(zhí)行語(yǔ)句V5__schedule.sql
4. 修改metersphere_version 表對(duì)應(yīng)版本的的success值為1
5. 執(zhí)行msclt reload