random “MongoError: não autorizado no XXX para executar o comando {YYY}” com o mongo 3.2

Question

desde muito recentemente eu tenho erros aleatórios como estes:

2016-06-06T18:17:55.386Z pid:2458 worker:3 MongoError: not authorized on db to execute command {...someQuery...}
2016-06-06T18:17:55.386Z pid:2458 worker:3     at Function.MongoError.create (/var/lib/strong-pm/svc/1/work/a6e0bde254cbdedde6345bdf94e29e51828c5fa2.1465232211706/node_modules/loopback-connector-mongodb/node_modules/mongodb-core/lib/error.js:31:11)
2016-06-06T18:17:55.386Z pid:2458 worker:3     at queryCallback (/var/lib/strong-pm/svc/1/work/a6e0bde254cbdedde6345bdf94e29e51828c5fa2.1465232211706/node_modules/loopback-connector-mongodb/node_modules/mongodb-core/lib/cursor.js:200:36)
2016-06-06T18:17:55.386Z pid:2458 worker:3     at Callbacks.emit (/var/lib/strong-pm/svc/1/work/a6e0bde254cbdedde6345bdf94e29e51828c5fa2.1465232211706/node_modules/loopback-connector-mongodb/node_modules/mongodb-core/lib/topologies/server.js:119:3)
2016-06-06T18:17:55.386Z pid:2458 worker:3     at null.messageHandler (/var/lib/strong-pm/svc/1/work/a6e0bde254cbdedde6345bdf94e29e51828c5fa2.1465232211706/node_modules/loopback-connector-mongodb/node_modules/mongodb-core/lib/topologies/server.js:397:23)
2016-06-06T18:17:55.387Z pid:2458 worker:3     at Socket.<anonymous> (/var/lib/strong-pm/svc/1/work/a6e0bde254cbdedde6345bdf94e29e51828c5fa2.1465232211706/node_modules/loopback-connector-mongodb/node_modules/mongodb-core/lib/connection/connection.js:302:22)
2016-06-06T18:17:55.387Z pid:2458 worker:3     at emitOne (events.js:90:13)
2016-06-06T18:17:55.387Z pid:2458 worker:3     at Socket.emit (events.js:182:7)
2016-06-06T18:17:55.387Z pid:2458 worker:3     at readableAddChunk (_stream_readable.js:153:18)
2016-06-06T18:17:55.388Z pid:2458 worker:3     at Socket.Readable.push (_stream_readable.js:111:10)
2016-06-06T18:17:55.388Z pid:2458 worker:3     at TCP.onread (net.js:529:20)

Estou correndo o mongo 3.2, usando o mais recente driver nodeJs mongodb (node-mongodb-native 2.1.21) e framework de API strongloop (mais recente de qualquer componente e dependência relacionada)

O esquema de autenticação é SCRAM-SHA-1 sobre um replicaset de 2 (P / S) +1 (A)

Não é um problema de conexão nem de senha. está saindo do nada em um pool de conexões existente configurado pela estrutura da API

Alguém está experimentando algo semelhante?

    

Answer 1

Provavelmente é a regressão recente do driver de nó: link . Downgrade para 2.1.18.