-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Component/s: Monitoring
-
Labels:None
When i start it with ./bin/mongosqld -vvv, I get this panic after sampling is completed:
panic: send on closed channel
goroutine 36 [running]:
github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster.(*Monitor).startMonitoringServer.func1(0xc420138240, 0xc420138120)
/Users/wisdom/gopath/src/github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster/monitor.go:188 +0x92
created by github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster.(*Monitor).startMonitoringServer
/Users/wisdom/gopath/src/github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster/monitor.go:190 +0x12f```
The panic is caused by this line: https://github.com/10gen/sqlproxy/blob/1ed515047a089fed7c64906948622743252eafeb/server/server.go#L103 though it's not clear why the driver bugs out because of that Close().
I suspect it is a problem in the Go driver but haven't been able to pin it down.