Rocket chat generates continuous errors on mongodb arbiter that the user doesn't exist. How to fix this?

Description

Hi,

Rocket chat generates continuous errors in mongodb arbiter that the user doesn’t exist.

2019-10-13T18:55:30.047-0400 I ACCESS [conn17785627] SASL SCRAM-SHA-1 authentication failed for rcuser-inst1 on rocket-inst1 from client <ip>:35528 ; UserNotFound: Could not find user rcuser-inst1@rocket-inst1

Yes, the user doesn’t exist on mongo db arbiter, but exist on the main database. I don’t understand if my rocket chat configuration is wrong or if my arbiter setup is wrong. Please suggest.

Server Setup Information

  • Version of Rocket.Chat Server: 1.2.0
  • Operating System: Centos - 7
  • Deployment Method: Source Code
  • Number of Running Instances: 13
  • DB Replicaset Oplog: Yes
  • NodeJS Version: v8.11.4
  • MongoDB Version: 4.0.11
  • Proxy: nginx
  • Firewalls involved: No

Any additional Information

      MONGO_URL="mongodb://${RC_MONGO_USR}:${RC_MONGO_PWD}@${MONGO_NODE1}:27017,${MONGO_NODE2}:27017/${RC_MONGO_DBNAME}?replicaSet=${RC_MONGO_REPLICA}&readPreference=primary"
MONGO_OPLOG_URL="mongodb://${RC_MONGO_USR}:${RC_MONGO_PWD}@${MONGO_NODE1}:27017,${MONGO_NODE2}:27017/local?authSource=${RC_MONGO_DBNAME}&replicaSet=${RC_MONGO_REPLICA}"