Hello everyone,
I have configured a community version 7.0.7 on Ubuntu 22.04.
When checking the logs, I noticed the following error appearing continuously:
{"t":{"$date":"2024-11-06T09:31:13.828-03:00"},"s":"I","c":"ACCESS","id":20436,"ctx":"conn19904","msg":"Checking authorization failed","attr":{"error":{"code":13,"codeName":"Unauthorized","errmsg":"not authorized on visitapp to execute command { collStats: \"system.profile\", maxTimeMS: 30000, lsid: { id: UUID(\"5ed068f5-7066-4867-bad1-e904164cb017\") }, $clusterTime: { clusterTime: Timestamp(1730896270, 1), signature: { hash: BinData(0, DFCA93327D59E1645FB5682ACBE1D0B7DF159C34), keyId: 7394444859068645383 } }, $db: \"visitapp\", $readPreference: { mode: \"primaryPreferred\" } }"}}
The thing is, this ‘visitapp’ database has already been dropped.
This error occurs on several different databases.
Does anyone have any idea what could be causing this? Or how to identify which user is facing the authentication failure?