We are unable to connect to MongoDB using the username and password. Unfortunately, the password was changed, and even after setting a new one, authentication errors persist.
We explored various solutions found online, including removing the DB machine from the replica set and running it as a standalone instance. Even then, in no-auth mode, we were able to connect to the database.
We are currently taking a full dump of the database, but with its size being 1.8TB, the restoration process is taking a significant amount of time. Additionally, setting up a new machine in the new AWS account is further adding to the delay.
We are attaching logs from the primary of that set. and mongod logs.
2025-07-29T18:11:19.515+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Connecting to 000.00.00.000:27017
2025-07-29T18:11:19.515+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Failed to connect to 000.00.00.000:27017 - HostUnreachable: Connection refused
2025-07-29T18:11:19.515+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to 000.00.00.000:27017 due to failed operation on a connection
2025-07-29T18:11:19.515+0000 I REPL_HB [replexec-2] Error in heartbeat (requestId: 348) to 000.00.00.000:27017, response status: HostUnreachable: Connection refused
2025-07-29T18:11:19.515+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Failed to connect to 000.00.00.000:27017 - HostUnreachable: Connection refused
2025-07-29T18:11:19.515+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to 000.00.00.000:27017 due to failed operation on a connection
2025-07-29T18:11:19.515+0000 I REPL_HB [replexec-4] Error in heartbeat (requestId: 350) to 000.00.00.000:27017, response status: HostUnreachable: Connection refused
2025-07-29T18:11:19.643+0000 D TRACKING [monitoring keys for HMAC] Cmd: NotSet, TrackingId: trackingid
2025-07-29T18:11:19.844+0000 D TRACKING [monitoring keys for HMAC] Cmd: NotSet, TrackingId: trackingid
2025-07-29T18:11:20.045+0000 D TRACKING [monitoring keys for HMAC] Cmd: NotSet, TrackingId: trackingid
monogdb.log file
2025-07-29T17:03:25.238+0000 I ACCESS [conn163] SCRAM-SHA-1 authentication failed for __system on local from client 00.000.0.000:49348 ; AuthenticationFailed: It is not possible to authenticate as the __system user on servers started without a --keyFile parameter
2025-07-29T17:03:25.261+0000 I NETWORK [conn163] end connection 00.000.0.000:49348 (0 connections now open)
2025-07-29T17:03:25.361+0000 I NETWORK [listener] connection accepted from 00.000.0.00:39460 #164 (1 connection now open)
2025-07-29T17:03:25.361+0000 I NETWORK [conn164] received client metadata from 00.000.0.00:39460 conn: { driver: { name: "NetworkInterfaceASIO-Replication", version: "3.6.3" }, os: { type: "Linux", name: "Ubuntu", architecture: "x86_64", version: "18.04" } }
2025-07-29T17:03:25.361+0000 I NETWORK [listener] connection accepted from 00.000.0.000:32916 #165 (2 connections now open)
2025-07-29T17:03:25.361+0000 I NETWORK [conn165] received client metadata from 00.000.0.000:32916 conn: { driver: { name: "NetworkInterfaceASIO-Replication", version: "3.6.3" }, os: { type: "Linux", name: "Ubuntu", architecture: "x86_64", version: "18.04" } }
2025-07-29T17:03:25.383+0000 I ACCESS [conn165] SCRAM-SHA-1 authentication failed for __system on local from client 00.000.0.000:32916 ; AuthenticationFailed: It is not possible to authenticate as the __system user on servers started without a --keyFile parameter
2025-07-29T17:03:25.384+0000 I ACCESS [conn164] SCRAM-SHA-1 authentication failed for __system on local from client 00.000.0.00:39460 ; AuthenticationFailed: It is not possible to authenticate as the __system user on servers started without a --keyFile parameter
2025-07-29T17:03:25.405+0000 I NETWORK [conn165] end connection 00.000.0.000:32916 (1 connection now open)
2025-07-29T17:03:25.407+0000 I NETWORK [conn164] end connection 00.000.0.00:39460 (0 connections now open)
monogd.log file