amsamba with current smbclient: unrecognised option quiet
On a Debian 10.6 backup server with samba-4.12.8 I get these warnings: /-- srv01 my-dle lev 1 STRANGE sendbackup: info BACKUP=APPLICATION sendbackup: info APPLICATION=amsamba sendbackup: info RECOVER_CMD=/usr/lib/amanda/application/amsamba restore [./file-to-restore]+ sendbackup: info end ? smbclient: tarmode: unrecognised option quiet ? smbclient: tar: dumped 0 files and 0 directories sendbackup: size 32 sendbackup: native-CRC 6b21b321:10240 sendbackup: client-CRC 6b21b321:10240 sendbackup: end \ Does anyone else see this? Seems like smbclient doesn't support that option "quiet" anymore, I will try to check that. A grep shows that this is set in lines 646 and 648 of amsamba.pl ... either I patch it there or there is a way to override it somewhere else?
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 29.06.20 um 19:19 schrieb Stefan G. Weichinger: >> I tried: >> >> next if /^Unable to initialize messaging context/g; >> >> next if /Unable to initialize messaging context/g; >> >> next if /Unable to initialize messaging context/; > > Did someone solve this? > > I get it again today on a fresh Debian 10.4 installation. > > Maybe I have to use a non-standard samba from another repo (I have an > idea ...) samba-4.10.15 from the van-belle repo https://apt.van-belle.nl/ solved this. nice
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 06.01.19 um 10:53 schrieb Stefan G. Weichinger: > Am 05.01.19 um 00:31 schrieb Uwe Menges: >> On 1/4/19 7:51 PM, Stefan G. Weichinger wrote: >>> I couldn't find a way to exclude/ignore such messages from smbclient >>> within amsamba. And browsing the script itself it wasn't clear to me >>> non-coder how and where to add that. >> >> I'm not able to test that, my perl is rusty, I didn't take a close look, >> yadda yadda.. >> >> Try to add to amsamba after both (L433 + L521): >> next if /^WARNING/g; >> +next if /^Unable to initialize messaging context/g; >> >> Or if the message doesn't really start at first column, omit the ^. > > Thanks for the suggestion, I tried three variations now without success. > Always the warning in the email reports. > > I tried: > > next if /^Unable to initialize messaging context/g; > > next if /Unable to initialize messaging context/g; > > next if /Unable to initialize messaging context/; Did someone solve this? I get it again today on a fresh Debian 10.4 installation. Maybe I have to use a non-standard samba from another repo (I have an idea ...)
Re: smbclient
Hi, Just a little update about this issue, L ORIG-GB 0 68 0 121 1 27 1 26 So the level 1 is smaller. Cheers, Nuno On Thu, 2020-04-23 at 08:46 -0400, Nathan Stratton Treadway wrote: > On Thu, Apr 23, 2020 at 10:40:25 +0100, Nuno Dias wrote: > > The "estimate server" solved the problem, definitely the amsamba > > don't > > like in the estimate the NT_STATUS_ACCESS_DENIED even when is not > > in > > the PATH. > > So, with "estimate server" the backup was able to complete the full > dump > phase successfully? > > It would be interesting to know if there are any NT_STATUS errors in > the > Amsamba logs for that successfully run and also to hear if the > second day's (level 1) backup is actually smaller than the full dump, > as > expected. > > > Nathan > > --- > - > Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic > region > Ray Ontko & Co. - Software consulting services - > http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: > 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 -- Nuno Dias LIP
Re: smbclient
Yes, the full dump was successful, and yes, there are still NT_STATUS errors in the logs, but seems this is only critical for the estimate fase when the estimate is on the client. For the level 1 I need to wait a few more days. Cheers, Nuno On Thu, 2020-04-23 at 08:46 -0400, Nathan Stratton Treadway wrote: > On Thu, Apr 23, 2020 at 10:40:25 +0100, Nuno Dias wrote: > > The "estimate server" solved the problem, definitely the amsamba > > don't > > like in the estimate the NT_STATUS_ACCESS_DENIED even when is not > > in > > the PATH. > > So, with "estimate server" the backup was able to complete the full > dump > phase successfully? > > It would be interesting to know if there are any NT_STATUS errors in > the > Amsamba logs for that successfully run and also to hear if the > second day's (level 1) backup is actually smaller than the full dump, > as > expected. > > > Nathan > > --- > - > Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic > region > Ray Ontko & Co. - Software consulting services - > http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: > 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 -- Nuno Dias LIP
Re: smbclient
On Thu, Apr 23, 2020 at 10:40:25 +0100, Nuno Dias wrote: > The "estimate server" solved the problem, definitely the amsamba don't > like in the estimate the NT_STATUS_ACCESS_DENIED even when is not in > the PATH. So, with "estimate server" the backup was able to complete the full dump phase successfully? It would be interesting to know if there are any NT_STATUS errors in the Amsamba logs for that successfully run and also to hear if the second day's (level 1) backup is actually smaller than the full dump, as expected. Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: smbclient
First of all big thanks for everyone help and suggestions. The "estimate server" solved the problem, definitely the amsamba don't like in the estimate the NT_STATUS_ACCESS_DENIED even when is not in the PATH. Cheers, Nuno On Tue, 2020-04-21 at 11:10 -0400, Nathan Stratton Treadway wrote: > On Tue, Apr 21, 2020 at 13:06:13 +0100, Nuno Dias wrote: > > I tried everything, I'm using the Administrator user in windows > > 10, I > > check and he has the rights to do everything, nevertheless in > > smbclient > > I have several ERRORS saying "NT_STATUS_ACCESS_DENIED listing" this > > is > > system files or system directories. > > > > The backup I want to do is the users directories, and I can read > > that > > directories and files, it seems amanda fails because of the > > previous > > ERRORS. > > > > Even if I put something like this //pcwindows/c$/Users/user/files > > and > > I'm positive that I can read these dir and files, I still have > > error > > in //pcwindows/c$/Progranas > > NT_STATUS_ACCESS_DENIED listing \Programas\* > > > > And this is not in the PATH of the backup :( > > Yeah, that does seem wierd :( > > It may be that the estimate phase inadvertently tries to access files > that are outside the specified directory tree, or something. (In my > case we are only backing up "data file" shares on the Windows PC, so > the > system directories are not included anywhere on the shares in > question.) > > Windows clients are definitely not my strong point, but if you want > you > could go ahead and send me (off-list) the Amsamba.*debug file that > corresponds to the failed estimate (and probably your amanda.conf and > disklist files too) and I can see if I can determine anything by > comparing that with the logs from my working system > > The other thing that just occurred to me is that if it seems like its > the estimate phase that is failing, you could trying adding "estimate > server" to the amsamba dumptype to see if that at least allows Amanda > to > proceed to the dumping phase. > > > Nathan > > --- > - > Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic > region > Ray Ontko & Co. - Software consulting services - > http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: > 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 -- Nuno Dias LIP
Re: smbclient
On Tue, Apr 21, 2020 at 01:06:13PM +0100, Nuno Dias wrote: > Hi, > > I tried everything, I'm using the Administrator user in windows 10, I > check and he has the rights to do everything, nevertheless in smbclient > I have several ERRORS saying "NT_STATUS_ACCESS_DENIED listing" this is > system files or system directories. > > The backup I want to do is the users directories, and I can read that > directories and files, it seems amanda fails because of the previous > ERRORS. > > Even if I put something like this //pcwindows/c$/Users/user/files and > I'm positive that I can read these dir and files, I still have error > in //pcwindows/c$/Progranas > NT_STATUS_ACCESS_DENIED listing \Programas\* > > And this is not in the PATH of the backup :( Putting on my "way back hat". I recall problems backing up Windows due to it refusal to allow multiple processes to access the same file simultaneously. The work-around that M$ introduced was called, I think, Volume Shadow Copy (VSC?). The Zmanda windows client (again I think) uses VSC to overcome this deficiency in M$ file systems. Might smbclient be bumping up against this M$ limitation? Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: smbclient
On Tue, Apr 21, 2020 at 13:06:13 +0100, Nuno Dias wrote: > I tried everything, I'm using the Administrator user in windows 10, I > check and he has the rights to do everything, nevertheless in smbclient > I have several ERRORS saying "NT_STATUS_ACCESS_DENIED listing" this is > system files or system directories. > > The backup I want to do is the users directories, and I can read that > directories and files, it seems amanda fails because of the previous > ERRORS. > > Even if I put something like this //pcwindows/c$/Users/user/files and > I'm positive that I can read these dir and files, I still have error > in //pcwindows/c$/Progranas > NT_STATUS_ACCESS_DENIED listing \Programas\* > > And this is not in the PATH of the backup :( Yeah, that does seem wierd :( It may be that the estimate phase inadvertently tries to access files that are outside the specified directory tree, or something. (In my case we are only backing up "data file" shares on the Windows PC, so the system directories are not included anywhere on the shares in question.) Windows clients are definitely not my strong point, but if you want you could go ahead and send me (off-list) the Amsamba.*debug file that corresponds to the failed estimate (and probably your amanda.conf and disklist files too) and I can see if I can determine anything by comparing that with the logs from my working system The other thing that just occurred to me is that if it seems like its the estimate phase that is failing, you could trying adding "estimate server" to the amsamba dumptype to see if that at least allows Amanda to proceed to the dumping phase. Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: smbclient
Hi, I tried everything, I'm using the Administrator user in windows 10, I check and he has the rights to do everything, nevertheless in smbclient I have several ERRORS saying "NT_STATUS_ACCESS_DENIED listing" this is system files or system directories. The backup I want to do is the users directories, and I can read that directories and files, it seems amanda fails because of the previous ERRORS. Even if I put something like this //pcwindows/c$/Users/user/files and I'm positive that I can read these dir and files, I still have error in //pcwindows/c$/Progranas NT_STATUS_ACCESS_DENIED listing \Programas\* And this is not in the PATH of the backup :( Cheers, Nuno On Mon, 2020-04-20 at 18:05 -0400, Nathan Stratton Treadway wrote: > On Sat, Apr 18, 2020 at 11:44:18 +0100, Nuno Dias wrote: > > Hi, > > > > The OS is Fedora 30 with amanda-3.5.1-19.fc30.x86_64 and samba- > > client-4.10.14-0.fc30.x86_64 (this are the packages from the OS). > > > > The error that I have is accessing some files, > > > > ERROR smbclient: NT_STATUS_ACCESS_DENIED listing > > Windows\\System32\\config\\systemprofile\\AppData\\Local\\Microsoft > > \\Wi > > ndows\\INetCache\\Content.IE5\\*" > > > > Can this be the reason all the estimates fails? > > Yes, it could be (though I would expect to see a more explict failure > message from the estimate phase later on in the log file if that were > the case). > > You will certainly need to connect to your Windows client using a > username which has sufficient permissions to read all files, and also > to > update the "archive bit" on the backed-up files so that level 1 dumps > work as expected. > > I haven't delived into the nuances of NTFS permissions and have only > gone through this on a single windows client machine, but in my > experimentation I found that setting the following permissions using > Server Manager for the particular shares in question produced a > working > level-1 backup with no error messages in the log, while also at least > preventing obvious editing of the share by the backup user : > permissions (for the smbclient user) enabled: > "Read & exectue", > "List folder contents", > "Read" > > Advanced Attributes enabled: > "Traverse folder/execute file", > "List folder/read data", > "Read attributes", > "Read extended attributes", > "Read permissions" > "Write attributes" > > (On this particular client box, then Sharing tab already had "Full > Control" granted to Everyone, so I did not have to fine-tune the > settings there to get Amanda working.) > > Hope that is at least somewhat helpful... > > > Nathan > > --- > - > Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic > region > Ray Ontko & Co. - Software consulting services - > http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: > 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 -- Nuno Dias LIP
Re: smbclient
Hi Diego,
Unfortunately your patch didn't solve my problem.
But thanks for replying.
Cheers,
Nuno
On Tue, 2020-04-21 at 08:01 +0200, Diego Zuccato wrote:
> Il 17/04/20 20:51, Nuno Dias ha scritto:
>
> > I'm trying to use the amsamba plugin, put fails everytime in the
> > estimate.
> Probably unrelated, but...
>
> > A search in google got me some results saying that some time ago
> > the
> > samba version 4.x was incompatible with amanda, anyone knows if
> > this is
> > still true?
> I have had to apply this patch:
>
> root@nas1:/usr/lib/amanda/application# diff -u amsamba.ori amsamba
> --- amsamba.ori 2019-07-16 09:09:28.430585521 +0200
> +++ amsamba 2019-07-18 10:44:37.257853728 +0200
> @@ -462,6 +462,7 @@
> debug("stderr: " . $_);
> next if /^Domain=/;
> next if /^WARNING/g;
> + next if /^Unable to initialize messaging context/;
> # message if samba server is configured with 'security = share'
> next if /Server not using user level security and no password
> supplied./;
> $self->print_to_server("smbclient: $_",
> @@ -554,6 +555,7 @@
> next if /^Domain=/;
> next if /dumped \d+ files and directories/;
> next if /^WARNING/g;
> + next if /^Unable to initialize messaging context/;
> # message if samba server is configured with 'security = share'
> next if /Server not using user level security and no password
> supplied./;
> debug("stderr: $_");
> @@ -758,6 +760,7 @@
> return if $line =~ /tarmode is now /;
> return if $line =~ /tar_re_search set/;
> return if $line =~ /WARNING/g;
> + return if $line =~ /^Unable to initialize messaging context/;
> if ($line =~ /dumped (\d+) files and directories/) {
> $nb_files = $1;
> return;
>
--
Nuno Dias
LIP
Re: smbclient
Il 17/04/20 20:51, Nuno Dias ha scritto:
> I'm trying to use the amsamba plugin, put fails everytime in the
> estimate.
Probably unrelated, but...
> A search in google got me some results saying that some time ago the
> samba version 4.x was incompatible with amanda, anyone knows if this is
> still true?
I have had to apply this patch:
root@nas1:/usr/lib/amanda/application# diff -u amsamba.ori amsamba
--- amsamba.ori 2019-07-16 09:09:28.430585521 +0200
+++ amsamba 2019-07-18 10:44:37.257853728 +0200
@@ -462,6 +462,7 @@
debug("stderr: " . $_);
next if /^Domain=/;
next if /^WARNING/g;
+ next if /^Unable to initialize messaging context/;
# message if samba server is configured with 'security = share'
next if /Server not using user level security and no password
supplied./;
$self->print_to_server("smbclient: $_",
@@ -554,6 +555,7 @@
next if /^Domain=/;
next if /dumped \d+ files and directories/;
next if /^WARNING/g;
+ next if /^Unable to initialize messaging context/;
# message if samba server is configured with 'security = share'
next if /Server not using user level security and no password
supplied./;
debug("stderr: $_");
@@ -758,6 +760,7 @@
return if $line =~ /tarmode is now /;
return if $line =~ /tar_re_search set/;
return if $line =~ /WARNING/g;
+ return if $line =~ /^Unable to initialize messaging context/;
if ($line =~ /dumped (\d+) files and directories/) {
$nb_files = $1;
return;
--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
Re: smbclient
On Mon, Apr 20, 2020 at 18:29:13 +0100, Nuno Dias wrote: > So, after countless hours with this issue without success, let me ask > the community about smbtar. > > Can I use smbtar with amanda? if yes how? do I need to write a new > plugin? > (At least here on my Ubuntu system, smbtar is just a wrapper shell script around smbclient, so I doubt that adding that level of indirection into the pipeline Amanda is trying to execute would make things work better However, it does remind me that when I was trying to get this working I did extract the actual "smbclient" command from the .debug file and run it manually from the command line in order to experiment. For example, the .debug file for the estimate phase shows the command /usr/bin/smbclient -d 0 -U backup -E -W -c archive 0;recurse;du , so then I set the USER and PASSWD environment variables in my shell session [running on the Amanda server machine], and did experimentation using /usr/bin/smbclient -d 0 -E -W -c "archive 0;recurse;du" ... and similarly for the command taken from the sendbackup runs where the command was something more along the lines of "cd TestDirectory/; tarmod full reset hidden system quiet; tar c -" etc. This allowed me to try out permissions changes on the Share volumes in real time, rather than having to kick off a full Amanda run to see the results of my changes.) Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: smbclient
On Sat, Apr 18, 2020 at 11:44:18 +0100, Nuno Dias wrote: > Hi, > > The OS is Fedora 30 with amanda-3.5.1-19.fc30.x86_64 and samba- > client-4.10.14-0.fc30.x86_64 (this are the packages from the OS). > > The error that I have is accessing some files, > > ERROR smbclient: NT_STATUS_ACCESS_DENIED listing > Windows\\System32\\config\\systemprofile\\AppData\\Local\\Microsoft\\Wi > ndows\\INetCache\\Content.IE5\\*" > > Can this be the reason all the estimates fails? Yes, it could be (though I would expect to see a more explict failure message from the estimate phase later on in the log file if that were the case). You will certainly need to connect to your Windows client using a username which has sufficient permissions to read all files, and also to update the "archive bit" on the backed-up files so that level 1 dumps work as expected. I haven't delived into the nuances of NTFS permissions and have only gone through this on a single windows client machine, but in my experimentation I found that setting the following permissions using Server Manager for the particular shares in question produced a working level-1 backup with no error messages in the log, while also at least preventing obvious editing of the share by the backup user : permissions (for the smbclient user) enabled: "Read & exectue", "List folder contents", "Read" Advanced Attributes enabled: "Traverse folder/execute file", "List folder/read data", "Read attributes", "Read extended attributes", "Read permissions" "Write attributes" (On this particular client box, then Sharing tab already had "Full Control" granted to Everyone, so I did not have to fine-tune the settings there to get Amanda working.) Hope that is at least somewhat helpful... Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: smbclient
So, after countless hours with this issue without success, let me ask the community about smbtar. Can I use smbtar with amanda? if yes how? do I need to write a new plugin? Thanks, Nuno On Sat, 2020-04-18 at 11:44 +0100, Nuno Dias wrote: > Hi, > > The OS is Fedora 30 with amanda-3.5.1-19.fc30.x86_64 and samba- > client-4.10.14-0.fc30.x86_64 (this are the packages from the OS). > > The error that I have is accessing some files, > > ERROR smbclient: NT_STATUS_ACCESS_DENIED listing > Windows\\System32\\config\\systemprofile\\AppData\\Local\\Microsoft\\ > Wi > ndows\\INetCache\\Content.IE5\\*" > > Can this be the reason all the estimates fails? > > Thanks, > Nuno > > On Sat, 2020-04-18 at 00:56 -0400, Nathan Stratton Treadway wrote: > > On Fri, Apr 17, 2020 at 19:51:47 +0100, Nuno Dias wrote: > > > Hi, > > > > > > I'm trying to use the amsamba plugin, put fails everytime in the > > > estimate. > > > > I have a vague recollection of running in to an unexpected warning > > message from from smbclient when I first set up Amanda 3.5.x with > > Samba > > 4.7.x), but it sounds like a different problem from yours. > > > > What error messages do you find in the > > .../client//Amsamba.2020*.debug log file? > > > > (Knowing your OS and Amanda versions [and exact version of Samba] > > might > > be helpful, too.) > > > > Nathan > > > > --- > > - > > Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic > > region > > Ray Ontko & Co. - Software consulting services - > > http://www.ontko.com/ > > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: > > 1023D/ECFB6239 > > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB > > 6239 -- Nuno Dias LIP
Re: smbclient
Hi, The OS is Fedora 30 with amanda-3.5.1-19.fc30.x86_64 and samba- client-4.10.14-0.fc30.x86_64 (this are the packages from the OS). The error that I have is accessing some files, ERROR smbclient: NT_STATUS_ACCESS_DENIED listing Windows\\System32\\config\\systemprofile\\AppData\\Local\\Microsoft\\Wi ndows\\INetCache\\Content.IE5\\*" Can this be the reason all the estimates fails? Thanks, Nuno On Sat, 2020-04-18 at 00:56 -0400, Nathan Stratton Treadway wrote: > On Fri, Apr 17, 2020 at 19:51:47 +0100, Nuno Dias wrote: > > Hi, > > > > I'm trying to use the amsamba plugin, put fails everytime in the > > estimate. > > I have a vague recollection of running in to an unexpected warning > message from from smbclient when I first set up Amanda 3.5.x with > Samba > 4.7.x), but it sounds like a different problem from yours. > > What error messages do you find in the > .../client//Amsamba.2020*.debug log file? > > (Knowing your OS and Amanda versions [and exact version of Samba] > might > be helpful, too.) > > Nathan > > --- > - > Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic > region > Ray Ontko & Co. - Software consulting services - > http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: > 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 -- Nuno Dias LIP
Re: smbclient
Hi,
Yes smbclient and smbtar work without problems.
Cheers,
Nuno
On Fri, 2020-04-17 at 16:57 -0700, Alan Hodgson wrote:
> On Fri, 2020-04-17 at 23:53 +0100, Nuno Dias wrote:
> > Hi,
> >
> > In my case is amanda 3.5.1 and samba 4.10.14
> >
> > This is my configuration
> >
> > define application-tool app_amsamba {
> > plugin "amsamba"
> > property "SMBCLIENT-PATH" "/usr/bin/smbclient"
> > property "GNUTAR-PATH" "/bin/tar"
> > property "AMANDAPASS" "/etc/amandapass"
> > #property "ALLOW-ANONYMOUS" "guest"
> > }
> >
> > define dumptype samba {
> > global
> > comment "Samba"
> > program "APPLICATION"
> > application "app_amsamba"
> > }
> >
> > Can you tell me if is same as your? And what was the problem with
> > amandapass?
> >
>
> I have:
>
> define application-tool app_amsamba {
> comment "amsamba"
> plugin "amsamba"
> property "SMBCLIENT-PATH" "/usr/bin/smbclient"
> property "GNUTAR-PATH" "/bin/tar"
> property "ALLOW-ANONYMOUS" "NO"
> property "RECOVER-MODE" "tar"
> property "REGEX-MATCH" "NO"
> }
>
> Looks pretty similar.
>
> I don't remember what the amandapass issue was, it looks like the
> examples in the amsamba man page. I do seem to have it both in /etc
> and symlinked in /etc/amanda, which suggests I had a file location
> issue and didn't finish cleaning it up
>
> Have you tested smbclient to make sure it works?
>
--
Nuno Dias
LIP
Re: smbclient
On Fri, Apr 17, 2020 at 19:51:47 +0100, Nuno Dias wrote: > Hi, > > I'm trying to use the amsamba plugin, put fails everytime in the > estimate. I have a vague recollection of running in to an unexpected warning message from from smbclient when I first set up Amanda 3.5.x with Samba 4.7.x), but it sounds like a different problem from yours. What error messages do you find in the .../client//Amsamba.2020*.debug log file? (Knowing your OS and Amanda versions [and exact version of Samba] might be helpful, too.) Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: smbclient
On Fri, 2020-04-17 at 23:53 +0100, Nuno Dias wrote:
> Hi,
>
> In my case is amanda 3.5.1 and samba 4.10.14
>
> This is my configuration
>
> define application-tool app_amsamba {
> plugin "amsamba"
> property "SMBCLIENT-PATH" "/usr/bin/smbclient"
> property "GNUTAR-PATH" "/bin/tar"
> property "AMANDAPASS" "/etc/amandapass"
> #property "ALLOW-ANONYMOUS" "guest"
> }
>
> define dumptype samba {
> global
> comment "Samba"
> program "APPLICATION"
> application "app_amsamba"
> }
>
> Can you tell me if is same as your? And what was the problem with
> amandapass?
>
I have:
define application-tool app_amsamba {
comment "amsamba"
plugin "amsamba"
property "SMBCLIENT-PATH" "/usr/bin/smbclient"
property "GNUTAR-PATH" "/bin/tar"
property "ALLOW-ANONYMOUS" "NO"
property "RECOVER-MODE" "tar"
property "REGEX-MATCH" "NO"
}
Looks pretty similar.
I don't remember what the amandapass issue was, it looks like the
examples in the amsamba man page. I do seem to have it both in /etc and
symlinked in /etc/amanda, which suggests I had a file location issue and
didn't finish cleaning it up
Have you tested smbclient to make sure it works?
Re: smbclient
Hi,
In my case is amanda 3.5.1 and samba 4.10.14
This is my configuration
define application-tool app_amsamba {
plugin "amsamba"
property "SMBCLIENT-PATH" "/usr/bin/smbclient"
property "GNUTAR-PATH" "/bin/tar"
property "AMANDAPASS" "/etc/amandapass"
#property "ALLOW-ANONYMOUS" "guest"
}
define dumptype samba {
global
comment "Samba"
program "APPLICATION"
application "app_amsamba"
}
Can you tell me if is same as your? And what was the problem with
amandapass?
Thanks,
Nuno
On Fri, 2020-04-17 at 13:19 -0700, Alan Hodgson wrote:
> On Fri, 2020-04-17 at 19:51 +0100, Nuno Dias wrote:
> > Hi,
> >
> > I'm trying to use the amsamba plugin, put fails everytime in the
> > estimate.
> >
> > A search in google got me some results saying that some time ago
> > the
> > samba version 4.x was incompatible with amanda, anyone knows if
> > this is
> > still true?
>
> I'm backing up one machine with amsamba from Amanda 3.5.1, using
> Samba version 4.11.6. So it can work.
>
> I seem to recall having some issues getting amandapass right to start
> with.
--
Nuno Dias
LIP
Re: smbclient
On Fri, 2020-04-17 at 19:51 +0100, Nuno Dias wrote: > Hi, > I'm trying to use the amsamba plugin, put fails everytime in > theestimate. > A search in google got me some results saying that some time ago > thesamba version 4.x was incompatible with amanda, anyone knows if > this isstill true? I'm backing up one machine with amsamba from Amanda 3.5.1, using Samba version 4.11.6. So it can work. I seem to recall having some issues getting amandapass right to start with.
smbclient
Hi, I'm trying to use the amsamba plugin, put fails everytime in the estimate. A search in google got me some results saying that some time ago the samba version 4.x was incompatible with amanda, anyone knows if this is still true? Thanks, Nuno -- Nuno Dias LIP
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 05.01.19 um 00:31 schrieb Uwe Menges: > On 1/4/19 7:51 PM, Stefan G. Weichinger wrote: >> I couldn't find a way to exclude/ignore such messages from smbclient >> within amsamba. And browsing the script itself it wasn't clear to me >> non-coder how and where to add that. > > I'm not able to test that, my perl is rusty, I didn't take a close look, > yadda yadda.. > > Try to add to amsamba after both (L433 + L521): > next if /^WARNING/g; > + next if /^Unable to initialize messaging context/g; > > Or if the message doesn't really start at first column, omit the ^. Thanks for the suggestion, I tried three variations now without success. Always the warning in the email reports. I tried: next if /^Unable to initialize messaging context/g; next if /Unable to initialize messaging context/g; next if /Unable to initialize messaging context/;
Re: smbclient usage fails with "Unable to initialize messaging context"
On 1/4/19 7:51 PM, Stefan G. Weichinger wrote: > I couldn't find a way to exclude/ignore such messages from smbclient > within amsamba. And browsing the script itself it wasn't clear to me > non-coder how and where to add that. I'm not able to test that, my perl is rusty, I didn't take a close look, yadda yadda.. Try to add to amsamba after both (L433 + L521): next if /^WARNING/g; + next if /^Unable to initialize messaging context/g; Or if the message doesn't really start at first column, omit the ^. Yours, Uwe
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 03.01.19 um 09:56 schrieb Uwe Menges: > On 1/2/19 8:19 PM, Stefan G. Weichinger wrote: >>> at first: happy new year to all you amanda-users! > > Happy new year as well! thank you ;) > I don't use smb or amsamba, so I don't know what it does in depth. > But I don't yet understand from your e-mail what's happening at all. > > Is this an error that prevents it from working or just a message you > want to get rid of? Exit status 1 (from amsamba, but probably also from > smbclient?) indicates more than a nuisance. > > Do you get the same error from a shell when trying smbclient command > that amanda/amsamba produces? Maybe the issue needs to be analyzed and > solved underneath amanda. Yes, it is also given back by smbclient on the shell, when run by the backup/amanda user. Rowland Penny on the samba-mailing-list told me that it can be ignored, but amanda does not do that yet. So far I noticed that amdumps work, but the reports are "tainted" (is that the word?) by the ugly message and therefore marked as FAILED. I couldn't find a way to exclude/ignore such messages from smbclient within amsamba. And browsing the script itself it wasn't clear to me non-coder how and where to add that. Filing an issue at github seems non-working to me, as I wait for a single beep of feedback for two weeks now after filing my last issue there (additionally to posting here). Stefan
Re: smbclient usage fails with "Unable to initialize messaging context"
On 1/2/19 8:19 PM, Stefan G. Weichinger wrote: >> at first: happy new year to all you amanda-users! Happy new year as well! >> Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails >> to amcheck/amdump: >> >> Amanda Backup Client Hosts Check >> ---- >> HOST backup ERROR: smbclient: Unable to initialize messaging context >> HOST backup ERROR: //192.168.16.230/ELBA5: Application 'amsamba': exited >> with status 1 [...] >> https://lists.samba.org/archive/samba/2019-January/220209.html >> >> maybe it is safe and working to ignore it, I will try to let amsamba >> ignore that message. > > I'd be thankful for any help with patching amsamba. I don't use smb or amsamba, so I don't know what it does in depth. But I don't yet understand from your e-mail what's happening at all. Is this an error that prevents it from working or just a message you want to get rid of? Exit status 1 (from amsamba, but probably also from smbclient?) indicates more than a nuisance. Do you get the same error from a shell when trying smbclient command that amanda/amsamba produces? Maybe the issue needs to be analyzed and solved underneath amanda. Yours, Uwe
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 02.01.19 um 11:19 schrieb Stefan G. Weichinger: at first: happy new year to all you amanda-users! -- Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails to amcheck/amdump: Amanda Backup Client Hosts Check HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/ELBA5: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/BMDDocs: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context etc I googled and found issues with samba, reported it already: https://lists.samba.org/archive/samba/2019-January/220209.html maybe it is safe and working to ignore it, I will try to let amsamba ignore that message. I'd be thankful for any help with patching amsamba.
smbclient usage fails with "Unable to initialize messaging context"
at first: happy new year to all you amanda-users! -- Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails to amcheck/amdump: Amanda Backup Client Hosts Check HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/ELBA5: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/BMDDocs: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context etc I googled and found issues with samba, reported it already: https://lists.samba.org/archive/samba/2019-January/220209.html maybe it is safe and working to ignore it, I will try to let amsamba ignore that message. Anyone else hitting this?
Re: Another problem with smbclient for Samba 4
Olivier, Do not use the 'GNUTAR' program. Use the amsamaba application. Jean-Louis 2018-07-04 5:51 GMT-04:00 Olivier : > Hi, > > I noticed that the command > smbclient olivier\\drivec -U on\%password -E -W samba -d0 -Tqca - > does not behave the same with Samba 3 and Samba 4. The smbclient tar > ends with giving the size of the data transfered, but the message is > slightly different and Amanda cannot parse the size returned by Samba 4, > resulting in an error >amanda //olivier/drivec lev 0 FAILED [no backup size line] > > Below is the end of the smbclient command for Samba 4: > > ./WINDOWS/Zapotec.bmp > ./WINDOWS/zipgenius.xml > tar:717 Total bytes received: 84969332671 > > and for Samba 3 > > ./ECsamples/TQM - Baldrige competition.ahp > ./ECsamples/VoiceOfCustomer Part I Prioritizing Market Segments.ahp > ./ECsamples/VoiceOfCustomer Part II Prioritizing Customer Requirements .ahp > ./ECsamples/VP of Development Selection.ahp > tar: dumped 51410 files and directories > Total bytes written: 27800975872 > > Thank you, > > Olivier > -- >
Re: Another problem with smbclient for Samba 4
Olivier writes: > Hi, > > I noticed that the command > smbclient olivier\\drivec -U on\%password -E -W samba -d0 -Tqca - > does not behave the same with Samba 3 and Samba 4. The smbclient tar > ends with giving the size of the data transfered, but the message is > slightly different and Amanda cannot parse the size returned by Samba 4, > resulting in an error >amanda //olivier/drivec lev 0 FAILED [no backup size line] > > Below is the end of the smbclient command for Samba 4: > > ./WINDOWS/Zapotec.bmp > ./WINDOWS/zipgenius.xml > tar:717 Total bytes received: 84969332671 > > and for Samba 3 > > ./ECsamples/TQM - Baldrige competition.ahp > ./ECsamples/VoiceOfCustomer Part I Prioritizing Market Segments.ahp > ./ECsamples/VoiceOfCustomer Part II Prioritizing Customer Requirements .ahp > ./ECsamples/VP of Development Selection.ahp > tar: dumped 51410 files and directories > Total bytes written: 27800975872 > > Thank you, > > Olivier I think I found the patch, for some reason, it did not make it to FreeBSD ports tree. Best regards, Olivier --
Another problem with smbclient for Samba 4
Hi, I noticed that the command smbclient olivier\\drivec -U on\%password -E -W samba -d0 -Tqca - does not behave the same with Samba 3 and Samba 4. The smbclient tar ends with giving the size of the data transfered, but the message is slightly different and Amanda cannot parse the size returned by Samba 4, resulting in an error amanda //olivier/drivec lev 0 FAILED [no backup size line] Below is the end of the smbclient command for Samba 4: ./WINDOWS/Zapotec.bmp ./WINDOWS/zipgenius.xml tar:717 Total bytes received: 84969332671 and for Samba 3 ./ECsamples/TQM - Baldrige competition.ahp ./ECsamples/VoiceOfCustomer Part I Prioritizing Market Segments.ahp ./ECsamples/VoiceOfCustomer Part II Prioritizing Customer Requirements .ahp ./ECsamples/VP of Development Selection.ahp tar: dumped 51410 files and directories Total bytes written: 27800975872 Thank you, Olivier --
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: 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 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 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.
Problem with smbclient for Samba 4
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 Is there a way to configure the smblient command without patching Amanda? Best regards, Olivier --
smbclient errors
amanda-3.4.5 samba-4.5.10 I get this in the report mail: ? smbclient: cli_setatr failed: NT_STATUS_ACCESS_DENIED ? smbclient: cli_setatr failed: NT_STATUS_ACCESS_DENIED Look in the '/var/spool/amanda/tmp/log.error/mail.gemeinde.local.srvaw01_backup.0.20170613220359.errout' file for full error messages and that file ends with (hundreds of ACCESS_DENIED lines ...): ? smbclient: cli_setatr failed: NT_STATUS_ACCESS_DENIED ? smbclient: cli_setatr failed: NT_STATUS_ACCESS_DENIED ? smbclient: cli_setatr failed: NT_STATUS_ACCESS_DENIED ? smbclient: cli_setatr failed: NT_STATUS_ACCESS_DENIED sendbackup: size 622749.166992188 sendbackup: native-CRC 72aac7eb:639262720 sendbackup: client-CRC 73d7eb64:107821777 sendbackup: end Does that mean amanda can't set something on the backed up files, like an archive bit or so? Do these files miss from the dump then?
Re: ERROR smbclient: NT_STATUS_ACCESS_DENIED on some files => Amanda doesn't backup anything on that share
The problem look to be that smbclient do not print the 'Total number of bytes' on it's stderr, so the estimate will never succeed. You can try to set: 'estimate server' for that dle. But you will probably get a similar error when doing the backup. What can we do if smbclient do not tell if the backup is correct? Jean-Louis On 08/02/17 08:38 AM, Tobias Köck wrote: > > Hi, > > I am using Amanda 3.3.9 with the newest amsamba patches. smbclient is > 4.5.4+dfsg-1 version on Debian Stretch. > > The problem is that a few files doesn't have the appropriate file > sharing permissions. The Planner stops and amsamba doesn't backup any > data from that share. > > Shouldn't AMANDA / amsama just ignore those files and move on with the > other files? But that's not what happens. It just don't backup any > files from that share. > > Any advice how to fix that behavior? > > Greetings and thanks > > Tobias > > --- > amstatus a2g-1: > > localhost://192.168.0.250/kunden 0 failed: planner: [Application 'am > > samba': ERROR smbclient: NT_STATUS_ACCESS_DENIED listing > Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\2012 > > 0227_Testdateien-Betamoo-TD\PI_Cordless-blubb_DE\*] > > --- > > Amsamba.20170206141259000.debug: > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: warning: Use of > uninitialized value $regex_match in pattern match (m//) at > /usr/lib/amanda/application/amsamba line 91. > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: Arguments: > estimate --message line --config a2g-1 --host localhost --device > //192.168.0.250/kunden --disk //192.168.0.250/kunden --level 0 -- > > amandapass /etc/amandapass > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: command: estimate > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: amandapass: > /etc/amandapass > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: password_wtr 4 > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: password_rdr 3 > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: warning: > close() on unopened filehandle 0 at > /usr/lib/amanda/application/amsamba line 502. > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: warning: > close() on unopened filehandle 1 at > /usr/lib/amanda/application/amsamba line 503. > > Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: execute: > /usr/bin/smbclient /usr/bin/smbclient //192.168.0.250/kunden -d 0 -U > backup -E -c archive 0;recurse;du > > Mon Feb 6 14:13:45 2017: thd-0x562125870800: Amsamba: stderr: > NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe > FLA\Betamoo-FLA-Kopie-von-lokal\20120227_Testdateien-Betamoo-TD\PI_Cordless-blubb_DE\* > > Mon Feb 6 14:13:45 2017: thd-0x562125870800: Amsamba: smbclient: > NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe > FLA\Betamoo-FLA-Kopie-von-lokal\20120227_Testdateien-Betamoo-TD\PI_Cordless-blubb_DE\* > > Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: stderr: > NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe > FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2ABIM\[0102]comDB[0123]geraetxxy_28_09_10_20100929131651\* > > Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: smbclient: > NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe > FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2ABIM\[0102]comDB[0123]geraetxxy_28_09_10_20100929131651\* > > Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: stderr: > NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe > FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2product\group102_geraetxxy_de_20100928114804\* > > Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: smbclient: > NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe > FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2product\group102_geraetxxy_de_20100928114804\* > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_utime : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_stime : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_maxrss : 27592 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_ixrss : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_idrss : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_isrss : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_minflt : 4096 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_majflt : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_nswap : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_inblock : 0 > > Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsam
ERROR smbclient: NT_STATUS_ACCESS_DENIED on some files => Amanda doesn't backup anything on that share
Hi, I am using Amanda 3.3.9 with the newest amsamba patches. smbclient is 4.5.4+dfsg-1 version on Debian Stretch. The problem is that a few files doesn't have the appropriate file sharing permissions. The Planner stops and amsamba doesn't backup any data from that share. Shouldn't AMANDA / amsama just ignore those files and move on with the other files? But that's not what happens. It just don't backup any files from that share. Any advice how to fix that behavior? Greetings and thanks Tobias --- amstatus a2g-1: localhost://192.168.0.250/kunden 0 failed: planner: [Application 'am samba': ERROR smbclient: NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\2012 0227_Testdateien-Betamoo-TD\PI_Cordless-blubb_DE\*] --- Amsamba.20170206141259000.debug: Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: warning: Use of uninitialized value $regex_match in pattern match (m//) at /usr/lib/amanda/application/amsamba line 91. Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: Arguments: estimate --message line --config a2g-1 --host localhost --device //192.168.0.250/kunden --disk //192.168.0.250/kunden --level 0 -- amandapass /etc/amandapass Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: command: estimate Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: amandapass: /etc/amandapass Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: password_wtr 4 Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: password_rdr 3 Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: warning: close() on unopened filehandle 0 at /usr/lib/amanda/application/amsamba line 502. Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: warning: close() on unopened filehandle 1 at /usr/lib/amanda/application/amsamba line 503. Mon Feb 6 14:12:59 2017: thd-0x562125870800: Amsamba: execute: /usr/bin/smbclient /usr/bin/smbclient //192.168.0.250/kunden -d 0 -U backup -E -c archive 0;recurse;du Mon Feb 6 14:13:45 2017: thd-0x562125870800: Amsamba: stderr: NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\20120227_Testdateien-Betamoo-TD\PI_Cordless-blubb_DE\* Mon Feb 6 14:13:45 2017: thd-0x562125870800: Amsamba: smbclient: NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\20120227_Testdateien-Betamoo-TD\PI_Cordless-blubb_DE\* Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: stderr: NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2ABIM\[0102]comDB[0123]geraetxxy_28_09_10_20100929131651\* Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: smbclient: NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2ABIM\[0102]comDB[0123]geraetxxy_28_09_10_20100929131651\* Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: stderr: NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2product\group102_geraetxxy_de_20100928114804\* Mon Feb 6 14:13:53 2017: thd-0x562125870800: Amsamba: smbclient: NT_STATUS_ACCESS_DENIED listing Betamoo\Übergabe FLA\Betamoo-FLA-Kopie-von-lokal\20111026_Uebergabe-Riki\Webdav_folder\2product\group102_geraetxxy_de_20100928114804\* Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_utime : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_stime : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_maxrss : 27592 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_ixrss : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_idrss : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_isrss : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_minflt : 4096 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_majflt : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_nswap : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_inblock : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_oublock : 24 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_msgsnd : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_msgrcv : 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_nsignals: 0 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_nvcsw : 7 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: ru_nivcsw : 3 Mon Feb 6 14:13:54 2017: thd-0x562125870800: Amsamba: pid 14630 finish time Mon Feb 6 14:13:54 2017
Re: using smbclient-4.x
Am 2016-11-14 um 10:45 schrieb Stefan G. Weichinger: > > remember amanda-3.3.9 using a recent smbclient? > > I get: > > smbclient: Error reading password from file descriptor 3: empty password > > Has anyone found a workaround (aside from downgrading samba)? > Is that fixed in 3.4? > backported https://github.com/zmanda/amanda/commit/c03e795ce338f01707ab0548ad9558347779e858 to amanda-3.3.9 now Works now with samba-4.2.11 : solved for me
using smbclient-4.x
remember amanda-3.3.9 using a recent smbclient? I get: smbclient: Error reading password from file descriptor 3: empty password Has anyone found a workaround (aside from downgrading samba)? Is that fixed in 3.4?
AW: smbclient 4.33 - samba 4 problem
Sounds great. Keep me informed. -Ursprüngliche Nachricht- Von: Stefan G. Weichinger [mailto:s...@amanda.org] Gesendet: Montag, 18. Januar 2016 18:18 An: Tobias Köck; amanda-users@amanda.org Betreff: Re: smbclient 4.33 - samba 4 problem Am 2016-01-12 um 10:06 schrieb Tobias Köck: > There seem to be a similar problem with smbclient 4.33. > > > > It works with > > > > smbclient --version > > Version 4.1.17-Debian > > > > Either the smbclient 4.33 has a problem and/or AMANDA cannot handle > the new smbclient version. Tobias, it seems nobody except us two hit that issue ... fedora23 brings an update to 4.3.4 now, I will test that.
Re: smbclient 4.33 - samba 4 problem
Am 2016-01-12 um 10:06 schrieb Tobias Köck: > There seem to be a similar problem with smbclient 4.33. > > > > It works with > > > > smbclient --version > > Version 4.1.17-Debian > > > > Either the smbclient 4.33 has a problem and/or AMANDA cannot handle the > new smbclient version. Tobias, it seems nobody except us two hit that issue ... fedora23 brings an update to 4.3.4 now, I will test that.
smbclient 4.33 - samba 4 problem
There seem to be a similar problem with smbclient 4.33. It works with smbclient --version Version 4.1.17-Debian Either the smbclient 4.33 has a problem and/or AMANDA cannot handle the new smbclient version. Greetings Tobias
Upgrading 2.6 to 3.3 smbclient and amsamba
Hi there,
for various reasons I have to upgrade my Debian Squeeze to wheezy. With this
change the new version of Amanda 3.3.1 comes along and I could not find out how
to backup my WindowsServers for now on.
With 2.6 everything was done with smbclient /etc/amandapass and the following
dumptype definition.
dumptype root-tar {
program GNUTAR
comment root partitions dumped with tar
compress client fast
index yes
priority medium
auth bsdtcp
}
Do I have to change anything on this practice according to Amanda 3.3?
I would like to exclude two files in two different directories in order to have
less errors. The problem is that the diretories itself have to be backed up.
So I thought I could do this as follows:
dumptype root-tar {
program GNUTAR
comment root partitions dumped with tar
compress client fast
index yes
priority medium
auth bsdtcp
exclude /System/SQLBasys/Log/*
exclude /System/SQLBasys/Data/*
}
Does this work?
And what is about this amsamba program I read about? Do I have to use it or
not???
Thanks
Can a parameter be added to the smbclient command?
Hi, is it possible to tell amanda to add the -p 139 option to smbclient when doing a backup of windows shares? Samba 3.6.0 has a bug, that breaks smbclient when using it on Windows NT4 shares: # /usr/bin/smbclient //molek-04/lightcycler -U administrator protocol negotiation failed: NT_STATUS_IO_TIMEOUT If you add the -p 139 to smbclient, it works. Can I tell amanda direclty do add this parameter or do I have to write a wrapper? Regards, Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Labormedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780 http://www.medizinische-genetik.de
amanda and smbclient
I realize this is more of a smbclient issue, but thought someone might have an answer as to how files residing on Windows shares can be backed up without ensuring they are not in use. The problem is sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -xpGf - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | Domain=[MAI] OS=[Windows Server 2003 3790 Service Pack 1] Server=[Windows Server 2003 5.2] ? NT_STATUS_SHARING_VIOLATION opening remote file ... Is my only solution making sure that all users shutdown the applications that are opening the files causing this problem? Thanks. -- Brandon
Re: amanda not using smbclient for samba clients?
Marc Muehlfeld wrote: Dan Brown schrieb: # disklist # Design Resources Mac coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne coralie //coralie/design_resources/ tar-comp-srvbest-ne The first column is the name of the machine who connect to the samba share, not the client. Here's one of my DLEs for example: nucleus.mr.lfmg.de//amplicon/backup$ SMB_Low_Client-Fast Explanation: Nucleus does the connect to my client Amplicon and collect the data. The machine must not be the backupserver itself. E. g. if you have a remote subnet, connected with a slow connection, you can configure a remote linux machine to collect and compact your data and then transfer it from there to your backup server to save bandwidth. It's wasting bandwidth of the WAN connection to transfer the whole samba data to your backup server and do the compact there. Surely you can do this in your local subnet too, to keep the load of your backupserver low. It can't be the backup server itself or shouldn't? I was following the 15 minute setup example on zmanda.com and it used the backup server itself. Isn't that the point of having --with-smbclient in the compile script? It doesn't really matter how loaded down the backup server is, as long as the computers with the shares I am backing up don't experience a huge load. Out of curiosity I've changed it to the backup server itself: ministryofinformation //coralie/design_resources_archive/ tar-comp-srvbest-ne but now on the target computer I see no connection attempts at all via tcpdump. These computers are all on the same subnet and are qualified addresses of an internal domain (although it's FQDN would be ministryofinformation.thezoo). --- Dan Brown
amanda not using smbclient for samba clients?
I've been through the docs a bunch of times to try to figure out what exactly I'm doing wrong but either I'm not doing anything wrong (unlikely) or there's something I keep thinking is right but isn't (more likely). When I run a check on the Amanda setup, it queries the samba client (a Mac OS X computer) but tries to communicate via Amanda ports rather than trying to mount and check the samba share. Here's the output as well as disklist and amanda.conf. I'm guessing that the problem is the disklist but the problem is non-obvious to me. # su - amanda -c amcheck -c Macs Amanda Backup Client Hosts Check WARNING: coralie: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.000 seconds, 1 problem found (brought to you by Amanda 2.5.2p1) # tcpdump -i en0|grep 192.168.0.32 23:29:59.871691 IP 192.168.0.32.919 192.168.0.61.amanda: UDP, length: 125 23:29:59.871738 IP 192.168.0.61 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable 23:30:09.870724 IP 192.168.0.32.919 192.168.0.61.amanda: UDP, length: 125 23:30:09.870788 IP 192.168.0.61 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable 23:30:19.870655 IP 192.168.0.32.919 192.168.0.61.amanda: UDP, length: 125 23:30:19.870731 IP 192.168.0.61 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable # disklist # Design Resources Mac coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne coralie //coralie/design_resources/ tar-comp-srvbest-ne # amanda.conf org Macs # your organization name for reports mailto amanda [EMAIL PROTECTED] # space separated list of operators at your site dumpuser amanda # the user to run dumps under inparallel 16 # maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h dumporder sssSsssStttTbbbB# specify the priority order of each dumper # s - smallest size # S - biggest size # t - smallest time # T - biggest time # b - smallest bandwitdh # B - biggest bandwitdh # try BTBTBTBTBTBT if you are not holding # disk constrained taperalgo first # The algorithm used to choose which dump image to send # to the taper.+ # Possible values: # [first|firstfit|largest|largestfit|smallest|last] # Default: first. # first First in - first out. # firstfit The first dump image that will fit # on the current tape. # largest The largest dump image. # largestfitThe largest dump image that will fit # on the current tape. # smallest The smallest dump image. # last Last in - first out. displayunit m # Possible values: k|m|g|t # Default: k. # The unit used to print many numbers. # k=kilo, m=mega, g=giga, t=tera netusage 1 Kbps# maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 30 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2 bumppercent 20 # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 256# A positive integer telling taper how many # 32k buffers to allocate. The default is 20 usetimestamps yes runtapes 1 # number of tapes to be used in a single run of amdump tapedev /dev/nst0 # the no-rewind tape device to be used rawtapedev
Re: amanda not using smbclient for samba clients?
Dan Brown schrieb: # disklist # Design Resources Mac coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne coralie //coralie/design_resources/ tar-comp-srvbest-ne The first column is the name of the machine who connect to the samba share, not the client. Here's one of my DLEs for example: nucleus.mr.lfmg.de//amplicon/backup$ SMB_Low_Client-Fast Explanation: Nucleus does the connect to my client Amplicon and collect the data. The machine must not be the backupserver itself. E. g. if you have a remote subnet, connected with a slow connection, you can configure a remote linux machine to collect and compact your data and then transfer it from there to your backup server to save bandwidth. It's wasting bandwidth of the WAN connection to transfer the whole samba data to your backup server and do the compact there. Surely you can do this in your local subnet too, to keep the load of your backupserver low. Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: amanda not using smbclient for samba clients?
Stefan G. Weichinger schrieb: The machine must not be the backupserver itself. You mean: The machine does not have to be the backupserver itself Right? Oh hell. Better I go back home. Getting up at 6am doesn't seem to be good for me. :-) Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: amanda not using smbclient for samba clients?
Marc Muehlfeld schrieb: Stefan G. Weichinger schrieb: The machine must not be the backupserver itself. You mean: The machine does not have to be the backupserver itself Right? Oh hell. Better I go back home. Getting up at 6am doesn't seem to be good for me. :-) Same here, same here. The problem is: I *am* at home. ;) Greets, Stefan
Re: smbclient backups on RHEL/centos 5
On Thu, 9 Aug 2007 at 12:27pm, Joshua Baker-LePain wrote On Thu, 9 Aug 2007 at 5:52pm, Paul Bijnens wrote On 2007-08-09 17:18, Joshua Baker-LePain wrote: I haven't been able to get smbclient backups to work via a centos-5 client. I've had them working for a long while with centos-4, but the exact same config just plain doesn't work in centos-5. I've tried the version of amanda included in centos-5 (2.5.0p2), my old standby (2.4.5p1), and the most recent (2.5.2p1). They all fail fundamentally in the same way, with a message saying: samba access error: //$WINHOST/$SHARE: session setup failed: NT_STATUS_LOGON_FAILURE: returned 1 I'm starting to suspect the samba version (3.0.23c) to be at fault. Has anyone else encountered this? Anybody worked around it? I have no problem using the centos-5 smbclient to connect to PC's. (I did have some problems to connect to Vista-PC's, even with older samba-versions; but that's easily solved by tweaking the registry.) $ smbclient --version Version 3.0.23c-2.el5.2.0.2 And using it through the command line: smbclient //host/share -U username -W workgroup does it give the same error? (and you're sure the password etc is correct?) Hrmph. I was sure I'd tried that before and had it work, but now it's not working. And doing pointed me at some issues in the samba setup that may be getting in the way. *sigh* Sorry for the noise. OK, so I'm *not* going crazy. This is a CentOS-5 Linux client and a XPSP2 'doze client. The amanda version on the Linux client is 2.5.2p1. smbclient by itself works fine: [EMAIL PROTECTED] ~]$ smbclient buck\\das -U amanda -E -d0 Password: Domain=[BUCK] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] smb: \ But if I try it with the exact same commands I see in the amanda debug log it doesn't work: [EMAIL PROTECTED] ~]$ smbclient buck\\das -U amanda -E -d0 -TXqca - ./RECYCLER /dev/null session setup failed: NT_STATUS_LOGON_FAILURE The same thing happens if I naively put a echo $SMBPASSWD piped into the smbclient command. Any ideas? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
smbclient backups on RHEL/centos 5
I haven't been able to get smbclient backups to work via a centos-5 client. I've had them working for a long while with centos-4, but the exact same config just plain doesn't work in centos-5. I've tried the version of amanda included in centos-5 (2.5.0p2), my old standby (2.4.5p1), and the most recent (2.5.2p1). They all fail fundamentally in the same way, with a message saying: samba access error: //$WINHOST/$SHARE: session setup failed: NT_STATUS_LOGON_FAILURE: returned 1 I'm starting to suspect the samba version (3.0.23c) to be at fault. Has anyone else encountered this? Anybody worked around it? Thanks! -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: smbclient backups on RHEL/centos 5
On 2007-08-09 17:18, Joshua Baker-LePain wrote: I haven't been able to get smbclient backups to work via a centos-5 client. I've had them working for a long while with centos-4, but the exact same config just plain doesn't work in centos-5. I've tried the version of amanda included in centos-5 (2.5.0p2), my old standby (2.4.5p1), and the most recent (2.5.2p1). They all fail fundamentally in the same way, with a message saying: samba access error: //$WINHOST/$SHARE: session setup failed: NT_STATUS_LOGON_FAILURE: returned 1 I'm starting to suspect the samba version (3.0.23c) to be at fault. Has anyone else encountered this? Anybody worked around it? I have no problem using the centos-5 smbclient to connect to PC's. (I did have some problems to connect to Vista-PC's, even with older samba-versions; but that's easily solved by tweaking the registry.) $ smbclient --version Version 3.0.23c-2.el5.2.0.2 And using it through the command line: smbclient //host/share -U username -W workgroup does it give the same error? (and you're sure the password etc is correct?) -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: smbclient backups on RHEL/centos 5
On Thu, 9 Aug 2007 at 5:52pm, Paul Bijnens wrote On 2007-08-09 17:18, Joshua Baker-LePain wrote: I haven't been able to get smbclient backups to work via a centos-5 client. I've had them working for a long while with centos-4, but the exact same config just plain doesn't work in centos-5. I've tried the version of amanda included in centos-5 (2.5.0p2), my old standby (2.4.5p1), and the most recent (2.5.2p1). They all fail fundamentally in the same way, with a message saying: samba access error: //$WINHOST/$SHARE: session setup failed: NT_STATUS_LOGON_FAILURE: returned 1 I'm starting to suspect the samba version (3.0.23c) to be at fault. Has anyone else encountered this? Anybody worked around it? I have no problem using the centos-5 smbclient to connect to PC's. (I did have some problems to connect to Vista-PC's, even with older samba-versions; but that's easily solved by tweaking the registry.) $ smbclient --version Version 3.0.23c-2.el5.2.0.2 And using it through the command line: smbclient //host/share -U username -W workgroup does it give the same error? (and you're sure the password etc is correct?) Hrmph. I was sure I'd tried that before and had it work, but now it's not working. And doing pointed me at some issues in the samba setup that may be getting in the way. *sigh* Sorry for the noise. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
smbclient got signal 13
Does size provoke the message sendbackup: time 2069.484: error [/usr/local/bin/smbclient got signal 13]? Total bytes written: 5200947200 remuda# more sendbackup.20070701083211.debug sendbackup: debug 1 pid 4208 ruid 2 euid 2: start at Sun Jul 1 08:32:11 2007 /usr/local/libexec/amanda/sendbackup: version 2.4.5 parsed request as: program `GNUTAR' disk `//pillbox/primary' device `//pillbox/primary' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;compress-best;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.52851 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.65194 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.58013 sendbackup: time 0.000: waiting for connect on 52851, then 65194, then 58013 sendbackup: time 0.002: stream_accept: connection from 10.0.3.148.64749 sendbackup: time 0.002: stream_accept: connection from 10.0.3.148.51619 sendbackup: time 0.002: stream_accept: connection from 10.0.3.148.52604 sendbackup: time 0.002: got all connections sendbackup: time 0.002: spawning /usr/bin/gzip in pipeline sendbackup: argument list: /usr/bin/gzip --best sendbackup-gnutar: time 0.005: pid 4210: /usr/bin/gzip --best sendbackup-gnutar: time 0.034: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup-gnutar: time 0.035: backup of \\pillbox\primary sendbackup: time 0.035: spawning /usr/local/bin/smbclient in pipeline sendbackup: argument list: smbclient \\pillbox\primary -U administrator -E -W ro under -d0 -Tqca - sendbackup-gnutar: time 0.036: /usr/local/bin/smbclient: pid 4213 sendbackup: time 0.042: started index creator: /usr/bin/gtar -tf - 2 /dev/null | sed -e 's/^\.//' sendbackup: time 0.116: 124: strange(?): Domain=[PILLBOX] OS=[Windows Server 200 3 3790 Service Pack 1] Server=[Windows Server 2003 5.2] sendbackup: time 2069.440: 75: normal(|): tar: dumped 1545 files and directori es sendbackup: time 2069.441: 53:size(|): Total bytes written: 5200947200 sendbackup: time 2069.443: index created successfully sendbackup: time 2069.484: error [/usr/local/bin/smbclient got signal 13] sendbackup: time 2069.484: pid 4208 finish time Sun Jul 1 09:06:40 2007 remuda# Total bytes written: 105021440 = remuda# more sendbackup.20070702015031.debug sendbackup: debug 1 pid 6612 ruid 2 euid 2: start at Mon Jul 2 01:50:31 2007 /usr/local/libexec/amanda/sendbackup: version 2.4.5 parsed request as: program `GNUTAR' disk `//pillbox/admin' device `//pillbox/admin' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;compress-best;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.49450 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.50956 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.58958 sendbackup: time 0.000: waiting for connect on 49450, then 50956, then 58958 sendbackup: time 0.002: stream_accept: connection from 10.0.3.148.55230 sendbackup: time 0.002: stream_accept: connection from 10.0.3.148.55837 sendbackup: time 0.002: stream_accept: connection from 10.0.3.148.54857 sendbackup: time 0.002: got all connections sendbackup: time 0.006: spawning /usr/bin/gzip in pipeline sendbackup: argument list: /usr/bin/gzip --best sendbackup-gnutar: time 0.007: pid 6614: /usr/bin/gzip --best sendbackup-gnutar: time 0.047: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup-gnutar: time 0.048: backup of \\pillbox\admin sendbackup: time 0.048: spawning /usr/local/bin/smbclient in pipeline sendbackup: argument list: smbclient \\pillbox\admin -U administrator -E -W roun der -d0 -Tqca - sendbackup-gnutar: time 0.049: /usr/local/bin/smbclient: pid 6617 sendbackup: time 0.069: started index creator: /usr/bin/gtar -tf - 2 /dev/null | sed -e 's/^\.//' sendbackup: time 0.133: 124: strange(?): Domain=[PILLBOX] OS=[Windows Server 200 3 3790 Service Pack 1] Server=[Windows Server 2003 5.2] sendbackup: time 863.858: 75: normal(|): tar: dumped 240 files and directories sendbackup: time 863.859: 53:size(|): Total bytes written: 105021440 sendbackup: time 863.861: index created successfully sendbackup: time 863.896: pid 6612 finish time Mon Jul 2 02:04:55 2007 remuda# nvloke smbclient interactively and the tar succeeds remuda# smbclient //pillbox/primary -U administrator% -E -W rounder -d0 -Tqca - | gzip -c /scratch2/justsmb Domain=[PILLBOX] OS=[Windows Server 2003 3790 Service Pack 1] Server=[Windows Server 2003 5.2] tar: dumped 1545 files
Re: amanda-2.5.0p2 hanging on smbclient with configure
quote who=Gavin Henry quote who=Gavin Henry quote who=Gavin Henry quote who=Paul Bijnens On 2006-08-08 16:17, Gavin Henry wrote: Currently trying to compile 2.5.0p2 with: ./configure --with-user=amanda --with-group=disk --with-ssh-security --with-config=Suretec --with-changer-device=/dev/sg2 --with-tape-device=/dev/nst0 But configure just sits there at: checking for smbclient... /usr/bin/smbclient Upgrading to Samba 3.0.23b fixed it. Not sure, but can now move on. Thanks. Same when adding --with-smbclient=/usr/bin/smbclient If you do not need smbclient support, then you can configure with --without-smbclient and work around this problem. I have tried that, and with --with-smbclient=no. I've been going through configure.in to see what the probs are. If you do need it... then try to investigate what is blocking. It seems like configure is hanging in one of the next steps. Configure tries to find out what version of smbclient you have by running the command: smbclient '\\not.a.host.name\notashare' -U nosuchuser -N -Tx /dev/null Looks like it's this. It just hangs. Must be smbclient, as it is taking forever, even when I jsut run: smblcient with no options. Forget it, will debug smbclient. Nothing wrong with Amanda. Thanks all. strace smbclient -d 5 show it sitting at: futex(0x2bdf2dc0, FUTEX_WAIT, 2, NULL Hmm. I just setup 2 clients on Fedora Core 5 with 2.5.0p2, and they both are fine. The server is on a SUSE 9.3 x86_64 box, that has (Is a Samba PDC too): free -m total used free sharedbuffers cached Mem: 3961296 3665 0 48 154 -/+ buffers/cache: 93 3868 Swap: 2070 0 2070 uname -a Linux nas1 2.6.14.2-smp #2 SMP Thu Nov 17 15:31:40 GMT 2005 x86_64 x86_64 x86_64 GNU/Linux df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage lsscsi [0:0:0:0]diskATA HTS541080G9SA00 MB4O /dev/sda [4:0:1:0]tapeCERTANCE ULTRIUM 21775 /dev/st0 [4:0:1:1]mediumx QUANTUM UHDL 000E - [6:0:0:0]diskArecaARC-1160-VOL#00 R001 /dev/sdb What happens if you run that manually? Hangs The output of that step does not appear on screen however, so it could be that configure is actually hanging on the step after that. I think it's smbclient that is the problem. The next step is finding out where the gzip program lives. Is does that by looking in several directories. If one of those directories happens to be mounted on a non-responsive NFS-server, you hang here too. The list of directories is: /bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd:/etc:/usr/etc /usr/local/sbin:/usr/local/bin:/usr/ccs/bin and the value of $PATH from the user that runs configure. Anything strange when trying test -e /bin/gzip? (Try that for all the above dirs) Nope, looks fine. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
amanda-2.5.0p2 hanging on smbclient with configure
Dear All, Currently trying to compile 2.5.0p2 with: ./configure --with-user=amanda --with-group=disk --with-ssh-security --with-config=Suretec --with-changer-device=/dev/sg2 --with-tape-device=/dev/nst0 But configure just sits there at: checking for smbclient... /usr/bin/smbclient Same when adding --with-smbclient=/usr/bin/smbclient Any tips? Thanks. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E [EMAIL PROTECTED] Open Source. Open Solutions(tm). http://www.suretecsystems.com/
Re: amanda-2.5.0p2 hanging on smbclient with configure
On 2006-08-08 16:17, Gavin Henry wrote: Currently trying to compile 2.5.0p2 with: ./configure --with-user=amanda --with-group=disk --with-ssh-security --with-config=Suretec --with-changer-device=/dev/sg2 --with-tape-device=/dev/nst0 But configure just sits there at: checking for smbclient... /usr/bin/smbclient Same when adding --with-smbclient=/usr/bin/smbclient If you do not need smbclient support, then you can configure with --without-smbclient and work around this problem. If you do need it... then try to investigate what is blocking. It seems like configure is hanging in one of the next steps. Configure tries to find out what version of smbclient you have by running the command: smbclient '\\not.a.host.name\notashare' -U nosuchuser -N -Tx /dev/null What happens if you run that manually? The output of that step does not appear on screen however, so it could be that configure is actually hanging on the step after that. The next step is finding out where the gzip program lives. Is does that by looking in several directories. If one of those directories happens to be mounted on a non-responsive NFS-server, you hang here too. The list of directories is: /bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd:/etc:/usr/etc /usr/local/sbin:/usr/local/bin:/usr/ccs/bin and the value of $PATH from the user that runs configure. Anything strange when trying test -e /bin/gzip? (Try that for all the above dirs) -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amanda-2.5.0p2 hanging on smbclient with configure
quote who=Paul Bijnens On 2006-08-08 16:17, Gavin Henry wrote: Currently trying to compile 2.5.0p2 with: ./configure --with-user=amanda --with-group=disk --with-ssh-security --with-config=Suretec --with-changer-device=/dev/sg2 --with-tape-device=/dev/nst0 But configure just sits there at: checking for smbclient... /usr/bin/smbclient Same when adding --with-smbclient=/usr/bin/smbclient If you do not need smbclient support, then you can configure with --without-smbclient and work around this problem. I have tried that, and with --with-smbclient=no. I've been going through configure.in to see what the probs are. If you do need it... then try to investigate what is blocking. It seems like configure is hanging in one of the next steps. Configure tries to find out what version of smbclient you have by running the command: smbclient '\\not.a.host.name\notashare' -U nosuchuser -N -Tx /dev/null Looks like it's this. It just hangs. I just setup 2 clients on Fedora Core 5 with 2.5.0p2, and they both are fine. The server is on a SUSE 9.3 x86_64 box, that has (Is a Samba PDC too): free -m total used free sharedbuffers cached Mem: 3961296 3665 0 48154 -/+ buffers/cache: 93 3868 Swap: 2070 0 2070 uname -a Linux nas1 2.6.14.2-smp #2 SMP Thu Nov 17 15:31:40 GMT 2005 x86_64 x86_64 x86_64 GNU/Linux df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage lsscsi [0:0:0:0]diskATA HTS541080G9SA00 MB4O /dev/sda [4:0:1:0]tapeCERTANCE ULTRIUM 21775 /dev/st0 [4:0:1:1]mediumx QUANTUM UHDL 000E - [6:0:0:0]diskArecaARC-1160-VOL#00 R001 /dev/sdb What happens if you run that manually? Hangs The output of that step does not appear on screen however, so it could be that configure is actually hanging on the step after that. I think it's smbclient that is the problem. The next step is finding out where the gzip program lives. Is does that by looking in several directories. If one of those directories happens to be mounted on a non-responsive NFS-server, you hang here too. The list of directories is: /bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd:/etc:/usr/etc /usr/local/sbin:/usr/local/bin:/usr/ccs/bin and the value of $PATH from the user that runs configure. Anything strange when trying test -e /bin/gzip? (Try that for all the above dirs) Nope, looks fine. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amanda-2.5.0p2 hanging on smbclient with configure
quote who=Gavin Henry quote who=Paul Bijnens On 2006-08-08 16:17, Gavin Henry wrote: Currently trying to compile 2.5.0p2 with: ./configure --with-user=amanda --with-group=disk --with-ssh-security --with-config=Suretec --with-changer-device=/dev/sg2 --with-tape-device=/dev/nst0 But configure just sits there at: checking for smbclient... /usr/bin/smbclient Same when adding --with-smbclient=/usr/bin/smbclient If you do not need smbclient support, then you can configure with --without-smbclient and work around this problem. I have tried that, and with --with-smbclient=no. I've been going through configure.in to see what the probs are. If you do need it... then try to investigate what is blocking. It seems like configure is hanging in one of the next steps. Configure tries to find out what version of smbclient you have by running the command: smbclient '\\not.a.host.name\notashare' -U nosuchuser -N -Tx /dev/null Looks like it's this. It just hangs. Must be smbclient, as it is taking forever, even when I jsut run: smblcient with no options. Forget it, will debug smbclient. Nothing wrong with Amanda. Thanks all. I just setup 2 clients on Fedora Core 5 with 2.5.0p2, and they both are fine. The server is on a SUSE 9.3 x86_64 box, that has (Is a Samba PDC too): free -m total used free sharedbuffers cached Mem: 3961296 3665 0 48154 -/+ buffers/cache: 93 3868 Swap: 2070 0 2070 uname -a Linux nas1 2.6.14.2-smp #2 SMP Thu Nov 17 15:31:40 GMT 2005 x86_64 x86_64 x86_64 GNU/Linux df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage lsscsi [0:0:0:0]diskATA HTS541080G9SA00 MB4O /dev/sda [4:0:1:0]tapeCERTANCE ULTRIUM 21775 /dev/st0 [4:0:1:1]mediumx QUANTUM UHDL 000E - [6:0:0:0]diskArecaARC-1160-VOL#00 R001 /dev/sdb What happens if you run that manually? Hangs The output of that step does not appear on screen however, so it could be that configure is actually hanging on the step after that. I think it's smbclient that is the problem. The next step is finding out where the gzip program lives. Is does that by looking in several directories. If one of those directories happens to be mounted on a non-responsive NFS-server, you hang here too. The list of directories is: /bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd:/etc:/usr/etc /usr/local/sbin:/usr/local/bin:/usr/ccs/bin and the value of $PATH from the user that runs configure. Anything strange when trying test -e /bin/gzip? (Try that for all the above dirs) Nope, looks fine. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amanda-2.5.0p2 hanging on smbclient with configure
quote who=Gavin Henry quote who=Gavin Henry quote who=Paul Bijnens On 2006-08-08 16:17, Gavin Henry wrote: Currently trying to compile 2.5.0p2 with: ./configure --with-user=amanda --with-group=disk --with-ssh-security --with-config=Suretec --with-changer-device=/dev/sg2 --with-tape-device=/dev/nst0 But configure just sits there at: checking for smbclient... /usr/bin/smbclient Same when adding --with-smbclient=/usr/bin/smbclient If you do not need smbclient support, then you can configure with --without-smbclient and work around this problem. I have tried that, and with --with-smbclient=no. I've been going through configure.in to see what the probs are. If you do need it... then try to investigate what is blocking. It seems like configure is hanging in one of the next steps. Configure tries to find out what version of smbclient you have by running the command: smbclient '\\not.a.host.name\notashare' -U nosuchuser -N -Tx /dev/null Looks like it's this. It just hangs. Must be smbclient, as it is taking forever, even when I jsut run: smblcient with no options. Forget it, will debug smbclient. Nothing wrong with Amanda. Thanks all. strace smbclient -d 5 show it sitting at: futex(0x2bdf2dc0, FUTEX_WAIT, 2, NULL Hmm. I just setup 2 clients on Fedora Core 5 with 2.5.0p2, and they both are fine. The server is on a SUSE 9.3 x86_64 box, that has (Is a Samba PDC too): free -m total used free sharedbuffers cached Mem: 3961296 3665 0 48 154 -/+ buffers/cache: 93 3868 Swap: 2070 0 2070 uname -a Linux nas1 2.6.14.2-smp #2 SMP Thu Nov 17 15:31:40 GMT 2005 x86_64 x86_64 x86_64 GNU/Linux df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage lsscsi [0:0:0:0]diskATA HTS541080G9SA00 MB4O /dev/sda [4:0:1:0]tapeCERTANCE ULTRIUM 21775 /dev/st0 [4:0:1:1]mediumx QUANTUM UHDL 000E - [6:0:0:0]diskArecaARC-1160-VOL#00 R001 /dev/sdb What happens if you run that manually? Hangs The output of that step does not appear on screen however, so it could be that configure is actually hanging on the step after that. I think it's smbclient that is the problem. The next step is finding out where the gzip program lives. Is does that by looking in several directories. If one of those directories happens to be mounted on a non-responsive NFS-server, you hang here too. The list of directories is: /bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd:/etc:/usr/etc /usr/local/sbin:/usr/local/bin:/usr/ccs/bin and the value of $PATH from the user that runs configure. Anything strange when trying test -e /bin/gzip? (Try that for all the above dirs) Nope, looks fine. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
RE: Restoring windows partition written using smbclient
Another one for you maybe?
Although I think this one might just be a case of it not going to work
like this and needing to change it...
DLE:
autonomy.deanst.rroom.net /mnt_f/Websites
comp-root-tar-win
From amanda.conf
define dumptype comp-root-tar-win {
root-tar
comment Root partitions with compression
compress client fast
index
#exclude list /var/lib/amanda/exclusions.txt
}
So I'm doing this (and version of it):
# /usr/sbin/amrestore -p /dev/nst0 autonomy.deanst.rroom.net
'/mnt_f/Websites' | gtar --numeric-owner -xpvf -
And get
gzip: stdin: not in gzip format
Error 32 (Broken pipe) offset 32768+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
Any ideas?
Thanks in advance!! - jc
-Original Message-
From: Paul Bijnens [mailto:[EMAIL PROTECTED]
Sent: 07 June 2006 14:40
To: John Clement
Cc: amanda-users@amanda.org
Subject: Re: Restoring windows partition written using smbclient
On 2006-06-07 15:23, John Clement wrote:
I'm trying to restore the contents of
AMANDA: FILE 20060601 orinoco.deanst.rroom.net
//tlswindev1.deanst.rroom.net/e$ lev 0 comp .gz program
/usr/bin/smbclient
However I don't know how to get this off the tape into a
usable format.
The first 32K block of the file on tape contains the instructions.
Have you read:
http://wiki.zmanda.com/index.php/Restoring_files
Especially the secion about restoring with amrestore.
The windows tar is compatible with gnutar, so to restore on
the server itself, just use gnutar.
It was generated from the DLE
orinoco.deanst.rroom.net//tlswindev1.deanst.rroom.net/e$
comp-root-tar-win
And from amanda.conf
define dumptype comp-root-tar-win {
root-tar
comment Root partitions with compression
compress client fast
index
#exclude list /var/lib/amanda/exclusions.txt
}
I need to restore it to the amanda server as I'm still trying to
reinstall 'tlswindev1' after its only disk (yes, I know, when its
replaced I'll be insisting on RAID) died last night, and I can't
afford the network traffic (the dump to tape should be about 30GB).
Something like this should work (untested):
# cd /space/tmp # somewhere with enough free diskspace
# mt -t /dev/st0 rewind # fill in your tape device
# amrestore -p /dev/nst0 orinoco.deanst.rroom.net
'//tlswindev1.deanst.rroom.net/e\$' | gtar --numeric-owner -xpvf -
--
Paul Bijnens, xplanation Technology ServicesTel +32
16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32
16 397.512
http://www.xplanation.com/ email:
[EMAIL PROTECTED]
**
*
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z,
^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close,
bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort,
hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$,
shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock,
Stop-A, ... *
* ... Are you sure? ... YES ... Phew ... I'm out
*
**
*
Restoring windows partition written using smbclient
I'm trying to restore the contents of
AMANDA: FILE 20060601 orinoco.deanst.rroom.net
//tlswindev1.deanst.rroom.net/e$ lev 0 comp .gz program
/usr/bin/smbclient
However I don't know how to get this off the tape into a usable format.
It was generated from the DLE
orinoco.deanst.rroom.net//tlswindev1.deanst.rroom.net/e$
comp-root-tar-win
And from amanda.conf
define dumptype comp-root-tar-win {
root-tar
comment Root partitions with compression
compress client fast
index
#exclude list /var/lib/amanda/exclusions.txt
}
I need to restore it to the amanda server as I'm still trying to
reinstall 'tlswindev1' after its only disk (yes, I know, when its
replaced I'll be insisting on RAID) died last night, and I can't afford
the network traffic (the dump to tape should be about 30GB).
Any suggestions much appreciated!
Thanks, John
Re: Restoring windows partition written using smbclient
On 2006-06-07 15:23, John Clement wrote:
I'm trying to restore the contents of
AMANDA: FILE 20060601 orinoco.deanst.rroom.net
//tlswindev1.deanst.rroom.net/e$ lev 0 comp .gz program
/usr/bin/smbclient
However I don't know how to get this off the tape into a usable format.
The first 32K block of the file on tape contains the instructions.
Have you read:
http://wiki.zmanda.com/index.php/Restoring_files
Especially the secion about restoring with amrestore.
The windows tar is compatible with gnutar, so to restore on the
server itself, just use gnutar.
It was generated from the DLE
orinoco.deanst.rroom.net//tlswindev1.deanst.rroom.net/e$
comp-root-tar-win
And from amanda.conf
define dumptype comp-root-tar-win {
root-tar
comment Root partitions with compression
compress client fast
index
#exclude list /var/lib/amanda/exclusions.txt
}
I need to restore it to the amanda server as I'm still trying to
reinstall 'tlswindev1' after its only disk (yes, I know, when its
replaced I'll be insisting on RAID) died last night, and I can't afford
the network traffic (the dump to tape should be about 30GB).
Something like this should work (untested):
# cd /space/tmp # somewhere with enough free diskspace
# mt -t /dev/st0 rewind # fill in your tape device
# amrestore -p /dev/nst0 orinoco.deanst.rroom.net
'//tlswindev1.deanst.rroom.net/e\$' |
gtar --numeric-owner -xpvf -
--
Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... Are you sure? ... YES ... Phew ... I'm out *
***
RE: Restoring windows partition written using smbclient
Thanks Paul!!! That worked a treat.
-Original Message-
From: Paul Bijnens [mailto:[EMAIL PROTECTED]
Sent: 07 June 2006 14:40
To: John Clement
Cc: amanda-users@amanda.org
Subject: Re: Restoring windows partition written using smbclient
On 2006-06-07 15:23, John Clement wrote:
I'm trying to restore the contents of
AMANDA: FILE 20060601 orinoco.deanst.rroom.net
//tlswindev1.deanst.rroom.net/e$ lev 0 comp .gz program
/usr/bin/smbclient
However I don't know how to get this off the tape into a
usable format.
The first 32K block of the file on tape contains the instructions.
Have you read:
http://wiki.zmanda.com/index.php/Restoring_files
Especially the secion about restoring with amrestore.
The windows tar is compatible with gnutar, so to restore on
the server itself, just use gnutar.
It was generated from the DLE
orinoco.deanst.rroom.net//tlswindev1.deanst.rroom.net/e$
comp-root-tar-win
And from amanda.conf
define dumptype comp-root-tar-win {
root-tar
comment Root partitions with compression
compress client fast
index
#exclude list /var/lib/amanda/exclusions.txt
}
I need to restore it to the amanda server as I'm still trying to
reinstall 'tlswindev1' after its only disk (yes, I know, when its
replaced I'll be insisting on RAID) died last night, and I can't
afford the network traffic (the dump to tape should be about 30GB).
Something like this should work (untested):
# cd /space/tmp # somewhere with enough free diskspace
# mt -t /dev/st0 rewind # fill in your tape device
# amrestore -p /dev/nst0 orinoco.deanst.rroom.net
'//tlswindev1.deanst.rroom.net/e\$' | gtar --numeric-owner -xpvf -
--
Paul Bijnens, xplanation Technology ServicesTel +32
16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32
16 397.512
http://www.xplanation.com/ email:
[EMAIL PROTECTED]
**
*
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z,
^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close,
bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort,
hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$,
shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock,
Stop-A, ... *
* ... Are you sure? ... YES ... Phew ... I'm out
*
**
*
sendsize - smbclient du
I have amanda 2.4.5 install on a FC4 machine. I plan to use this machine to backup several Windows 2K and XP machines. It is replacing a machine that is running amanda 2.4.4 running on FC2. The new machine has smbclient 3.0.14a-2, while the old has 3.0.10-1.fc2. I have not been able to get the new machine to backup a windows machine yet. It seems to hang while getting the estimates. So, I tried to issue the du command from the smb prompt after I connected to a share. du seems to take forever. After 10 minutes, it has not timed out. I searched the samba site and google for issues with du in the smbclient, and found nothing. Have others run into this problem? Clearly, it is not and amanda issue, but I thought this group might be able to provide some useful information. I built amanda from source, but I installed samba from rpm. Thanks
SMBCLIENT program not available
I am running a new backup server with a vanilla load of RedHat with an LTO library: Red Hat Enterprise Linux ES release 3 (Taroon). I have tried the stock amanda and samba packages, and got this error on amcheck: ERROR: localhost: [This client is not configured for samba: //sleepy/netapps] ERROR: localhost: [This client is not configured for samba: //sleepy/c$] ERROR: localhost: [SMBCLIENT program not available] smbclient works fine with these shares. I have compiled amanda again to make sure that smbclient support is included. And when I check with amadmin, it is listed correctly. I have verified and rebuilt the /etc/amandapass file. I used to run amanda backups on the same shares on my previous backup server (running RedHat 8 and a DLT library), and it worked fine. I have compiled and installed both amanda and samba, with the same results. samba-3.0.14a amanda-2.4.4p2 --Dave
Re: SMBCLIENT program not available
On Wed, Jun 29, 2005 at 01:52:02PM -0700, David Howard wrote: I am running a new backup server with a vanilla load of RedHat with an LTO library: Red Hat Enterprise Linux ES release 3 (Taroon). I have tried the stock amanda and samba packages, and got this error on amcheck: ERROR: localhost: [This client is not configured for samba: //sleepy/netapps] ERROR: localhost: [This client is not configured for samba: //sleepy/c$] ERROR: localhost: [SMBCLIENT program not available] smbclient works fine with these shares. I have compiled amanda again to make sure that smbclient support is included. And when I check with amadmin, it is listed correctly. I have verified and rebuilt the /etc/amandapass file. I used to run amanda backups on the same shares on my previous backup server (running RedHat 8 and a DLT library), and it worked fine. Don't know, but might the use of localhost in your disklist be the problem. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: SMBCLIENT program not available
David Howard wrote: I am running a new backup server with a vanilla load of RedHat with an LTO library: Red Hat Enterprise Linux ES release 3 (Taroon). I have tried the stock amanda and samba packages, and got this error on amcheck: ERROR: localhost meeep meeep. localhost-error. Please use FQDNs in your disklist before you proceed. Apart from that I'd check my dumptypes for GNUTAR -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: SMBCLIENT program not available
Jon LaBadie wrote: On Wed, Jun 29, 2005 at 01:52:02PM -0700, David Howard wrote: I am running a new backup server with a vanilla load of RedHat with an LTO library: Red Hat Enterprise Linux ES release 3 (Taroon). I have tried the stock amanda and samba packages, and got this error on amcheck: ERROR: localhost: [This client is not configured for samba: //sleepy/netapps] ERROR: localhost: [This client is not configured for samba: //sleepy/c$] ERROR: localhost: [SMBCLIENT program not available] smbclient works fine with these shares. I have compiled amanda again to make sure that smbclient support is included. And when I check with amadmin, it is listed correctly. I have verified and rebuilt the /etc/amandapass file. I used to run amanda backups on the same shares on my previous backup server (running RedHat 8 and a DLT library), and it worked fine. Don't know, but might the use of "localhost" in your disklist be the problem. Hmm. No go with FQDN's, I tried the amanda server's FQDN and also use localhost.localdomain, but it still does not work. It seems as if amanda still does not see the smbclient program. When I run "amadmin DailySet1 version" it does show the smbclient correctly: SAMBA_CLIENT="/usr/bin/smbclient" GNUTAR="/bin/gtar" and /usr/bin/smbclient by itself works fine. Is there a way to force amanda to the absolute path for smbclient on the command line? Dave
Re: SMBCLIENT program not available
Please don't send HTML email. And why is Thunderbird mucking with the quoting so much? On Wed, 29 Jun 2005 at 2:29pm, David Howard wrote Hmm. No go with FQDN's, I tried the amanda server's FQDN and also use localhost.localdomain, but it still does not work. It seems as if amanda still does not see the smbclient program. When I run amadmin DailySet1 version it does show the smbclient correctly: SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/gtar and /usr/bin/smbclient by itself works fine. Is there a way to force amanda to the absolute path for smbclient on the command line? You don't happen to have 2 sets of amanda binaries, do you? I.e., is the one compiled before smbclient was installed still hanging around somewhere? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: SMBCLIENT program not available
Joshua Baker-LePain wrote: Please don't send HTML email. And why is Thunderbird mucking with the quoting so much? On Wed, 29 Jun 2005 at 2:29pm, David Howard wrote Hmm. No go with FQDN's, I tried the amanda server's FQDN and also use localhost.localdomain, but it still does not work. It seems as if amanda still does not see the smbclient program. When I run amadmin DailySet1 version it does show the smbclient correctly: SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/gtar and /usr/bin/smbclient by itself works fine. Is there a way to force amanda to the absolute path for smbclient on the command line? You don't happen to have 2 sets of amanda binaries, do you? I.e., is the one compiled before smbclient was installed still hanging around somewhere? ARGH! I think that did it. The compiled amandad went to /usr/local/libexec/amandad and the xinetd.d/amanda was pointing to /usr/lib/amanda/amandad I'll flog myself later... ;)Thank you all for the suggestions. Dave
smbclient and amandapass problem
Hi! I'm new in the list! I'm experiencing some dificulties with amanda and smb shares: in the file /etc/amanda/DailySet1/disklist, I have: backup//apolo/ARGOS nocomp-user-gnutar backup //homero/D$/Netscape nocomp-user-gnutar and in the file /etc/amandapass I have: //apolo/ARGOS [EMAIL PROTECTED] MYWORKGROUP //homero/D$/Netscape [EMAIL PROTECTED] MYWORKGROUP but when I run /usr/sbin/amcheck DailySet1, I got the follow error: [EMAIL PROTECTED]:~$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /usr/local/amanda/dumps: 11480512 KB disk space available, that's plenty Holding disk /var/backups/amanda/dumps: 9209888 KB disk space available, that's plenty amcheck-server: slot 4: date 20041019 label DailySet104 (exact label match) NOTE: skipping tape-writable test Tape DailySet104 label ok NOTE: info dir /var/lib/amanda/DailySet1/curinfo/backup/__homero_D$_Netscape: does not exist Server check took 0.313 seconds Amanda Backup Client Hosts Check ERROR: backup: [cannot find password for //homero/D$/Netscape] Client check: 1 host checked in 26.793 seconds, 1 problem found (brought to you by Amanda 2.4.4p3) amanda can find the password for //apolo/ARGOS but not for //homero/D$/Netscape. I tried with //homero/D$ and then amanda can find the password :-( I can't find what's wrong with this :-(. I hope someone can help me here :-) PS: I'm using amanda on a Debian GNU/Linux (testing / sarge) Thanks in advance. -- Julián
smbclient error
I've been using amanda 2.4.1p1 and Samba 2.0.6, for 2 or 3 years, to back up a network of solaris and NT workstations. However, I'm increasingly finding that one of the NT filesystem backups fails with the following error: servb //mainserver/Users lev 0 FAILED [/usr/local/samba/bin/smbclient returned 1] There are also a lot of error messages such as: ? Error reading file ... ? Didn't get entire file. size=6250496, nread=65520 ? Expected SMBtrans2 response, got command 0x08 ? code 0 listing ... I have recently upgraded from Amanda 2.4.1p1 to 2.4.4p1, but the problem is still present. Has anyone else seen these sort of errors? Would it help to upgrade Samba - if so which version? Thanks, Julian _ Get Paid to Surf the Web! http://www.alladvantage.com/home.asp?refid=AVZ855
Re: smbclient error
Julian C H Stevens wrote: I've been using amanda 2.4.1p1 and Samba 2.0.6, for 2 or 3 years, to ... ? Error reading file ... ? Didn't get entire file. size=6250496, nread=65520 ? Expected SMBtrans2 response, got command 0x08 ? code 0 listing ... I have recently upgraded from Amanda 2.4.1p1 to 2.4.4p1, but the problem is still present. To salvage samba errors, it seem to a better alternative is to upgrade samba. 2.0.6 is prehistoric! Has anyone else seen these sort of errors? Would it help to upgrade Samba - if so which version? samba 3.0 is fine. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: smbclient error
On Tuesday 09 December 2003 11:56, Julian C H Stevens wrote: I've been using amanda 2.4.1p1 and Samba 2.0.6, for 2 or 3 years, to back up a network of solaris and NT workstations. However, I'm increasingly finding that one of the NT filesystem backups fails with the following error: Yikes, that is by now, a very grey, dusty version of samba. A lot has been happening just in the last 2 weeks, so I'd get the absolute latest version and build it. I don't use it here for amanda as this is an all linux house. But I can sure follow the threads of late. servb //mainserver/Users lev 0 FAILED [/usr/local/samba/bin/smbclient returned 1] There are also a lot of error messages such as: ? Error reading file ... ? Didn't get entire file. size=6250496, nread=65520 ? Expected SMBtrans2 response, got command 0x08 ? code 0 listing ... I have recently upgraded from Amanda 2.4.1p1 to 2.4.4p1, but the problem is still present. Has anyone else seen these sort of errors? Would it help to upgrade Samba - if so which version? Thanks, Julian _ Get Paid to Surf the Web! http://www.alladvantage.com/home.asp?refid=AVZ855 -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
anyone used smbclient -T with the r option?
I'm trying to find someone with experience or documentation for the use of pattern matching in samba's smbclient when using its tar (-T) exclude and include options. My objective is to write an smbclient wrapper that would allow multiple items to be excluded via an file containing a list of patterns. I had my first significant success last evening, but can not use wildcard patterns. Each excluded file must be specifically listed. For seven samba shares, here was my total STRANGE report last evening. Normally it seems to be more than a page. FAILURE AND STRANGE DUMP SUMMARY: butch //tec/C lev 0 STRANGE ... /-- butch //tec/C lev 0 STRANGE sendbackup: start [butch://tec/C level 0] sendbackup: info BACKUP=/usr/sfw/bin/smbclient sendbackup: info RECOVER_CMD=/usr/sfw/bin/smbclient -f... - sendbackup: info end ? NT_STATUS_SHARING_VIOLATION opening remote file \WINNT\Temp\JET7D2A.tmp (\WINNT\Temp\) ? NT_STATUS_SHARING_VIOLATION opening remote file \WINNT\Temp\JETAEF6.tmp (\WINNT\Temp\) | tar: dumped 26444 files and directories | Total bytes written: 1827618304 sendbackup: size 1784784 sendbackup: end \ BTW the comments in amanda.conf regarding exclude and samba are not up to date. # exclude - specify files and directories to be excluded from the dump. # Useful with gnutar only; silently ignored by dump and samba. In fact you can do a single file exclude. But you can't do a list or an append (in my experience). My smbclient wrapper checks if this excluded file is in fact a file on the samba host rather than the client. If it is a file on the host, it is assumed to contain a list of files to be excluded. BTW2, the smbclient man page does indicate it can do Includes as well as Excludes. For fans of this feature, perhaps it can be incorporated into amanda backups using smbclient in the future. Maybe it already is, but I've not checked and if so, the comments are similarly out of date. Back to my inability to use patterns; The smbclient man page says to do an exclude on tar file creation you can do -TcX options. Further, it says adding an r (-TcXr) will let the files names to be patterns, either regular expressions or simple wildcards depending on smbclient compile options. Whenever I try to add the r option, even to an smbclient command line that excludes files properly with no wild cards, I get a message like tar_re set on but nothing at all is excluded, even things that were without the r. FWIW, my samba install is the one supplied with Solaris 9, a version 2.2.???. I've looked for docs beyond the man page that describe the feature but have found nothing, and no example command lines. I looked for samba mailing lists and found either non-English lists :( or ones that in the last 500 messages or so did not even mention smbclient. Anyone care to share their experience using smbclient (or I guess smbtar) with the combination of X and r options? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: anyone used smbclient -T with the r option?
On Mon, Aug 18, 2003 at 09:17:47PM +0200, Gregor Ibic wrote: I tried the regular expresion and excluding files, and it works just fine. Samba version 3? Or a version 2? Here are some smbclient sample lines (the args from my wrapper log) I've been trying. See any problem compared with your attempts. 1. Generated by amanda, unmodified by my wrapper: CmdLine: \\tec\E -U administrator -E -W tec -d0 -TXqc - /bins Properly excludes the PC file E:\bins. Could be ./bins or /bins in my experience. 2. Same line as above generated by amanda, modified by my wrapper to: CmdLine: \\tec\E -U administrator -E -W tec -d0 -TXqcr - /bins Whether given as /bins or ./bins, it is not excluded if the r is present. Though I did not expect it to matter, I've tried different positions for the r, like -TrXqc, -TXrqc. Still does not get excluded. 3. Similar line to the first, but giving the file to be excluded with with a wildcard. Unmodified by my wrapper: CmdLine: \\tec\E -U administrator -E -W tec -d0 -TXqc - /bin? The E:\bins file was not excluded as the wildcarding was not turned on. Similarly for wildcards of ., *, and .*. Also, a * or .* in front of the / in the file name. 4. Similar line number 3, but then modified by my wrapper to add the r: CmdLine: \\tec\E -U administrator -E -W tec -d0 -TXqcr - /bin? Again, could not get it to exclude anything. Also tried things like *.html. In each case where the r is given, there is a message in the amdump report about the tar_re search being set: /-- butch //tec/E lev 0 STRANGE sendbackup: start [butch://tec/E level 0] sendbackup: info BACKUP=/usr/sfw/bin/smbclient sendbackup: info RECOVER_CMD=/usr/sfw/bin/smbclient -f... - sendbackup: info end ? tar_re_search set | tar: dumped 20 files and directories | Total bytes written: 355328 sendbackup: size 347 sendbackup: end \ Which makes it sound like something should be trying wildcard matching. Either regular expression or simple patterns as per the man page. Any ideas? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: anyone used smbclient -T with the r option?
Samba3rc1. i tried to exclude smbclient //server/share -TcaqrX backup.tar *.doc and it worked then tried to exclude pagefile.sys smbclient //server/share -TcaqrX backup.tar pagefile.sys didnt work / but it is not a proper regular expression. this is ok. smbclient //server/share -TcaqrX backup.tar *pagefile.sys worked fine that's it. i moded samba like i said, but im a little wondered why i get segfault on selecting some directories in amrecover. regards, gregor
can't recover data from backup with smbclient
Hello, I found this message in my report email below: /-- jupiter-ba //exploitsrvdc2/christian.moliere$ lev 0 STRANGE sendbackup: start [jupiter-backup://exploitsrvdc2/christian.moliere$ level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Internet Explorer.lnk (\profil\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Outlook Express.lnk (\profil\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Macros complémentaires\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Modèles\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Office\Fichiers récents\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Office\Récents\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Requêtes\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Word\DÉMARRAGE\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Épreuve\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Favoris\La Boutique des [EMAIL PROTECTED] (\profil\Favoris\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Favoris\Média\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Favoris\Événements Web.url (\profil\Favoris\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Menu Démarrer\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Mes documents\Mes images\Athlète.jpg (\profil\Mes documents\Mes images\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Modèles\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\CR_CarnetSanté_VoilaMail_1311.doc.lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\Disquette 3½ (A).lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\dossier développeur.lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\Informatique - Analyste Qualité - 6 postes à pourvoir.rtf.lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\Inventaire parc machinesà sauvegarder.xls (2).lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\Inventaire parc machinesà sauvegarder.xls.lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\Offre_salariés.ppt.lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\Référentiel Fiches Pratiques Réseau.xls.lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Recent\VM-EX23-Désactivation des BAL des spammeurs.doc.lnk (\profil\Recent\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\SendTo\Bureau (créer un raccourci).DeskLink (\profil\SendTo\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\SendTo\Disquette 3½ (A).lnk (\profil\SendTo\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Voisinage réseau\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil2\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Internet Explorer.lnk (\profil2\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil2\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Outlook Express.lnk (\profil2\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Application Data\Microsoft\Macros complémentaires\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Application Data\Microsoft\Modèles\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Application Data\Microsoft\Office\Fichiers récents\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Application Data\Microsoft\Office\Récents\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Application Data\Microsoft\Requêtes\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Application Data\Microsoft\Word\DÉMARRAGE\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Application Data\Microsoft\Épreuve\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil2\Favoris\La Boutique des [EMAIL PROTECTED] (\profil2\Favoris\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Favoris\Média\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil2\Favoris\Événements Web.url (\profil2\Favoris\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil2\Menu Démarrer\* ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil2\Mes
Re: can't recover data from backup with smbclient
Moliere Christian wrote: ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Internet Explorer.lnk (\profil\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Outlook Express.lnk (\profil\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Macros complémentaires\* ...etc... The above msgs have to do with the codepage setting of your samba. I still haven't figured out the exact details, but tweeking the smb.conf file helps. I had to add: character set = ISO8859-1 to the global section. This solved that problem for win2000 and WinNT4 systems, but it introduced the problem to Win9x. That was a long time ago; and we have no Win9x anymore in your disklist. I can't find any index file in the index directory and of course when I try to recover them, mrecover command tell me : sethost jupiter-backup 501 No index records for host: jupiter-backup. Have you enabled indexing? We'll repeat the question. Have you enable indexing? Here it is my disklist : jupiter-backup //exploitsrvdc2/christian.moliere$ nocomp-user-gnutar The dumptype nocomp-user-gnutar should have indexing enabled. Verify this with: amadmin YourConfig disklist jupiter-backup \ '//exploitsrvdc2/christian.moliere$' and see if it has index YES or index NO. If it has index YES, then we'll need more information, like the relevant debug files in /tmp/amanda/*. I have a backup file and I can recover some datas with dd command. The singular of data is datum :-) (restored from my latin archive backups). Do you mean you understand how to work with the bare files using dd and gnutar, and also how using amrestore? Or do you mean that not all the data can be restored? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: can't recover data from backup with smbclient
Paul Bijnens wrote: Moliere Christian wrote: ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Internet Explorer.lnk (\profil\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \profil\Application Data\Microsoft\Internet Explorer\Quick Launch\Démarrer Outlook Express.lnk (\profil\Application Data\Microsoft\Internet Explorer\Quick Launch\) ? NT_STATUS_OBJECT_NAME_NOT_FOUND listing \profil\Application Data\Microsoft\Macros complémentaires\* ...etc... The above msgs have to do with the codepage setting of your samba. I still haven't figured out the exact details, but tweeking the smb.conf file helps. I had to add: character set = ISO8859-1 to the global section. This solved that problem for win2000 and WinNT4 systems, but it introduced the problem to Win9x. That was a long time ago; and we have no Win9x anymore in your disklist. I set this parameter character set = ISO8859-1 in the smb.conf. I can't find any index file in the index directory and of course when I try to recover them, mrecover command tell me : sethost jupiter-backup 501 No index records for host: jupiter-backup. Have you enabled indexing? We'll repeat the question. Have you enable indexing? No I didn't. I set it in my dumptype and tried again a backup. That has resolved my error messages in the email report because I have no more error messages in it. I checked if I have now an index file and I have it. Here it is my disklist : jupiter-backup //exploitsrvdc2/christian.moliere$ nocomp-user-gnutar The dumptype nocomp-user-gnutar should have indexing enabled. Verify this with: amadmin YourConfig disklist jupiter-backup \ '//exploitsrvdc2/christian.moliere$' and see if it has index YES or index NO. If it has index YES, then we'll need more information, like the relevant debug files in /tmp/amanda/*. I have a backup file and I can recover some datas with dd command. The singular of data is datum :-) (restored from my latin archive backups). Do you mean you understand how to work with the bare files using dd and gnutar, and also how using amrestore? Or do you mean that not all the data can be restored? That meant I was able to restore all the data in the backup file. Finaly I tried to restore all the new data and it was ok. Thanks for your speed help. -- Sincerely, Cordialement, Christian MOLIERE Tél : +33 1 43 60 11 50 Mobile : +33 6 73 37 36 33
Amanda and smbclient not working
Hi, I have been trying to get amanda to backup some of our windows servers, without much luck. Here is what the configuration looks like: /etc/amandapass file: //server/share administrator%password disklist entry: server //server/share central The dump program is set to GNUTAR. When I run amcheck it reports that the host is down. I used strace to see what amcheck is doing, and it seems that amcheck thinks the server is a unix/linux amanda client (it is sending data to port 10080 (amanda client's udp port). I am using amanda 2.4.4 and samba 2.2.8a on Redhat linux 7.3. If you have any ideas please let me know. thanks, -- Mark Le Noury Barone, Budge Dominick Tel. (+2711)532 8415 Cell. +27825624412 E-mail: [EMAIL PROTECTED] This e-mail is confidential and subject to the disclaimer published on the website http://www.bbd.co.za/emaildisclaimer.htm.
Re: Amanda and smbclient not working
On 23 Jun 2003 at 3:45pm, Mark Le Noury wrote disklist entry: server //server/share central The dump program is set to GNUTAR. When I run amcheck it reports that the host is down. I used strace to see what amcheck is doing, and it seems that amcheck thinks the server is a unix/linux amanda client (it is sending data to port 10080 (amanda client's udp port). The client needs to be a *nix box. It then runs smbclient and grabs the data off the 'doze box. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
smbclient question
Good Morning, I have setup amanda to archive my win 2k clients, and all appeared to be well in testing. I have a client that has a 63G file, that smbclient is only showing as 170M. This is what amanda archived and if I view the file with smbclient the size of the file is reported as 170M. I am running 2.4.2p2 on linux. Any ideas why smbclient is reporting the size incorrectly? Thank you, Drew
Re: smbclient question
On Wed, Nov 06, 2002 at 10:38:43AM -0500, [EMAIL PROTECTED] wrote: I have setup amanda to archive my win 2k clients, and all appeared to be well in testing. I have a client that has a 63G file, that smbclient is only showing as 170M. This is what amanda archived and if I view the file with smbclient the size of the file is reported as 170M. I think this is a restriction of smbfs which has a maximum file size of 2GB. You'll probably find that 170M = actual file size MOD 2GB. Regards, Niall O Broin
Re: smbclient question
The interesting thing is that I restored it an it was only 170M locally on my archive host. Are you saying when I move it over it will expand? I really do not see how that is possible, but I am no smb expert.. Thank you, Drew On Wed, 6 Nov 2002, Niall O Broin wrote: On Wed, Nov 06, 2002 at 10:38:43AM -0500, [EMAIL PROTECTED] wrote: I have setup amanda to archive my win 2k clients, and all appeared to be well in testing. I have a client that has a 63G file, that smbclient is only showing as 170M. This is what amanda archived and if I view the file with smbclient the size of the file is reported as 170M. I think this is a restriction of smbfs which has a maximum file size of 2GB. You'll probably find that 170M = actual file size MOD 2GB. Regards, Niall O Broin
Re: smbclient question
On Wed, Nov 06, 2002 at 11:28:35AM -0500, [EMAIL PROTECTED] wrote: The interesting thing is that I restored it an it was only 170M locally on my archive host. Are you saying when I move it over it will expand? I Of course not - what did I say that makes you think that ? really do not see how that is possible, but I am no smb expert.. That's not possible, even for smb experts. A snake oil salesman might be able to help you. Regards, Niall O Broin
smbclient and tar
Where do I need to look if I want to add some functionality to the smbclient. Unless I am mistaken the newer versions of smbclient allows you to specify an exclude list not just a single file. From the sambatar man page we have the following: o X - Exclude files and directories. Causes tar files to be excluded from an extract or create. See example below. Filename globbing works in one of two ways now. See r below. o r - Regular expression include or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not com- piled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. This is used in conjunction with the -T option. This could make the samba component of amrecover a bit more like the normal recover. I'm also having to track down exactly where the tar arguments are built for a backup. =G=
Resoved: SMBCLIENT program not available
Am Montag, 5. August 2002 23:38 schrieben Sie: Hi, it was too easy: It just took a while for me to make out, that I need in the .amandahosts not the server running samba, but Winpc with it's name and my amanda login-name (additional the entry in the amandapass). I found out after deinstalling samba and amanda, getting the whole stuff fresh from the internet, installing it, having the same problem as before, and at last reading for the 10th time the same articles there is a hint in the book mentioned on the amanda-page to the .amandahosts. Now samba-shares are backuped (Yeeeh ), but my local disks tell me something about beeing offline. I installed the latestet version of gnutar, nothing changes, but I am still looking in articles, mailling-list, etc. ... maybe I'll find out. Thanks a lot to all who helped me and were occupied with my problem. Martin Am Freitag, 12. Juli 2002 20:06 schrieben Sie: hello, Did you ever get this resolved? I just remembered also that if samba isn't setup correctly, this might produce this error. I believe in order for samba to work at all, it needs an smb.conf file in the appropriate location. --jason Hi, I had to do a new installation because of hardware problems ( High Voltage because of thunderstorm), so my tests were interrupted. No, I have the same problem. Thanks for Your hint to the samba-configuration, the only thing I found was, because in the newer SuSE-dist. the config files are in /etc/samba, so I copied the smb.conf to /etc, but this did not change. I can manually call smbclient as user amanda and see the shares, but amcheck (and amdump) don't work. I would really like to use amanda, but one of the points is, that I have to backup several NT's and one DEC OSF/1 . I think I will try the hard way: I do a smbmount for every NT-Server and try to backup the dir. I hope DEC OSF will do better. martin
smbclient backup problem, sometimes complete, sometimes incomplete!
Hello,
We use AMANDA to full backup (level 0 everyday) our files at Windows
2000 Server by using the smbclient support, but I found that sometimes
it backup all the files but sometimes seems it doesn't!
We have 14G files at one of the server share but sometimes the amanda
reports it only backup 4G of them! The share has 33000 files inside it
but amanda report it only backup 16000 of them!
We found that when the problem happens, there are some strange messages
displayed:
? SUCCESS - 0 listing \folder path*
Other shares backed up completely won't has such message!
We're using AMANDA 2.4.3b3 and SAMBA 2.2.5, the system is a Debian 2.2
system with Linux kernel 2.2.17. Please help us!
Best Regards,
Charles
Below is some amconfig we've set for one of our tapes
org org name
mailto root
dumpuser backup
inparallel 1
netusage 1000
dumpcycle 0 days
tapecycle 1 tapes
bumpsize 2000 MB
bumpdays 1
bumpmult 4
tapedev /dev/nst0
etimeout3600
tapetype HP-DAT24
labelstr ^[R|G|B][0-3][0-9]$
Below is one of the problem report we received for one of our tapes
These dumps were to tape B08.
The next tape Amanda expects to use is: R30.
FAILURE AND STRANGE DUMP SUMMARY:
localhost //server/share lev 0 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:01
Run Time (hrs:min) 0:54
Dump Time (hrs:min)0:53 0:53 0:00
Output Size (meg)4692.5 4692.50.0
Original Size (meg) 4692.5 4692.50.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) 1520.9 1520.9--
Tape Time (hrs:min)0:53 0:53 0:00
Tape Size (meg) 4692.6 4692.60.0
Tape Used (%) 19.1 19.10.0
Filesystems Taped 1 1 0
Avg Tp Write Rate (k/s) 1520.9 1520.9--
FAILED AND STRANGE DUMP DETAILS:
/-- localhost //server/share lev 0 STRANGE
sendbackup: start [localhost://server/share level 0]
sendbackup: info BACKUP=/usr/sbin/smbclient
sendbackup: info RECOVER_CMD=/usr/sbin/smbclient -f... -
sendbackup: info end
? SUCCESS - 0 opening remote file \hk264\BD\AA\AG0104.dwg
(\hk264\BD\AA\)
? SUCCESS - 0 opening remote file \hk264\BD\AA\AG0105.dwg
(\hk264\BD\AA\)
? SUCCESS - 0 opening remote file \hk264\BD\AA\old.dwg (\hk264\BD\AA\)
? SUCCESS - 0 opening remote file \hk264\BD\AA\plot.log
(\hk264\BD\AA\)
? SUCCESS - 0 opening remote file \hk264\BD\AA\TEMP.dwg
(\hk264\BD\AA\)
? SUCCESS - 0 listing \hk264\BD\Disapproval\*
? SUCCESS - 0 listing \hk264\BD\Ext\*
? SUCCESS - 0 listing \hk264\BD\Hoarding\*
? SUCCESS - 0 listing \hk264\BD\Lift\*
? SUCCESS - 0 listing \hk264\BD\Phasing\*
? SUCCESS - 0 listing \hk264\BD\_1st Submission\*
? SUCCESS - 0 listing \hk264\Block\*
? SUCCESS - 0 listing \hk264\In\*
? SUCCESS - 0 listing \hk264\Kwan\*
? SUCCESS - 0 listing \hk264\Out\*
? SUCCESS - 0 listing \hk264\Plot\*
? SUCCESS - 0 opening remote file \hk264\plot.log (\hk264\)
? SUCCESS - 0 listing \hk264\Prog\*
? SUCCESS - 0 listing \hk264\Register\*
? SUCCESS - 0 listing \hk264\Sketch\*
? SUCCESS - 0 listing \hk264\Xref\*
? SUCCESS - 0 listing \hk279\*
? SUCCESS - 0 listing \hk282\*
? SUCCESS - 0 listing \hk283s\*
? SUCCESS - 0 listing \hk284\*
? SUCCESS - 0 listing \hk290\*
? SUCCESS - 0 listing \hk292\*
? SUCCESS - 0 listing \hk293\*
? SUCCESS - 0 listing \hk295\*
? SUCCESS - 0 listing \hk297\*
? SUCCESS - 0 listing \hk300\*
? SUCCESS - 0 listing \hk302\*
? SUCCESS - 0 listing \hk303\*
? SUCCESS - 0 listing \hk304\*
? SUCCESS - 0 listing \In\*
? SUCCESS - 0 listing \Invoice 2002-2003\*
? SUCCESS - 0 listing \Lib\*
? SUCCESS - 0 listing \ouhk\*
? SUCCESS - 0 listing \Plot Styles\*
? SUCCESS - 0 listing \Plot Styles.20020704\*
? SUCCESS - 0 listing \Plot Styles.20020706\*
? SUCCESS - 0 listing \PROGRAM FILES\*
? SUCCESS - 0 listing \ptpc007\*
? SUCCESS - 0 listing \ptpc020\*
? SUCCESS - 0 listing \ptpc022\*
? SUCCESS - 0 listing \Ptpc038\*
? SUCCESS - 0 listing \ptpc044\*
? SUCCESS - 0 listing \ptpc058\*
? SUCCESS - 0 listing \ptpc074\*
? SUCCESS - 0 listing \ptpc076\*
? SUCCESS - 0 listing \ptpc078\*
? SUCCESS - 0 listing \ptpc086\*
? SUCCESS - 0 listing \ptpc092\*
? SUCCESS - 0 listing \ptpc099\*
? SUCCESS - 0 listing \ptpc121\*
? SUCCESS - 0 listing \report\*
? SUCCESS - 0 listing \Restore\*
? SUCCESS - 0 listing \Shatin\*
? SUCCESS - 0 listing \TEMPORARY FOLDER\*
? SUCCESS - 0 listing \test\*
| tar: dumped 16917 files and directories
| Total bytes written: 4913287168
sendbackup: size 4798132
sendbackup: end
\
NOTES:
taper: tape B08 kb 4805216 fm 1 [OK]
DUMP SUMMARY:
DUMPER STATS
Re: SMBCLIENT program not available
hello, Did you ever get this resolved? I just remembered also that if samba isn't setup correctly, this might produce this error. I believe in order for samba to work at all, it needs an smb.conf file in the appropriate location. --jason On Tue, Jun 25, 2002 at 11:25:26PM +0200, Martin Schmidt wrote: Hi, I am just testing amanda on my privat network before I will install it in the company. I have a SuSE-Linux 7.3 (rappelkasten) with samba, amanda and tape, and for testing a Win-Nt4 (rumpl). There is no problem running amanda on the linux. So I tried to backup a share from the NT. I created a user amanda on the NT with all privileges on one share. When I do a smbclient from commandline I can see the contents of that share. When I start amcheck, I get the messages: Amanda Backup Client Hosts Check ERROR: localhost: [This client is not configured for samba: //rumpl/lwd] ERROR: localhost: [SMBCLIENT program not available] Client check: 1 host checked in 0.084 seconds, 2 problems found (brought to you by Amanda 2.4.2p2) -- First i supposed, amanda is not configured with-smbclient when I install it from SuSE's CDs, so I got the file from source-forge and did a configure with --with-smbclient=/usr/bin/smbclient --with-user=amanda --with-group=disk (smbclient _is_ there, user and group I took from SuSE's default ). The messages are the same. There is no hint in the FAQs, the doc - directory, but several questions in the mailing list, but all unanswered. So I hope, I get an answer and wipe this problem off. Thanks Martin -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
SMBCLIENT program not available
su operator -c 'smbclient [blither]' works. Does anyone know why I would be getting this from amcheck? Amanda Backup Client Hosts Check ERROR: amnesiac.maxen.net: [This client is not configured for samba: //cwx1/W$] ERROR: amnesiac.maxen.net: [This client is not configured for samba: //cwx1/C$] ERROR: amnesiac.maxen.net: [This client is not configured for samba: //cwx4/M$] ERROR: amnesiac.maxen.net: [This client is not configured for samba: //cwx4/C$] ERROR: amnesiac.maxen.net: [SMBCLIENT program not available] Client check: 1 host checked in 0.114 seconds, 5 problems found -- David L. Aldridge The Aldridge Company 713-403-9150 (fax: 713-621-1826) http://www.aldridge.com/ Powered by Pentium/FreeBSD/Apache - Because it works.
smbclient signal 11
I randomly get these messages - what does smbclient signal 11 mean?? -Michael Blinn FAILURE AND STRANGE DUMP SUMMARY: localhost //ntserver/businesswork lev 0 FAILED [/usr/local/samba/bin/smbclient got signal 11] FAILED AND STRANGE DUMP DETAILS: /-- localhost //ntserver/businesswork lev 0 FAILED [/usr/local/samba/bin/smbclient got signal 11] sendbackup: start [localhost://ntserver/businesswork level 0] sendbackup: info BACKUP=/usr/local/samba/bin/smbclient sendbackup: info RECOVER_CMD=/usr/local/samba/bin/smbclient -f... - sendbackup: info end sendbackup: error [/usr/local/samba/bin/smbclient got signal 11] \ NOTES: taper: tape daily5 kb 146208 fm 4 [OK] DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - localhost-sinesswork 0 FAILED --- localhost-er/ppidocs 0 456299 123392 27.0 8:32 241.2 26:38 77.3 mail /configs0 70 32 45.7 0:00 150.0 0:01 44.4 mail -cal/apache 0 79580 21888 27.5 0:38 582.2 4:38 78.9 mail -/lib/mysql 05930768 13.0 0:01 549.2 0:17 46.2 (brought to you by Amanda version 2.4.2p2)
RE: configure and smbclient
Thanks guys! Once I deleted config.cache (which had the bad smbclient info) configure was happy with the smbclient this time. ;^) Thanks again! -Original Message- From: Christopher Odenbach [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 3:06 AM To: [EMAIL PROTECTED]; John R. Jackson; Davidson, Brian Cc: [EMAIL PROTECTED] Subject: Re: configure and smbclient Hi, checking for smbclient... (cached) /usr/local/samba/bin Two thoughts. First, that (cached) says ./configure is finding the information from a previous run. Remove config.cache and try again. Second, make sure you don't have the SAMBA_CLIENT environment variable set. If you don't specify --with-smbclient=/path/..., ./configure will get the value from this variable. Another thought: --with-smbclient=/path/to/smbclient should _not_ be the only path containing the smbclient binary but the binary itself! So configure with --with-smbclient=/usr/local/samba/bin/smbclient should work. Greets, Christopher
Amcheck error with smbclient
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having trouble trying to get a windows client backed up. First i have a setup like this. The amanda server is Marvin. The PC to be backup is called Win2k. The machine running smbclient is Aries. Disklist on Marvin:- aries //Win2k's IP/C$comp-user-tar /etc/amandapass on Aries:- //Win2k's IP/C$ username%password Output from running amcheck on Marvin:- Amanda Backup Client Hosts Check - ERROR: aries: [PC SHARE //Win2k's IP/C$ access error: host down or invalid password?] Client check: 1 host checked in 0.837 seconds, 1 problem found Output from amadad.debug on Aries:- amandad: debug 1 pid 32285 ruid 34 euid 34 start time Fri Jun 7 03:51:14 2002 amandad: version 2.4.1p1 amandad: build: VERSION=Amanda-2.4.1p1 amandad:BUILT_DATE=Mon Jun 12 23:14:52 MDT 2000 amandad:BUILT_MACH=Linux rover 2.2.15pre15 #1 Thu Mar 23 02:22:27 MST 2000 i686 unknown amandad:CC=gcc amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient amandad:GNUTAR=/bin/tar COMPRESS_PATH=/bin/gzip amandad:UNCOMPRESS_PATH=/bin/gzip MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY amandad:USE_AMANDAHOSTS CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc got packet: - Amanda 2.4 REQ HANDLE 000-20AD0708 SEQ 1023393074 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR //Win2k's IP/C$ 0 OPTIONS |;bsd-auth;compress-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; - sending ack: - Amanda 2.4 ACK HANDLE 000-20AD0708 SEQ 1023393074 - bsd security: remote host marvin amanda local user backup amandahosts security check passed amandad: running service /usr/lib/amanda/selfcheck added interface ip=192.168.1.4 bcast=192.168.1.255 nmask=255.255.255.0 session request to Win2k's IP failed (Called name not present) session request to 203 failed (Called name not present) session setup failed: ERRDOS - ERRnoaccess (Access denied.) amandad: sending REP packet: - Amanda 2.4 REP HANDLE 000-20AD0708 SEQ 1023393074 OPTIONS ; running /usr/bin/smbclient Win2k's IP\\C$ -E -U backup -c quit ERROR [PC SHARE //Win2k's IP/C$ access error: host down or invalid password?] OK /usr/lib/amanda/runtar executable OK /bin/tar executable OK /var/lib/amanda/amandates read/writable OK /var/lib/amanda/gnutar-lists/. read/writable OK /usr/bin/smbclient executable OK [/etc/amandapass is readable, but not by all] OK /bin/gzip executable OK /dev/null read/writable OK /tmp has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /var/lib has more than 64 KB available. - amandad: got ack: - I must have missed something or is it my setup is wrong. I don't have smbclient on the Marvin but i do have smbclient on Aries. I tried runing smbclient by hand it works. /usr/bin/smbclient Win2k's IP\\C$ -E -U backup -c quit -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8/8hRInIYkBVpGqURAry+AJ9RUfRu1ZCRVD11w4oF+2cwu8pePwCfale5 ZTZLA0XLSuXSguxrYzKs99s= =8VxJ -END PGP SIGNATURE-
restore program for /usr/bin/smbclient not available
I'm using amanda 2.4.2p2 and samba 2.2.2. I'm trying to restore a windows file with amrecover but I have an error message. When I restore another file, I've no problem. I don't understand why amanda will use restore program because I use GNUTAR to backup the windows host. Dump and restore programs are installed on the server. My server is under Linux debian. Is it a probeme with my amanda or samba configuration ? error message : amrecover extract Extracting files using tape drive /dev/nst0 on host mars.mond.net. The following tapes are needed: mer@sem2 Restoring files into directory /usr/local/sbin Continue? [Y/n]: Y Load tape mer@sem2 now Continue? [Y/n]: Y warning: restore program for /usr/bin/smbclient not available. amrecover couldn't exec: No such file or directory problem executing restore extract_list - child returned non-zero status: 1 Continue? [Y/n]: Y I have an error in the amidxtaped debug file : amidxtaped: debug 1 pid 2755 ruid 1004 euid 1004 start time Wed May 22 16:00:23 2002 amidxtaped: version 2.4.2p2 SECURITY USER root bsd security: remote host mars.mond.net user root local user amanda amandahosts security check passed 6 amrestore_nargs=6 -h -p /dev/nst0 mars.mond.net ^//ns5/users$ 20020522 Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = /dev/nst0 argv[4] = mars.mond.net argv[5] = ^//ns5/users$ argv[6] = 20020522 amrestore: 0: skipping start of tape: date 20020522 label mer@sem2 amrestore: 1: skipping venus.mond.net._root_sauvegarde_dump_courant.20020522.1 amrestore: 2: skipping ns1.webindustrie.fr._home_svg_conf.20020522.1 amrestore: 3: skipping adminicure._data_dossiers.20020522.2 amrestore: 4: skipping ns1.webindustrie.fr._usr_www_vhost.20020522.2 amrestore: 5: restoring mars.mond.net.__ns5_users.20020522.1 Error 32 (Broken pipe) offset 32768+32768, wrote 0 amrestore: pipe reader has quit in middle of file. amrestore: skipping ahead to start of next file, please wait... amidxtaped: amrestore terminated normally with status: 2 Rewinding tape: done amidxtaped: pid 2755 finish time Wed May 22 16:01:18 2002 Please help !! Benoit GUEPRATTE ___ Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Smbclient data timeout
Hi fellow Amanda users,
I'm having a problem backing up one of my Windows 2000 boxes with
amanda and smbclient. It's a Compaq Deskpro EXM 815 with a SMC EZ
Card 10/100 1211TX NIC. I'm backing up several other Win2k boxes
fromthe same Amanda server and smbclient fine. This machine has
never backed up.
What happens is that when it starts the backup, everything works fine
for a while, then it just hangs. Both machines (the amanda server
and the Win2k problem client) are still usable and able to
communicate on the network. Ethereal and tcpdump show that there is
no SMB data being sent between these two machines after it hangs.
I can still ping, telnet, start a new smbclient, etc. between the
boxes, but the original smbclient is hung. The sendbackup and
smbclient processes still show up in the process table.
Also, when I run smbclient ... -T... manually, the same thing
happens. So maybe I'm posting to the wrong list because maybe this is
a smbclient problem?
I'm using amanda 2.4.2p2, samba 2.2.1a, and GNU tar version 1.13.19
running on Red Hat 7.2 (2.4.7-10).
Following is an excerpt from /tmp/amanda/sendbackup.*.debug
sendbackup: try_socksize: send buffer size is 65536
sendbackup: stream_server: waiting for connection: 0.0.0.0.1350
sendbackup: stream_server: waiting for connection: 0.0.0.0.1351
sendbackup: stream_server: waiting for connection: 0.0.0.0.1352
waiting for connect on 1350, then 1351, then 1352
sendbackup: stream_accept: connection from xxx.xxx.xxx.xxx.1353
sendbackup: stream_accept: connection from xxx.xxx.xxx.xxx.1354
sendbackup: stream_accept: connection from xxx.xxx.xxx.xxx.1355
got all connections
sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00
GMT
sendbackup-gnutar: backup of \\belk\mydoc$
sendbackup: started index creator: /bin/tar -tf - 2/dev/null | sed
-e 's/^\.//'
sendbackup: spawning /usr/bin/smbclient in pipeline
sendbackup: argument list: smbclient \\belk\mydoc$ -U backup -E -d0
-Tqca -
sendbackup-gnutar: /usr/bin/smbclient: pid 5154
sendbackup: index pipe returned 36096
Now, an excerpt from the log file...
FAIL dumper bkupsrv1 //belk/mydoc$ 0 [data timeout]
sendbackup: start [bkupsrv1://belk/mydoc$ level 0]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
| added interface ip=xxx.xxx.xxx.xxx bcast=xxx.xxx.xxx.xxx
nmask=255.255.255.0
? Error reading file \Stuff of Laurie\Begosian.ppt : code 0
? Didn't get entire file. size=20328960, nread=5045040
? Error reading file \Stuff of Laurie\Projector.exe. Got 0 bytes
? Didn't get entire file. size=7588587, nread=0
? Expected SMBtrans2 response, got command 0x08
? code 0 listing \Utility\*
SUCCESS taper bkupsrv1 //belk/mydoc$ 20020515 0 [sec 2345.752 kb
87104
kps 37.1 {wr: writers 2722 rdwait 2306.853 wrwait 35.607 filemark
3.078}]
Thanks for any help.
Eric Patterson
