Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

panic: WatchGlobalConfig #6860

Closed
dbsid opened this issue Jul 31, 2023 · 1 comment · Fixed by #6866
Closed

panic: WatchGlobalConfig #6860

dbsid opened this issue Jul 31, 2023 · 1 comment · Fixed by #6866
Assignees
Labels
affects-7.1 severity/moderate The issue's severity is moderate. type/bug The issue is confirmed as a bug.

Comments

@dbsid
Copy link

dbsid commented Jul 31, 2023

Bug Report

What did you do?

restart pd

What did you expect to see?

no panic

What did you see instead?

pd panic

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x20491a4]

goroutine 546 [running]:
github.com/tikv/pd/server.(*GrpcServer).WatchGlobalConfig(0x4002820d50, 0x4002f106c0, {0x3929bb0, 0x4002f0ab60})
        /mnt/data1/jenkins/workspace/build-common@4/go/src/github.com/pingcap/pd/server/grpc_service.go:2366 +0x144
github.com/pingcap/kvproto/pkg/pdpb._PD_WatchGlobalConfig_Handler({0x2b851e0?, 0x4002820d50}, {0x3926ee8, 0x4002ac9cc8})
        /root/go/pkg/mod/github.com/pingcap/kvproto@v0.0.0-20230727073445-53e1f8730c30/pkg/pdpb/pdpb.pb.go:10273 +0xd0
github.com/grpc-ecosystem/go-grpc-middleware.ChainStreamServer.func1.1({0x2b851e0?, 0x4002820d50?}, {0x3926ee8?, 0x4002ac9cc8?})
        /root/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.0.1-0.20190118093823-f849b5445de4/chain.go:71 +0x9c
github.com/grpc-ecosystem/go-grpc-prometheus.(*ServerMetrics).StreamServerInterceptor.func1({0x2b851e0, 0x4002820d50}, {0x3927a28?, 0x40013d2cc0}, 0x20?, 0x4002f128c0)
        /root/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0/server_metrics.go:121 +0x108
github.com/grpc-ecosystem/go-grpc-middleware.ChainStreamServer.func1.1({0x2b851e0?, 0x4002820d50?}, {0x3927a28?, 0x40013d2cc0?})
        /root/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.0.1-0.20190118093823-f849b5445de4/chain.go:74 +0x74
go.etcd.io/etcd/etcdserver/api/v3rpc.newStreamInterceptor.func1({0x2b851e0, 0x4002820d50}, {0x3927a28, 0x40013d2cc0}, 0x4002ac9c80?, 0x4002f128c0)
        /root/go/pkg/mod/go.etcd.io/etcd@v0.5.0-alpha.5.0.20220915004622-85b640cee793/etcdserver/api/v3rpc/interceptor.go:237 +0x420
github.com/grpc-ecosystem/go-grpc-middleware.ChainStreamServer.func1({0x2b851e0, 0x4002820d50}, {0x3927a28, 0x40013d2cc0}, 0x4002ac9c80, 0x36851c0)
        /root/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.0.1-0.20190118093823-f849b5445de4/chain.go:79 +0x17c
google.golang.org/grpc.(*Server).processStreamingRPC(0x4002822480, {0x392df80, 0x4002823080}, 0x4002f08700, 0x400067cf60, 0x49a5860, 0x0)
        /root/go/pkg/mod/google.golang.org/grpc@v1.26.0/server.go:1244 +0xb9c
google.golang.org/grpc.(*Server).handleStream(0x4002822480, {0x392df80, 0x4002823080}, 0x4002f08700, 0x0)
        /root/go/pkg/mod/google.golang.org/grpc@v1.26.0/server.go:1317 +0x82c
google.golang.org/grpc.(*Server).serveStreams.func1.1()
        /root/go/pkg/mod/google.golang.org/grpc@v1.26.0/server.go:722 +0x84
created by google.golang.org/grpc.(*Server).serveStreams.func1
        /root/go/pkg/mod/google.golang.org/grpc@v1.26.0/server.go:720 +0xdc

What version of PD are you using (pd-server -V)?

[root@tiup-0 v7.3.0-alpha-nightly-20230730]# ./pd-server -V
Release Version: v7.3.0-alpha
Edition: Community
Git Commit Hash: fe52361cf48a7f5ed8c69bcd02db77e25162f207
Git Branch: heads/refs/tags/v7.3.0-alpha
UTC Build Time:  2023-07-28 02:25:10
@dbsid dbsid added the type/bug The issue is confirmed as a bug. label Jul 31, 2023
@dbsid
Copy link
Author

dbsid commented Jul 31, 2023

/assign @bufferflies

@dbsid dbsid changed the title panic: panic: WatchGlobalConfig Jul 31, 2023
@HuSharp HuSharp added the severity/moderate The issue's severity is moderate. label Jul 31, 2023
@github-actions github-actions bot added this to Need Triage in Questions and Bug Reports Jul 31, 2023
Questions and Bug Reports automation moved this from Need Triage to Closed Jul 31, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jul 31, 2023
close #6860

Signed-off-by: husharp <jinhao.hu@pingcap.com>
Signed-off-by: husharp <ihusharp@gmail.com>

Co-authored-by: lhy1024 <admin@liudos.us>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Aug 10, 2023
close tikv#6860

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this issue Aug 10, 2023
close #6860

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: husharp <jinhao.hu@pingcap.com>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Aug 10, 2023
close tikv#6860

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Aug 10, 2023
close tikv#6860

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Aug 10, 2023
close tikv#6860

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this issue Aug 10, 2023
close #6860

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: husharp <jinhao.hu@pingcap.com>
ti-chi-bot bot pushed a commit that referenced this issue Aug 11, 2023
close #6860

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: husharp <jinhao.hu@pingcap.com>
ti-chi-bot bot pushed a commit that referenced this issue Aug 11, 2023
close #6860

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: husharp <jinhao.hu@pingcap.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.1 severity/moderate The issue's severity is moderate. type/bug The issue is confirmed as a bug.
Projects
Development

Successfully merging a pull request may close this issue.

3 participants