MongoDB 7.0.22 is out and is ready for production deployment. This release contains only fixes since 7.0.21, and is a recommended upgrade for all 7.0 users.
Fixed in this release:
SERVER-95523 upsert does not handle DuplicateKey retry correctly
SERVER-95524 Avoid retrying on duplicate key error for upserts in multidocument transactions
SERVER-96197 ExpressionContext's _resolvedNamespaces can't distinguish between collections with the same name in different dbs
SERVER-98386 Shard does not correctly check the ShardVersion received for timeseries collections
Both on versions 7.0.22 and 8.0.10 where the same audit changes were done, audit stopped working.
Upon startup audit options on the mongod.cfg don’t get recognized but were working fine before:
This was the original config which doesn’t get recognized since these versions 7.0.22 and 8.0.10:
auditLog:
destination: syslog
filter: ‘{ atype: { $in: [ “authenticate” ] } }’
but it doesn’t work either with this:
auditLog:
filter: ‘{ atype: { $in: [ “authenticate” ] } }’
destination: file
format: JSON
path: “/apps/mongo/AFB1S/log/mongodb-AFB1S.audit.log”
It sounds like you’re running MongoDB Enterprise based on the usage of database auditing, which suggests you may have a support subscription. Assuming that is the case, could you open a support case with Customer Support via the support portal? They’d be able to assist with this.
If you don’t have a subscription, could you instead file a bug report following this guide?