samba - Nov 2024 - Slow reply to "smbclient -NL localhost" : strace

05.11.2024 12:36, Gilles via samba wrote:
> On 04/11/2024 15:11, Rowland Penny via samba wrote:
>> As I said previously, I do not think this has anything to do with
>> Samba. In an earlier post, you had this output when you ran the same
>> command using 'time':
>>
>> real??? 0m12.500s
>> user??? 0m0.732s
>> sys???? 0m0.102s
>>
>> The 'real' time is the total time it took to run the command,
but
>> 'user' + 'sys' is the actual time it took for the Samba
part of it, in
>> this case 0.834 seconds, the remaining 11.666 seconds is where your
>> problem lies, what is causing this ?
>> That is what you need to trace, what is getting in the way, it
doesn't
>> seem to be anything to do with Samba.
>>
>> When it comes down to it, your 'strace' appears to be useless
in this
>> context, there is no 'time' involved.
> 
> Thanks. So I'll look elsewhere to understand why that command is taking
so long.
Rowland gives unverified information here, and is
adding to the confusion and distracting attention
from actual problem to somewhere else.

time command shows *CPU* time spent in user space
or system space.  There, CPU time spent by the user
space is 0.7s, and in system is 0.1s.

But the rest of the time might be spent in any system
call which is waiting for something.

For example:

  $ time sleep 5
  real	0m5,001s
  user	0m0,001s
  sys	0m0,000s


If smbclient were just to run usleep() function, it will
show exactly the same behavior.

What's happening here, most likely, is that smbclient is
making some network calls and is waiting for the reply.

It might be a DNS problem or samba (configuration) problem,
depending on where and what it is waiting for.

And yes, this will be visible in the strace output.
> FWIW, there's no delay after I run it once? but only for a couple of
minutes.
This suggests it might be a name resolution issue.

/mjt

On 05/11/2024 18:16, Michael Tokarev wrote:
> If smbclient were just to run usleep() function, it will
> show exactly the same behavior.
>
> What's happening here, most likely, is that smbclient is
> making some network calls and is waiting for the reply.
>
> It might be a DNS problem or samba (configuration) problem,
> depending on where and what it is waiting for.
>
> And yes, this will be visible in the strace output.
>
>> FWIW, there's no delay after I run it once? but only for a couple
of
>> minutes.
>
> This suggests it might be a name resolution issue. 
What files could help find the source of the problem?

Here's the smb.conf:
==========[global]
workgroup = WORKGROUP
netbios name = SHEEVAPLUG

security = user
;added, but makes no difference
server role = standalone server

map to guest = Bad User
guest account = www-data

log level = 2

disable netbios = yes
client min protocol = SMB2_02
server min protocol = SMB2_02
smb ports = 445

printcap name = /dev/null
load printers = no
printing = bsd

[nginx]
path = /usr/share/nginx
;comment = No need for Unix/Samba passwords
guest ok = yes
writeable=yes
browseable=yes
create mode = 0644

[sdcard]
path = /mnt/sdcard
guest ok = yes
writeable=yes
browseable=yes
;don't work with vfat fs
;create mode = 0644 ; still -rw-r-xr-x
===========