Gene,
Send us a PS color template and I will be happy to include it in the
distribution.
Jean-Louis
Gene Heskett wrote:
Greetings all;
One of the reasons my old epson c82 has been such a hockey puck is amanda, as
I have it printing the nightly report, and this does a quite decent job of
Mister Olli wrote:
Why do you want to do that?
cause the host does not exist anymore. so there's no need to backup the
system, and the recorded data is useless for me.
oh by the way, does deleting a DLE also delete the used tape space, if
you use vtapes?
No, the delete command only
Which amanda release?
Post the amcheck.*.debug file
Jean-Louis
Steve Jacobson wrote:
All
A couple of weeks ago after working for about two months amcheck started
crashing on my system. It dumps the following trace to stderr.
Any thoughts on where to begin looking to track this down
Sven, Jordan
I swear i already tested it and it behaved as i explained. It was in the
2.4.x timeframe.
I found the bug Jordan hit and it will not be easy to fix, amandad get
hung trying to write data for one dle and doesn't proceed the other dle.
- two DLEs on the same client.
- bsd (or
Amanda should stop one of the dle, terminate the second, write it to
tape and restart the first dle.
Which release are you using?
Can you post the amdump log file?
Jean-Louis
Jordan Desroches wrote:
Dear Amanda community,
I am running two dumpers simultaneously, and using software
Tony van der Hoff wrote:
On 25 Apr at 13:22 Stefan G. Weichinger [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]
Tony van der Hoff schrieb:
Using Amanda 2.5.1p1 under Debian Etch, my backups work fine, and I can
recover partitions from tape using dd, etc.
However: [EMAIL
You don't need to upgrade gcc or glibc.
You need to install pkg-config and glib.
Jean-Louis
Craig Dewick wrote:
Ok well putting the problems with 2.5.2p1 aside for now, I decided to
give the brand new 2.6.0 source tree a go, but it's failed during the
configure phase with this:
start
Craig,
What's the output of:
grep HAVE_SOCKADDR_STORAGE config/config.h
If it is defined, then how 'struct sockaddr_storage'is defined on your
machine? It should be in socket.h under /usr/include
Jean-Louis
Craig Dewick wrote:
Hi everyone,
Ok I've had another go at compiling Amanda
Darrell,
Thanks for reporting the problem.
Can you try the attached patch?
Jean-Louis
Telsin wrote:
I noticed this problem after upgrading to 2.6.0 from 2.5.something.
All of a sudden it wouldn't complete a backup run and I was getting
messages from cron about the planner segfaulting. I
Good, your client works as expected.
Do you upgraded something else on the server? or just amanda?
Do the server receive the PREP and REP packet, look in amdump.1 log file.
Disable all firewall on the client and server.
On the 2.5.2 client, add 'debug_auth 1' in /etc/amanda/amanda-client.conf
Use
Post the complete log and debug files.
amdump.X, log.TIMESTAMPS and the taper.TIMESTAMPS.debug files
Jean-Louis
imacat wrote:
Dear all,
Hi. This is imacat from Taiwan. I downloaded and upgraded the
newly-release Amanda 2.6.0 a couple of days ago. After that, I saw
this message for
Charles, Dustin,
I think the 127.0.0.2 is the source of the problem.
Check the named configuration and host database, NIS, /etc/hosts.
Why the hostname (fiume.localnet) resolve to 127.0.0.2?
Do you have an interface configured for 127.0.0.2?
Jean-Louis
Dustin J. Mitchell wrote:
On Fri, Apr
Theodotos Andreou wrote:
Tony van der Hoff wrote:
On 2 Apr at 9:47 Theodotos Andreou [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]
Is there a way to tell a Backup job not to start if there is no correct
label found on the changer? I do not want to use amflush later because
via 'make installcheck'.
* Amanda configuration file changes
o amanda.conf changes
+ flush-threshold-dumped
+ flush-threshold-scheduled
+ taperflush
+ device_property
+ usetimestamps default to yes
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20080401 14:33]:
Hello,
The Amanda core team is pleased to announce the release of Amanda 6.2.
It takes courage to release on April 1st!
And I suppose this is meant to be 2.6 :)
I'd love to test but how to I get
Mister Olli wrote:
I just re-read the docs about ports, and I hope to understand it right.
- If I have a firewall between the backup client and server, the
easiest thing is to compile the client with custom --with-tcpportrange
and --with-udpportrange settings, and then open these ports in the
Jean-Francois Malouin wrote:
However amadmin info' still reports only one tape at level 0.
Is this the expected behaviour?
It's expected behavior, 'amadmin info' reports only the tape for the
last PART.
Jean-Louis
Hello,
The Amanda core team is pleased to announce the third beta release of
Amanda 2.6.0, the 2.6.0b3 release. It has a complete rewrite of the tape
handling code (Device API).
It can be downloaded from http://www.amanda.org or
https://sourceforge.net/project/showfiles.php?group_id=120
Jean-Francois,
It's a known bug in amrecover, (will be fixed in 2.6.0b3). it try to
recover from dump even if not all part are available.
From amdadmin, only part 158, 159 and 160 are available.
You said all the parts are available on tapes, but why amadmin doesn't
list them?
Did it gives
John,
By defaults, amanda will never do more than runtapes * tape_length,
unless you set 'maxdumpsize', added in 2.4.4.
Jean-Louis
John Hein wrote:
Yes, it's the classic problem. I understand the cause, but I have a
question.
a little background for those who don't know about this one...
There is no option to do that.
Jean-Louis
Nicki Messerschmidt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
is it possible to define (in a dumptype) what holding disk to use?
I have a server which backups itself and this server has two raid
arrays. I placed a holding disk on each
What's in the FAILED AND STRANGE DUMP DETAILS section of the email report?
Which amanda release?
Which tar release?
Did you upgraded something on the system?
Jean-Louis
Rodrigo Ventura wrote:
Hello,
I'm getting sporadically errors like this:
FAILURE AND STRANGE DUMP SUMMARY:
omni/
to restore before.
Like I said, I have included the files in case you want to look at them. I
can understand if you don't since this appears to be a case of a bad backup
(from my humble guess).
Thanks again for all of your time and trouble.
Regards,
Gordon
-Original Message-
From: Jean-Louis
Set an CLIENT_USERNAME in amanda-client.conf.
Jean-Louis
Donald Murray, P.Eng. wrote:
I'm attempting an amrecover on a Fedora 8 client (amanda-client-2.5.2p1-8.fc8),
with a Fedora Core 6 tape-server (amanda-backup_server-2.5.1p3-1.fc6).
I've done all the mucking around with ssh keys as
Dustin J. Mitchell wrote:
On Fri, Feb 22, 2008 at 12:48 PM, Gordon J. Mills III
[EMAIL PROTECTED] wrote:
My first question is: How can I have Amanda use a different path for this
task. I have an NFS mounted external drive that has much more room on it.
If you're using amrecover, you
amrecover only write to disk the files you asked for extraction.
amrecover extract in the current directory when we executed amrecover
(not on /tmp/Amanda), you can use the lcd command to change the cwd.
Can you post the complete output of the amrecover session and the
complete
julien brule wrote:
Hello,
i'm using the split parameter and i see that the splitdump_buffer file
have always the size i wrote in the amanda.conf file.
is it ok ?
yes.
i got another question. when you use two or more set of tape.
sometimes you are in the situation where one tape is
The files are installed in /usr/local/libexec/amanda if gnuplot is found
at configure time.
I don't know why the font are big on fc8.
Jean-Louis
Gene Heskett wrote:
Greetings;
Has amplot and friends been removed from amanda?
The reason I ask is that when I got done cleaning up duplicated
Paul Crittenden wrote:
FAILURE DUMP SUMMARY:
maple.simpson.edu /export/home/pdc/Patches RESULTS MISSING
driver: FATAL schedule line 1: syntax error (bad estimated time)
This is strange, can you send me the amdump.X log file and the
planner.*.debug files.
Jean-Louis
Your xinetd config doesn't have the correct path for the amandad binary.
Jean-Louis
Paul Crittenden wrote:
Thanks to Jean-Louis I got backup working but when I try to do an
amrecover I get another error:
# amrecover
AMRECOVER Version 2.6.0b2. Contacting server on maple.simpson.edu ...
Hello,
The Amanda core team is pleased to announce the second beta release of
Amanda 2.6.0, the 2.6.0b2 release. It has a complete rewrite of the tape
handling code (Device API).
It can be dowloaded from http://www.amanda.org or
https://sourceforge.net/project/showfiles.php?group_id=120
Hello,
The Amanda core team is pleased to announce the first beta release of
Amanda 2.6.0, the 2.6.0b1 release. It has a complete rewrite of the tape
handling code (Device API).
It can be dowloaded from http://www.amanda.org (not yet available) or
Byarlay, Wayne A. wrote:
Starting from scratch now, yields the following similar but different
all-recursive error. I got rid of my old Amanda-2.5.2p1 directory and
did a fresh tar -xvf and then a fresh ./configure. My path is:
-bash-3.00# echo $PATH
You must use the 'amoldrecover' command.
The amrecover command (in 2.5.1 and newer) can only talk to 2.5.1 or
newer server.
amoldrecover must be used to talk to older server.
Jean-Louis
Scot Hetzel wrote:
We have an Amanda backup server running 2.4.4, we are able to run
amrecover on this
Scot Hetzel wrote:
Thanks for the hint to use amoldrecover, but I'm still having problems
with it:
# amoldrecover -C Daily -s backup -t backup
AMRECOVER Version 2.5.1p1. Contacting server on backup ...
220 backup AMANDA index server (2.4.4p3) ready.
200 Access OK
Setting restore date to today
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20071220 15:57]:
Tim,
Amanda add the 'r'.
It's historical, it try to be smart and do the following conversion.
/dev/sd0a - /dev/rsd0a
/dev/dsk/c0t0d0s0 - /dev/rdsk/c0t0d0s0 - /dev/dsk/rc0t0d0s0
Because DUMP works
A 2.4 server should works with a 2.5 client.
We could help you if you posted your error.
Jean-Louis
[EMAIL PROTECTED] wrote:
Hi all,
Recently I tried to add a host to our backup system.
The client was running amanda 2.5, the server 2.4
After a few tries I gave up and installed 2.4 on the
Tim,
Amanda add the 'r'.
It's historical, it try to be smart and do the following conversion.
/dev/sd0a - /dev/rsd0a
/dev/dsk/c0t0d0s0 - /dev/rdsk/c0t0d0s0 - /dev/dsk/rc0t0d0s0
Because DUMP works with the raw device, not the block device.
Try the attached patch.
Jean-Louis
Tim Bunnell wrote:
zuki wrote:
There are a number of issues here that are hard to answer without
more information about your setup, volume of data and budget. These
are things that every backup administrator has to answer, and there
is no particular right answer.
One issue is how and when to do archives with
Thomas Ginestet wrote:
Sorry for the delay, we just changed the backup server and it does the
same thing on the new one (i suppose there is a mistake in my amanda
configuraiton).
Like before, the full dump should have been made on 2007-11-30 instead
of the incremental level 4.
I expected:
Your xinetd amanda service is configure for bsdtcp auth, but you are
using bsd.
Edit your dumptype to include: auth bsdtcp
Jean-Louis
Tech wrote:
I am in the process of learning Amanda and I am hoping someone can help me
with a problem I am having.
I have been using this website as a
I tested it, and tar doesn't exit after the first occurrence. Maybe
because it read from a pipe.
Anyway, amidxtaped will read the complete image from tape, decompress
it, send it to amrecover. amrecover will fail because tar would have exited.
Jean-Louis
Paul Bijnens wrote:
On 2007-11-23
What's the error message in the email report?
Jennifer Luisi wrote:
Hi there,
I'm new to Amanda and am trying to get a disk-to-disk backup going.
When I run amcheck, everything seems fine. Then, when I run amdump,
nothing ever gets written to disk (virtual tape). The amanda log file
your amanda service is configured for bsdtcp auth, which auth are you
using in amrecover, the default is 'bsd', you can set it in
amanda-client.conf or using '-oauth=bsdtcp' as argument to amrecover.
Jean-Louis
Charles Stroom wrote:
Hi all,
today I tried to restore a couple of files, but
I don't know why the backup seems to hang.
Nothing say the problem is with the vtape.
Post the dumper.*.debug, taper.*.debug, amdump.1 and log.200711... files
Alos post the amandad.*.debug file from the client.
Jean-Louis
Jennifer Luisi wrote:
Jean-Louis Martineau wrote:
What's the dumper
Charles Stroom wrote:
I tried Jean-Louis's suggestion:
fiume:~ # amrecover -oauth=bsdtcp
AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
[request failed: recv error: Connection reset by peer]
the reply is different now and instantaneous. So I checked a bit
further and my
I only want debug files for a failed run.
I think I found the problem, can you try the attached patch on the server.
The hmm, disk was stranded on waitq message hide a connection problem.
Jean-Louis
Francis Galiegue wrote:
Le Wednesday 21 November 2007 20:07:47, vous avez écrit :
You
Are you sure about the size of your tape?
DLT4000 is 20GB Native, 40GB compressed.
Since you use software compression, you can only write 20GB to each tape.
Jean-Louis
Martin.Hepworth wrote:
Wayne
So what happens if you change runtapes to 1? Ie use a minimum of 1 tape.
--
Martin Hepworth
Snr
You should never get a hmm, disk was stranded on waitq error message.
Post the complete amdump.X log file from the server and the complete
amanda.*.debug and sendsize.*.debug files from the client.
Jean-Louis
Francis Galiegue wrote:
[Resend... Without the attachments. Looks like the mailing
The problem is in the changer script, it doesn't use the -otapedev.
The fix is to tell amdump to not use the changer:
amdump ... -o tapedev=/no/such/device -o tpchanger=
Jean-Louis
Gerrit A. Smit -TI- wrote:
We have a tape-robot with tapes to dump on, but sometimes I don't want to dump
to
Steven Backus wrote:
Here is gen13-excludelist:
./gen13/coal/r03/noback/
I'm using amanda 2.5.2p1. Is this too deep to exclude? Can anyone
help me debug this?
I think your exclude will match nothing, you should read gnutar
documentation.
Use './gen13/coal/r03/noback' or
bandwidth estimation is done using the previous backup of the DLE,
You can get the 'dump rates' with: amadmin config info
Jean-Louis
Marc Muehlfeld wrote:
Hello,
I have a question about the dumporder parameter. To what are the two
bandwidth options (B and b) related? Client/Server connection
man amanda
Look at the HOST DISK EXPRESSION section.
Jean-Louis
Francis Galiegue wrote:
Le Friday 16 November 2007 20:40:36 Jean-Francois Malouin, vous avez écrit :
[...]
adadmin conf force [ hostname [ disks ]* ]+
^
this is a regex so you have to
You must defined a split_diskbuffer if the dump go directly to tape
without using a holding disk.
In this case, there is no advantage to use a tape_splitsize bigger than
your memory size. Also, on a 32 bit system, it is limited to below 2Gb.
Jean-Louis
Charles Curley wrote:
I added
The problem is with the sendsize program, wah't in the sendsize.*.debug
file?
Did amcheck succeed?
Jean-Louis
Mark Scheufele wrote:
Hi amanda users,
I am currently having the problem that yesterday's dump is hanging at
the stage of getting estimates.
[EMAIL PROTECTED]:/opt/amanda]#amstatus
amanda can't do it automaticaly, but it is planned.
You could restore everything on the holding disk and use amflush to
flush them to the new tape.
amrecover will correctly works with the new tape.
if your blocksize on tape is 32k, it is a simple as:
cd /holding/disk/path.
mkdir
Brian Cuttler wrote:
Hello amanda users,
This isn't an issue of great import, I'm just trying to avoid
clutter in the config directory.
I must be using logdir in amanda.conf incorrectly...
I'd thought this would allow me to push my log files (log.YYMMDD
and amdump.N) into a subdirectory, but
fedora wrote:
this is the logs on dumper on server:
dumper: connect_portrange: connect from 0.0.0.0.5 failed: Connection
timed out
dumper: connect_portrange: connect to 202.53.250.159.37782 failed:
Connection timed out
dumper: stream_client: Could not bind to port in range 5 - 50100.
Linda Pahdoco wrote:
Jon LaBadie wrote:
Amrecover, not amrestore, would be the command to extract a directory
tree from that holding disk (or tape).
If that is what you used, and you were unable to see the index of files
in the dump, was the record parameter set to yes when the dump was
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20071030 10:40]:
This bug is fixed in 2.5.3alpha, but the patch was not backported to
2.5.2p1.
Can you try the attached patch?
Looks like the patch did it.
amadmin now reports correctly and amfetchdump can
Are you sure the server receive the request?
Did amandad get execute on the server? Post its debug log.
Check your firewall/network log.
Jean-Louis
fedora wrote:
hi all,
I am having problem with amrecover..
amrecover DailySet1
AMRECOVER Version 2.5.1p3. Contacting server on server.com ...
This bug is fixed in 2.5.3alpha, but the patch was not backported to
2.5.2p1.
Can you try the attached patch?
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
With amanda-2.5.2p1 I did an archive a few days ago and trying to
restore it caused me a few problems: amfetchdump tells me that
there is
Your disks are new, only full dump is possible.
You have no tape.
amanda go in degraded mode.
You don't allow full dump in degraded mode (see reserve option)
amanda can't dump the new disks.
Either set 'reserve' to a smaller value or put a tape.
The amanda-client.conf files are not needed, even
On a 32 bits machine, tape_splitsize is limited to 2gb.
Jean-Louis
Julien Brulé wrote:
hi,
i try to split a DLE with this dumtype
define dumptype nocomp-high-split {
global
tape_splitsize 4 gb
split_diskbuffer /Data/amanda/amanda_split
fallback_splitsize 1 gb
comment very
Why /var/lib/amanda/DAILYSET/index does not exist?
Do you generate index? What's the index setting on your dumptype?
What's the output of: amadmin DAILYSET disklist
Did it list 'index yes' for all DLE?
Jean-Louis
Ingo Freund wrote:
Hi,
when I try to run amrecover and call it like:
[EMAIL
Index are needed for amrecover, you must enabled them.
Add 'index yes' to your dumptype.
amrecover will only works your newer dump.
Ingo Freund wrote:
On 22.10.2007 17:17, Jean-Louis Martineau wrote (please find the answer below
the original text):
Why /var/lib/amanda/DAILYSET/index does
You can only define one lbl-templ, but you can easily print another one:
amreport config -o TAPETYPE:XYZ:lbl-templ=/path/to/label-8.5x11.ps
-l /path/to/logdir/log.x
Replace XYZ by the tapetype you use.
Jean-Louis
Paul Lussier wrote:
Hi all,
Is there a way to use multiple lbl-templ
Paul Lussier wrote:
Hi all,
I'm seeing an error I've never seen before, and google didn't turn up
anything useful. amstatus is reporting this for several file systems
on different machines:
ra:/var 0 driver: (aborted:[request failed: error sending REQ: send
REQ to
Krahn, Anderson wrote:
After creating a amada-client.conf in /etc/Amanda..
I get the following error
/opt/amanda/server/sbin/amrecover Full
AMRECOVER Version 2.5.2p1. Contacting server on prdapp16-qa-master ...
NAK: amindexd: invalid service, add 'amindexd' as argument to amandad
#cat
Look in amandad.*.debug files
Check for a line with amandad: creating new service: sendsize
send all following lines starting with OPTIONS, GNUTAR or DUMP to
sendsize stdin.
Jean-Louis
Olivier Nicole wrote:
Hi,
Is there a way to manually run sendsize? What are the arguments? When
I run it
Paul Lussier wrote:
You should add a spindle for dle on the same physical disk, it can be
a lot faster.
I don't understand this statement. Could you clarify please?
man amanda
search for spindle
All DLE of a physical disk should have the same spindle (0).
It's generally faster to run
wrote:
Jean-Louis Martineau [EMAIL PROTECTED] writes:
If sendsize is not running, it's because it crashed.
Hmm, it's definitely not running, but I don't see any trace of a crash.
Is there more verbose logging that can be turned on somewhere?
I don't understand why amandad finish
It's not a dtimeout problem.
The socket can't be connected, do you have a firewall between client and
server?
Jean-Louis
Rob Dyke wrote:
Hello List,
One of my backup clients started failing recently. All other clients are fine.
Using /var/lib/amanda/cwnbackup/amdump.1 from Fri Oct 12
Paul Lussier wrote:
Jean-Louis Martineau [EMAIL PROTECTED] writes:
Why you never posted the error in the amandad debug file?
I thought I had. I've got etimeout set to 72000, so seeing it timeout
near 21000 set off alarms for me
Paul Lussier wrote:
Jean-Louis Martineau [EMAIL PROTECTED] writes:
It's weird.
Do you have an amdump log file or just amdump.1?
The only way to get this is if you killed amanda process on the
server, maybe a server crash.
Do you still have amanda process running on the server?
I do
There is difference between system services (amanda, amanaidx and
amidxtaped) and
amanda services (amdump, selfcheck, sendsize, sendbackup, ...)
amandad is neither.
You want the amanda system service to be able to launch the amdump
amanda service.
change your inetd.conf to:
amanda dgram
They are not due for a full dump, why do you think they should do one?
With your config, they will do a full at every 7 days.
These DLE are done Monday, the will continue to be done Monday, that's
your config.
You must force them to the next full on Friday with (amadmin config
force serv1).
When you forced the full, did it succeeded?
Thomas Ginestet wrote:
Sorry, i forgot one thing: i've already forced on Friday all DLE to do
a full, but it was the same problem the week after.
Thomas Ginestet
Jean-Louis Martineau a écrit :
They are not due for a full dump, why do you think
Ginestet wrote:
Yes, it did for all the DLE.
Thomas Ginestet
Jean-Louis Martineau a écrit :
When you forced the full, did it succeeded?
Thomas Ginestet wrote:
Sorry, i forgot one thing: i've already forced on Friday all DLE to
do a full, but it was the same problem the week after.
Thomas
Krahn, Anderson wrote:
2). I installed mtx on the system and using the
tpchanger chg-mtx # the tape-changer glue script
in Amanda.conf.
How does Amanda know to use mtx when a tape becomes full during a backup?
chg-mtx is not maintained, you should use 'chg-zd-mtx'.
Jean-Louis
Krahn, Anderson wrote:
Here is the output of the sendsize file:
sendsize: debug 1 pid 27914 ruid 30063 euid 30063: start at Fri Oct 5
12:07:00 2007
sendsize: version 2.5.2p1
Could not open conf file /etc/amanda/amanda-client.conf: No such file
or directory
Reading conf file
Paul Lussier wrote:
Hi all,
I'm using amanda 2.5.1p1-2.1 from Debian/stable.
I have several file systems which take hours to estimate and dump.
My amanda.conf contains:
etimeout 10800 # 3 hours
dtimeout 7200 # 2 hours
ctimeout 30
My sendsize log reports the following:
$ egrep
Paul Lussier wrote:
Jean-Louis Martineau [EMAIL PROTECTED] writes:
Look at the amdump log file, it list all estimate received from the clients.
Are you sure the sendsize debug file you look at is the correct one?
sendsize will continue even after an estimate timeout.
It was the only
man amanda.conf
DUMPTYPE SECTION
client_username string
Default: CLIENT_LOGIN. Specify the username to connect on
the client, only use with rsh/ssh authentification.
Cameron Matheson wrote:
Hello,
I have an amanda setup using auth-ssh, but I'm running into a bit of
It's weird.
Do you have an amdump log file or just amdump.1?
The only way to get this is if you killed amanda process on the server,
maybe a server crash.
Do you still have amanda process running on the server?
Paul Lussier wrote:
Jean-Louis Martineau [EMAIL PROTECTED] writes:
Can you
What's the maxdumps setting?
Jean-Louis
Paul Lussier wrote:
Hi all,
I recently changed my disklist such that all DLEs which pertain to my
NFS appliance have a -1 spindle entry. My understanding of the man
page was that a -1 spindle setting for a set of DLEs on the same host
means they would
stan wrote:
I added 2 new clients to a working amanda system. Both of these clients
are Ubuntu Edgy machines running Amanda 2.5.2p1. The Amanda server(Amanda 2.5.2p1)
is Ubuntu Fiesty 50+ clients
of arious OSes/versions
of Amanda which work. The error reported on the edgy machines from
stan wrote:
On Wed, Oct 03, 2007 at 11:00:57AM -0400, Jean-Louis Martineau wrote:
stan wrote:
I added 2 new clients to a working amanda system. Both of these clients
are Ubuntu Edgy machines running Amanda 2.5.2p1. The Amanda
server(Amanda 2.5.2p1) is Ubuntu Fiesty 50+ clients
The amdump log file show that one backup was done, the IPv6 problem is
fixed.
Craig Dewick wrote:
Recompiling with the --without-ipv6 option didn't change anything
unfortunately, and I noticed in the report email that all of the file
systems targetted for backup are being reported as:
Craig Dewick wrote:
On 01/10/2007, *Jean-Louis Martineau* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
The amdump log file show that one backup was done, the IPv6 problem is
fixed.
That is what I was thinking too.
yoda /dev/dsk/c3t1d0s4 RESULTS MISSING
driver
Craig Dewick wrote:
6 [EMAIL PROTECTED] # more dumper.20070928130458000.debug
dumper: debug 1 pid 15243 ruid 982 euid 0: start at Fri Sep 28
13:04:58 2007
dumper: debug 1 pid 15243 ruid 982 euid 0: rename at Fri Sep 28
13:04:58 2007
dumper: time 173.205: connect_port: Try port 0:
Can you post a dumper.*.debug and chunker.*.debug files?
Jean-Louis
Craig Dewick wrote:
Ok the manual run is completed and I've made the logfile with the
extra debug information available at:
http://jedi.apana.org.au/~amanda/amdump.28092007
I'd appreciate any feedback on what the extended
What failed?
You show us the taper wrote it's TAPEEND block, it's good.
What's the error?
Jean-Louis
Christopher McCrory wrote:
Hello...
RHEL5 x86_64 , amanda 2.5.2p1
I am using 'server_encrypt /usr/sbin/amcrypt-ossl-asym '
I can do backups. I can flush to tape. If I add 'autoflush
Craig, Can you fix the reply-to field of your email message.
You can set 'debug_auth 1' in amand.conf, debug files will show more
details.
The problem is not with the planner, but with the dumper-chunker socket.
Post dumper and chunker debug files.
What's the resolution for localhost?
What's
Craig Dewick wrote:
What's the resolution for localhost?
What's the resolution for 127.0.0.1?
Do you have a route for 127.0.0.1 and localhost?
I'm not sure what you're asking with these. 8-)
ping localhost
ping 127.0.0.1
grep localhost /etc/hosts
I have:
/usr/include/netinet/in.h: typedef uint16_t in_port_t;
Can you fix your reply-to to have a valid field.
Jean-Louis
Craig Dewick wrote:
On Fri, 21 Sep 2007, Jean-Louis Martineau wrote:
It looks like your system include files doesn't define the in_port_t
type.
Find where
Takashi Kurakata wrote:
Thank you for answering my question.
krb5keytab and krb5principal are global parameter, they are not
dumptype parameter.
I deleted krb5keytab and krb5principal from dumptype.
When I executed amcheck in the kerberos environment, the following
messages were
output.
It looks like your system include files doesn't define the in_port_t type.
Find where it is defined with: grep -r in_port_t /usr/include
Try to include this file from common-src/amanda.h
Jean-Louis
Craig Dewick wrote:
Now that I seem to have sorted out Amanda on the server host, I've
turned
You should read the documentation for your release.
ssh_keys was added in 2.5.1.
With 2.5.0, it used the default key of the user.
Jean-Louis
Takashi Kurakata wrote:
Hi all,
I am using amanda that the bundle is being done by RHEL5 now.
The version of amanda is 2.5.0p2-4.
I want to construct
krb5keytab and krb5principal are global parameter, they are not
dumptype parameter.
If you want to use ssh or krb5, I strongly suggest to upgrade to 2.5.2p1.
Jean-Louis
Takashi Kurakata wrote:
Hi all,
I am using amanda that the bundle is being done by RHEL5 now.
The version of amanda is
1101 - 1200 of 1694 matches
Mail list logo
