Details
-
Bug
-
Resolution: Duplicate
-
Major
-
5.5.0
-
centos cluster
-
Untriaged
-
No
Description
Build : 5.5.0-2958 (RC4)
Test : -test tests/integration/test_allFeatures_vulcan.yml -scope tests/integration/scope_Xattrs_Vulcan.yml
Iteration : 4th
Scale : 3
In the longevity test, there is a step to stop and start couchbase service on some nodes. On one of the nodes, when couchbase is started, projector services crashes immediately after startup twice with the following panic:
2018-07-14T19:48:02.549-07:00 [Info] Projector started with command line: [/opt/couchbase/bin/projector -kvaddrs=127.0.0.1:11210 -adminport=:9999 -diagDir=/opt/couchbase/var/lib/couchbase/crash -ipv6=false 127.0.0.1:8091]
|
2018-07-14T19:48:02.549-07:00 [Info] Parsing the args
|
2018-07-14T19:48:02.550-07:00 [Info] uid: 996; gid: 994; hostname: localhost.localdomain
|
2018-07-14T19:48:02.550-07:00 [Info] amd64 linux; cpus: 8; GOMAXPROCS: 8; version: go1.7.6
|
2018-07-14T19:48:03.099-07:00 [Error] GetSettingsConfig() failed: Get http://127.0.0.1:8091/_metakv/indexing/settings/config: Unable to find given hostport in cbauth database: `127.0.0.1:8091'
|
panic: Get http://127.0.0.1:8091/_metakv/indexing/settings/config: Unable to find given hostport in cbauth database: `127.0.0.1:8091'
|
|
|
goroutine 1 [running]:
|
panic(0xab93e0, 0xc420134cf0)
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/panic.go:500 +0x1a1 fp=0xc42017f980 sp=0xc42017f8f0
|
github.com/couchbase/indexing/secondary/common.CrashOnError(0x1257200, 0xc420134cf0)
|
goproj/src/github.com/couchbase/indexing/secondary/common/util.go:404 +0x5c fp=0xc42017f9b0 sp=0xc42017f980
|
github.com/couchbase/indexing/secondary/projector.NewProjector(0x400, 0xc420018f30, 0xc42017fe88)
|
goproj/src/github.com/couchbase/indexing/secondary/projector/projector.go:54 +0x177 fp=0xc42017fe18 sp=0xc42017f9b0
|
main.main()
|
goproj/src/github.com/couchbase/indexing/secondary/cmd/projector/main.go:111 +0x70d fp=0xc42017ff38 sp=0xc42017fe18
|
runtime.main()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/proc.go:183 +0x1f4 fp=0xc42017ff90 sp=0xc42017ff38
|
runtime.goexit()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc42017ff98 sp=0xc42017ff90
|
After running into this issue twice, it was able to startup fine, and no further issues were seen. This behaviour was seen only once so far, and only on one node - 172.23.108.104. So this is an intermittent issue and also not harmful.
It would be good to handle this error and retry if cbauth database isnt accessible at startup rather than crash.
Supportal link : http://supportal.couchbase.com/snapshot/85277d8dde1234d3615f37137f90624c::1