Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
1
Description
Problem
During a Service restart situational test, after stopping one node with 'service couchbase-server stop', gocb/core reports a panic - " panic: runtime error: invalid memory address or nil pointer dereference", and then seg faults.
[516.65 DEBUG] (SSHCommand execute:75) Running service couchbase-server stop on 172.23.99.69
|
[518.85 INFO] (SDKD log:137) panic: runtime error: invalid memory address or nil pointer dereference
|
[518.85 INFO] (SDKD log:137) [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x6f8da9]
|
[518.85 INFO] (SDKD log:137)
|
[518.85 INFO] (SDKD log:137) goroutine 2758 [running]:
|
[518.85 INFO] (SDKD log:137) bufio.(*Reader).Reset(...)
|
[518.85 INFO] (SDKD log:137) /usr/local/go/src/bufio/bufio.go:71
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10/memd.releaseReadBuf(0x0)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memd/conn.go:63 +0x29
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10/memd.(*Conn).Release(...)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memd/conn.go:543
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10.(*memdConnWrap).Release(0xc0791767c0)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memdconn.go:62 +0x37
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10.(*memdClient).closeConn(0xc07916a7e0, 0x0, 0x0, 0x9766a0)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memdclient.go:545 +0xc9
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10.(*memdClient).Close(0xc07916a7e0, 0xc006cced80, 0xc00ec400c0)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memdclient.go:564 +0x60
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10.(*memdClientDialerComponent).SlowDialMemdClient(0xc0052b2a00, 0xc006cced80, 0xc00685658c, 0x12, 0x455e00, 0x0, 0xc0068545e0, 0xc010268fc0, 0x3, 0x3, ...)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memdclientdialer_component.go:128 +0x304
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10.(*kvMux).newKVMuxState.func1(0xc006cced80, 0x0, 0x45bb21, 0xc006dc90c0)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/kvmux.go:669 +0xff
|
[518.85 INFO] (SDKD log:137) github.com/couchbase/gocbcore/v10.(*memdPipelineClient).Run.func1(0xc0102bf2c0, 0xc0102bf560, 0xc0764ef920)
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memdpipelineclient.go:219 +0x38
|
[518.85 INFO] (SDKD log:137) created by github.com/couchbase/gocbcore/v10.(*memdPipelineClient).Run
|
[518.85 INFO] (SDKD log:137) /root/jenkins/workspace/sdk-go-situational-release/go-sdk-situational-all/pkg/mod/github.com/couchbase/gocbcore/v10@v10.0.7-0.20220119184459-18c8b7b04a33/memdpipelineclient.go:218 +0x27b
|
Environment
This is with a 4 node cluster with services:
N1: kv
N2: kv,n1ql,index,fts
N3: kv,n1ql,index,fts
N4: kv,n1ql,index,fts
And it occurs with all CB server versions when connecting without TLS (7.0, 6.6, 6.0, 5.5). With TLS enabled it does not happen.
Working on getting full SDK logs.