Initialization error: MongoError: a collection already exists

[octo-kumo]

I am using the following constructor

new winston.transports.MongoDB({
    name: "http",
    db: process.env.MONGODB_URL,
    options: {
        poolSize: 2, useNewUrlParser: true,
        useUnifiedTopology: true
    },
    tryReconnect: true,
    collection: 'http',
    level: 'info'
})

It runs without issue for the first time, but whenever I run the code again, it gives me this error

winston-mongodb, initialization error:  MongoError: a collection 'database.http' already exists
    at MessageStream.messageHandler (/.../node_modules/mongodb/lib/cmap/connection.js:266:20)
    at MessageStream.emit (events.js:314:20)
    at processIncomingData (/.../node_modules/mongodb/lib/cmap/message_stream.js:144:12)
    at MessageStream._write (/.../node_modules/mongodb/lib/cmap/message_stream.js:42:5)
    at writeOrBuffer (_stream_writable.js:352:12)
    at MessageStream.Writable.write (_stream_writable.js:303:10)
    at TLSSocket.ondata (_stream_readable.js:714:22)
    at TLSSocket.emit (events.js:314:20)
    at addChunk (_stream_readable.js:304:12)
    at readableAddChunk (_stream_readable.js:280:9) {
  operationTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1596430109 },
  ok: 0,
  code: 48,
  codeName: 'NamespaceExists',
  '$clusterTime': {
    clusterTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1596430109 },
    signature: { hash: [Binary], keyId: [Long] }
  }
}

[Swagtex]

@misuti
My current "fix": npm install mongodb@3.3.3

[a1300]

Thank you very much @Swagtex 👍
This worked for me!

[BNHDev]

@Swagtex Thank you for your solution 👍👍👍

[keyyuki]

I have same issue and solution of @Swagtex not work for me T_T

[backflip]

This seems to be related to Changes in behavior of Db.prototype.createCollection in mongodb@3.6.0 (see PR). So everything before 3.6.0 should work.

[backflip]

Possible fix: #176

[ceopaludetto]

If you use various versions of mongodb in your codebase(such as mongoose), another solution is resolutions field in package.json, add:

"resolutions": {
    "mongoose/**/mongodb": "3.3.3"
},

Then reinstall packages running yarn

[yurijmikhalevich]

Fixed in winston-mongodb@5.0.3.

[BasitMaqsood]

@misuti
My current "fix": npm install mongodb@3.3.3

Helpful, Thanks a lot