Failure on NodeBB 1.3 to 1.4 Update with MongoDB

[scottalanmiller]

Run the update process and this is the error that I get in the logs:

10/12 09:39 [22179] - info: [database] Checking database indices done!
10/12 09:39 [22179] - error:  MongoError: Index with name: _key_1_value_-1 already exists with different options
    at Function.MongoError.create (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/error.js:31:11)
    at /opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/pool.js:462:72
    at authenticateStragglers (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/pool.js:410:16)
    at Connection.messageHandler (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/pool.js:444:5)
[cluster] Child Process (22179) has exited (code: 0, signal: null)
    at Socket.<anonymous> (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/connection.js:306:22)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at TCP.onread (net.js:548:20)

[exodo]

duplicate key error index issue · Issue #5265 · NodeBB/NodeBB

Please include the following information when submitting a bug report/issue: NodeBB 1.4.0 Database Mongo I got that error on the upgrade and after removing like 30 objects on the db managed to run and complete the upgrade ( https://commu...

GitHub (github.com)

[jarey]

@exodo doesn't seem like the same error. On the logs probided on this thread, specific keys are not referenced, it is only reported an error over an i dex.

[exodo]

It is relates to key_1_value-1 already exists issue

[scottalanmiller]

The 1.4.1 update seems to have fixed the issue for me. More testing this evening. Thanks.