Displaying 20 results from an estimated 6000 matches similar to: "Slow reply to "smbclient -NL localhost" : strace"
2024 Nov 04
1
Slow reply to "smbclient -NL localhost" : strace
On Sat, 2 Nov 2024 22:18:59 +0100
Gilles via samba <samba at lists.samba.org> wrote:
> Hello,
>
> In case it makes sense to someone in the list, here's the output of
> "strace smbclient -NL localhost", where it takes a good 10s to get
> the list of shares:
>
> https://pastebin.com/raw/Q5GPxBKW
>
> Could it be something missing in smb.conf?
>
2024 Nov 05
2
Slow reply to "smbclient -NL localhost" : strace
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
>
2024 Nov 05
1
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
2024 Nov 05
1
Slow reply to "smbclient -NL localhost" : strace
On Tue, 5 Nov 2024 10:36:49 +0100
Gilles via samba <samba at lists.samba.org> 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
2024 Nov 06
2
Slow reply to "smbclient -NL localhost" : strace
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.
2024 Nov 06
1
Slow reply to "smbclient -NL localhost" : strace
On 06/11/2024 08:04, Michael Tokarev wrote:
> Take a closer look at strace.? You've already noticed
> the recv() call takes a noticeable time, - find all of
> them.
>
> BTW, in your strace output you omitted some important
> pieces, for example, it isn't visible what FD#5 corresponds
> to, since you omitted its creation/open.
>
> The prob might not be the (host)
2024 Nov 05
1
Slow reply to "smbclient -NL localhost" : strace
On 05/11/2024 11:12, Rowland Penny via samba wrote:
> I took a look at your strace again and I noticed that the hostname was
> 'sheevaplug', now I can only really think of one reason why such a
> hostname would be used, if it was an actual Sheevaplug.
>
> If this is a Sheevaplug, then that could be your problem.
> From memory, the Sheevaplug had a single core ARM CPU,
2024 Nov 06
1
Slow reply to "smbclient -NL localhost" : strace
06.11.2024 08:59, Gilles via samba wrote:
>>> 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?
That's a strange question. Without understanding what the
actual problem is, it's hardly possible to point to the
2024 Nov 06
1
Slow reply to "smbclient -NL localhost" : strace
06.11.2024 12:32, Gilles via samba ?????:
> On 06/11/2024 08:04, Michael Tokarev wrote:
>> Take a closer look at strace.? You've already noticed
>> the recv() call takes a noticeable time, - find all of
>> them.
>>
>> BTW, in your strace output you omitted some important
>> pieces, for example, it isn't visible what FD#5 corresponds
>> to, since
2011 Feb 24
2
[1.4.39.2] Simple AGI doesn't reply
Hello
The following, dead simple Bash script ran as AGI doesn't reply to
Asterisk:
============= extensions.conf
[from_fxo]
exten => s,1,Wait(2)
exten => s,n,Set(CID=${CALLERID(num)})
exten => s,n,AGI(/var/tmp/basic.agi)
exten => s,n,Hangup()
============= /var/tmp/basic.agi
#!/bin/bash
#Ripped from
#http://lists.digium.com/pipermail/asterisk-users/2003-July/008554.html
while
2003 Sep 27
1
smbclient -L localhost fails
[root@cheezetoast samba] smbclient -L localhost
added interface ip=192.168.1.3 bcast=192.168.1.255 nmask=255.255.255.0
Password:
Anonymous login successful
Domain=[V-NET] OS=[UNIX] Server=[Samba 2.2.7a]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
All of the network configurations are correct. I've been searching the web
and old mail lists for a week now and need help. I'm running
2016 May 06
0
Error al ejecutar /usr/local/samba/bin/smbclient -L localhost -U%
I had the same error, but I believe that is why the way that if it
passed the User "root" which is not in AD, so try
/ Usr / local / samba / bin / smbclient -L localhost -UAdministrator
To min thus occurred success.
hug
Em 06-05-2016 00:30, Fausto Disla escreveu:
> Hola,
>
> Tod at s,
>
> Estoy tratando de instalar un DC con samba 4 y luego de crear el dominio
>
2019 Oct 29
0
AD domain member cannot authenticate user in remote forest unless smbclient uses "localhost"
On 29/10/2019 15:26, Nathaniel W. Turner via samba wrote:
> I see. =)
>
> I probably should have set the backend to autorid for "*", but I didn't
> think the ID mapping really mattered for the specific test I was doing.
From your point of view (multiple forests) 'autorid' will probably be
the way to go
>
> The "realm list" output shows the client
2019 Oct 29
0
AD domain member cannot authenticate user in remote forest unless smbclient uses "localhost"
On 29/10/2019 15:59, Nathaniel W. Turner via samba wrote:
> On Tue, Oct 29, 2019 at 11:43 AM Rowland penny via samba <
> samba at lists.samba.org> wrote:
>
>> A) You do not need 'realmd', 'sssd' etc
>>
> Understood. Using realmd is a convenience, as it automates some
> housekeeping, but I'm happy to take it out of the picture for the purposes
2019 Feb 20
1
samba installed but smbclient -L localhost -N fails
Hi,
Finally have samba installed in ubuntu 18.04. Ran dc setup..
Server Role: active directory domain controller
Hostname: dc1
NetBIOS Domain: REDACTED
DNS Domain: internal
DOMAIN SID: S-1-5-21-3313626214-3140439515-2095946098
smbstatus:
Samba version 4.7.6-Ubuntu
PID Username Group
Machine
2019 Oct 29
1
AD domain member cannot authenticate user in remote forest unless smbclient uses "localhost"
On Tue, Oct 29, 2019 at 5:37 AM Rowland penny via samba <
samba at lists.samba.org> wrote:
>
> If you require help setting up Unix domain members with winbind, can I
> suggest you read this:
>
> https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member
Well, I was not having problems with the actual process of joining using
"realm join
2019 Oct 29
2
AD domain member cannot authenticate user in remote forest unless smbclient uses "localhost"
Hi Rowland,
On Tue, Oct 29, 2019 at 5:37 AM Rowland penny via samba <
samba at lists.samba.org> wrote:
>
> I am sorry but you seem to be asking on the wrong list, you appear to be
> using sssd (which isn't supported with Samba from 4.8.0), Samba isn't
> doing the authentication.
>
What part of my problem description, or which log entries make you think I
am using
2010 Oct 18
8
Asterisk to switch on electric heaters remotely?
Hello
I'm sure someone has already tried this: I use a couple of electric
heaters to heat my office.
I'd like to somehow connect them to Asterisk so that I could switch
them on remotely by either calling the IVR or sending an e-mail to the
Asterisk host, so that the room is warm when I get to the office :-)
Any information appreciated.
Thank you.
2016 May 06
1
Error al ejecutar /usr/local/samba/bin/smbclient -L localhost -U%
You're right, Samba as member of an AD domain or Samba as AD DC are relying
on AD database to get its list of users. root user is not into AD database,
you can't use it to authenticate yourself against AD.
Note that you should be able to create a root user into AD database and
then you would be able to log with root against AD but I don't think this
is a good idea...
2016-05-06 16:56
2019 Oct 29
2
AD domain member cannot authenticate user in remote forest unless smbclient uses "localhost"
I see. =)
I probably should have set the backend to autorid for "*", but I didn't
think the ID mapping really mattered for the specific test I was doing.
The "realm list" output shows the client software as winbind (not sssd) and
the logs show messages from winbindd as it handles the authentication (in
the successful cases), so I think that indicates that winbind is in