Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-39

creating a new cluster panics if mongod isn't running

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      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.

      Attachments

        Activity

          People

            sam.rossi@mongodb.com Samuel Rossi (Inactive)
            adinoyi.omuya@mongodb.com Adinoyi Omuya
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: