Invalid configuration: default RocksDB exists, but RaftDB does not exist

translator_bot · June 21, 2024, 5:06am

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: invalid configuration: default rocksdb exist, but raftdb not exist

| username: Quino

[TiDB Usage Environment] Production Environment
[TiDB Version] 7.5.0
[Reproduction Path] None
[Encountered Problem: Problem Phenomenon and Impact] Deployed TiDB using k8s+kubesphere+operator, one day found that a TiKV failed to start
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Another question is that the default deployed TiDB cluster is in UTC time zone. I want to change it to Shanghai time zone. Do I need to restart kv, pd, and tidb? What is the restart order?

translator_bot · June 21, 2024, 5:06am

| username: Kongdom | Original post link

This is the standard startup and shutdown sequence.

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Sure, thank you for your reply. Regarding the issue of TiKV failing to start, how can I resolve it? After deployment, I haven’t manually restarted it. It should be automatically scheduled and started by k8s. There were always 3 KV nodes before.

translator_bot · June 21, 2024, 5:06am

| username: 小龙虾爱大龙虾 | Original post link

To modify the time zone configuration without restarting the components, use

SET GLOBAL time_zone = timezone;

Reference: 时区支持 | PingCAP 文档中心

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

If TiFlash, Drainer, and TiCDC are not deployed, can they be skipped?

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

The images you provided are not visible. Please provide the text content for translation.

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Thank you, thank you

translator_bot · June 21, 2024, 5:06am

| username: Kongdom | Original post link

The TiKV error seems to be a configuration file issue. It is recommended to check whether the configuration files under the node are different from those under other nodes.

translator_bot · June 21, 2024, 5:06am

| username: Kongdom | Original post link

Yes, it can be skipped.

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Okay, I see if there are any differences between the game configuration files and other KV.

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Sorry to bother you. I have another question. The built-in dashboard panel in the cluster sometimes doesn’t open when scheduled to other nodes because there are three nodes deployed. So, I manually deployed an independent dashboard, but when I open the webpage, I get this prompt:

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

The image you provided is not visible. Please provide the text you need translated.

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

{
“error”: true,
“message”: “Invalid Semantic Version”,
“code”: “common.internal”,
“full_text”: “Invalid Semantic Version\n at github.com/pingcap/tidb-dashboard/util/rest.Error()\n\t/go/src/github.com/pingcap/tidb-dashboard/util/rest/context_helpers.go:19\n at github.com/pingcap/tidb-dashboard/pkg/apiserver/info.(*Service).infoHandler()\n\t/go/src/github.com/pingcap/tidb-dashboard/pkg/apiserver/info/info.go:86\n at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n at github.com/pingcap/tidb-dashboard/util/rest.ErrorHandlerFn.func1()\n\t/go/src/github.com/pingcap/tidb-dashboard/util/rest/error.go:70\n at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n at github.com/gin-contrib/gzip.Gzip.func2()\n\t/go/pkg/mod/github.com/gin-contrib/gzip@v0.0.1/gzip.go:47\n at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n at github.com/gin-gonic/gin.CustomRecoveryWithWriter.func1()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/recovery.go:99\n at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n at github.com/gin-gonic/gin.(*Engine).handleHTTPRequest()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/gin.go:489\n at github.com/gin-gonic/gin.(*Engine).ServeHTTP()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/gin.go:445\n at github.com/pingcap/tidb-dashboard/pkg/apiserver.(*Service).handler()\n\t/go/src/github.com/pingcap/tidb-dashboard/pkg/apiserver/apiserver.go:244\n at net/http.HandlerFunc.ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2109\n at github.com/pingcap/tidb-dashboard/pkg/utils.(*ServiceStatus).NewStatusAwareHandler.func1()\n\t/go/src/github.com/pingcap/tidb-dashboard/pkg/utils/service_status.go:67\n at net/http.HandlerFunc.ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2109\n at net/http.(*ServeMux).ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2487\n at net/http.serverHandler.ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2947\n at net/http.(*conn).serve()\n\t/usr/local/go/src/net/http/server.go:1991\n at runtime.goexit()\n\t/usr/local/go/src/runtime/asm_amd64.s:1594”
}

translator_bot · June 21, 2024, 5:06am

| username: Kongdom | Original post link

I haven’t encountered this error before, let’s see if any other classmates have experienced it.

translator_bot · June 21, 2024, 5:06am

| username: ShawnYan | Original post link

First time seeing this +1

