What's in 20091122180002?
Mike Chesnut wrote:
amdump got stuck for me the other day, and after running amcleanup, it
seems to have lost track of a holding dir. My holding disk has these
directories in it:
20091121180002
20091122180002
However, doing amadmin config holding list only lists
Try amfetchdump instead of amrestore.
Jean-Louis
Brian Cuttler wrote:
Dustin, et al,
Periodically while I'm performing a restore with # amrestore
the cronjob # amcheck grabs and swaps out the tape on me.
Is there a way to interlock these two jobs so that doesn't happen ?
For my money, I
Do the backup succeeded? It looks it failed.
flow...@hagsc.org wrote:
I'm running a fresh install of amanda 2.6.1pl1 (I recently upgraded to
p2 and experienced the same problem). When performing full dumps, the
curinfo/machine/disk/info files are getting updated (they have proper
ownership),
pre-host-backup and post-host-backup can't be executed on client, they
can be executed on the server only.
execute-where server
Jean-Louis
Benjamin Boksa wrote:
Hi List,
I am using the Script API to execute some commands on the clients to be backed
up. I would like to execute those
Benjamin Boksa wrote:
Hi Jean-Louis,
pre-host-backup and post-host-backup can't be executed on client, they can be
executed on the server only.
Thanks for your fast answer, I modified http://wiki.zmanda.com/index.php/Script_API
accordingly - maybe you or others could step in an
Benjamin Boksa wrote:
Hi Jean-Louis,
So as (pre|post)-host-backup can't be executed on the client: What is the best
way to stop some services on the client before the first DLE is backed up and
restart them after the client has been backed up?
A solution is to run a script on
Dustin J. Mitchell wrote:
On Sun, Dec 6, 2009 at 2:21 PM, Jean-Louis Martineau
martin...@zmanda.com wrote:
After your hint I took a closer look at running (pre|post)-host-backup on
the server. It seems that(pre|post)-host-backup gets executed for each DLE
which is not exactly what I need
Benjamin,
It's a bug, try the attached patch.
Jean-Louis
Benjamin Boksa wrote:
I'd hate to see too much work go into hacking *around* the script API
-- it's brand new! The best outcome would be to fix/improve the script
API as appropriate, but at the very least, let's make sure that the
The first patch was not correct. Try this new one.
Jean-Louis
Jean-Louis Martineau wrote:
Benjamin,
It's a bug, try the attached patch.
Jean-Louis
Benjamin Boksa wrote:
I'd hate to see too much work go into hacking *around* the script API
-- it's brand new! The best outcome would be to fix
Increase your holding disk size.
Amanda reserve all the space needed for a dle when it start it, even if
'df' show it is free, the space is reserved.
Nomad wrote:
I've noticed that the inparallel setting appears to not be honored.
The server is running 2.6.1p2, redhat enterprise 5.4, it has
The backup size is larger than the estimate size.
Amanda try to use more holding space, but it is reserved for others dle,
it wait for some dle to be flushed to tape before it can use more
holding disk and continue the dump.
Jean-Louis
Nomad wrote:
(Sorry for the quickfire question
amrecover -oauth=bsdtcp
Jean-Louis
stan wrote:
Tried to do some recovering yesterday, using amrecover, and could not get
past the timeout waiting for ack on systems that were working, the last
time I checked.
Goggle led me to a post on the Zamnda forum suggesting that I needed an
The dump is still on holding and will be flushed on the next run.
The error is because amanda tried to flush it, but failed because the
tape was full and your flush_* criteria doesn't allowed amanda to use
another tape.
You will et an error like this at every run, it is the latest dle amanda
Hi Charles,
Thanks for the good work. I have a few comments:
* Written in C.
should be:
* Written in C and perl
* Supports Kerberos 4 and 5 security, including encrypted dumps.
should be:
* Supports Kerberos 5 security, including encrypted dumps.
Kerboros 4 is no longer supported.
* Full
What's the output of: amadmin CONF version | grep BUILT_REV.
This bug is fixed in 2362
Download the latest 20091218 snapshot if you have an early build.
Jean-Louis
Gene Heskett wrote:
Greetings;
More of the same with 20091217's snapshot. Comments inserted.
-- Forwarded Message
Amanda should remove the snapshot. It's a bug if it doesn't.
The pre_dle_* scripts create the snapshot and the post_dle_* scripts
remove them. Do you configured the post_dle_* scripts?
Jean-Louis
Brian Cuttler wrote:
Amanda 2.6.1p1 on Solaris 10/x86.
We have been running great! However
In case of hard failure, the post_dle_* scripts are not executed and the
snapshot are not removed, you must removed them manually.
Jean-Louis
Brian Cuttler wrote:
Jean-Louis,
On Wed, Jan 06, 2010 at 10:15:48AM -0500, Jean-Louis Martineau wrote:
Amanda should remove the snapshot. It's
Steve Wray wrote:
On the client, in the sendbackup.20100106012630.debug log I see:
sendbackup-gnutar: time 0.056: /usr/lib/amanda/runtar: pid 3348
sendbackup: time 0.057: started backup
sendbackup: time 90.352: index tee cannot write [Broken pipe]
sendbackup: time 90.352: pid 3346 finish time
Steve Wray wrote:
Jean-Louis Martineau wrote:
Steve Wray wrote:
On the client, in the sendbackup.20100106012630.debug log I see:
sendbackup-gnutar: time 0.056: /usr/lib/amanda/runtar: pid 3348
sendbackup: time 0.057: started backup
sendbackup: time 90.352: index tee cannot write [Broken pipe
Steve Wray wrote:
Dustin J. Mitchell wrote:
On Wed, Jan 6, 2010 at 4:01 PM, Steve Wray steve.w...@cwa.co.nz wrote:
Am I to understand that there could be a problem in having 'too
many' DLE's
for bsd or bsdudp to cope with?
I never thought of there being a limit to the number of DLE's
Run 'amadmin CONFIG disklist' and check the auth is set as expected
for all dles.
Jean-Louis
Steve Wray wrote:
Jean-Louis Martineau wrote:
Steve Wray wrote:
Jean-Louis Martineau wrote:
Steve Wray wrote:
On the client, in the sendbackup.20100106012630.debug log I see:
sendbackup-gnutar
Don't edit the tapelist by hand, run: amadmin CONF no-reuse DailySet107
Jean-Louis
mailinglis...@brennt.net wrote:
Hello,
On Mon, 11 Jan 2010 14:34:18 -0800, Paul Yeatman pyeat...@zmanda.com
wrote:
I think the command you are thinking of is amrmtape? Running this
will cause Amanda to
Jean-Francois,
It is a bug that the index files are removed for 'strategy skip' dles.
The attached patch fix it.
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
Last Friday we got bitten by a rather vicious raid controller
firmware/codeset that corrupted some of our raidsets when a disk
failed
What is the error you get from amcheck?
The '229.046' time is high for amcheck, try increasing ctimeout.
Jean-Louis
stan wrote:
WE are still having major issues with our Amanda backups. Most of the
machines that are failing still use UDP, and we recognize the need to get
newer version of
Stan, can you post the problem at the beginning of your post, I don't
like to read a long post when I don't know why I read it. It's worse
than top-posting :-).Subject should describe the problem, not how you feel.
Post the taper debug files
Jean-Louis
ps. according to amcheck output, you
stan wrote:
1263560285.332896: taper: changer: 3
rait:{file:/vtapes/DailyDump/vtape3,tape:/dev/nst0}
1263560285.333214: taper: status = complete
1263560285.447278: taper: warning: Inconsistent volume labels/datestamps: Got
DailyDump52/20100113222821 on file:/vtapes/DailyDump/vtape3 against
Are you sure the current slot is the correct one,
Check the /vtapes/DailyDump/data link? Did it link to the slot with the
DailyDump53 volume?
Jean-Louis
stan wrote:
On Fri, Jan 15, 2010 at 09:31:47AM -0500, Jean-Louis Martineau wrote:
stan wrote:
1263560285.332896: taper: changer
The recover protocol changed, you are still configured for the old
protocol, you can use it with the 'amoldrecover' command.
But you can also configure the server for the new protocol.
Yogesh Hasabnis wrote:
Hi All,
We are using amanda 2.5.2p1 in our setup. The backup server and the
client
Dustin J. Mitchell wrote:
If I restart euclid's inetd config to run it with the wrong -auth
parameter, then amcheck says:
WARNING: euclid: selfcheck request failed: timeout waiting for ACK
Client check: 2 hosts checked in 30.030 seconds. 1 problem found.
xinetd is still configured to accept
Parse the output of: amadmin CONF find
Not exactly what you want: amanda CONF due
Jean-Louis
stan wrote:
Beacuse of the ongoing problems we ar having with getting reliable Amanda
backups here, it has dawned on me that it would be nice to have a report
showing how old the newest level zero is
William,
pre-host-backup and post-host-backup script can only be run on server.
Jean-Louis
William Taylor wrote:
Im having a problem with getting a pre script to run.
Here is my relevant config. I have tried pre-dle-backup and
pre-host-backup
amanda.conf:
define script-tool
1265152485.007169: sendbackup: Spawning
/usr/libexec/amanda/application/findnetappfulls findnetappfulls
PRE-DLE-BACKUP --execute-where client --config DailySet1 --host
foo.host.net http://foo.host.net --disk /backups/ --device /backups/
--level 1 in pipeline
The debug file show the script is
Jerome Ibanes wrote:
This is a followup from the forum's question:
http://forums.zmanda.com/showthread.php?p=9221
Why did you recommend 1000 and not 100 for the thresholds?
Must be something above runtapes*100, I just took a big value.
The method I'm using right now is to do the dump first
Easy to do.
Every days run: amdump CONF -otpchanger= -otapedev= -oreserve=0
To flush to tape: amflush CONF
Jean-Louis
Dimiter Maznekov wrote:
Is it posible to be setup this way of backuping?
Daily make backup according DLE, but storring on holding disk and at
the end of the week to be
Jobst,
What you do looks good, post the sendbackup.*.debug file.
Jean-Louis
Jobst Schmalenbach wrote:
Hi.
I have one client host that refuses to listen to the exclude list option in the dumptype.
I know it works, for example I backup a 120GB /amanda directory/parition on the tape
host
).
They should be in /tmp/amanda but they are not (except on the
tape host itslef). Bugger. Need to do some research.
Jobst
-Original Message-
From: Jean-Louis Martineau martin...@zmanda.com
To: Jobst Schmalenbach jo...@barrett.com.au
Cc: amanda-users@amanda.org
Subject: Re: exclude list
Gene,
Neither Dustin nor me had the privilege to fix the permission issue.
Permission get fixed, I uploaded the latest snapshot.
Jean-Louis
Gene Heskett wrote:
On Sunday 28 February 2010, Dustin J. Mitchell wrote:
On Sat, Feb 27, 2010 at 7:34 PM, Gene Heskett gene.hesk...@verizon.net
I never like using two configs. Recovery is complex.
Why not use one config? amanda don't allow it, but you can cheat.
Edit amanda.conf every days to change the tpchanger and strategy, if
could be done by a simple script, or more easily, put the difference in
separate file and use
Brian Cuttler wrote:
On Thu, Mar 04, 2010 at 06:28:08AM -0500, Jean-Louis Martineau wrote:
I never like using two configs. Recovery is complex.
Why not use one config? amanda don't allow it, but you can cheat.
Edit amanda.conf every days to change the tpchanger and strategy, if
could
Disable the tapedev and tpchanger:
amdump CONF -otapedev= -otpchanger=
Jean-Louis
Dr 440 wrote:
Is there a way to get a backup to remain in the holding disk? In the
morning when I get in to work, I review the backup jobs from the night
prior, and occasionally there is an error in one of
* configuration override for dumptype works with inheritance.
Jean-Louis Martineau
With the amgtar application (in 3.1.0), an exit status of 1 from runtar
is not an error.
file changed as we read it will still result in STRANGE result, but
you can add a regex to turn it into a SUCCESS.
Jean-Louis
Toomas Aas wrote:
Hello!
I upgraded Amanda from 2.5.1p3 to 2.6.1p2 on my
Look in the amlabel.*.debug file, it might gives a better error message.
Jean-Louis
whale wrote:
Hi,
I testing amanda-3.1.0rc08-20100317 with chg:robot on ubuntu server 8.04 LTS
and everything is working fine. I tried to upgrade to beta1
I'm able to compile and install from source. Config
Gene,
You need perl-devel.
Jean-Louis
Gene Heskett wrote:
Greetings all;
Trying to run my scripts to make amanda on an mdv system ends with:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../config -I../common-src
-I../common-src -I../amandad-src -I../amar-src -I../xfer-src -I../perl/amglue
Gene,
Do the tapelist is correct?
Do all log files are found?
Do the dump are listed in the output of: amadmin Daily find
Post the amindexd debug file.
Jean-Louis
Gene Heskett wrote:
Greeting all;
I just built the latest snapshot, and I still cannot do an amrecover as it
is not finding the
You lost all log files, They should in the `amgetconf Daily
logdir`/oldlog directory, moved them to
`amgetconf test logdir`.
Jean-Louis
Gene Heskett wrote:
On Thursday 22 April 2010, Dustin J. Mitchell wrote:
On Thu, Apr 22, 2010 at 11:00 AM, Gene Heskett gene.hesk...@verizon.net
Jean-Francois,
Thanks for testing.
Can you try the attached patch? It fix a bug I added :-(
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
More toying with 3.1.0beta2.
Using amrecover to extract a multi virtual tape dump I see something
confusing even though in the end the dump is
$man amdump
SYNOPSIS
amdump config [host [disk...]...] [{-o configoption}...]
The config must be the first argument:
Jean-Louis
Brian Cuttler wrote:
Amanda 2.6.1p1
I thought this used to work, its current in the man page.
# amdump -o tapedev=/dev/nst1 cascade cascade
Hi Gene,
Can you confirm you are using the 'bsd' auth?
Try the attached patch.
Thanks for testing.
Jean-Louis
Gene Heskett wrote:
Greetings;
Built 3.2-3003 earlier today, amcheck worked fine.
amrecover OTOH, killed the canary:
[r...@coyote amanda-3.2.0alpha.svn.3003]# amrecover
Robert,
You can override it like all amanda confoguration.
$ amflush CONF -otaperflush=0
Jean-Louis
McGraw, Robert P wrote:
Running amanda 2.6.1/p2 Sun Solaris 10 x86
In my amanda.conf file I have
flush-threshold-dumped100
flush-threshold-scheduled 100
#taperflush
McGraw, Robert P wrote:
Running Amanda-2.6.1-p2 On Solaris 10 X86
Why is this considered an error?
No reason, already fixed it in 3.1, it is not an error.
Jean-Louis
I check the error status of my amdump and base on the error status after it
finishes I take certain actions.
Is there
Gunnar,
This bug is already fixed in the svn repository.
Thanks for testing and reporting the problem.
Jean-Louis
Gunnarsson, Gunnar wrote:
While testing amrecover I got core dump see below on Solaris sparc
amrecover extract
Extracting files from holding disk on host localhost.
The
Gunnar,
As a workaround, you just need to create an empty tapelist file.
Thanks for reporting this problem.
Jean-Louis
Gunnarsson, Gunnar wrote:
I got the fatal error see below while testing the new option
autolabel, the configuration was empty and amcheck -s was ok.
The next tape Amanda
Hello,
The Amanda core team is pleased to announce the release of Amanda 3.1.0.
Source tarballs are available from
* http://www.amanda.org
* https://sourceforge.net/project/showfiles.php?group_id=120
Binaries for many systems are available from
*
Robert,
You are using calcsize for the estimate, it doesn't use check the device
number.
But when you do the backup, tar check the device, as you mount it every
time, it have different device number and it backup all files.
Set the CHECK-DEVICE property of amgtar to NO. (man amgtar)
exclude doesn't works amstar.
Jean-Louis
Brian Cuttler wrote:
Amanda Users,
Dustin,
We are using amanda 2.6.1p1 on a Solaris 10x86 system with ZFS snapshots.
We where aware that one of the file systems was too large to fit
on a single tape volume, even though it was an LTO4 tape.
This is
But the manpage says:
etimeout int
. A negative value will be interpreted as a total amount of time to wait
per client instead of per disk.
Who's wrong? Manpage or program code?
Well, it was changed in this commit:
commit 1a2051ece2e27fea65b9bf05dac235a7e358f52a
Author: Jean-Louis
use-slots is a property, each property is an array.
You should do something like:
$properties = changer_config_getconf($ss, $CHANGER_CONFIG_PROPERTY);
#get all properties
@slot_range = $properties-{'use-slots'}; #get 'use-slots' property
You must then use the first element of the
Hello,
The Amanda core team is pleased to announce the release of Amanda 3.1.1.
It is a bug file release.
Source tarballs are available from
* http://www.amanda.org
* https://sourceforge.net/project/showfiles.php?group_id=120
Binaries for many systems are available from
*
McGraw, Robert P wrote:
inetadm -l amanda/udp
SCOPENAME=VALUE
name=amanda
endpoint_type=dgram
proto=udp
isrpc=FALSE
wait=TRUE
exec=/local/amanda/amanda/libexec/amanda/amandad
-auth=bsdtcp amdump amindexd amidxtaped
Stefan G. Weichinger wrote:
Since amanda-3.1.x my backups nearly always FAIL (the
amanda-report-mails tell me so).
Without going into detail: is there some list of events triggering that
FAIL ?
Is it just because not all DLEs fit onto tape every time?
No, it's because one of the DLEs was
Exit code to amgtar and amdump are not related.
Look at the amdump man page for exit code of amdump, you can filter the
bit (16) you don't care about.
Jean-Louis
McGraw, Robert P wrote:
Running amanda-3.1.1
I am using the following to save on tape usage
flush-threshold-dumped100
It works for me.
Either it is a bug in your regex library or you are running an older
amstar, its version is on the first line of the amstar debug file.
Jean-Louis
Dennis Benndorf wrote:
Hello @all,
I had a conversation with Dustin about amstar and the regex. Here is what we
discussed:
I
try: amflush -otaperflush=0 daily
solaris require that all dash argument are before the config name.
except for amdump which is a shell script.
Jean-Louis
McGraw, Robert P wrote:
I am trying to run something like
amflush daily -otaperflush=0
but I get Argument '-otaperflush=0'
Hi Jean-François,
Try the attached patch, it will works with newer log files only.
Thanks for reporting the bug.
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
With amanda-3.1 seems we lost the tape usage in the summary report
output by amstatus. Prior versions were showning which tape has been
Do you checked the debug log on the client? Any error in them?
Do you have 'record' set to yes in the dumptype?
post the output of: amadmin CONF disklist
Can you stat a few files after two different backup to be sure that
nothing change.
Jean-Louis
Jim Kusznir wrote:
Hi all:
I've got a
Do the dump was done with the patched taper?
Jean-Louis
Jean-Francois Malouin wrote:
Hello Jean-Louis,
I was away hence the delay.
* Jean-Louis Martineau martin...@zmanda.com [20100719 08:31]:
Hi Jean-François,
Try the attached patch, it will works with newer log files only.
Thanks
I assume you put a tape you think amanda can use in the changer?
What is on that tape?
Is it labeled? is it new? What's is your autolabel setting?
What is the tapecycle? How many reusable tape in the tapelist file?
What's the output of: amtape CONF taper
It fail on the first or second tape?
Brian Cuttler wrote:
What's the output of: amtape CONF taper
It fail on the first or second tape?
~# su amanda -c ~amanda/sbin/amtape down taper
slot 25: volume 'av48-2_down_Q00060' is still active and cannot be overwritten
slot 26: volume 'av48-2_down_Q00061' is still active and cannot
Robert, can you try the attached patch?
Jean-Louis
McGraw, Robert P wrote:
As a followup, I ran amoverview and removed the WARNINGS messages and it seems
to be working correctly.
Here is a snippet
date NM TO 08 08 08 08 08 08 08 08 08 08 08
08 08 08 08 08
Dustin J. Mitchell wrote:
On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau
martin...@zmanda.com wrote:
Robert, can you try the attached patch?
(only the amoverview hunk is required, right Jean-Louis?)
yes, The correct patch is attached.
Jean-Louis
diff --git a/server-src
Try to do the same command as amanda do:
MAILER=`amgetconf daily mailer`
$MAILER -s subject off...@123.at l...@345.at w@678.at
Type a small message and end it with ctrl-D
Do the email are sent?
Jean-Louis
Stefan G. Weichinger wrote:
For a while I have problems with missing mails from
Brian,
The only workaround is to remove the big dump from the history.
Go in the curinfo/HOST/DLE directory, edit the info file.
Remove the 'history:' line for the dump.
First number is the level
Second number is the uncompressed size
Third number is the compressed size
forth number is the date
Big change to the driver and taper was committed yesterday.
Can you post the taper debug file and the amdump.1 file.
Jean-Louis
Gene Heskett wrote:
Yesterdays 3411 failed last night, all DEL's timed out waiting for writing
to tape.
The install, which ends in an amcheck:
install done, now
Can you provide the complete amflush.1 or amdump.1 files
Dustin J. Mitchell wrote:
On Mon, Sep 20, 2010 at 3:25 PM, Stefan G. Weichinger s...@amanda.org wrote:
does that help?
Perhaps. I'm strongly suspecting that this is a problem with the new
multi-tape support. Jean-Louis, do
What's your flush-threshold setting?
amgetconf CONF flush-threshold-scheduled
amgetconf CONF flush-threshold-dumped
amgetconf CONF taperflush
Stefan G. Weichinger wrote:
Am 21.09.2010 00:09, schrieb Jean-Louis Martineau:
Can you provide the complete amflush.1 or amdump.1 files
gene heskett wrote:
Butting in here, but a nice bright light bulb just came on.
I get a big fat 0 for all three amgetconf's above. Izzat my problem?
[r...@coyote amanda]# amgetconf Daily flush-threshold-scheduled
0
[r...@coyote amanda]# amgetconf Daily flush-threshold-dumped
0
[r...@coyote
I can't find why it flush nothing.
Can you upgrade to latest SVN and try the attached patch, it add mode
degugging.
Add 'debug-driver 1' in amanda.conf
Retry amflush and send me the resulting amflush.1 file.
Jean-Louis
Stefan G. Weichinger wrote:
Am 21.09.2010 00:09, schrieb Jean-Louis
Attachment included.
Jean-Louis
Jean-Louis Martineau wrote:
I can't find why it flush nothing.
Can you upgrade to latest SVN and try the attached patch, it add mode
degugging.
Add 'debug-driver 1' in amanda.conf
Retry amflush and send me the resulting amflush.1 file.
Jean-Louis
Stefan G
Stefan,
Remove the log, amdump or amflush file from the log dir.
Jean-Louis
Stefan G. Weichinger wrote:
Am 21.09.2010 19:55, schrieb Jean-Louis Martineau:
Attachment included.
Jean-Louis
Jean-Louis Martineau wrote:
I can't find why it flush nothing.
Can you upgrade to latest SVN
What's the taperalgo? Is it firstfit, largestfit or smallest
Have you enabled splitting?
Try the attached patch
Jean-Louis
Gene Heskett wrote:
On Wednesday, September 22, 2010 06:01:08 am Jean-Louis Martineau did opine:
Attachment included.
Jean-Louis
Jean-Louis Martineau wrote
Try this one!
Jean-Louis
Jon LaBadie wrote:
On Sat, Oct 02, 2010 at 04:24:46PM -0500, Dustin J. Mitchell wrote:
On Sat, Oct 2, 2010 at 1:03 PM, Jon LaBadie j...@jgcomp.com wrote:
When running amtape --help the usage message
is printed twice.
A *real* nitpick! Cool!
Fix is
Add: amrecover-changer chg-manual
in amanda.conf
Jean-Louis
Gunnarsson, Gunnar wrote:
Hi,
I'm using the the poor mans changer-manual on one system and
amrecover is not so happy with it. The setup works with andump.
Thanks Gunnar Gunnarsson
amanda.conf
tpchanger chg-manual
mezzie wrote:
Mon Oct 4 09:18:28 2010: amidxtaped: critical (fatal): '[sec -1.00 kb 32
kps -32.00 orig-kb 1290]' at
/usr/lib/perl5/site_perl/5.8.8/Amanda/DB/Catalog.pm line 677
The value of '-1' show that something is corrupted, the backup image is
probably not valid, that's why you
to
import/export slots when completed
o command-line syntax has changed incompatibly; see manpage or
'amvault --help'
* Rewritten and improved:
o amoverview
o amcheckdump
Jean-Louis Martineau
Can you restore file that have no umlaut? try: add *
Can you post the debug files
amrecover.*.debug from the client
amandad.*.debug, amindexd.*.debug and amidxtaped.*.debug from the server
Send them for both run, with the 2.6.1p2 and 3.2 client.
Jean-Louis
Marc Muehlfeld wrote:
It's
Marc Muehlfeld wrote:
/bin/tar: This does not look like a tar archive
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64 headers
/bin/tar: Read 7944 bytes from -
It has nothing to do with umlauts.
I suspect a bug in the handling of the bsd auth in amrecover.
Can
Marc,
It's a bug that can only be seen with the bsd auth.
Attached patch fix it, can you try it?
Jean-Louis
Jean-Louis Martineau wrote:
Marc Muehlfeld wrote:
/bin/tar: This does not look like a tar archive
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64
Stupid me :-(
Try this new patch, remove previous patch befora applying this one.
Jean-Louis
Marc Muehlfeld wrote:
Hi Jean-Louis,
It's a bug that can only be seen with the bsd auth.
Attached patch fix it, can you try it?
thanks for the patch. I applied it to the client and server (both
Gunnar,
Try the attached patch.
Jean-Louis
Gunnarsson, Gunnar wrote:
Hi,
I version 3.2.0 amgtar is not using PROPERTY directory
amzfs-snapshot, has something changed regarding this in 3.2.0 ?
This has been working in the previous version of amanda, snipped from
debug file:
Jon,
What is the exact error message you get?
Where do you put the allow-split? Post the complete dumptype.
Jean-Louis
Jon LaBadie wrote:
My amanda server is running Fedora 13. I recently
updated the amanda package from 3.1.3 to 3.2.0.
Both versions were Zmanda-built packages for Fedora 12.
.
In the dumptype, you write (allow-split) if you want the dle to be split
or not.
Jean-Louis
Jon LaBadie wrote:
On Tue, Oct 26, 2010 at 11:30:04AM -0400, Jean-Louis Martineau wrote:
Jon,
What is the exact error message you get?
Where do you put the allow-split? Post the complete dumptype
What amanda version on the client that failed?
Which auth are you using?
On server, what's the output of: amgetconf CONF unreserved-tcp-port
On client, what's the output of: amgetconf --client CONF unreserved-tcp-port
Do the port are open on the firewall?
Can you post the dumper.*.debug files
.
* The problem disappears directly when I downgrade amanda back to
2.6.1p2. So should be no config/firewall issue.
Am 27.10.2010 12:23, schrieb Jean-Louis Martineau:
What amanda version on the client that failed?
All clients run versions between 2.5.0 and 3.2.0. Most are 2.5.0p2. I
checked
Dennis Benndorf wrote:
Hi,
I am using the new reovery-limit which is set to:
---
recovery-limit same-host localhost
---
Is it the global or dle recovery-limit?
What is the dle recovery-limit? That's what amindexd is using?
Jean-Louis
It was set to the DNS name of the server before but
Send me the amdump.? file for which you get the error.
Jean-Louis
Dennis Benndorf wrote:
Hello,
after upgrading to 3.2.0 on the server `amstatus config` is throwing the
following messeges:
** (process:20136): WARNING **: Use of uninitialized value $getest{***...} in
The bug is not with the amstatus program. The current log file is
corrupted because many program write to it at the same time and they use
buffered output.
Try the attached patch, it make the file descriptor unbufferred. You
should not see that error on the following run.
Jean-Louis
Previous patch do not work, file are already in unbufferred mode.
The file needs to be opened in append mode so that each process can
append to the file.
Newest patch fix it.
Jean-Louis
Jean-Louis Martineau wrote:
The bug is not with the amstatus program. The current log file is
corrupted
Jon LaBadie wrote:
On Tue, Nov 02, 2010 at 07:26:47AM -0400, Chris Hoogendyk wrote:
On 11/1/10 10:10 PM, Jon LaBadie wrote:
I've started backing up my amanda files nightly
in a separate amdump run after my primary amdump.
My plan was to leave it on the holding disk and
let it autoflush
Chris Hoogendyk wrote:
Amanda dump and flush only the listed dle
It is not flushing '.bigcow. Amanda' because it is not on the command
line.
We can change this behavior.
What user expect from dle on the amdump command line:
- dump/flush only the listed dle (actual behavior)
or
- dump only
801 - 900 of 1694 matches
Mail list logo
