Re: Amanda 3.5.3-1.fc38 aborts dump on EOF error to planner
Hi Lou, I'm using the same version as you, although in Fedora 37 amanda-3.5.3-1.fc37.x86_64 and I don't see that behaviour, I have some machines that are down and the rest of the backups were made. In my case I have this planner: ERROR Request to MACHINE failed: Connection refused From what you wrote, it seems gallifrey.ivriel is not down is responding, but has some problems reporting the size. Maybe this page will help https://www.zmanda.com/knowledge-base/eof-on-read-error-from-a-client/ Although if is aborting all the planner it seems a bug, or there are other reasons for aborting all the planner, maybe checking if the etimeout is not very low. Cheers, Nuno On Tue, 2023-07-18 at 13:50 -0700, Lou Hafer wrote: > Folks, > > I've been using amanda for several years on a simple home > network. > Hosts are often powered down. Up through amanda 3.5.2, this worked > like > a charm. If the host didn't respond, it was simply skipped. Hosts > that > responded were properly backed up. > > With amanda 3.5.3, the behaviour has changed. If a host doesn't > respond to the planner size request, the planner aborts the entire > backup with the error > > planner: ERROR Request to gallifrey.ivriel failed: > EOF on read from gallifrey.ivriel > > I've confirmed that my configuration is generally correct --- as long > as > all hosts in the disklist respond to the size request, the backup > succeeds. > > Is this a bug? Do I need to change some parameter in my configuration > to > persuade planner to soldier on? Any thoughts would be appreciated. > > As context, this problem came about with an upgrade from Fedora > 37 > to Fedora 38, with a matching upgrade from amanda 3.5.2 to amanda > 3.5.3. > > Thanks, > Lou > -- Nuno Dias LIP
amanda-3.5.3 problems
Hi, After upgrading amanda from amanda-3.5.1 to amanda-3.5.3 using the rpm from Fedora, I have this 2 problems, every man page of amanda is empty for example ... - $ man amanda.conf DUMMY Manual page amanda.conf(5) line 1/2 (END) (press h for help or q to quit) -- The other problem is, if I use a disk as tape, every run of amdump will fail after backup the first machine/disk in disklist, with this error x:/y 20230428141427 131m dump to tape done x:// 20230428141427 0 6244m terminated while waiting for dumping The mail saying FAIL driver xx //z 20230428141220 0 [can't do degraded dump without holding disk] Downgrading to the previous version, this problems will not happen. The last problem do not happens if the tape is a real tape not a disk! I tested in Fedora 36 and Fedora 37 with the same results. My question is, anyone has this problems? Thanks, Nuno -- Nuno Dias LIP
Re: amrecover usage with chg-robot
That messages seems ok, but usually the "kb" will increase with
the time, the same "kb" everytime seems a little strange,
unfortunately I can't help more than this! I think you need
someone that understand more of amanda.
cheers,
Nuno
On Wed, 2022-05-25 at 14:50 +0200, Stefan G. Weichinger wrote:
>
> Am 25.05.22 um 14:41 schrieb Nuno Dias:
> > My conf (the relevant parts)
> >
> > tpchanger "robot"
> >
> > define changer robot {
> > tpchanger "chg-robot:/dev/changer"
> > changerfile "/etc/amanda//changer-state"
> > property "tape-device" "0=tape:/dev/nst0"
> > property "eject-before-unload" "no"
> > property "use-slots" "1-100"
> > property "load-poll" "0s poll 3s until 120s"
> > }
> >
> > amrecover_changer "/dev/changer"
> >
> > and /dev/changer is a sym link to /dev/sg11
> >
> > So let me explain what is /dev/sg11 ... this is the device
> > that
> > allows the manipulation and see the tapes and drives of the
> > robot, for example can be used with the command mtx
> >
> > $ mtx -f /dev/sg11 status
>
> Sure, thanks, I know what /dev/sg11 is ;-) in my case
> /dev/sg21
>
> (although that seems to change with reboots sometimes ..
> another topic)
>
> The difference between your and my conf is only that symlink.
>
> I directly have
>
> tpchanger "chg-robot:/dev/sg21"
>
> and
>
> amrecover_changer "/dev/sg21"
>
> -
>
> Currently I have another amrecover running. It restored from
> tape1 ..
> and now I only see these lines in the current debug file
> "amidxtaped.20220525123652.debug":
>
> Wed May 25 14:48:25.078884308 2022: pid 705002: thd-
> 0x556f690aca00:
> amidxtaped:
> /usr/lib64/perl5/vendor_perl/5.32/Amanda/Restore.pm:1719:info:4
> 90
> 12472320 kb
> Wed May 25 14:48:40.090891256 2022: pid 705002: thd-
> 0x556f690aca00:
> amidxtaped:
> /usr/lib64/perl5/vendor_perl/5.32/Amanda/Restore.pm:1719:info:4
> 90
> 12472320 kb
> Wed May 25 14:48:55.102880465 2022: pid 705002: thd-
> 0x556f690aca00:
> amidxtaped:
> /usr/lib64/perl5/vendor_perl/5.32/Amanda/Restore.pm:1719:info:4
> 90
> 12472320 kb
>
> ... for hours now.
>
> Is that OK? Maybe tar still "scans" through that first tarball
> on tape ... ?
>
--
Nuno Dias
LIP
Re: amrecover usage with chg-robot
My conf (the relevant parts)
tpchanger "robot"
define changer robot {
tpchanger "chg-robot:/dev/changer"
changerfile "/etc/amanda//changer-state"
property"tape-device" "0=tape:/dev/nst0"
property "eject-before-unload" "no"
property "use-slots" "1-100"
property "load-poll" "0s poll 3s until 120s"
}
amrecover_changer "/dev/changer"
and /dev/changer is a sym link to /dev/sg11
So let me explain what is /dev/sg11 ... this is the device that
allows the manipulation and see the tapes and drives of the
robot, for example can be used with the command mtx
$ mtx -f /dev/sg11 status
Cheers,
Nuno
On Wed, 2022-05-25 at 12:35 +0200, Stefan G. Weichinger wrote:
> Am 25.05.22 um 12:17 schrieb Nuno Dias:
> >
> > I have "tapedev" in /etc/amanda/amanda-client.conf but is
> > commented, maybe was used a long time ago, but right now is
> > not
> > necessary with my configuration.
> >
> > And yes I do not choose any device or changer when I
> > execute
> > amrecover.
>
> OK, great.
>
> My amrecover still wants to use /dev/nst0, even after setting
> "amrecover_changer"
>
> I can edit it, no problem, but I try to configure it as good as
> possible
> ... and write a decent howto.
>
> Setting "robot" as device in amrecover doesn't work.
>
> What do you have in "tpchanger" ?
>
> pls share the relevant blocks
>
>
>
>
>
>
>
>
--
Nuno Dias
LIP
Re: amrecover usage with chg-robot
I have "tapedev" in /etc/amanda/amanda-client.conf but is commented, maybe was used a long time ago, but right now is not necessary with my configuration. And yes I do not choose any device or changer when I execute amrecover. Cheers, NUno On Wed, 2022-05-25 at 11:58 +0200, Stefan G. Weichinger wrote: > Am 25.05.22 um 11:50 schrieb Nuno Dias: > > Hi, > > > > I have a similar configuration and works as expected. > > The only thing different is > > > > amrecover_changer "/dev/changer" > > > > where /dev/changer is a sym link to /dev/sg11 (The Robot) > > > > When I recover something I do not define anything and the > > changer and tapes devices are obtain in the CONF of > > amanda.conf > > > > I only execute this as root and the recover works > > > > $ amrecover CONF -s amanda -t amanda > > Thanks, Nuno. > > Do you have a "tapedev" in /etc/amanda/amanda-client.conf ? > > That one also determines how amrecover behaves. > > So you don't choose any device within amrecover, right? > -- Nuno Dias LIP
Re: amrecover usage with chg-robot
Hi,
I have a similar configuration and works as expected.
The only thing different is
amrecover_changer "/dev/changer"
where /dev/changer is a sym link to /dev/sg11 (The Robot)
When I recover something I do not define anything and the
changer and tapes devices are obtain in the CONF of amanda.conf
I only execute this as root and the recover works
$ amrecover CONF -s amanda -t amanda
Cheers,
Nuno
On Wed, 2022-05-25 at 09:07 +0200, Stefan G. Weichinger wrote:
>
>
> At a customer I decided to do some recovery testing.
>
> We use the chg-robot changer there, with one tape drive.
>
> See below:
>
> * tapetype
> * changer
> * taperscan
> * storage
> * amrecover_changer
>
> (I could also show the whole config, but don't want to flood
> the list ...)
>
> Amdumps work fine.
> Recovery ... I have questions:
>
> I decided to restore a DLE with a lev1 on one tape and the lev0
> on
> another tape, to test the whole handling of 2 or more tapes.
>
> That lead to amrecover reading the lev1 tarball from tape 1,
> and then
> hours of waiting ... it never got to the point of requesting
> tape 2 or
> changing it on its own.
>
> I read the manpages etc, and I am unsure if to use "robot" (=
> changer
> name) as tape device in amrecover, or "tape:/dev/nst0"
> directly.
>
> tested both, no difference
>
> Maybe the tape drive doesn't return some of those EOM/EOT
> messages?
>
> It's a HP Ultrium 4-SCSI, Rev: B12H ... as far as I remember
> that worked
> before.
>
> Thanks for any hints here.
>
> (ah, for reference: Amanda-3.5.1 on Debian 11.3 right now)
>
> ---
>
> here the configs:
>
>
> define tapetype LTO-4 {
> │
> comment "Created by amtapetype; compression disabled;
> 2017-10-31 sgw" │
> length 698510208 kbytes
> │
> filemark 0 kbytes
> │
> speed 36696 kps
> │
> blocksize 2 mbytes
> │
> readblocksize 2 mbytes
> │
> }
> │
>
> │
> define changer robot {
> │
> tpchanger "chg-robot:/dev/sg21" # lsscsi -g
> │
> property "tape-device" "0=tape:/dev/nst0"
> │
> property "eject-before-unload" "no"
> │
> property "use-slots" "1-24"
> │
> changerfile "/etc/amanda/abt/chg-robot-dev-sg21"
> │
> }
> │
>
> │
> define taperscan lexi {
> │
> comment "none"
> │
> plugin "lexical"
> │
> }
> │
>
> │
> define storage abt {
> │
> tapepool "abt"
> │
> tapetype "LTO-4"
> │
> tpchanger "robot"
> │
> runtapes 1
> │
> taperscan "lexi"
> │
>
> │
> flush-threshold-dumped 300
> │
> flush-threshold-scheduled 300
> │
> taperflush 300
> │
> autoflush yes
> │
>
> │
> #labelstr "^ABT-[0-9][0-9]*$"
> │
> autolabel "ABT-%b"
> │
> }
> │
>
> │
> reserve 30
> │
>
> │
> amrecover_changer "robot"
>
--
Nuno Dias
LIP
Re: amanda-3.5.1 : server crc
Sometimes I have these errors, I solve the problem running $ amcleanupdisk -r CONF This will clean the damage files in the holdingdisk If this doesn't solve the problem, I locate the file in holddisk and remove it manually. If this happens in every run of amanda and for the same server, you probably have a holding disk with problems. Cheers, Nuno On Fri, 2020-05-08 at 11:53 +0200, Stefan G. Weichinger wrote: > Am 25.10.18 um 18:03 schrieb Stefan G. Weichinger: > > I see this on a debian 9.5 machine > > > > FAILURE DUMP SUMMARY: > > server /var date 20180829231504 lev 0 partial taper: source > > server > > crc (61305989:15470559232) and input server crc > > (fd9a566b:15470397520) > > differ) > > > > > > (both amanda server and client are Debian 9.5, running amanda- > > 3.5.1) > > > > The crc-"numbers" are the same every day. How to fix that, is it > > problematic? > > anyone ? > > we still see that on a debian 10.3 server ... > > could someone explain which step fails here? -- Nuno Dias LIP
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
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
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
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
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
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: amstatus error
The problem I have is due to windows backups using zmanda, if I delete de backups on holding disk from zmanda, the amstatus works as expected! Cheers, Nuno On Sun, 2019-08-11 at 09:29 +0200, Stefan G. Weichinger wrote: > Am 02.08.19 um 10:56 schrieb Nuno Dias: > > Hi, > > > > Since two days ago I have this error, everytime I try to run > > amstatus > > > > amstatus: bad status on taper SHM-WRITE (taper): 16 at > > /usr/lib64/perl5/vendor_perl/Amanda/Status.pm line 935, <$fd> line > > 9210. > > > > I can see that the amdump is still running, the taper process also > > running, and I see no errors in logs about the tape. > > > > How I solve this issue? anyone knows? > > I don't know but I also notice that the output of amstatus changed > ... I > don't get any (perl) errors but the whole information around the > taper > seems not to be updated. > > A run over 5 tapes still shows "searching for a tape" while I can see > that it wrote to several tapes already (by looking at the tape > inventory > and the fact it changed through tapes). > > debian-9.9 here, amanda-3.5.1 > > Your error message also points to a line mentioning taper problems. > > -- Nuno Dias LIP smime.p7s Description: S/MIME cryptographic signature
amstatus error
Hi, Since two days ago I have this error, everytime I try to run amstatus amstatus: bad status on taper SHM-WRITE (taper): 16 at /usr/lib64/perl5/vendor_perl/Amanda/Status.pm line 935, <$fd> line 9210. I can see that the amdump is still running, the taper process also running, and I see no errors in logs about the tape. How I solve this issue? anyone knows? Thanks, Nuno -- Nuno Dias LIP smime.p7s Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
Hi Debra,
Yes, this will work if I use different labels not related with the
name of the diskdevice, the only problem is more work when I run
amstatus and amrecover to match the label with the disk/diredctory
Cheers,
Nuno
On Thu, 2019-06-27 at 18:37 +, Debra S Baddorf wrote:
> > On Jun 27, 2019, at 7:38 AM, Nuno Dias wrote:
> >
> > > I guess another possible solution is to using disknames of a form
> > > that
> > > are designend to be unique, e.g. something like (not tested)
> > >
> > > > --
> > > > MACHINE dir-main /dir {
> > > > tar
> > > > exclude "./subdir/*"
> > > > }
> > > >
> > > > MACHINE dir-subdir /dir {
> > > > tar
> > > > include "./subdir/*"
> > > > }
> > > > --
> > >
> > > ... and use those disknames on the amdump command line... (But
> > > you
> > > have to choose disknames carefully so your Amanda Mail Report
> > > looks
> > > reasonable, etc.)
> > >
> > >
> > > Nathan
> > >
> Possibly not tested, but that was what I was describing. I use text-
> only disknames
> like that all the time. No slashes in them, so they cannot be
> confused with actual disk designations!
>
> Deb Baddorf
> Fermilab
>
>
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
Hi Nathan,
Thanks for the reply, in my configuration I need the includes, I make
backups of terabytes of data, so split and the use of includes are
essencial.
I opened a bug in github.
Cheers,
Nuno
On Wed, 2019-06-26 at 18:48 -0400, Nathan Stratton Treadway wrote:
> On Wed, Jun 26, 2019 at 16:57:33 +0100, Nuno Dias wrote:
> > But if I have something like this
> >
> > --
> > MACHINE /dir {
> > tar
> > exclude "./subdir/*"
> > }
> >
> > MACHINE /dir/subdir /dir {
> > tar
> > include "./subdir/*"
> > }
> > --
> >
> > the commands
> >
> > $ amdump CONF MACHINE ^/dir$
> > and
> > $ amdump CONF MACHINE =/dir
> >
> > Don't work as expected, both backups (/dir and /dir/subdir) are
> > made
> >
> > From "man disklist"
> >
> > diskname
> > The name of the disk (a label). In most case, you set your
> > diskname
> > to the diskdevice and you don't set the diskdevice. If you
> > want
> > multiple entries with the same diskdevice, you must set a
> > different
> > diskname for each entry. It's the diskname that you use on the
> > commandline for any Amanda command. Look at the
> > example/disklist
> > file for example.
> >
> > So from this, if it's the diskname that is used in the command, it
> > seems that the reality is amdump is using the diskdevice instead!!
>
> Thanks for the additional info, which certainly helps explain what is
> happening to you
>
> My understanding of the inner workings of this part of Amanda is
> quite
> fuzzy, but assuming I have followed the program flow behind "amdump"
> correctly, it looks like the code in question is found in
> server-src/diskfile.c:match_disklist() , which contains the following
> lines:
> if ([...] &&
> (match_disk(sargv[i], dp->name) ||
> (dp->device && match_disk(sargv[i], dp->device {
>
> ..so I believe that in fact arguments specified on the amdump command
> line
> are matched against BOTH the "diskname" and "diskdevice" fields, and
> if
> either one matches the argument then that DLE is selected (which
> I
> agree doesn't match the wording of the manpage).
>
> (As far as I can tell from git, this code has been like that since
> at least 2006.)
>
>
> In this particular example I think you could work around the problem
> by
> changing your disklist to
>
> --
> MACHINE /dir {
> tar
> exclude "./subdir/*"
> }
>
> MACHINE /dir/subdir {
> tar
> }
> --
>
> (in which case presumably using either ^/dir$ or =/dir would not
> match
> the second DLE) ... but obviously that doesn't help if you ever want
> to
> have a DLE which uses "include" to pull in multiple subdirectories of
> /dir.
>
> I guess another possible solution is to using disknames of a form
> that
> are designend to be unique, e.g. something like (not tested)
>
> > --
> > MACHINE dir-main /dir {
> > tar
> > exclude "./subdir/*"
> > }
> >
> > MACHINE dir-subdir /dir {
> > tar
> > include "./subdir/*"
> > }
> > --
>
> ... and use those disknames on the amdump command line... (But you
> have to choose disknames carefully so your Amanda Mail Report looks
> reasonable, etc.)
>
>
> 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
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
Hi all,
Sorry to only now reply to this, but I was testing ... so the problem
is this
If I have something like this in disklist
--
MACHINE /dir {
tar
exclude "./subdir/*"
}
MACHINE /dir/subdir tar
--
and run
$ amdump CONF MACHINE ^/dir$
or
$ amdump CONF MACHINE =/dir
It works as expected the only backup made is /dir
But if I have something like this
--
MACHINE /dir {
tar
exclude "./subdir/*"
}
MACHINE /dir/subdir /dir {
tar
include "./subdir/*"
}
--
the commands
$ amdump CONF MACHINE ^/dir$
and
$ amdump CONF MACHINE =/dir
Don't work as expected, both backups (/dir and /dir/subdir) are made
From "man disklist"
diskname
The name of the disk (a label). In most case, you set your diskname
to the diskdevice and you don't set the diskdevice. If you want
multiple entries with the same diskdevice, you must set a different
diskname for each entry. It's the diskname that you use on the
commandline for any Amanda command. Look at the example/disklist
file for example.
So from this, if it's the diskname that is used in the command, it
seems that the reality is amdump is using the diskdevice instead!!
Cheers,
Nuno
On Mon, 2019-06-17 at 21:47 +, Debra S Baddorf wrote:
> I’ve been on vacation, so I’m coming late to this discussion.
> I’ve had problems trying to one-off dump a DLE is its name matches
> another name. It’s true we haven’t answered why the $ doesn’t fix
> that.
> But --
>
> I give them “nicknames”.
>
> disklist file:
> MACHINE Main2019 /dir/subdir/name/2019 ….. {
> tar
> exclude "./subdir/*"
>
> }
>
> MACHINE SubOf2019 /dir/subdir/name/2019/subdir tar
>
> Then I do dumps or restores by using the “nickname” which is not
> multiple matched.
>
> amdump CONFIG MACHINE Main2019
> amdump CONFIG MACHINE SubOf2019
>
> Deb Baddorf
> Fermilab
>
> > On Jun 11, 2019, at 9:32 PM, Jon LaBadie wrote:
> >
> > On Tue, Jun 11, 2019 at 11:47:15AM +0100, Nuno Dias wrote:
> > > Thanks, but I'm already doing that (the exclude)
> > >
> > > This is what I have in disklist
> > >
> > > MACHINE /dir/subdir/name/2019 {
> > > tar
> > > exclude "./subdir/*"
> > >
> > > }
> > >
> > > MACHINE /dir/subdir/name/2019/subdir tar
> > >
> > > Because this are very big directories, I want to dump only one
> > > every
> > > time, anyone know how I can do this?
> > >
> >
> > Two ideas
> >
> > 1) instead of trying to exclude everything you don't want,
> > consider including the one you do want. That should auto-
> > exclude all else.
> >
> > 2) have a separate DLE for each directory you want. Have
> > them do only full backups. Run your amdump in such a way
> > that only one DLE is dumped each day.
> >
> > --
> > Jon H. LaBadie j...@jgcomp.com
> > 11226 South Shore Rd. (703) 787-0688 (H)
> > Reston, VA 20190 (703) 935-6720 (C)
>
>
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
Hi Gene,
The exclude here, is to exclude a subdir that are to big to go in one
backup, that's the reason I have another line in the disklist so I can
backup the exclude in next backup.
The quotes are necessary because sometimes users put spaces in file
and dir names!!
Cheers,
Nuno
On Tue, 2019-06-11 at 07:47 -0400, Gene Heskett wrote:
> On Tuesday 11 June 2019 06:47:15 am Nuno Dias wrote:
>
> > Thanks, but I'm already doing that (the exclude)
> >
> > This is what I have in disklist
> >
> > MACHINE /dir/subdir/name/2019 {
> > tar
> > exclude "./subdir/*"
>
> looks wrong, excludes are in the dumptype specified, in the
> amanda,conf
>
> ./subdir in your exclude s/b sufficient to block any and all access
> below that level. and the dbl-qoutes at not needed.
>
> All of this s/b in the dumptype section in your amanda.conf, and
> your
> disklist should contain only the dumptype which is then referenced
> to
> determine if there even is an exclude, or exclude list if more than
> 1
> exclude, in which case the name of the exclude list is any handy name
> to
> identify to you, which dumptype its to be used with.
>
> I don't believe the disklist is scanned for any exclude info, just
> the
> dumptype, that is what specifies all of that profile.
> > }
> >
> > MACHINE /dir/subdir/name/2019/subdir tar
> >
> > Because this are very big directories, I want to dump only one
> every
> > time, anyone know how I can do this?
> >
> > Thanks
> > Nuno
> >
> > On Fri, 2019-06-07 at 16:37 -0400, Jon LaBadie wrote:
> > > On Fri, Jun 07, 2019 at 11:04:48AM +0100, Nuno Dias wrote:
> > > > Hi,
> > > >
> > > > I'm trying to use amanda to backup only one dir from a list of
> > > > dirs
> > > > that are in disklist file
> > > >
> > > > I run amdump like this
> > > >
> > > > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > > > ^/dir/subdir/name/2019$
> > > >
> > > > and with ps I can see the amdump running
> > > >
> > > > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper
> > > > MACHINE ^/dir/subdir/name/2019$
> > > >
> > > > The problem is instead of only one dir I have two dirs in the
> > > > backup
> > > >
> > > > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g
> > > > dumping
> > > > (18g done (3.74%)) (15:39:26)
> > > >
> > > > MACHINE:/dir/subdir/name/2019/another 20190606153859
> > > > 1 244g
> > > > wait for dumping
> > > >
> > > >
> > > > From the amanda-match man page
> > > >
> > > > /usr$
> > > > Will match the disks /usr but not /usr/local.
> > > >
> > > > So, this is a bug or I'm doing something wrong?
> > >
> > > Not wrong, just a misconception.
> > > The directory you give is a "starting" directory. amdump will
> > > backup everything under that directory unless it could cross
> > > a mount point (file system) or if something is excluded.
> > >
> > > So, assuming you have a DLE for ".../2019" and that your
> "another"
> > > directory is the only problem, add a directive to the DLE to
> > > exclude another. If you don't have a DLE for 2019, PERHAPS
> > > the -o option to amdump can be used to add an exclude directive.
> > > I don't know if it can or cannot.
> > >
> > > Jon
> > >
> > > > I'm using amanda-3.5.1-16.fc29.x86_64
> > > >
> > > > thanks,
> > > > Nuno
> > > > --
> > > > Nuno Dias
> > > > LIP
> > > >
> > > > > > End of included message <<<
>
>
>
> Copyright 2019 by Maurice E. Heskett
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <http://geneslinuxbox.net:6309/gene>
>
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
Re: exact-match
On Tue, 2019-06-11 at 07:04 -0400, Nathan Stratton Treadway wrote: > On Fri, Jun 07, 2019 at 11:04:48 +0100, Nuno Dias wrote: > > I'm trying to use amanda to backup only one dir from a list of > > dirs > > that are in disklist file > > > > I run amdump like this > > > > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE > > ^/dir/subdir/name/2019$ > > > > and with ps I can see the amdump running > > > > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper MACHINE > > ^/dir/subdir/name/2019$ > > > > The problem is instead of only one dir I have two dirs in the > > backup > > > > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g > > dumping > > (18g done (3.74%)) (15:39:26) > > > > MACHINE:/dir/subdir/name/2019/another 20190606153859 > > 1 244g > > wait for dumping > > Am I correct you have many DLEs in your disklist file, and if you > don't > put the "MACHINE ^/dir/subdir/name/2019$" on the amdump line they all > get dumped? (That is, the "match" is mostly is working to restrict > the > DLEs dumped, only the trailing "$" is not working?) Yes, to all the questions. > > What version of Amanda is this? amanda-3.5.1-16.fc29.x86_64 > > 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 smime.p7s Description: S/MIME cryptographic signature
Re: ***UNCHECKED*** exact-match
Thanks, but I'm already doing that (the exclude)
This is what I have in disklist
MACHINE /dir/subdir/name/2019 {
tar
exclude "./subdir/*"
}
MACHINE /dir/subdir/name/2019/subdir tar
Because this are very big directories, I want to dump only one every
time, anyone know how I can do this?
Thanks
Nuno
On Fri, 2019-06-07 at 16:37 -0400, Jon LaBadie wrote:
> On Fri, Jun 07, 2019 at 11:04:48AM +0100, Nuno Dias wrote:
> > Hi,
> >
> > I'm trying to use amanda to backup only one dir from a list of
> > dirs
> > that are in disklist file
> >
> > I run amdump like this
> >
> > $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > ^/dir/subdir/name/2019$
> >
> > and with ps I can see the amdump running
> >
> > /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper MACHINE
> > ^/dir/subdir/name/2019$
> >
> > The problem is instead of only one dir I have two dirs in the
> > backup
> >
> > MACHINE:/dir/subdir/name/2019 20190606153859 0 486g
> > dumping
> > (18g done (3.74%)) (15:39:26)
> >
> > MACHINE:/dir/subdir/name/2019/another 20190606153859
> > 1 244g
> > wait for dumping
> >
> >
> > From the amanda-match man page
> >
> > /usr$
> > Will match the disks /usr but not /usr/local.
> >
> > So, this is a bug or I'm doing something wrong?
> >
> Not wrong, just a misconception.
> The directory you give is a "starting" directory. amdump will
> backup everything under that directory unless it could cross
> a mount point (file system) or if something is excluded.
>
> So, assuming you have a DLE for ".../2019" and that your "another"
> directory is the only problem, add a directive to the DLE to
> exclude another. If you don't have a DLE for 2019, PERHAPS
> the -o option to amdump can be used to add an exclude directive.
> I don't know if it can or cannot.
>
> Jon
> > I'm using amanda-3.5.1-16.fc29.x86_64
> >
> > thanks,
> > Nuno
> > --
> > Nuno Dias
> > LIP
> > > > End of included message <<<
--
Nuno Dias
LIP
smime.p7s
Description: S/MIME cryptographic signature
exact-match
Hi, I'm trying to use amanda to backup only one dir from a list of dirs that are in disklist file I run amdump like this $ /usr/sbin/amdump -o reserve=0 --no-taper MACHINE ^/dir/subdir/name/2019$ and with ps I can see the amdump running /usr/bin/perl /usr/sbin/amdump -o reserve=0 --no-taper MACHINE ^/dir/subdir/name/2019$ The problem is instead of only one dir I have two dirs in the backup MACHINE:/dir/subdir/name/2019 20190606153859 0 486g dumping (18g done (3.74%)) (15:39:26) MACHINE:/dir/subdir/name/2019/another 20190606153859 1 244g wait for dumping From the amanda-match man page /usr$ Will match the disks /usr but not /usr/local. So, this is a bug or I'm doing something wrong? I'm using amanda-3.5.1-16.fc29.x86_64 thanks, Nuno -- Nuno Dias LIP smime.p7s Description: S/MIME cryptographic signature
Re: includefile in disklist
Hi, The question was answer ... see the link, with a patch from Jean-Louis Martineau https://readlist.com/lists/amanda.org/amanda-users/3/19166.html Cheers, Nuno On Wed, 2016-03-09 at 18:13 +0100, Mikalai Krot wrote: > Found a similar question that was not answered > > http://archives.zmanda.com/amanda-archives/viewtopic.php?t=7063 > > and a related question about an earlier version of amanda. > > http://archives.zmanda.com/amanda-archives/viewtopic.php?t=6669 > > > On 03/09/2016 05:07 PM, Mikalai Krot wrote: > > Hallo > > > > Sorry, I should have included version info. So, I am using amanda > > 3.3.3, from rhel7. > > > > And yes, the DLEs are unique. > > > > I experimented with changing the order of includefile directives > > and found out that the last one always wins. > > > > Thanks in advance, > > Nikolai Krot > > > > On 03/09/2016 04:06 PM, Bill Carlson wrote: > > > Hello, > > > > > > What version of amanda are you using? > > > > > > Is the combined disklist composed of only unique entries? > > > > > > Thanks, > > > -- > > > > > > Bill Carlson > > > > > > Anything is possible, given Time and Money. > > > On 03/08/2016 03:48 PM, Mikalai Krot wrote: > > > > Hi list members, > > > > > > > > My question is how to combine in a single disklist file > > > > definitions of DLE and includefile directives. Seems that this > > > > is impossible. I tried the following cases: > > > > > > > > ### case 1 that worked > > > > > > > > disklist contains only DLE entries of the form > > > > > > > > server.domain.com /etc comp-root-tar > > > > server.domain.com /var/www comp-root-tar > > > > > > > > Result: everything works fine > > > > > > > > ### case 2, that did not work > > > > > > > > I wanted to add more DLEs to the abive disklist by including > > > > them from an automatically generated file > > > > > > > > server.domain.com /etc comp-root-tar > > > > server.domain.com /var/www comp-root-tar > > > > > > > > includefile "disklist.auto" > > > > > > > > Result: only entries from included disklist.auto work (and > > > > reported by amadmin CONFIG disklist) > > > > > > > > ### case 3, again, no luck > > > > > > > > I thought that mixing two types of entries is not possible and > > > > extracted case 1 into disklist.manual. Now my disklist is > > > > > > > > includefile "disklist.manual" > > > > includefile "disklist.auto" > > > > > > > > Result: again, only disklist.auto works. Only the last of > > > > included files works > > > > > > > > ### WTF? > > > > > > > > I reread the disklist manual and found an interesting clause > > > > > > > > < The disklist file determines which disks will be backed up by > > > > Amanda. The file contains includefile directive or disklist > > > > entry (DLE). > > > > > > > > so.. literally, only *one* includefile directive xor DLEs. Do I > > > > understand it correctly? Is it a kind of a joke or there is a > > > > reason behind this design? > > > > > > > > Best regards, > > > > Nikolai Krot > > > > > > > > > > > > -- > > > > Mikalai Krot > > > > Sprachwissenschaftliches Institut > > > > GB 3/143 > > > > Ruhr-Universität Bochum > > > > DE-44801 Bochum > > > > fon +49 234 32-23910 > > > > cell +49 157 80283908 > > > > > > > -- > > Mikalai Krot > > Sprachwissenschaftliches Institut > > GB 3/143 > > Ruhr-Universität Bochum > > DE-44801 Bochum > > fon +49 234 32-23910 > > cell +49 157 80283908 > > -- > Mikalai Krot > Sprachwissenschaftliches Institut > GB 3/143 > Ruhr-Universität Bochum > DE-44801 Bochum > fon +49 234 32-23910 > cell +49 157 80283908 -- Nuno Dias <nd...@lip.pt> LIP smime.p7s Description: S/MIME cryptographic signature
Re: Amanda consumes all the memory
Trying to reproduce the problem, but this usually happens when the previous backup do not terminates well, I usually use the command amcleanup -r -k CONF to terminate and clean the running process, but the dumper processes don't end. 2112 amandab+ 20 0 106016 4628 3304 R 99.6 0.0 64:00.96 dumper 2158 amandab+ 20 0 108200 4880 3444 R 99.6 0.0 1015:02 dumper 2165 amandab+ 20 0 108200 4940 3464 R 99.6 0.0 922:39.01 dumper 2118 amandab+ 20 0 108200 4952 3472 R 99.3 0.0 54:37.08 dumper 2140 amandab+ 20 0 108200 4888 3456 R 99.3 0.0 921:26.73 dumper This is a bug? or do I need everytime to kill it manually? Thanks, Nuno On Wed, 2013-11-06 at 07:54 -0500, Jean-Louis Martineau wrote: Nuno, Which process consume a lot of memory? Can you run strace on the process? and gdb to get a few stacktrace? I want to find want the process is doing. Posting the debug file of the process can be useful too. Jean-Louis On 11/06/2013 07:30 AM, Nuno Dias wrote: Hi all, I'm using amanda-3.3.3 and right now, when I run amdump in the fase of planner all the memory of the machine is consumed by amanda and eventually the amdump is killed. The machine has 24 Giga of memory, so is not a problema of low memory. I need help to debug this problem. Thanks, Nuno -- Nuno Dias nd...@lip.pt LIP smime.p7s Description: S/MIME cryptographic signature
Amanda consumes all the memory
Hi all, I'm using amanda-3.3.3 and right now, when I run amdump in the fase of planner all the memory of the machine is consumed by amanda and eventually the amdump is killed. The machine has 24 Giga of memory, so is not a problema of low memory. I need help to debug this problem. Thanks, Nuno -- Nuno Dias nd...@lip.pt LIP smime.p7s Description: S/MIME cryptographic signature
Re: diskname length
Hi, In attach I send the amdump (only the part where the diskname is listed, the amdump file is big). The version of amanda is amanda-3.3.2-3.fc18.x86_64 Thanks, Nuno On Mon, 2013-04-15 at 08:57 -0700, Jean-Louis Martineau wrote: Hi Nuno, The length is limited to 254 characters. Can you post the amdump file amstatus is using? Which amanda version are you using? Jean-Louis On 04/15/2013 02:41 AM, Nuno Dias wrote: Hi, Is there a limit in the length of a diskname in the disklist file? I have a directory with 198 caracteres and when the backup is running, when I run amstatus the command stops at listing this directory and eats all the memory of the machine, what seems a nasty bug. Cheers, Nuno -- Nuno Dias nd...@lip.pt LIP planner: time 0.211: setting up estimates for xxx.x.lip.pt:/aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy xxx.x.lip.pt:/aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy overdue 15808 days for level 0 setup_estimate: xxx.x.lip.pt:/aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: command 0, options: nonelast_level -1 next_level0 -15808 level_days 0 getting estimates 0 (-3) -1 (-3) -1 (-3) planner: time 11.888: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - -3K, -1 - -3K, -1 - -3K planner: time 16.532: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - -3K, -1 - -3K, -1 - -3K planner: time 19.897: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - -3K, -1 - -3K, -1 - -3K planner: time 102.767: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - -3K, -1 - -3K, -1 - -3K planner: time 232.179: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - -3K, -1 - -3K, -1 - -3K planner: time 635.563: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - -3K, -1 - -3K, -1 - -3K planner: time 649.851: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - -3K, -1 - -3K, -1 - -3K planner: time 724.479: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - 222961690K, -1 - -3K, -1 - -3K planner: time 766.786: got partial result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - 222961690K, -1 - -3K, -1 - -3K planner: time 767.791: got result for host xxx.x.lip.pt disk /aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy: 0 - 222961690K, -1 - -3K, -1 - -3K pondering xxx.x.lip.pt:/aa/lip/rpcpet/y/Documents//Data/PPP-Systems/RPC-Scanner/Scatter-Fraction-Phantom/180_cm-Length-Phantom/WSD-WPA/Count-Rates-Data/NEMA-2001/MM-Data/Coarse-Position-Policy... next_level0 -15808 last_level -1 (due for level 0) (new disk, can't switch to degraded mode
diskname length
Hi, Is there a limit in the length of a diskname in the disklist file? I have a directory with 198 caracteres and when the backup is running, when I run amstatus the command stops at listing this directory and eats all the memory of the machine, what seems a nasty bug. Cheers, Nuno -- Nuno Dias nd...@lip.pt LIP
includefile in disklist
Hi, In amanda-3.3.2 if I use includefile directive in disklist, that directive must be the first thing in the file, and only one includefile is allowed, this is a feature or a bug? Cheers, Nuno -- Nuno Dias nd...@lip.pt LIP
Re: ssh with no standard ports
Hi Jean-Louis, Thanks, the patch solved the problem :) Nuno On Thu, 2012-03-08 at 08:05 -0500, Jean-Louis Martineau wrote: On 03/08/2012 05:42 AM, Nuno Dias wrote: Hi, This is a solution for one machine, I have several machines with different ports, I can create several dumptypes one for each machine, but I think this is complicate the configuration ... Why amanda force port 22 and do not uses the default? You are right, this is what the attached patch do. Jean-Louis Thanks Nuno On Wed, 2012-03-07 at 13:15 -0500, Jean-Louis Martineau wrote: Add a client-port in the dumptype: client-port 5 Jean-Louis On 03/07/2012 12:34 PM, Nuno Dias wrote: Hi, In version 3.1.3 of amanda I used .ssh/config with a configuration like this Host machine_name Port 5 To do backups of a machine through a tunnel ssh. But with version 3.3.0 this is not working anymore, what I can see in the logs is this /usr/bin/ssh SSH_OPTIONS -l amanda -p 22 -i /var/lib/amanda/.ssh/id_rsa machine_name /usr/lib64/amanda/amandad -auth=ssh Because the port is specified (-p 22) the port in .ssh/config it's not used. This is a feature? or can I change this? Thanks Nuno -- Nuno Dias nd...@lip.pt LIP
ssh with no standard ports
Hi, In version 3.1.3 of amanda I used .ssh/config with a configuration like this Host machine_name Port 5 To do backups of a machine through a tunnel ssh. But with version 3.3.0 this is not working anymore, what I can see in the logs is this /usr/bin/ssh SSH_OPTIONS -l amanda -p 22 -i /var/lib/amanda/.ssh/id_rsa machine_name /usr/lib64/amanda/amandad -auth=ssh Because the port is specified (-p 22) the port in .ssh/config it's not used. This is a feature? or can I change this? Thanks Nuno -- Nuno Dias nd...@lip.pt LIP
amrecover
Hi,
I'm trying to recover some backups from my amanda server, using a
client machine.
When I try to issue the command amrecover in the client machine, I have
the message
[request failed: timeout waiting for ACK]
Seeing the logs in my amanda server I got this error ...
amandad: time 0.000: dgram_recv(dgram=0x2ae03a48, timeout=0,
fromaddr=0x2ae13a40)
amandad: time 0.000: (sockaddr_in *)0x2ae13a40 = { 2, 987,
xxx.xxx.xxx.xxx }
amandad: time 0.000: security_handleinit(handle=0x50e4d0,
driver=0x2ae00540 (BSD))
amandad: time 0.001: security_seterror(handle=0x50e4d0,
driver=0x2ae00540 (BSD) error=.xxx.xxx.xx doesn't resolve to
itself, it resolves to .xxx.xx.xx)
The machine client has two names, that resolve to the same IP, the IP
resolves to the two names, this is a problem for amanda? how can I
resolve this issue, without removing one of the names?
Nuno
--
Nuno Dias nd...@lip.pt
LIP
tar options
Hi, When I use tar to make backups in amanda, I see things like this in the logs, runtar XXX02 /bin/tar --create --file /dev/null --directory /x/ --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/x/_0.new --sparse --xattrs --ignore-failed-read --totals . Is there any way to change these options in tar ? for example If I don't want gnutar to use --sparse --xattrs options how can I change this ? Thanks, ND -- Nuno Dias [EMAIL PROTECTED] LIP
Solaris amanda-2.5.1p2
Hi, I'm trying to compile amanda 2.5.1p2 in solaris 8 (sparc). I'm getting errors with libtermcap, but even after I dig in the google, and make configure like this, ./configure --with-user=amanda --with-group=sys --without-termcap --without-ltermcap --without-LIBTERMCAP --with-ncurses=yes --with-lncurses=yes --with-LIBNCURSES=yes The compilation crash with the same error, Text relocation remains referenced against symbol offset in file unknown 0xa0c /usr/local/lib/libtermcap.a(tparam.o) unknown 0xa10 /usr/local/lib/libtermcap.a(tparam.o) unknown 0xa14 /usr/local/lib/libtermcap.a(tparam.o) unknown 0xa18 /usr/local/lib/libtermcap.a(tparam.o) unknown 0xa1c /usr/local/lib/libtermcap.a(tparam.o) unknown 0xa20 /usr/local/lib/libtermcap.a(tparam.o) unknown 0xa24 /usr/local/lib/libtermcap.a(tparam.o) can some one help ? Thank's ND -- Nuno Dias [EMAIL PROTECTED] LIP
Re: amtapetype problem
On Sun, 2006-01-15 at 18:30 -0500, Jon LaBadie wrote: On Sun, Jan 15, 2006 at 10:56:18PM +, Nuno Dias wrote: Hi, I compiled the amanda-2.4.5p1 and when I try to run the command amtapetype I'm get this error. # amtapetype -o -f /dev/nrst10 Estimate phase 1... Writing 4096 Mbyte compresseable data: 260 sec Estimate phase 2...amtapetype: could not write any data in this pass: short write I'm trying to use DDS3 cartridge in a DDS4 TAPE, this is possible ? Does the drive manufacturer say you can? Yes. Can you check the status and move a tape with the mt command? Yes. Can you write data to the tape with commands other than amanda commands eg. dd, tar, cat, ... Yes. ND -- Nuno Dias [EMAIL PROTECTED] LIP
amtapetype problem
Hi, I compiled the amanda-2.4.5p1 and when I try to run the command amtapetype I'm get this error. # amtapetype -o -f /dev/nrst10 Estimate phase 1... Writing 4096 Mbyte compresseable data: 260 sec Estimate phase 2...amtapetype: could not write any data in this pass: short write I'm trying to use DDS3 cartridge in a DDS4 TAPE, this is possible ? Thank's ND -- Nuno Dias [EMAIL PROTECTED] LIP
Re: lev 0 FAILED [Estimate timeout from ******]
I think is not a problem of firewall because, if i put only one filesystem in disklist it work. ND On Thu, 2004-12-02 at 18:21 +0100, Christoph Scheeder wrote: Hi, Completly shure? many modern linux distros (AFAIK at least suse and redhat) come up with default firewall-installations blocking many things if you do not explicitly disable these firewalls. So there might be a firewall on the linux-box even if you didn't configure it. Christoph Nuno Dias schrieb: No, the two machines are in the same network, no firewall. ND On Thu, 2004-12-02 at 17:55 +0100, Christoph Scheeder wrote: Nuno Dias schrieb: Hi, I have a Digital Unix machine that give me some strange results when i try to use amanda. If i configure disklist with 2 or more disks of the Digital Unix machine, the amanda report tell me this: xxx/ lev 0 FAILED [Estimate timeout from xx] xxx/usr lev 0 FAILED [Estimate timeout from xx] xxx/ lev 0 FAILED [Estimate timeout from xx] The amandad.20041202142753000.debug file in Digital Machine have this error: amandad: time 200.266: dgram_recv: timeout after 10 seconds amandad: time 200.266: waiting for ack: timeout, retrying amandad: time 210.267: dgram_recv: timeout after 10 seconds amandad: time 210.267: waiting for ack: timeout, retrying amandad: time 220.267: dgram_recv: timeout after 10 seconds amandad: time 220.267: waiting for ack: timeout, retrying amandad: time 230.267: dgram_recv: timeout after 10 seconds amandad: time 230.267: waiting for ack: timeout, retrying amandad: time 240.267: dgram_recv: timeout after 10 seconds amandad: time 240.267: waiting for ack: timeout, giving up! amandad: time 240.267: pid 22594 finish time Thu Dec 2 14:31:54 2004 The strange thing is, if i configure only one disk in disklist, the backup run ok, and no problem is report in amanda report. I increased the etimeout/ctimeout to a big number ... and did not work. I have a Linux machine that is the master and the Digital Unix machine is the client, the version of amanda is 2.4.4p4 Thank's for some help. ND Hi, could this be a firewall-timeout on the linux-machine? Christoph -- Nuno Dias [EMAIL PROTECTED] LIP
lev 0 FAILED [Estimate timeout from ******]
Hi, I have a Digital Unix machine that give me some strange results when i try to use amanda. If i configure disklist with 2 or more disks of the Digital Unix machine, the amanda report tell me this: xxx/ lev 0 FAILED [Estimate timeout from xx] xxx/usr lev 0 FAILED [Estimate timeout from xx] xxx/ lev 0 FAILED [Estimate timeout from xx] The amandad.20041202142753000.debug file in Digital Machine have this error: amandad: time 200.266: dgram_recv: timeout after 10 seconds amandad: time 200.266: waiting for ack: timeout, retrying amandad: time 210.267: dgram_recv: timeout after 10 seconds amandad: time 210.267: waiting for ack: timeout, retrying amandad: time 220.267: dgram_recv: timeout after 10 seconds amandad: time 220.267: waiting for ack: timeout, retrying amandad: time 230.267: dgram_recv: timeout after 10 seconds amandad: time 230.267: waiting for ack: timeout, retrying amandad: time 240.267: dgram_recv: timeout after 10 seconds amandad: time 240.267: waiting for ack: timeout, giving up! amandad: time 240.267: pid 22594 finish time Thu Dec 2 14:31:54 2004 The strange thing is, if i configure only one disk in disklist, the backup run ok, and no problem is report in amanda report. I increased the etimeout/ctimeout to a big number ... and did not work. I have a Linux machine that is the master and the Digital Unix machine is the client, the version of amanda is 2.4.4p4 Thank's for some help. ND -- Nuno Dias [EMAIL PROTECTED] LIP
Re: lev 0 FAILED [Estimate timeout from ******]
No, the two machines are in the same network, no firewall. ND On Thu, 2004-12-02 at 17:55 +0100, Christoph Scheeder wrote: Nuno Dias schrieb: Hi, I have a Digital Unix machine that give me some strange results when i try to use amanda. If i configure disklist with 2 or more disks of the Digital Unix machine, the amanda report tell me this: xxx/ lev 0 FAILED [Estimate timeout from xx] xxx/usr lev 0 FAILED [Estimate timeout from xx] xxx/ lev 0 FAILED [Estimate timeout from xx] The amandad.20041202142753000.debug file in Digital Machine have this error: amandad: time 200.266: dgram_recv: timeout after 10 seconds amandad: time 200.266: waiting for ack: timeout, retrying amandad: time 210.267: dgram_recv: timeout after 10 seconds amandad: time 210.267: waiting for ack: timeout, retrying amandad: time 220.267: dgram_recv: timeout after 10 seconds amandad: time 220.267: waiting for ack: timeout, retrying amandad: time 230.267: dgram_recv: timeout after 10 seconds amandad: time 230.267: waiting for ack: timeout, retrying amandad: time 240.267: dgram_recv: timeout after 10 seconds amandad: time 240.267: waiting for ack: timeout, giving up! amandad: time 240.267: pid 22594 finish time Thu Dec 2 14:31:54 2004 The strange thing is, if i configure only one disk in disklist, the backup run ok, and no problem is report in amanda report. I increased the etimeout/ctimeout to a big number ... and did not work. I have a Linux machine that is the master and the Digital Unix machine is the client, the version of amanda is 2.4.4p4 Thank's for some help. ND Hi, could this be a firewall-timeout on the linux-machine? Christoph -- Nuno Dias [EMAIL PROTECTED] LIP