github.com/kubernetes-sigs/blob-csi-driver

Helm package gives Error: Invalid Semantic Version

opened 07:36PM - 13 Nov 20 UTC

closed 01:09PM - 30 Jan 21 UTC

songjiaxun

**What happened**: `helm package blob-csi-driver` under `latest` folder gives `Error: Invalid Semantic Version`. Helm version: version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"clean", GoVersion:"go1.14.11"} **What you expected to happen**: **How to reproduce it**: **Anything else we need to know?**: **Environment**: - CSI Driver version: - Kubernetes version (use `kubectl version`): - OS (e.g. from /etc/os-release): - Kernel (e.g. `uname -a`): - Install tools: - Others:

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Haha, okay. Thank you, thank you.

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Not sure if my deployment configuration is incorrect.

translator_bot · June 21, 2024, 5:06am

| username: ShawnYan | Original post link

Adjusted the error format

{
    "error": true,
    "message": "Invalid Semantic Version",
    "code": "common.internal",
    "full_text": "Invalid Semantic Version\n 
	at github.com/pingcap/tidb-dashboard/util/rest.Error()\n\t/go/src/github.com/pingcap/tidb-dashboard/util/rest/context_helpers.go:19\n 
	at github.com/pingcap/tidb-dashboard/pkg/apiserver/info.(*Service).infoHandler()\n\t/go/src/github.com/pingcap/tidb-dashboard/pkg/apiserver/info/info.go:86\n 
	at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n 
	at github.com/pingcap/tidb-dashboard/util/rest.ErrorHandlerFn.func1()\n\t/go/src/github.com/pingcap/tidb-dashboard/util/rest/error.go:70\n 
	at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n 
	at github.com/gin-contrib/gzip.Gzip.func2()\n\t/go/pkg/mod/github.com/gin-contrib/gzip@v0.0.1/gzip.go:47\n 
	at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n 
	at github.com/gin-gonic/gin.CustomRecoveryWithWriter.func1()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/recovery.go:99\n 
	at github.com/gin-gonic/gin.(*Context).Next()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/context.go:165\n 
	at github.com/gin-gonic/gin.(*Engine).handleHTTPRequest()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/gin.go:489\n 
	at github.com/gin-gonic/gin.(*Engine).ServeHTTP()\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.7.4/gin.go:445\n 
	at github.com/pingcap/tidb-dashboard/pkg/apiserver.(*Service).handler()\n\t/go/src/github.com/pingcap/tidb-dashboard/pkg/apiserver/apiserver.go:244\n 
	at net/http.HandlerFunc.ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2109\n 
	at github.com/pingcap/tidb-dashboard/pkg/utils.(*ServiceStatus).NewStatusAwareHandler.func1()\n\t/go/src/github.com/pingcap/tidb-dashboard/pkg/utils/service_status.go:67\n 
	at net/http.HandlerFunc.ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2109\n at net/http.(*ServeMux).ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2487\n 
	at net/http.serverHandler.ServeHTTP()\n\t/usr/local/go/src/net/http/server.go:2947\n at net/http.(*conn).serve()\n\t/usr/local/go/src/net/http/server.go:1991\n 
	at runtime.goexit()\n\t/usr/local/go/src/runtime/asm_amd64.s:1594"
}

It looks like the version information was not correctly retrieved.

github.com

pingcap/tidb-dashboard/blob/release-7.5/pkg/apiserver/info/info.go#L86


      
          // @Success 200 {object} InfoResponse
          // @Router /info/info [get]
          // @Security JwtAuth
          // @Failure 401 {object} rest.ErrorResponse
          func (s *Service) infoHandler(c *gin.Context) {
          	// Checking ngm deployments
          	// drop "-alpha-xxx" suffix
          	versionWithoutSuffix := strings.Split(s.params.Config.FeatureVersion, "-")[0]
          	v, err := semver.NewVersion(versionWithoutSuffix)
          	if err != nil {
          		rest.Error(c, err)
          		return
          	}
          	constraint, err := semver.NewConstraint(">= v5.4.0")
          	if err != nil {
          		rest.Error(c, err)
          		return
          	}
          
          	ngmState := utils.NgmStateNotSupported
          	if constraint.Check(v) {

Can you confirm the configuration of kubesphere? Are all pods interconnected, and are all ports open?

translator_bot · June 21, 2024, 5:06am

| username: Quino | Original post link

Thank you for the reply I will check the pod nodes, try pinging, and also check the ports.