RE: GNUTAR hanging
Chris, Was there ever any resolution to your problem? I'm having the same problem with amanda 2.5.1p3 and GNU tar 1.16 hanging on one of my Solaris 8 servers. The funny thing is that it only hangs when tarring up one of the disks...my root filesystem. 5 other disks on the same server get backed with gtar up just fine. It seems to try dumping the / filesystem twice before abandoning it due to data timeout. I have dtimeout set to 3600 in amanda.conf. However, the tar procs on the client keep running and never finish or die and the file at /usr/local/var/amanda/gnutar-lists/lci-nms-pri.lci.com__0.new on the client has a 0 size. Any ideas? Here are some log files: === (From Amanda 2.5.1p3 server /usr/local/etc/amanda/DailySet2/log.20070426040001.0) === FAIL dumper lci-nms-pri.lci.com / 20070426040001 0 [data timeout] sendbackup: start [lci-nms-pri.lci.com:/ level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f - ... sendbackup: info end PARTIAL chunker lci-nms-pri.lci.com / 20070426040001 0 [sec 3657.354 kb 3340 kps 0.9] . . . PARTIAL chunker lci-nms-pri.lci.com / 20070426040001 0 [sec 3634.416 kb 3340 kps 0.9] FAIL dumper lci-nms-pri.lci.com / 20070426040001 0 [data timeout] sendbackup: start [lci-nms-pri.lci.com:/ level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f - ... sendbackup: info end === (From Amanda 2.5.1p3 client /var/log/amanda/debug/client/DailySet2/sendbackup.20070426040348.debug) === sendbackup: debug 1 pid 11419 ruid 8 euid 8: start at Thu Apr 26 04:03:48 2007 sendbackup: version 2.5.1p3 Reading conf file "/usr/local/etc/amanda/amanda-client.conf". Could not open conf file "/usr/local/etc/amanda/DailySet2/amanda-client.conf": No such file or directory sendbackup: debug 1 pid 11419 ruid 8 euid 8: rename at Thu Apr 26 04:03:48 2007 sendbackup req: parsed request as: program `GNUTAR' disk `/' device `/' level 0 since 1970:1:1:0:0:0 options `|;auth=ssh;index;exclude-file=*/*.log;exclude-file=*/messages;exclude-f ile=*/messages.?;exclude-file=*/socket*;exclud e-file=*gnutar-lists*;exclude-list=/usr/local/etc/amanda/exclude_from_ba ckups.txt;' sendbackup: start: lci-nms-pri.lci.com:/ lev 0 sendbackup-gnutar: time 0.033: doing level 0 dump as listed-incremental to '/usr/local/var/amanda/gnutar-lists/lci-nms-pri.lci.com__0.new' sendbackup-gnutar: time 0.035: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: time 0.043: spawning /usr/local/libexec/runtar in pipeline sendbackup: argument list: runtar DailySet2 gtar --create --file - --directory / --one-file-system --listed-incremental /usr/local/var/amanda/gnuta r-lists/lci-nms-pri.lci.com__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendbackup._.20070426040348.exclude . sendbackup: time 0.048: started index creator: "/usr/local/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" sendbackup-gnutar: time 0.048: /usr/local/libexec/runtar: pid 11422 sendbackup: time 0.049: started backup (notice no finish time) === (From Amanda 2.5.1p3 client /var/log/amanda/debug/amandad/amandad.20070426040348.debug) === amandad: debug 1 pid 11418 ruid 8 euid 8: start at Thu Apr 26 04:03:48 2007 security_getdriver(name=ssh) returns ff2d8700 amandad: version 2.5.1p3 amandad: build: VERSION="Amanda-2.5.1p3" amandad:BUILT_DATE="Wed Apr 11 12:17:37 EDT 2007" amandad:BUILT_MACH="SunOS arl-collect1 5.8 Generic_117350-46 sun4u sparc SUNW,Sun-Fire-V240" amandad:CC="/usr/local/bin/gcc" amandad:CONFIGURE_COMMAND="'./configure' '--with-user=amanda' '--with-group=backups' '--with-index-server=arl-fratm-backups.qintra.com' '-- with-tape-server=arl-fratm-backups.qintra.com' '--with-gnutar=/usr/local/bin/tar' '--with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists' '--wit h-assertions=yes' '--with-debugging=/var/log/amanda/debug' '--with-fqdn=yes' '--with-pid-debug-files=yes' '--without-built-manpages' '--with-ssh-se curity' '--with-gnu-ld=yes' '--without-termcap' '--without-ltermcap' '--without-LIBTERMCAP' '--with-ncurses=yes' '--with-lncurses=yes' '--with-LIBN CURSES=yes' '--without-server'" amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" amandad:AMANDA_TMP
"STRANGE" dump summaries
Hi, I'm running Amanda 2.5.1p3 with tar 1.16. As I understand, 2.5.1p3 ignores tar 1.16's return code of 1 when it encounters "file changed as we read it". I verified that my files are still backed up even when this happens. However, is it possible to get Amanda to stop reporting this as "STRANGE" in the amdump mail reports? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
estimating dump sizes
Hi, I'm running my amdumps with a wrapper script that basically says if the holding disk is 90% full, then run amflush before doing an amdump -o tapedev=/dev/null -o tpchanger="", else just run amdump -o tapedev=/dev/null -o tpchanger="". The goal was to fit as many dumps onto one tape as possible so that I don't waste tape space. This works pretty well, but what happens if my holding disk is 89% full and the next dump will put it over 100% full? I don't think amdump will automatically write to a tape because of the -o tapedev=/dev/null -o tpchanger="" options, right? Is there a way to estimate the size of the next dump so that I can decide if I need to run amflush before the next amdump? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: amrecover using invalid ssh options on Solaris?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Chris Hoogendyk
> Sent: Friday, April 06, 2007 1:28 PM
> To: AMANDA users
> Subject: amrecover using invalid ssh options on Solaris?
>
>
> My amanda 2.5.1p3 installation on Solaris 9 has been doing backups
> smoothly for several weeks using ssh authentication.
>
> I can also do amrecover on the backup server, where I have sizeable
> spool capacity, and then move files from there across the
> network using scp.
>
> However, in trying to configure ssh authentication and use
> amrecover on
> the clients, I get:
>
> pilot:/var/tmp# /usr/local/sbin/amrecover
>
> command-line: line 0: Bad configuration option:
> PreferredAuthentications
> AMRECOVER Version 2.5.1p3. Contacting server on
> mormyrid.bio.mor.nsm ...
> [request failed: error sending REQ: write error to : Broken pipe]
>
> A google search indicates that the first error line is an error from
> ssh. The man pages on Solaris 9 ssh have no indication of an option
> "PreferredAuthentications". Just for comparison, I ducked into an
> OpenBSD machine that I have and did a man page on ssh. There
> is has this
> option. It is OpenSSH_3.9 with OpenSSL 0.9.7d. If I ask for
> the version
> on Solaris 9 (which is based on OpenSSH), I get SSH Version
> Sun_SSH_1.0.1, protocol versions 1.5/2.0.
Chris,
Search for PreferredAuthentications in {amanda_source}/common-src/ssh-security.c
I don't know C, but maybe you can edit that and recompile? Or maybe the
authors only intended Amanda to be compatible with OpenSSH.
Ray
>
> So, it seems that amrecover is opening a connection with SSH and then
> trying to contact the amanda server on that connection and getting a
> broken pipe error because the SSH connection attempt failed.
>
> I have followed the instructions from
> http://wiki.zmanda.com/index.php/Configuring_SSH_authenticatio
> n, and I
> have set up the amanda_client.conf on the client with the lines:
>
> conf "daily"# your config name
>
> index_server "mormyrid.bio.mor.nsm" # your amindexd server
> tape_server "mormyrid.bio.mor.nsm" # your amidxtaped server
> tapedev "LIB-162A5"# your tape device
>
> # auth- authentication scheme to use between server and
> client.
> # Valid values are "bsd", "krb4", "krb5"
> and "ssh".
> # Default: [auth "bsd"]
> auth "ssh"
>
> ssh_keys "/.ssh/id_rsa_amrecover" #
> your ssh
> keys file if you use ssh auth
>
>
> So, is this an amanda bug? Is there a workaround or patch? Or have I
> done something wrong in my setup? If so, what should I be
> looking for? I
> don't want to have to run around to all my Solaris 9 servers
> and install
> and configure OpenSSH. Not only would it be a lot of work,
> but it would
> complicate my configurations. Sun SSH is working just fine in
> all other
> respects. Switching to OpenSSH would have a cascade effect. Sun built
> tcp-wrappers into their system configuration, as well as
> various other
> security items, and if I installed OpenSSH, I would also have
> to install
> tcp-wrappers and replicate all the security work on all of my servers.
>
> TIA
>
>
> ---
>
> Chris Hoogendyk
>
> -
>O__ Systems Administrator
> c/ /'_ --- Biology & Geology Departments
> (*) \(*) -- 140 Morrill Science Center
> ~~ - University of Massachusetts, Amherst
>
> <[EMAIL PROTECTED]>
>
> ---
>
> Erdös 4
>
>
>
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
RE: Loading tape during amrecover
> -Original Message- > From: Paul Bijnens [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 05, 2007 12:06 PM > To: Lee, Raymond > Cc: amanda-users@amanda.org > Subject: Re: Loading tape during amrecover > > > On 2007-04-05 17:06, Lee, Raymond wrote: > > Nevermind, I just RTFM'd :) > > > > From amanda.org: > > > > amrestore and amrecover do not yet include any tape changer support > > directly, as amrestore knows nothing about the amanda.conf files or > > server-side databases. This is a deliberate decision to > keep amrestore > > independent, so it can be run from any host with a tape > drive, even if > > the original tape server host is down. To use amrestore in a > > tape-changer environment, use amtape to find the right > tape, then run > > amrestore giving the resulting tape device name. > > That doc is a bit dated... There is also in amanda.conf: > > amrecover_changer string > Default: "". Amrecover will use the changer if you use 'settape > ' and that string is the same as the amrecover_changer > setting. > > So, in plain english, this means: invent a string (I use "changer") > that you give a to amrecover when it asks for the tapedev, and the > server (which does have access to the config file!) will interpret > it to use the changer that is configured in amanda.conf, instead of > a simple tapedev. > > > http://wiki.zmanda.com/index.php/Restoring_files#Using_amrecover > > Ah, I see. Thanks for setting me straight, Paul. It worked great. I guess I should be going to the wiki for any documentation. Thanks, Ray > > > > > > >> -Original Message- > >> From: Lee, Raymond > >> Sent: Thursday, April 05, 2007 10:54 AM > >> To: amanda-users@amanda.org > >> Subject: Loading tape during amrecover > >> > >> > >> Hi, > >> > >> I'm using a tape changer with Amanda. Is there a way to tell > >> it to automatically load the requested tape(s) when I'm > >> running amrecover on a client? Just trying to eliminate the > >> need to go to the server to run amtape to load the > requested tape(s). > >> > >> Thanks, > >> Ray > >> > > > > > > This communication is the property of Qwest and may contain > confidential or > > privileged information. Unauthorized use of this > communication is strictly > > prohibited and may be unlawful. If you have received this > communication > > in error, please immediately notify the sender by reply > e-mail and destroy > > all copies of the communication and any attachments. > > > > > > -- > Paul Bijnens, xplanation Technology ServicesTel +32 > 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 > 16 397.512 > http://www.xplanation.com/ email: > [EMAIL PROTECTED] > ** > * > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, > ^Q, ^^, * > * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, > bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, > hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, > shutdown, * > * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, > Stop-A, ... * > * ... "Are you sure?" ... YES ... Phew ... I'm out > * > ** > * > >
Loading tape during amrecover
Hi, I'm using a tape changer with Amanda. Is there a way to tell it to automatically load the requested tape(s) when I'm running amrecover on a client? Just trying to eliminate the need to go to the server to run amtape to load the requested tape(s). Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: Loading tape during amrecover
Nevermind, I just RTFM'd :) >From amanda.org: amrestore and amrecover do not yet include any tape changer support directly, as amrestore knows nothing about the amanda.conf files or server-side databases. This is a deliberate decision to keep amrestore independent, so it can be run from any host with a tape drive, even if the original tape server host is down. To use amrestore in a tape-changer environment, use amtape to find the right tape, then run amrestore giving the resulting tape device name. > -Original Message----- > From: Lee, Raymond > Sent: Thursday, April 05, 2007 10:54 AM > To: amanda-users@amanda.org > Subject: Loading tape during amrecover > > > Hi, > > I'm using a tape changer with Amanda. Is there a way to tell > it to automatically load the requested tape(s) when I'm > running amrecover on a client? Just trying to eliminate the > need to go to the server to run amtape to load the requested tape(s). > > Thanks, > Ray > This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
Solaris packaging
Hi, I compiled and installed the amanda client on one of my Solaris 10 server and used pkgmk to create a package of all the files installed. Is that package compatible with all the other versions of Solaris, or do I have to create a separate package for each Solaris version that I want to install the client on? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: Multiple tars in parallel?
> -Original Message-
> From: Roy Heimbach [mailto:[EMAIL PROTECTED]
> Sent: Thu 3/29/2007 5:48 PM
> To: Lee, Raymond
> Cc: amanda-users@amanda.org
> Subject: Re: Multiple tars in parallel?
>
> The "maxdumps" parameter in amanda.conf sets a global upper bound
> on the number of dumps that can run concurrently on any given client.
> From the amanda.conf man page:
>
>maxdumps int
>Default: 1. The maximum number of backups from a single
>host that AMANDA will attempt to run in parallel. See also
>the inparallel option.
Ah, thanks. When I first read this, I thought "maximum number of backups"
meant the number of instances of amdump running to backup all the disks on a
client. But I guess that doesn't make much sense :) It makes sense now. I'll
give it a shot.
Thanks,
Ray
>
>Note that this parameter may also be set in a specific dumptype
>(see below). This value sets the default for all dumptypes
>so must appear in amanda.conf before any dumptypes are defined.
>
> HTH,
> Roy
> --
> Roy Heimbach <[EMAIL PROTECTED]> / 505-277-8348
> User Services / Center for High Performance Computing
> University of New Mexico
>
> On Thu, 29 Mar 2007, Lee, Raymond wrote:
>> Hi,
>>
>> I've just started using Amanda 2.5.1p3 on Solaris with GNU tar as my
>> choice of program. Is it possible for the Amanda client to run multiple
>> tars in parallel to speed up the backup? The client that I'm currently
>> testing with has 11 filesystems that need to backed up. So in my
>> disklist file, I have something like this:
>>
>> host.abc.com / {
>> user-tar-span
>> estimate calcsize
>> }
>>
>> host.abc.com /export/home {
>> user-tar-span
>> estimate calcsize
>> }
>>
>> host.abc.com /opt {
>> user-tar-span
>> estimate calcsize
>> }
>> .
>> .
>> .
>> host.abc.com /filesystem11 {
>> user-tar-span
>> estimate calcsize
>> }
>>
>>
>> When I run amdump on the Amanda server, the client tars up one
>> filesystem at a time. I looked through many of the docs and man pages,
>> but I didn't see any parameter to specify parallel tars on the client.
>> Is it possible to do that?
>>
>> Thanks,
> Ray
>>
>>
>> This communication is the property of Qwest and may contain confidential or
>> privileged information. Unauthorized use of this communication is strictly
>> prohibited and may be unlawful. If you have received this communication
>> in error, please immediately notify the sender by reply e-mail and destroy
>> all copies of the communication and any attachments.
>>
>>
Multiple tars in parallel?
Hi,
I've just started using Amanda 2.5.1p3 on Solaris with GNU tar as my
choice of program. Is it possible for the Amanda client to run multiple
tars in parallel to speed up the backup? The client that I'm currently
testing with has 11 filesystems that need to backed up. So in my
disklist file, I have something like this:
host.abc.com / {
user-tar-span
estimate calcsize
}
host.abc.com /export/home {
user-tar-span
estimate calcsize
}
host.abc.com /opt {
user-tar-span
estimate calcsize
}
.
.
.
host.abc.com /filesystem11 {
user-tar-span
estimate calcsize
}
When I run amdump on the Amanda server, the client tars up one
filesystem at a time. I looked through many of the docs and man pages,
but I didn't see any parameter to specify parallel tars on the client.
Is it possible to do that?
Thanks,
Ray
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
RE: amflush during amdump
> > Will there be a conflict if I run amflush while an amdump > is running? > > > > I'll be running amdump like this so that I can accumulate enough > > multiple dumps in my holding disk before I amflush it to tape: > > > > amdump DailySet1 -o tapedev=/dev/null -o tpchanger="" > > (thanks to Jean-Louis for the taper options patch) > > > > > > Then I'll have a cron job that periodically checks the > amount of space > > used in the holding disk. If the size is close to the > capacity of one > > of my tapes, then amflush will run. > > > > So my question is, if amflush runs while amdump is running, > will it try > > to flush the dump that amdump is currently working on and cause any > > problems? > > > > It won't run, it will complain there is another process > already running. > What I would do is set autoflush=yes in amanda.conf, then > instead of running > a separate cron job just write a wrapper around your amdump > job. If the data > is less than your required level, call it with your -o > options, if it is > above, call as usual and it will flush everything (including > that run) to > tape. > > Matt > Ah, great idea. Thanks, Matt! > -- > Matt Hyclak > Department of Mathematics > Department of Social Work > Ohio University > (740) 593-1263 > This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
amflush during amdump
Hi List, Will there be a conflict if I run amflush while an amdump is running? I'll be running amdump like this so that I can accumulate enough multiple dumps in my holding disk before I amflush it to tape: amdump DailySet1 -o tapedev=/dev/null -o tpchanger="" (thanks to Jean-Louis for the taper options patch) Then I'll have a cron job that periodically checks the amount of space used in the holding disk. If the size is close to the capacity of one of my tapes, then amflush will run. So my question is, if amflush runs while amdump is running, will it try to flush the dump that amdump is currently working on and cause any problems? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: autoflush off, but still flushing to tape after amdump
> Could you start from > http://www.iro.umontreal.ca/~martinea/amanda/amanda-2.5.1p1-20 > 061020.tar.gz > and apply the attached patch. > The patch will send the -o options to taper/dumper and > chunker process. > changer will not get the options. > > run: amdump DailySet1 -o tapedev=/dev/null -o tpchanger="" > > The -o tpchanger="" is to disable the use of the changer. > > Let me know if it work. Jean-Louis, The patch worked just as it was supposed to. amflush also ran cleanly and deleted the directories from my holding disk. Thanks a bunch! Ray > > Jean-Louis > > Lee, Raymond wrote: > >> H, > >> > >> The -o flags are not sent to all subprocess. the taper > >> process never get > >> your tapedev overwrite. > >> I will try to make a patch available for that soon. > >> > >> Are you using a changer? It might need fix too. > >> > >> > > > > > > Hi Jean-Louis. Yes, I am using a tape changer. Here's an > excerpt from > > my amanda.conf. > > > > tpchanger "/usr/local/libexec/chg-zd-mtx" > > tapedev "/dev/rmt/0cbn" > > changerfile "/usr/local/etc/amanda/DailySet1/chg-zd-mtx" > > changerdev "/dev/scsi/changer/c2t0d0" > > > > > > Thanks, > > Ray > > > > > > > >> Jean-Louis > >> > >> Lee, Raymond wrote: > >> > >>> Thanks, Sven. That's exactly what I'd like to do. > >>> > >> However, when I do > >> > >>> "amdump DailySet1 -o tapedev=/dev/null" option and don't change > >>> "tapedev=/dev/rmt/0cbn" in amanda.conf, amdump is still > flushing to > >>> tape. If I change it in amanda.conf, then amdump won't > >>> > >> flush to tape. > >> > >>> But then I have to change it back to /dev/rmt/0cbn before I > >>> > >> run amflush. > >> > >>> I noticed that the configuration overwrite section of the > >>> > >> man page says > >> > >>> "Most commands allow any amanda.conf configuration parameter to be > >>> overridden on the command line with -o option." Is the > >>> > >> tapedev option > >> > >>> not able to be overwritten or do I have the syntax wrong? > >>> > >>> Also, after I run amflush, I still see empty directories on > >>> > >> my holding > >> > >>> disk. I have "usetimestamps yes" in amanda.conf, so the empty > >>> directories are named like "20061023123346". The email I > get after > >>> amflush finishes says: > >>> > >>> *** THE DUMPS DID NOT FINISH PROPERLY! > >>> > >>> The dumps were flushed to tape DailySet1-GCB709S1. > >>> The next tape Amanda expects to use is: a new tape. > >>> . > >>> . > >>> . > >>> . > >>> NOTES: > >>> taper: tape DailySet1-GCB709S1 kb 237632 fm 2 [OK] > >>> > >>> > > Is amflush supposed to delete that directory after flushing? Is > >>> > > that > > > >>> the reason why the email reported that the dump didn't > >>> > >> finish properly? > >> > >>> Thanks, > >>> Ray > >>> > >>> This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: autoflush off, but still flushing to tape after amdump
> H, > > The -o flags are not sent to all subprocess. the taper > process never get > your tapedev overwrite. > I will try to make a patch available for that soon. > > Are you using a changer? It might need fix too. > Hi Jean-Louis. Yes, I am using a tape changer. Here's an excerpt from my amanda.conf. tpchanger "/usr/local/libexec/chg-zd-mtx" tapedev "/dev/rmt/0cbn" changerfile "/usr/local/etc/amanda/DailySet1/chg-zd-mtx" changerdev "/dev/scsi/changer/c2t0d0" Thanks, Ray > Jean-Louis > > Lee, Raymond wrote: > > Thanks, Sven. That's exactly what I'd like to do. > However, when I do > > "amdump DailySet1 -o tapedev=/dev/null" option and don't change > > "tapedev=/dev/rmt/0cbn" in amanda.conf, amdump is still flushing to > > tape. If I change it in amanda.conf, then amdump won't > flush to tape. > > But then I have to change it back to /dev/rmt/0cbn before I > run amflush. > > > > I noticed that the configuration overwrite section of the > man page says > > "Most commands allow any amanda.conf configuration parameter to be > > overridden on the command line with -o option." Is the > tapedev option > > not able to be overwritten or do I have the syntax wrong? > > > > Also, after I run amflush, I still see empty directories on > my holding > > disk. I have "usetimestamps yes" in amanda.conf, so the empty > > directories are named like "20061023123346". The email I get after > > amflush finishes says: > > > > *** THE DUMPS DID NOT FINISH PROPERLY! > > > > The dumps were flushed to tape DailySet1-GCB709S1. > > The next tape Amanda expects to use is: a new tape. > > . > > . > > . > > . > > NOTES: > > taper: tape DailySet1-GCB709S1 kb 237632 fm 2 [OK] > > > > > Is amflush supposed to delete that directory after flushing? Is that > > the reason why the email reported that the dump didn't > finish properly? > > > > Thanks, > > Ray > > > > > > This communication is the property of Qwest and may contain > confidential or > > privileged information. Unauthorized use of this > communication is strictly > > prohibited and may be unlawful. If you have received this > communication > > in error, please immediately notify the sender by reply > e-mail and destroy > > all copies of the communication and any attachments. > > > > > >
RE: autoflush off, but still flushing to tape after amdump
> > Gene Heskett <[EMAIL PROTECTED]> writes: > > >>However, when I run an amdump that only backs up a 200MB of > data, I can > >>see the dumps being written to /dump/amanda, but then it's > be flushed to > >>tape automatically at the end of amdump. I also tried > "autoflush no" > >>and commenting the line out (default should be "off", > right?), but it > >>always flushes to tape after a dump. Any ideas? > > > Std procedure is to remove the tape until such time as > there is a tapefull > > in the holding disk. > > With Amanda 2.5.1 the best way might be to overwrite the tapedev > config variable with a non-existing device (even /dev/null should > work), like: > > amdump DailySet1 -o tapedev=/dev/null > > So the tape is unavailable when you run the (scheduled) amdump but it > is there when you do the flush. > > Sven Thanks, Sven. That's exactly what I'd like to do. However, when I do "amdump DailySet1 -o tapedev=/dev/null" option and don't change "tapedev=/dev/rmt/0cbn" in amanda.conf, amdump is still flushing to tape. If I change it in amanda.conf, then amdump won't flush to tape. But then I have to change it back to /dev/rmt/0cbn before I run amflush. I noticed that the configuration overwrite section of the man page says "Most commands allow any amanda.conf configuration parameter to be overridden on the command line with -o option." Is the tapedev option not able to be overwritten or do I have the syntax wrong? Also, after I run amflush, I still see empty directories on my holding disk. I have "usetimestamps yes" in amanda.conf, so the empty directories are named like "20061023123346". The email I get after amflush finishes says: *** THE DUMPS DID NOT FINISH PROPERLY! The dumps were flushed to tape DailySet1-GCB709S1. The next tape Amanda expects to use is: a new tape. . . . . NOTES: taper: tape DailySet1-GCB709S1 kb 237632 fm 2 [OK] Is amflush supposed to delete that directory after flushing? Is that the reason why the email reported that the dump didn't finish properly? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: autoflush off, but still flushing to tape after amdump
> > On Fri, Oct 20, 2006 at 11:14:20AM -0500, Lee, Raymond wrote: > > I know Amanda wasn't designed to write to a tape until it's > full, but I > > need to do that for now since I don't have enough tapes to keep the > > number of days of backups that I want. So as the FAQ suggested, I'd > > like to keep all the dumps on the holding disk and just run amflush > > whenever the holding disk gets enough data to fill one tape. > > > > I'm running 2.5.1p1 with the following in amanda.conf: > > > > autoflush off > > > ... > > > > However, when I run an amdump that only backs up a 200MB of > data, I can > > see the dumps being written to /dump/amanda, but then it's > be flushed to > > tape automatically at the end of amdump. I also tried > "autoflush no" > > and commenting the line out (default should be "off", > right?), but it > > always flushes to tape after a dump. Any ideas? > > > > You've misunderstood the autoflush directive. > It is not clearly described in the manpage. > > Writing to tape during an amdump is considered the norm. > There is no directive controlling taping or not taping > during a dump, that is not considered "flushing". > > The autoflush directive only affects whether the holding > disk is looked at for OLD, previously untaped, dumps. > They are then added or not to the list of things to > tape this run of amdump. > > To collect on the holding disk, don't insert at tape. > Thanks for the clarification, John. It makes sense now. Maybe a better description should be included in future releases? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: autoflush off, but still flushing to tape after amdump
I forgot to add that I have 447GB available for my holding disk.
-Ray
>
> I know Amanda wasn't designed to write to a tape until it's
> full, but I
> need to do that for now since I don't have enough tapes to keep the
> number of days of backups that I want. So as the FAQ suggested, I'd
> like to keep all the dumps on the holding disk and just run amflush
> whenever the holding disk gets enough data to fill one tape.
>
> I'm running 2.5.1p1 with the following in amanda.conf:
>
> autoflush off
>
> holdingdisk hd1 {
> comment "main holding disk"
> directory "/dumps/amanda"
> use 155 Gb
> chunksize 1Gb
> }
>
> define dumptype global {
> comment "Global definitions"
> index yes
> record yes
> auth "ssh"
> ssh_keys "/usr/local/var/amanda/.ssh/id_rsa_amdump"
> exclude list "/usr/local/etc/amanda/exclude_from_backups.txt"
> holdingdisk yes
> }
>
> However, when I run an amdump that only backs up a 200MB of
> data, I can
> see the dumps being written to /dump/amanda, but then it's be
> flushed to
> tape automatically at the end of amdump. I also tried "autoflush no"
> and commenting the line out (default should be "off", right?), but it
> always flushes to tape after a dump. Any ideas?
>
> Thanks,
> Ray
>
>
> This communication is the property of Qwest and may contain
> confidential or
> privileged information. Unauthorized use of this
> communication is strictly
> prohibited and may be unlawful. If you have received this
> communication
> in error, please immediately notify the sender by reply
> e-mail and destroy
> all copies of the communication and any attachments.
>
>
autoflush off, but still flushing to tape after amdump
I know Amanda wasn't designed to write to a tape until it's full, but I
need to do that for now since I don't have enough tapes to keep the
number of days of backups that I want. So as the FAQ suggested, I'd
like to keep all the dumps on the holding disk and just run amflush
whenever the holding disk gets enough data to fill one tape.
I'm running 2.5.1p1 with the following in amanda.conf:
autoflush off
holdingdisk hd1 {
comment "main holding disk"
directory "/dumps/amanda"
use 155 Gb
chunksize 1Gb
}
define dumptype global {
comment "Global definitions"
index yes
record yes
auth "ssh"
ssh_keys "/usr/local/var/amanda/.ssh/id_rsa_amdump"
exclude list "/usr/local/etc/amanda/exclude_from_backups.txt"
holdingdisk yes
}
However, when I run an amdump that only backs up a 200MB of data, I can
see the dumps being written to /dump/amanda, but then it's be flushed to
tape automatically at the end of amdump. I also tried "autoflush no"
and commenting the line out (default should be "off", right?), but it
always flushes to tape after a dump. Any ideas?
Thanks,
Ray
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
RE: amrecover question.
Sometimes the files you're recovering are on a tape that's no longer in the changer, so you must manually insert it into the changer and mount it to a drive before telling amrecover to continue. I think it would be nice if Amanda could mount the tape automatically without asking you, if it knows that the required tape is already in the changer. Can it already do this, or will it be a feature in a future release? Ray -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of McGraw, Robert P. Sent: Tuesday, September 26, 2006 2:55 PM To: amanda-users@amanda.org Subject: amrecover question. I am running amanda-2.5.1 on a Sparc Solaris 10 When I run amrecover and do the extract, it tells me what tape needs to be mounted. I then have to go to another window and run amtape to mount the tape. Since it knows what tape to mount, what is the reason to go to another window to run amtape to mount the tape? Am I not doing it correctly? Am I missing something? Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: amanda over ssh
Steve, I had to go through this a few times to get it right myself. The howto-auth.txt was correct, but I thought some of it was a little confusing regarding what goes where on the server and what goes where on the client. Here's what I did (change the /path/to/amanda/home, /usr/local/libexec/amandad, /path/to/config/dir, user names, and hostnames to match your environment): ON THE AMANDA SERVER: 1. As the amanda user: ssh-keygen -t rsa -N "" -f /path/to/amanda/home/.ssh/id_rsa_amdump 2. Add the following to /path/to/config/dir/amanda.conf (I added it to the "global" dumptype) auth "ssh" ssh_keys "/path/to/amanda/home/.ssh/id_rsa_amdump" 3. As the amanda user, ssh [EMAIL PROTECTED] to add the host key to /path/to/amanda/home/.ssh/known_hosts (This part was key for me since I cofigured amanda --with-fqdn=yes. I had the client's hostname without the fqdn in my known_hosts before this, and amcheck was failing.) ON THE AMANDA CLIENT: 1. As root: ssh-keygen -t rsa -N "" -f /.ssh/id_rsa_amrecover 2. Append /.ssh/id_rsa_amrecover.pub from the Amanda client to /path/to/amanda/home/.ssh/authorized_keys on the Amanda server and prepend each line with: from="client.fqdn.com",no-port-forwarding,no-X11-forwarding,no-agent-for warding,command="/usr/local/libexec/amandad -auth=ssh amindexd amidxtaped" 3. Append /path/to/amanda/home/.ssh/id_rsa_amdump.pub from the Amanda server to /path/to/amanda/home/.ssh/authorized_keys on the Amanda client and prepend each line with: from="amanda_server.fqdn.com",no-port-forwarding,no-X11-forwarding,no-ag ent-forwarding,command="/usr/local/libexec/amandad -auth=ssh amdump" 4. Add this to /path/to/config/dir/amanda-client.conf on the client auth "ssh" ssh_keys "/.ssh/id_rsa_amrecover" 5. As root on the client, ssh [EMAIL PROTECTED] to add the host key to /.ssh/known_hosts Here's what your directories and files should look like (be careful of the linebreaks that your email program might add): SERVER: ([EMAIL PROTECTED])$ ls /path/to/amanda/home/.ssh authorized_keysid_rsa_amdump id_rsa_amdump.pub known_hosts ([EMAIL PROTECTED])$ cat /path/to/amanda/home/.ssh/authorized_keys # # Amanda server's amdump ssh key from ~amanda/.ssh/id_rsa_amdump.pub # from="amanda_server.fqdn.com",no-port-forwarding,no-X11-forwarding,no-ag ent-forwarding,command="/usr/local/libexec/amandad -auth=ssh amdump" ssh-rsa BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHB [EMAIL PROTECTED] # # Amanda clients' amrecover ssh keys from /.ssh/id_rsa_amrecover.pub # from="client1.fqdn.com",no-port-forwarding,no-X11-forwarding,no-agent-fo rwarding,command="/usr/local/libexec/amandad -auth=ssh amindexd amidxtaped" ssh-rsa BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHB [EMAIL PROTECTED] from="client2.fqdn.com",no-port-forwarding,no-X11-forwarding,no-agent-fo rwarding,command="/usr/local/libexec/amandad -auth=ssh amindexd amidxtaped" ssh-rsa BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHB [EMAIL PROTECTED] ([EMAIL PROTECTED])$ cat /path/to/amanda/home/.ssh/known_hosts amanda_server.fqdn.com,10.1.2.3 ssh-rsa BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAH amanda_client.fqdn.com,10.4.5.6 ssh-rsa BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAH CLIENT: ([EMAIL PROTECTED])$ ls /.ssh id_rsa_amrecoverid_rsa_amrecover.pub known_hosts ([EMAIL PROTECTED])$ cat known_hosts amanda_server.fqdn.com,10.1.2.3 ssh-rsa BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAH ([EMAIL PROTECTED])$ ls /path/to/amanda/home/.ssh authorized_keys ([EMAIL PROTECTED])$ cat /path/to/amanda/home/.ssh/authorized_keys from="amanda_server.fqdn.com",no-port-forwarding,no-X11-forwarding,no-ag ent-forwarding,command="/usr/local/libexec/amandad -auth=ssh amdump" ssh-rsa BLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAHBLAH [EMAIL PROTECTED] Hope this helps. Ray -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Newcomb Sent: Wednesday, September 20, 2006 12:23 PM To: amanda-users@amanda.org Subject: amanda over ssh We've been using Amanda continuously since 1999. Amanda has minimized our backup effort and headaches and it has saved us from serious data losses on several occasions. Brava! I was delighted to see that 2.5.1 now supports ssh, and if I could just get it to work, it would be a godsend to us. I have done everything that docs/howto-auth.txt specifies for the use of SSH. Unfortunately, the best result I can get from amcheck is: Amanda Backup Client Hosts Check WARNING: manche.coolheads.com: selfcheck request failed: EOF on read from manche.coolheads.com Client check: 1 host checked in 0.299 seconds, 1 problem found (brought to you by Amanda 2.5.1) So I think I'm connecting to the client OK, because it responds promptly. And, if I delete the auth "ssh" line from my dumptype, the response, after a 30-second delay, is: Amanda Backup Client Hosts Check -
RE: amanda 2.5.1 on Solaris 9
Thanks, Jon. That did the trick. I already had ncurses installed, but running configure --without-termcap, etc. still tried to use termcap. So I uninstalled termcap and ran configure again. The make install ran clean this time. amrecover is working fine, so I guess it's all good. Thanks, Ray -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie Sent: Wednesday, September 13, 2006 11:24 AM To: amanda-users@amanda.org Subject: Re: amanda 2.5.1 on Solaris 9 On Wed, Sep 13, 2006 at 09:29:38AM -0500, Lee, Raymond wrote: > P.S., I did a "make uninstall" and "make distclean" on the 2.5.0p2 > version before trying to install 2.5.1. > > Thanks, > Ray > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Lee, Raymond > Sent: Wednesday, September 13, 2006 10:15 AM > To: amanda-users@amanda.org > Subject: amanda 2.5.1 on Solaris 9 > > > Hi, > > I'm having trouble getting the amanda 2.5.1 server installed on Solaris > 9. It always gets hung during "make install" when it gets to > restore-src. The client-only install works fine. I tried the server > install on a couple of different Solaris 9 boxes with the same error. > 2.5.0p2 installed just fine on the same box before this. Here's what I > have: > > ./configure \ > --with-user=amanda \ > --with-group=backups \ > --with-index-server=amanda-server \ > --with-tape-server=amanda-server \ > --with-tape-device=/dev/rmt/0cbn \ > --with-changer-device=/dev/scsi/changer/c2t0d0 \ > --with-gnutar=/usr/local/bin/tar \ > --with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists \ > --with-assertions=yes \ > --with-debugging=/var/log/amanda/debug \ > --with-fqdn=yes \ > --with-pid-debug-files=yes \ > --without-built-manpages \ > --with-ssh-security > > > gcc -shared -Wl,-h -Wl,librestore-2.5.1.so -o .libs/librestore-2.5.1.so > .libs/restore.o -R/usr/local/lib -L/usr/local/lib -lamanda -lamtape > -lamserver -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lresolv -lintl > -lc > Text relocation remains referenced > against symbol offset in file >0xa24 > /usr/local/lib/libtermcap.a(tparam.o) > . Libtermcap has always seems to be a problem with Solaris. I eliminate it and use ncurses instead. Try adding these to your configure line: --without-termcap \ --without-ltermcap \ --without-LIBTERMCAP \ --with-ncurses=yes \ --with-lncurses=yes \ --with-LIBNCURSES=yes \ This assumes you have a libncurses available. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: amanda 2.5.1 on Solaris 9
P.S., I did a "make uninstall" and "make distclean" on the 2.5.0p2 version before trying to install 2.5.1. Thanks, Ray -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lee, Raymond Sent: Wednesday, September 13, 2006 10:15 AM To: amanda-users@amanda.org Subject: amanda 2.5.1 on Solaris 9 Hi, I'm having trouble getting the amanda 2.5.1 server installed on Solaris 9. It always gets hung during "make install" when it gets to restore-src. The client-only install works fine. I tried the server install on a couple of different Solaris 9 boxes with the same error. 2.5.0p2 installed just fine on the same box before this. Here's what I have: ./configure \ --with-user=amanda \ --with-group=backups \ --with-index-server=amanda-server \ --with-tape-server=amanda-server \ --with-tape-device=/dev/rmt/0cbn \ --with-changer-device=/dev/scsi/changer/c2t0d0 \ --with-gnutar=/usr/local/bin/tar \ --with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists \ --with-assertions=yes \ --with-debugging=/var/log/amanda/debug \ --with-fqdn=yes \ --with-pid-debug-files=yes \ --without-built-manpages \ --with-ssh-security ...and here's the error during the make install: Making install in restore-src /usr/local/tars/amanda-2.5.1/restore-src make[1]: Entering directory `/usr/local/tars/amanda-2.5.1/restore-src' make[2]: Entering directory `/usr/local/tars/amanda-2.5.1/restore-src' test -z "/usr/local/lib" || /bin/bash ../config/mkinstalldirs "/usr/local/lib" /bin/bash ../libtool --mode=install /usr/ucb/install 'librestore.la' '/usr/local/lib/librestore.la' libtool: install: warning: relinking `librestore.la' (cd /usr/local/tars/amanda-2.5.1/restore-src; /bin/bash ../libtool --tag=CC --mode=relink gcc -Wall -Wextra -Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare -Wfloat-equal -Wold-style-definition -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -o librestore.la -rpath /usr/local/lib -release 2.5.1 restore.lo ../common-src/libamanda.la ../tape-src/libamtape.la ../server-src/libamserver.la -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lresolv -lintl ) gcc -shared -Wl,-h -Wl,librestore-2.5.1.so -o .libs/librestore-2.5.1.so .libs/restore.o -R/usr/local/lib -L/usr/local/lib -lamanda -lamtape -lamserver -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lresolv -lintl -lc Text relocation remains referenced against symbol offset in file 0xa24 /usr/local/lib/libtermcap.a(tparam.o) 0xa28 /usr/local/lib/libtermcap.a(tparam.o) 0xa2c /usr/local/lib/libtermcap.a(tparam.o) . . . etc. . . . ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status libtool: install: error: relink `librestore.la' with the above command before in stalling it make[2]: *** [install-libLTLIBRARIES] Error 1 make[2]: Leaving directory `/usr/local/tars/amanda-2.5.1/restore-src' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/usr/local/tars/amanda-2.5.1/restore-src' make: *** [install-recursive] Error 1 I've tried GNU make and GNU ld as well...same error. Anyone else have the same problem? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
amanda 2.5.1 on Solaris 9
Hi, I'm having trouble getting the amanda 2.5.1 server installed on Solaris 9. It always gets hung during "make install" when it gets to restore-src. The client-only install works fine. I tried the server install on a couple of different Solaris 9 boxes with the same error. 2.5.0p2 installed just fine on the same box before this. Here's what I have: ./configure \ --with-user=amanda \ --with-group=backups \ --with-index-server=amanda-server \ --with-tape-server=amanda-server \ --with-tape-device=/dev/rmt/0cbn \ --with-changer-device=/dev/scsi/changer/c2t0d0 \ --with-gnutar=/usr/local/bin/tar \ --with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists \ --with-assertions=yes \ --with-debugging=/var/log/amanda/debug \ --with-fqdn=yes \ --with-pid-debug-files=yes \ --without-built-manpages \ --with-ssh-security ...and here's the error during the make install: Making install in restore-src /usr/local/tars/amanda-2.5.1/restore-src make[1]: Entering directory `/usr/local/tars/amanda-2.5.1/restore-src' make[2]: Entering directory `/usr/local/tars/amanda-2.5.1/restore-src' test -z "/usr/local/lib" || /bin/bash ../config/mkinstalldirs "/usr/local/lib" /bin/bash ../libtool --mode=install /usr/ucb/install 'librestore.la' '/usr/local/lib/librestore.la' libtool: install: warning: relinking `librestore.la' (cd /usr/local/tars/amanda-2.5.1/restore-src; /bin/bash ../libtool --tag=CC --mode=relink gcc -Wall -Wextra -Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wsign-compare -Wfloat-equal -Wold-style-definition -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -o librestore.la -rpath /usr/local/lib -release 2.5.1 restore.lo ../common-src/libamanda.la ../tape-src/libamtape.la ../server-src/libamserver.la -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lresolv -lintl ) gcc -shared -Wl,-h -Wl,librestore-2.5.1.so -o .libs/librestore-2.5.1.so .libs/restore.o -R/usr/local/lib -L/usr/local/lib -lamanda -lamtape -lamserver -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lresolv -lintl -lc Text relocation remains referenced against symbol offset in file 0xa24 /usr/local/lib/libtermcap.a(tparam.o) 0xa28 /usr/local/lib/libtermcap.a(tparam.o) 0xa2c /usr/local/lib/libtermcap.a(tparam.o) . . . etc. . . . ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status libtool: install: error: relink `librestore.la' with the above command before in stalling it make[2]: *** [install-libLTLIBRARIES] Error 1 make[2]: Leaving directory `/usr/local/tars/amanda-2.5.1/restore-src' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/usr/local/tars/amanda-2.5.1/restore-src' make: *** [install-recursive] Error 1 I've tried GNU make and GNU ld as well...same error. Anyone else have the same problem? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
