creating a new cluster panics if mongod isn't running

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      See:

      panic: send on closed channel
goroutine 8 [running]:
github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster.(*Monitor).startMonitoringServer.func1(0xc4201677a0, 0xc420167680)
	/Users/bedrich/gopath/src/github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster/monitor.go:185 +0x92
created by github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster.(*Monitor).startMonitoringServer
	/Users/bedrich/gopath/src/github.com/10gen/sqlproxy/vendor/github.com/10gen/mongo-go-driver/cluster/monitor.go:187 +0x12f

      This happens when cluster.New(...) is called with cluster options.

            Assignee:
            Samuel Rossi (Inactive)
            Reporter:
            Adinoyi Omuya (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: