Displaying 10 results from an estimated 10 matches for "old_write_time".
2019 Nov 14
6
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
Upgraded to Samba 4.11.2 and I?ve now too started seeing the message:
	get_share_mode_lock: get_static_share_mode_data failed: NT_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)...
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
0
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
...I?ve now too started seeing the message:
> 
> 	get_share_mode_lock: get_static_share_mode_data failed: 
> NT_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/...
2019 Nov 15
0
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
....2 and I?ve now too started seeing the message:
> 
> 	get_share_mode_lock: get_static_share_mode_data failed: 
NT_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...
2019 Nov 29
0
get_share_mode_lock:, get_static_share_mode_data failed: NT_STATUS_NO_MEMORY with Samba 4.11.2
...t an error ;-)
If you look at '/source3/locking/share_mode_lock.c' '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....
2019 Nov 29
0
get_share_mode_lock:, get_static_share_mode_data failed: NT_STATUS_NO_MEMORY with Samba 4.11.2
...g/share_mode_lock.c' 
> '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 par...
2019 Nov 03
1
[smbd] get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
...quot;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;
	}
None of these are memory related, confusingly. 
The full smb.conf Rowland asked for might help.
Otherwise, if you are confident and if you have self-compiled this then
if you can patch in a smb_panic() rather than the return NULL, and
catch it under gdb when it pani...
2019 Nov 14
1
get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY
...the message:
>> 
>> 	get_share_mode_lock: get_static_share_mode_data failed: 
>> NT_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]...
2018 Oct 16
2
high cpu load with share_conflict on browsing and opening files
...x0264a327 (40149799)
                  stale                    : 0x00 (0)
                  lease                    : NULL
          num_leases               : 0x00000000 (0)
          leases: ARRAY(0)
          num_delete_tokens        : 0x00000000 (0)
          delete_tokens: ARRAY(0)
          old_write_time           : gio gen  1 01:00:00 1970 CET.0
          changed_write_time       : gio gen  1 01:00:00 1970 CET.0
          fresh                    : 0x00 (0)
          modified                 : 0x01 (1)
          record                   : *
          id: struct file_id
              devid...
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