I followed the following link to uninstall mongodb in my kali, however when pressing mongod on my terminal and enter it results dictionary like object. What does it mean and also in my /etc/passwd file i have the following user mongodb:x:133:65534::/nonexistent:/usr/sbin/nologin. should i remove the above line and what does the following terminal output mean?

I have multiple mongodb 6.0.14 replica sets running on aws hosted machines. Recently i have faced multiple mongo service crashes on different machines, with same error. Mongodb Logs showed a fatal error where WiredTiger was unable to rename .turtle file because it was in use by another process. But it doesn’t tell exactly which user or process was using that file. Windows events viewer also only tells that MongoDB service interrupted abruptly without further details.
I have gone through other threads online so my guess is it’s probably a AV scanner process interfering with mongodb process. But since there is a separate team that manages AV scanner processes. Is there any way i can locally check myself which process interferred with mongodb service?

I have multiple mongodb 6.0.14 replica sets running on aws hosted machines. Recently i have faced multiple mongo service crashes on different machines, with same error. Mongodb Logs showed a fatal error where WiredTiger was unable to rename .turtle file because it was in use by another process. But it doesn’t tell exactly which user or process was using that file. Windows events viewer also only tells that MongoDB service interrupted abruptly without further details.
I have gone through other threads online so my guess is it’s probably a AV scanner process interfering with mongodb process. But since there is a separate team that manages AV scanner processes. Is there any way i can locally check myself which process interferred with mongodb service?

I have multiple mongodb 6.0.14 replica sets running on aws hosted machines. Recently i have faced multiple mongo service crashes on different machines, with same error. Mongodb Logs showed a fatal error where WiredTiger was unable to rename .turtle file because it was in use by another process. But it doesn’t tell exactly which user or process was using that file. Windows events viewer also only tells that MongoDB service interrupted abruptly without further details.
I have gone through other threads online so my guess is it’s probably a AV scanner process interfering with mongodb process. But since there is a separate team that manages AV scanner processes. Is there any way i can locally check myself which process interferred with mongodb service?

I have multiple mongodb 6.0.14 replica sets running on aws hosted machines. Recently i have faced multiple mongo service crashes on different machines, with same error. Mongodb Logs showed a fatal error where WiredTiger was unable to rename .turtle file because it was in use by another process. But it doesn’t tell exactly which user or process was using that file. Windows events viewer also only tells that MongoDB service interrupted abruptly without further details.
I have gone through other threads online so my guess is it’s probably a AV scanner process interfering with mongodb process. But since there is a separate team that manages AV scanner processes. Is there any way i can locally check myself which process interferred with mongodb service?

const collection = await db.runCommand({ collMod: “Organization”, validator: { $jsonSchema: { bsonType: “object”, properties: { orgname: { bsonType: ‘string’, description: ‘string and required’ }, orgsite: { bsonType: “string”, description: ‘string and required’, }, workingarea: { bsonType: ‘string’, description: ‘string and required’ }, contact: { bsonType: ‘number’, description: “number and required”, // pattern: “^[6-9]d{9}$” }, owner: […]

const collection = await db.runCommand({ collMod: “Organization”, validator: { $jsonSchema: { bsonType: “object”, properties: { orgname: { bsonType: ‘string’, description: ‘string and required’ }, orgsite: { bsonType: “string”, description: ‘string and required’, }, workingarea: { bsonType: ‘string’, description: ‘string and required’ }, contact: { bsonType: ‘number’, description: “number and required”, // pattern: “^[6-9]d{9}$” }, owner: […]

const collection = await db.runCommand({ collMod: “Organization”, validator: { $jsonSchema: { bsonType: “object”, properties: { orgname: { bsonType: ‘string’, description: ‘string and required’ }, orgsite: { bsonType: “string”, description: ‘string and required’, }, workingarea: { bsonType: ‘string’, description: ‘string and required’ }, contact: { bsonType: ‘number’, description: “number and required”, // pattern: “^[6-9]d{9}$” }, owner: […]

const collection = await db.runCommand({ collMod: “Organization”, validator: { $jsonSchema: { bsonType: “object”, properties: { orgname: { bsonType: ‘string’, description: ‘string and required’ }, orgsite: { bsonType: “string”, description: ‘string and required’, }, workingarea: { bsonType: ‘string’, description: ‘string and required’ }, contact: { bsonType: ‘number’, description: “number and required”, // pattern: “^[6-9]d{9}$” }, owner: […]

Closed 3 days ago.