Re: Problem with smbclient for Samba 4
Am 2018-07-02 um 08:28 schrieb Olivier: > Hi, > > Since I upgraded to Samba 4, I cannot backyp my Windows machine. > > Poking around, the command used by Amanda sendsize is: > > Mon Jul 2 00:14:39 2018: thd-0x805422c00: sendsize: Spawning > "/usr/bin/smbclient smbclient "olivier\\drivec" -d 0 -U backup -E -W > olivier -c "archive 1;recurse;du"" in pipeline > > When I try the following command in Samba 3, it works, but not in Samba > 4: > > smbclient "olivier\\drivec" -d 0 -U backup -E -W olivier -c "archive > 1;recurse;du" > > If I use single back-slash or no double-quote in Samba 4, it works. > > The error is NT_STATUS_UNSUCCESSFUL Try the command yourself on the shell and use "-d3" or higher to see the debug details.
Re: Problem with smbclient for Samba 4
"Stefan G. Weichinger" writes: > Am 2018-07-02 um 08:28 schrieb Olivier: >> Hi, >> >> Since I upgraded to Samba 4, I cannot backyp my Windows machine. >> >> Poking around, the command used by Amanda sendsize is: >> >> Mon Jul 2 00:14:39 2018: thd-0x805422c00: sendsize: Spawning >> "/usr/bin/smbclient smbclient "olivier\\drivec" -d 0 -U backup -E -W >> olivier -c "archive 1;recurse;du"" in pipeline >> >> When I try the following command in Samba 3, it works, but not in Samba >> 4: >> >> smbclient "olivier\\drivec" -d 0 -U backup -E -W olivier -c "archive >> 1;recurse;du" >> >> If I use single back-slash or no double-quote in Samba 4, it works. >> >> The error is NT_STATUS_UNSUCCESSFUL > > Try the command yourself on the shell and use "-d3" or higher to see the > debug details. $ smbclient "olivier\\drivec" -d 3 -U backup -E -W olivier -c "archive 1;recurse;du" lp_load_ex: refreshing parameters Initialising global parameters Processing section "[global]" added interface nfe0 ip=192.41.170.11 bcast=192.41.170.255 netmask=255.255.255.0 added interface nfe1 ip=10.41.170.11 bcast=10.41.170.255 netmask=255.255.255.0 Client started (version 4.6.15). resolve_lmhosts: Attempting lmhosts lookup for name <0x20> resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name <0x20> resolve_hosts: getaddrinfo failed for name [hostname nor servname provided, or not known] name_resolve_bcast: Attempting broadcast lookup for name <0x20> Connection to failed (Error NT_STATUS_UNSUCCESSFUL) And the working one: $ smbclient "\\olivier\drivec" -d 3 -U backup -E -W olivier -c "archive 1;recurse;du" lp_load_ex: refreshing parameters Initialising global parameters Processing section "[global]" added interface nfe0 ip=192.41.170.11 bcast=192.41.170.255 netmask=255.255.255.0 added interface nfe1 ip=10.41.170.11 bcast=10.41.170.255 netmask=255.255.255.0 Client started (version 4.6.15). resolve_lmhosts: Attempting lmhosts lookup for name olivier<0x20> resolve_wins: WINS server resolution selected and no WINS servers listed. resolve_hosts: Attempting host lookup for name olivier<0x20> Connecting to 192.41.170.57 at port 445 Thank ou, Olivier --
Re: Problem with smbclient for Samba 4
Am 2018-07-02 um 09:22 schrieb Olivier: > "Stefan G. Weichinger" writes: >> Try the command yourself on the shell and use "-d3" or higher to see the >> debug details. See the difference -> > resolve_lmhosts: Attempting lmhosts lookup for name <0x20> > resolve_wins: WINS server resolution selected and no WINS servers listed. > resolve_hosts: Attempting host lookup for name <0x20> > resolve_lmhosts: Attempting lmhosts lookup for name olivier<0x20> > resolve_wins: WINS server resolution selected and no WINS servers listed. > resolve_hosts: Attempting host lookup for name olivier<0x20> The failing command seems to look up an empty string ... (no "olivier" in first call). But both of your calls say: "Client started (version 4.6.15)" So the picture is a bit fuzzy. You want to backup using the 4.x-smbclient and/or a share on a 4.x-server?
Re: Problem with smbclient for Samba 4
"Stefan G. Weichinger" writes:
> Am 2018-07-02 um 09:22 schrieb Olivier:
>> "Stefan G. Weichinger" writes:
>>> Try the command yourself on the shell and use "-d3" or higher to see the
>>> debug details.
>
> See the difference ->
>
>> resolve_lmhosts: Attempting lmhosts lookup for name <0x20>
>> resolve_wins: WINS server resolution selected and no WINS servers listed.
>> resolve_hosts: Attempting host lookup for name <0x20>
>
>> resolve_lmhosts: Attempting lmhosts lookup for name olivier<0x20>
>> resolve_wins: WINS server resolution selected and no WINS servers listed.
>> resolve_hosts: Attempting host lookup for name olivier<0x20>
>
> The failing command seems to look up an empty string ... (no "olivier"
> in first call).
I agree, but in both cases, I use the same smbclient command and version
(the one on Amanda server). The only difference being I once specify the
share as "olivier\\drivec" and the other time I use
"\\olivier\drivec".
The first form is not working, this is the form cut and pasted from
Amanda log file. The second form is working.
So to me, it looks like that the syntax used by Amanda
("olivier\\drivec"), that was working fine with Samba 3.x is not
workihg anymore with Samba 4.x
>
> But both of your calls say:
>
> "Client started (version 4.6.15)"
>
> So the picture is a bit fuzzy.
>
> You want to backup using the 4.x-smbclient and/or a share on a 4.x-server?
I want to use 4.x-smbclient to back-up an WinXP machine (if is was a
4.x-server, it would be a Unix system, it would be easy :)
Thank you,
Olivier
--
Re: Weird amdump behavior
Are you using “localhost” as a node name? Perhaps you could try using a “fully qualified domain name” instead, in your disklist file and everywhere. I’ve heard issues with “localhost” in the past. Deb Baddorf Fermilab > On Jul 1, 2018, at 9:59 AM, Kamil Jońca wrote: > > kjo...@o2.pl (Kamil Jońca) writes: > >> Recently I noticed weird behavior of amdump. >> >> I have several localhost DLEs. >> >> When I call >> >> sudo -u backup amdump --no-taper alfa localhost >> >> everything goes ok. >> also >> >> sudo -u backup amdump --no-taper alfa laptop.kjonca >> >> works as expected and backup my laptop >> >> but when I call >> >> sudo -u backup amdump --no-taper alfa >> >> I got >> ERROR planner Request to localhost failed: timeout waiting for ACK >> >> What should I check/change? >> KJ > > Unfortunately this issue still persists. Any hints? > KJ > -- > http://wolnelektury.pl/wesprzyj/teraz/ > It was pity stayed his hand. > "Pity I don't have any more bullets," thought Frito. > -- _Bored_of_the_Rings_, a Harvard Lampoon parody of Tolkein >
Re: Weird amdump behavior
Debra S Baddorf writes: > Are you using “localhost” as a node name? Perhaps you could try > using a “fully qualified domain name” instead, in your disklist file > and everywhere. I’ve heard issues with “localhost” in the past. > > Deb Baddorf > Fermilab > > >> On Jul 1, 2018, at 9:59 AM, Kamil Jońca wrote: >> >> kjo...@o2.pl (Kamil Jońca) writes: >> >>> Recently I noticed weird behavior of amdump. >>> >>> I have several localhost DLEs. >>> >>> When I call >>> >>> sudo -u backup amdump --no-taper alfa localhost >>> >>> everything goes ok. >>> also >>> >>> sudo -u backup amdump --no-taper alfa laptop.kjonca >>> >>> works as expected and backup my laptop >>> >>> but when I call >>> >>> sudo -u backup amdump --no-taper alfa >>> >>> I got >>> ERROR planner Request to localhost failed: timeout waiting for ACK >>> >>> What should I check/change? >>> KJ It is worse I think. I make some calls to amdump recently, and some of these calls ended sucessfully. So we have two scenarios: 1. amdump ends with success 2. amdump ends with error, adn all localhost DLEs have estimate failed. Another thing: when amdump fails there is hanging alone planner process. It seems like race condition here. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html Unprovided with original learning, unformed in the habits of thinking, unskilled in the arts of composition, I resolved to write a book. -- Edward Gibbon
