search for: dbg_warn

Hello all, after the upgarde from Samba 4.10.7 to 4.11.2 we get lots of these in our logfiles: 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: [2019/11/28 20:40:44.886615, 1] ../../source3/locking/share_mode_lock.c:597(get_share_mode_lock) 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY There are no symptoms accept

...#39; 'get_share_mode_lock' The relevant part is this: ??? ??? status = get_static_share_mode_data( ??? ??? ??? static_share_mode_record, ??? ??? ??? id, ??? ??? ??? servicepath, ??? ??? ??? smb_fname, ??? ??? ??? old_write_time); ??? ??? if (!NT_STATUS_IS_OK(status)) { ??? ??? ??? DBG_WARNING("get_static_share_mode_data failed: %s\n", ??? ??? ??? ??? ??? nt_errstr(status)); ??? ??? ??? goto fail; ??? ??? } It calls 'get_static_share_mode_data' and the relevant part of that is this: ??? if (value.dptr == NULL) { ??? ??? d = fresh_share_mode_lock( ??? ??? ???...

...ant part is this: > > ??? ??? status = get_static_share_mode_data( > ??? ??? ??? static_share_mode_record, > ??? ??? ??? id, > ??? ??? ??? servicepath, > ??? ??? ??? smb_fname, > ??? ??? ??? old_write_time); > ??? ??? if (!NT_STATUS_IS_OK(status)) { > ??? ??? ??? DBG_WARNING("get_static_share_mode_data failed: %s\n", > ??? ??? ??? ??? ??? nt_errstr(status)); > ??? ??? ??? goto fail; > ??? ??? } > > It calls 'get_static_share_mode_data' and the relevant part > of that is this: > > ??? if (value.dptr == NULL) { > ??...

Hello Rawland, Thank you for your reply. We manage other zones other than the ad zone. These zones are stored in our AD (ldap). To do this, we have set up the named-sdb service which listens on 127.0.0.2. Samba AD forwards all DNS requests that do not match the AD domain zone to named-sdb. The problem is that these log errors only occur at 00:00:00 every day. Best Regards,