Displaying 9 results from an estimated 9 matches for "fresh_share_mode_lock".
2019 Nov 14
6
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
...STATUS_NO_MEMORY
A lot. I modified the source in source3/locking/share_mode_lock.c a bit in order to print out the values of the service path, smb_fname & old_write_time when it fails and it seems they are all NULL?
[2019/11/14 14:24:23.358441, 0] ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock)
servicepath=0x0, smb_fname=0x0, old_write_time=0x0
[2019/11/14 14:24:23.358965, 1] ../../source3/locking/share_mode_lock.c:598(get_share_mode_lock)
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
fresh_share_mode_lock() only get?s called from get_static_share_mod...
2019 Nov 03
1
[smbd] get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
...current version (but w older too)
> # smbd -V
> Version 4.11.2
>
> client - macos, (time machine session).
> where can i add this memory?
I don't think it is actually memory, but some more logs would help. If
talloc actually fails then it would say "talloc failed" in
fresh_share_mode_lock().
Can you check that for me?
Assuming it doesn't say that, then the conditions for returning
N_STATUS_NO_MEMORY from fresh_share_mode_lock() and
so get_static_share_mode_data() are:
if ((servicepath == NULL) || (smb_fname == NULL) ||
(old_write_time == NULL)) {
return NULL;
}
Non...
2019 Nov 14
0
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
...source in
> source3/locking/share_mode_lock.c a bit in order to print out
> the values of the service path, smb_fname & old_write_time
> when it fails and it seems they are all NULL?
>
>
> [2019/11/14 14:24:23.358441, 0]
> ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock)
> servicepath=0x0, smb_fname=0x0, old_write_time=0x0
> [2019/11/14 14:24:23.358965, 1]
> ../../source3/locking/share_mode_lock.c:598(get_share_mode_lock)
> get_share_mode_lock: get_static_share_mode_data failed:
> NT_STATUS_NO_MEMORY
>
>
> fresh_share_mode_lock() o...
2019 Nov 15
0
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
...ified the source in source3/locking/share_mode_lock.c a bit in
> order to print out the values of the service path, smb_fname &
> old_write_time when it fails and it seems they are all NULL?
>
>
> [2019/11/14 14:24:23.358441, 0]
> ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock)
> servicepath=0x0, smb_fname=0x0, old_write_time=0x0
> [2019/11/14 14:24:23.358965, 1]
> ../../source3/locking/share_mode_lock.c:598(get_share_mode_lock)
> get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
>
>
> fresh_share_mode_lock() only get?s c...
2019 Nov 29
4
get_share_mode_lock:, get_static_share_mode_data failed: NT_STATUS_NO_MEMORY with Samba 4.11.2
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
2019 Nov 14
1
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
.../locking/share_mode_lock.c a bit in order to print out
>> the values of the service path, smb_fname & old_write_time
>> when it fails and it seems they are all NULL?
>>
>>
>> [2019/11/14 14:24:23.358441, 0]
>> ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock)
>> servicepath=0x0, smb_fname=0x0, old_write_time=0x0
>> [2019/11/14 14:24:23.358965, 1]
>> ../../source3/locking/share_mode_lock.c:598(get_share_mode_lock)
>> get_share_mode_lock: get_static_share_mode_data failed:
>> NT_STATUS_NO_MEMORY
>>
>>
>...
2019 Nov 29
0
get_share_mode_lock:, get_static_share_mode_data failed: NT_STATUS_NO_MEMORY with Samba 4.11.2
..._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(
??? ??? ??? lock_db, servicepath, smb_fname, old_write_time);
??? ??? if (d == NULL) {
??? ??? ??? return NT_STATUS_NO_MEMORY;
??? ??? }
Which I hope you can see, is saying that it cannot find the share
record, this isn't an actual error.
It has also been fixed in Samba git, see here:...
2019 Nov 29
0
get_share_mode_lock:, get_static_share_mode_data failed: NT_STATUS_NO_MEMORY with Samba 4.11.2
...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(
> ??? ??? ??? lock_db, servicepath, smb_fname, old_write_time);
> ??? ??? if (d == NULL) {
> ??? ??? ??? return NT_STATUS_NO_MEMORY;
> ??? ??? }
>
> Which I hope you can see, is saying that it cannot find the share
> record, this isn't an actual error.
>
> It...
2019 Nov 02
7
suddenly change: idmap uid + gid
Hi
The server suddenly changed the uid + gid. this happened to times,
yesterday and the week after. The default group at example
The samba is a AD member where we have many users (>20 000) and we use
autorid in that way
[global]
security = ads
workgroup = CUSTOMER
realm = CUSTOMER.COM
winbind use default domain = yes
winbind enum users = yes
winbind enum group = yes