MacOSX_CompileError
--Client-only compile went OK but wasn't able to get things going from the host so I thought a complete compile would give me a system I could debug before working on host connection stuff. But the full compile fails with /bin/sh ../libtool --mode=link cc -g -O2-o amindexd amindexd.o disk_history.o list_dir.o ../common-src/libamanda.la libamserver.la ../tape-src/libamtape.la../common-src/libamanda.la -lm -lreadline -lcurses cc -g -O2 -o amindexd amindexd.o disk_history.o list_dir.o ../common-src/.libs/libamanda.a -lm -lreadline -lcurses .libs/libamserver.a -lm -lreadline -lcurses ../tape-src/.libs/libamtape.a -lm -lreadline -lcurses ../common-src/.libs/libamanda.a -lm -lreadline -lcurses -lm -lreadline -lcurses /usr/bin/ld: Undefined symbols: _start_time make[1]: *** [amindexd] Error 1 make: *** [all-recursive] Error 1 And the build --without-libtools gives the same error Help/direction would be appreciated thanks
No Subject
unsubscribe
unsubscribe
HP changer and BSD/OS 4.2
On Sat, Aug 11, 2001 at 01:06:31PM -0700, Michael Hall wrote:
We got the HP 24x6i DAT changer I had asked about and finally got a chance
to start playing with it. We're running BSD/OS 4.2 and I grabbed the
latest tarball (2.4.2p2) and having been making much headway. Got it
compiled, installed and setup the chg-scsi.conf only to get errors that
it couldn't run chg-scsi, and sure enough after looking at it chg-scsi
didn't even get built :-( There is no chio, mtx, etc. available under
BSD/OS 4.2, I grabbed mtx-1.2.13 (sourceforge) and it didn't even begin
to compile before bombing out, so it looks like chg-{chio,mtx} are out.
Not familiar with changers myself, this is the first, but what are the
options for getting this thing running with amanda and BSD/OS 4.2?
Anybody else here have this combo or something similar working?
Thanks.
--
Women are like programs. A smart man keeps a backup.
Mike Hall,
Unix Admin - Rock Island Communications <[EMAIL PROTECTED]>
System Admin - riverside.org<[EMAIL PROTECTED]>
Client Installationn on Solaris
I think I have stuffed up the installation of a client version of amanda on a sun sparc running solaris 2.5. The configure command I issued was ./configure --without server --with-user=amanda --with-group=sys. Somehow I get the feeling this is incomplete. Can someone please verify that this is right or is there something I missed out when I issued that command. Thanks Chandra
Re: level 0 dumps getting overwritten?
At 04:01 PM 8/28/2001, Kurt Yoder wrote: >Hello >My level 0 dumps seem to be getting overwritten. I run amadmin and see >only level 1 dumps: >[...] >Am I setting up my configuration file correctly? I've got: > >dumpcycle 7 days >runspercycle 6 >tapecycle 2 tapes So you're telling Amanda to make sure she has a full (level 0) backup of everything at least every 7 days, spread into 6 runs. But you're only giving her 2 tapes! *Buy more tapes!* Really. >I've got a third tape in my tapelist so I can flush dumps from my >holding disk. I'm trying to do 6 backups every 7 days (the 7th day has a >weekly backup set that isn't part of this configuration) using two tapes >(alternate between them). If you absolutely have to stick with two tapes, you pretty much need to do full dumps every run to be safe. (Take for instance the case where tape1 has level0's, tape2 has level1's, you go to do level0's on tape1 again and there's an error and the tape is fubar'd. You've just lost all hope of a restore.) Use 'dumpcycle 0' in the dumptype to force level 0's. >I must be setting up my "numbers" wrong, or? Or you need more tapes! >Thanks! >-Kurt Darin Dugan System Support Specialist Iowa State University Extension [EMAIL PROTECTED] http://www.extension.iastate.edu
RE: Still a newbie...but getting somewhere...amlabel troubles
I'm not sure why this posted again...sorry everyone...I've already had some responses I'm going to look into tomorrow. :) -Original Message- From: Rebecca Pakish [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 2:46 PM To: '[EMAIL PROTECTED]' Subject: Still a newbie...but getting somewhere...amlabel troubles Hi all... Thank you for all of your help on the ./tapetype issue. I learned a lot about my drive from the Seagate site (they have excellent documentation as far as I'm concerned) got my hardware compression turned off. Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) In amanda.conf: labelstr "^testtape[0-9][0-9]" (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c "amlabel backup testtape01" bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied And then I looked for the file called "tapelist" that the amlabel man page said it would write to, and I couldn't find it to change it's permissions. When I went back to re-execute the amlabel command so I could write down the error, this is what happens: $su amanda -c "amlabel backup testtape01" bash: /root.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking labelamlabel: couldn't write tapelist: Permission denied Which, I have to admit, for a girl who just learned how to tar on Friday and rpm yesterday, I'm pretty jacked to see that it read the label as testtape01 that second time! But of course, it still isn't right. oops. Can someone please help point me in the right direction? Thanks!! Rebecca
level 0 dumps getting overwritten?
Hello My level 0 dumps seem to be getting overwritten. I run amadmin and see only level 1 dumps: Dunedin# amadmin DailySet1 find dunedin Scanning /usr/local/amanda/holdingdisk... date host disklv tape or file file status 2001-08-25 dunedin.shcorp.com /dev/da0s1f 1 DS1tape01d 2 OK 2001-08-26 dunedin.shcorp.com /dev/da0s1f 1 DS1tape03 1 OK 2001-08-27 dunedin.shcorp.com /dev/da0s1f 1 DS1tape03 3 OK 2001-08-28 dunedin.shcorp.com /dev/da0s1f 1 DS1tape02 2 OK Am I setting up my configuration file correctly? I've got: dumpcycle 7 days runspercycle 6 tapecycle 2 tapes I've got a third tape in my tapelist so I can flush dumps from my holding disk. I'm trying to do 6 backups every 7 days (the 7th day has a weekly backup set that isn't part of this configuration) using two tapes (alternate between them). I must be setting up my "numbers" wrong, or? Thanks! -Kurt
Re: Still a newbie...but getting somewhere...amlabel troubles
On Tue, 28 Aug 2001 at 2:46pm, Rebecca Pakish wrote > Been working on the amanda.conf file, feel like I'm prepared to label my > first tape and dump something! Again, running RH 7.1 on a Dell 333 with a > SCSI Seagate external and just a 90mm tape for starters. (Had to download > the mt command from the rpm site, but everything seems to be effectively > communicating) Did you compile amanda or install the RPM? > In amanda.conf: > labelstr "^testtape[0-9][0-9]" > (**amanda.conf is in /usr/local/etc/amanda/backup**) > > What's happening... > $su amanda -c "amlabel backup testtape01" > bash: /root/.bashrc: Permission denied This says that the $HOME of the user amanda specified in /etc/passwd is /root, but the amanda user does not have read access to that directory. I would fix this by giving amanda a different $HOME (like /home/amanda). > rewinding, reading label, not an amanda tape > rewinding, writing label testape01, checking labelamlabel: couldn't write > tapelist: Permission denied The file 'tapelist' is created after the first successful amlabel, which is why you don't have one yet. It lives in the same directory as the amanda.conf and disklist for the configuration -- in this case /usr/local/etc/amanda/backup. So, amanda must not have write permissions in that directory. The easiest way to fix that would be 'chown -R amanda /usr/local/etc/amanda', which will give the user amanda ownership of /usr/local/etc/amanda and all the files and directories inside it. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Still a newbie...but getting somewhere...amlabel troubles
In the same directory as amanda.conf, try this: su -c amanda "touch tapetype" This will create a blank tapetype file that amanda can store info about tapes in. > -Original Message- > From: Rebecca Pakish [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 28, 2001 3:46 PM > To: '[EMAIL PROTECTED]' > Subject: Still a newbie...but getting somewhere...amlabel troubles > > > Hi all... > > Thank you for all of your help on the ./tapetype issue. I > learned a lot > about my drive from the Seagate site (they have excellent > documentation as > far as I'm concerned) got my hardware compression turned off. > > Been working on the amanda.conf file, feel like I'm prepared > to label my > first tape and dump something! Again, running RH 7.1 on a > Dell 333 with a > SCSI Seagate external and just a 90mm tape for starters. (Had > to download > the mt command from the rpm site, but everything seems to be > effectively > communicating) > > In amanda.conf: > labelstr "^testtape[0-9][0-9]" > (**amanda.conf is in /usr/local/etc/amanda/backup**) > > What's happening... > $su amanda -c "amlabel backup testtape01" > bash: /root/.bashrc: Permission denied > rewinding, reading label, not an amanda tape > rewinding, writing label testape01, checking labelamlabel: > couldn't write > tapelist: Permission denied > > And then I looked for the file called "tapelist" that the > amlabel man page > said it would write to, and I couldn't find it to change it's > permissions. > When I went back to re-execute the amlabel command so I could > write down the > error, this is what happens: > $su amanda -c "amlabel backup testtape01" > bash: /root.bashrc: Permission denied > rewinding, reading label testtape01 > rewinding, writing label testtape01, checking labelamlabel: > couldn't write > tapelist: Permission denied > > Which, I have to admit, for a girl who just learned how to > tar on Friday and > rpm yesterday, I'm pretty jacked to see that it read the > label as testtape01 > that second time! But of course, it still isn't right. oops. > > Can someone please help point me in the right direction? > Thanks!! > Rebecca > > >
Re: small changer problem yet
Hi, On Mon, Aug 27, 2001 at 11:49:51AM -0400, Gene Heskett wrote: > > I've about got amanda working with a Compaq/Seagate 4586 now, but one > thing I need to clarify. > > When I issue as user amanda, "amverify config 2" it should proceed to > do a verify run on slot 2's contents, or at least thats how I > understand it. > > What it does, even if slot 2 is loaded with the correct tape, is to > give an error from amtape indicating it can't load or read the tape. > It then proceeds to look at slot 3, see's a labeled but otherwise blank > tape there, then goes back to slot 1, does a full verify on that tape, > then reloads slot 2 and does a verify on that tape, which is what it > should have done in the first place. Is this a bug, or am I not > issueing the correct command syntax? > > Inquiring minds want to know. if you use chg-scsi it's a bug, and i'm working on a fix Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
Re: how do you test for a bad tape...?
John W. Price <[EMAIL PROTECTED]> wrote: > I'm sure this is something I should probably already know, aside from > being mildly off-topic, but is there a way to test a tape for quality > *before* you put a backup on it? I just had a brand new tape come back The built-in SCSI chg driver tests for soft error counters. Alternatively, if using the DISASTER_RECOVERY floppy I gave the URL recently in amanda.hackers you will be able to read the error counters and exercise the tape.
Still a newbie...but getting somewhere...amlabel troubles
Hi all... Thank you for all of your help on the ./tapetype issue. I learned a lot about my drive from the Seagate site (they have excellent documentation as far as I'm concerned) got my hardware compression turned off. Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) In amanda.conf: labelstr "^testtape[0-9][0-9]" (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c "amlabel backup testtape01" bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied And then I looked for the file called "tapelist" that the amlabel man page said it would write to, and I couldn't find it to change it's permissions. When I went back to re-execute the amlabel command so I could write down the error, this is what happens: $su amanda -c "amlabel backup testtape01" bash: /root.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking labelamlabel: couldn't write tapelist: Permission denied Which, I have to admit, for a girl who just learned how to tar on Friday and rpm yesterday, I'm pretty jacked to see that it read the label as testtape01 that second time! But of course, it still isn't right. oops. Can someone please help point me in the right direction? Thanks!! Rebecca
how do you test for a bad tape...?
Hi all: I'm sure this is something I should probably already know, aside from being mildly off-topic, but is there a way to test a tape for quality *before* you put a backup on it? I just had a brand new tape come back with i/o errors while trying to restore a backup (this after I had just started using amanda -- it was really fun trying to figure out whether the culprit was amanda, the restoration procedure, or the tape). John -- John Price *** ** ** *** [EMAIL PROTECTED] Where there is no solution, there is no problem. -- John G. Price (my father), ca. 1975. begin:vcard n:Price;John tel;fax:310-206-4397 tel;work:310-206-4943 x-mozilla-html:FALSE org:UCLA;Physics and Astronomy version:2.1 email;internet:[EMAIL PROTECTED] adr;quoted-printable:;;UCLA=0D=0ADepartment of Physics and Astronomy=0D=0A405 Hilgard Ave.;Los Angeles;CA;90095-1547; x-mozilla-cpt:;12384 fn:John Price end:vcard
Reading Indices
I didn't catch any answers to this the first time, but I may have missed it -- so I'm resending. -- Lorrie - Forwarded message from Lorrie Wood <[EMAIL PROTECTED]> - Date: Thu, 23 Aug 2001 16:40:24 -0700 From: Lorrie Wood <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Reading Indices User-Agent: Mutt/1.2.5i I have a fairly simple Amanda setup: Amanda: 2.4.2 Server OS: Red Hat 6.1 Client OS: Solaris 2.6 GNU tar: 1.13.11 (Linux) / 1.13 (Solaris) The index files work great... for the past three days. history from amrecover shows: amrecover> history 200- Dump history for config "bertha-us" host "us" disk "/export/home/us0" 201- 2001-08-23 4 DailySet155 3 201- 2001-08-22 4 DailySet154 3 201- 2001-08-21 4 DailySet153 3 ... only I have indices from much further back: [root@bertha _export_home_us0]# pwd /var/log/amanda/DailySet1/index/us/_export_home_us0 [root@bertha _export_home_us0]# ls 20010630_0.gz 20010712_3.gz 20010725_3.gz 20010807_3.gz 20010818_4.gz 20010630_3.gz 20010713_3.gz 20010726_3.gz 20010808_3.gz 20010821_4.gz 20010703_1.gz 20010714_3.gz 20010727_3.gz 20010809_3.gz 20010822_4.gz 20010704_2.gz 20010717_3.gz 20010728_0.gz 20010810_3.gz 20010823_4.gz 20010705_3.gz 20010718_3.gz 20010731_1.gz 20010811_3.gz 20010706_3.gz 20010719_3.gz 20010801_2.gz 20010814_3.gz 20010707_3.gz 20010720_3.gz 20010802_2.gz 20010815_3.gz 20010710_3.gz 20010721_3.gz 20010803_2.gz 20010816_4.gz 20010711_3.gz 20010724_3.gz 20010804_3.gz 20010817_4.gz ... and logs, too! [root@bertha DailySet1]# ls log* log.20010726.0 log.20010804.0 log.20010813.0 log.20010815.0 log.20010817.5 log.20010727.0 log.20010807.0 log.20010813.1 log.20010816.0 log.20010817.6 log.20010728.0 log.20010807.1 log.20010813.2 log.20010817.0 log.20010818.0 log.20010731.0 log.20010808.0 log.20010813.3 log.20010817.1 log.20010821.0 log.20010801.0 log.20010809.0 log.20010814.0 log.20010817.2 log.20010821.1 log.20010802.0 log.20010810.0 log.20010814.1 log.20010817.3 log.20010822.0 log.20010803.0 log.20010811.0 log.20010814.2 log.20010817.4 log.20010823.0 How can I access the index data from those older dates? I need to pull something off the 7 August tape, but trying that only gets me: amrecover> setdate ---07 200 Working date set to 2001-08-07. No index records for cwd on new date Setting cwd to mount point amrecover> No, the index files aren't corrupt, I already checked. Here's the head of last nights... [root@bertha _export_home_us0]# head 20010823_4 / /users/ /users/audio/ /users/audio/.cshrc So what's up with this? Thanks in advance! -- Lorrie - End forwarded message -
Re: AmandaOnMacOSX
Hi, "ThomasRatliffDDS" wrote: > Anyone have amanda running on MacOSX? There was some discussion of this back in May and then again in June. At that time, there was no "restore" program available from MacOS X (but "dump" did exist!?), and GNU tar was horrendously slow. Perhaps 10.1 remedies one or more of those problems, but I haven't seen any reports yet. Here's a URL to the archive search: http://groups.yahoo.com/group/amanda-users/messagesearch?query=MacOS%20X If you manage to get it working, please let us know! -Ben -- Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
AmandaOnMacOSX
Anyone have amanda running on MacOSX?
Re: Overland DLT LoaderXpress LXL1B10
On Tue, 28 Aug 2001, Karl, Matthew wrote: > Amanda-users, > > We have an Overland DLT LoaderXpress LXL1B10, and Amanda (latest) is running > on Solaris 7. We are unable to get Amanda to work the autoloader. I have > just recently started in this area, so please pardon my ignorance as I do > not know exactly what to ask. If anyone has any suggestions they would be > greatly appreciated. Thanks in advance for your time and assistance. > > > Regards, > > Matthew > > > Hi I m planning to use the same config than u except the fact that my server will be on solaris 8. But i would like to know if it works before buying the autoloader I had some contact with overland people and one told me that this changer work well with linux and mtx i guess then you should begin by trying to make mtx work on your solaris machine with your autoloader You can get it at the following url http://mtx.sourceforge.net/ That s the first step -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: Overland DLT LoaderXpress LXL1B10
On Tue, 28 Aug 2001, Karl, Matthew wrote: > We have an Overland DLT LoaderXpress LXL1B10, and Amanda (latest) is running > on Solaris 7. We are unable to get Amanda to work the autoloader. I have > just recently started in this area, so please pardon my ignorance as I do > not know exactly what to ask. If anyone has any suggestions they would be > greatly appreciated. Thanks in advance for your time and assistance. Step 1: Read docs/TAPE.CHANGERS Step 2: Choose a changer control program and an amanda changer script and configure amanda.conf to use them. Step 3: Test with amtape commands Step 4: Make any necessary changes, repeat 3 and 4 until happy. At any point where you're out of ideas, write back to amanda-users with a description of what you have, what's working and what isn't. Include as much documentation in the form of config info and error messages as you can and someone will most likely nudge you in the right direction. Typically it does take some effort to get through this part, but having amanda run everything for you on autopilot is really worth it, IMHO. -Mitch
Overland DLT LoaderXpress LXL1B10
Amanda-users, We have an Overland DLT LoaderXpress LXL1B10, and Amanda (latest) is running on Solaris 7. We are unable to get Amanda to work the autoloader. I have just recently started in this area, so please pardon my ignorance as I do not know exactly what to ask. If anyone has any suggestions they would be greatly appreciated. Thanks in advance for your time and assistance. Regards, Matthew
Re: tape reuse
On Mon, 27 Aug 2001 at 10:40pm, Oliver Aldulea wrote > Let's number the tapes 1 2 3 4. I would like to use them like this: > > Mon: level 0 on 1 > Tue: level 1 on 2 > Wed: level 1 on 3 > Thu: level 1 on 2 > Fri: level 1 on 3 > Mon: level 0 on 4 > Tue: level 1 on 2 > and so on. > > Is it possible using just one configuration? I got it working with two > configs, one for full, one for incremental level 1, but it's a pain when > it comes to restoring. I would have to restore a full, then an incr, > manually, as amrecover doesn't work with 2 indexes. I also can't use a > different backup system because this is pretty much the only gpl'd one > that can do samba (unless anyone has some ideeas). I can think of one way that it's "sorta" possible. "Sorta" in that I think this will work, it will require vigilance on your part, and it won't be quite as rigid as the above. Day 1: level 0 on 1 Day 2: level 1 on 2 Day 3: level 1 on 3 You notice two successful level 1s, and perform 'amrmtape Config 2' to remove tape 2 from amanda's knowledge. You then 'amlabel Config 2' to tell amanda it now has a new tape, which it will ask for next. So Day 4: level 1 on relabeled 2 Day 5: amrmtape/amlabel 3, level 1 on tape 3 Day 6: level 0 on 4 Of course, amanda is going to try to help you out by promoting filesystems to level 0s when it can, so all your level 0s may not always be on the same tape, which throws a big monkey wrench in all this. > By the way, is anyone working on a GUI/web interface for amrecover? (I > don't really care about setting up the system, because it's one-time, > I just don't want to drive 40 minutes and pay for parking just to > restore the pr0n that the boss erased the other day, or some other > similar event). Why not ssh? Regarding a web interface, I'll channel John R. Jackson (is he on a much-deserved vacation, or just dealing with the return of the undergrads *shudder*?) and say "are you volunteering?". ;) -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: config amanda to backup to holding disk instead of tape changer
On Mon, 27 Aug at 10:47pm, [EMAIL PROTECTED] wrote > Do you know if it is possible to have Amanda backup to the holding disk > instead of to tape? The reason is that my tape drive will arrive in two > weeks, but my professor would like Amanda to be installed on the pc and > backing up to the holding disk in the meantime. When the tape drive > arrives, then I can dump the contents of the holding disk to tape. If there's no tape, amanda will leave as many images as possible on the holding disk. When the tape drive arrives, you can 'amflush' them to tape. If you're starting out this way, you'll need to: 1) Have a holding disk big enough to hold one full backup of every disklist entry, as well as incrementals. 2) Set the "reserve" parameter (how much of the holding disk amanda reserves for incremental dumps) low enough to have the space required by the fulls of step 1. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: dump to tape failed
On Tue, 28 Aug 2001, wanadoo wrote: > driver: result time 3.503 from dumper0: FAILED 01-2 [taper port > open: Resource temporarily > unavailable] > driver: result time 123.497 from taper: TAPE-ERROR 00-1 [port > connect timeout] It sounds like another process already has the port that taper wants to use, hence it's failing when trying to open it. By any chance is there an old taper process still running from a previous amanda run? -Mitch
file permissions for rundump in 2.4.1p1
Dear all, We have amanda-2.4.2p2 running here internally well. This is mostly on Irix 6.5 machines. I also want to add a client machine running Irix 6.3 (upgrading is not an option at the moment). As there is no compiler on this machine I installed amanda 2.4.1p1 from a binary release (freeware.sgi.com). After adding this machine to the configuration, amcheck gives no errors. When doing dumps, this client is not able to do actual estimates/dumps. Looking at the debug logs on the client reveals amandad.debug - [...] got packet: Amanda 2.4 REQ HANDLE 008-10053470 SEQ 998942112 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=maroon; DUMP dks0d2s0 0 1970:1:1:0:0:0 -1 sending ack: Amanda 2.4 ACK HANDLE 008-10053470 SEQ 998942112 bsd security: remote host deepskyblue user amanda local user amanda bsd security check passed amandad: running service "/usr/freeware/libexec/sendsize" amandad: sending REP packet: Amanda 2.4 REP HANDLE 008-10053470 SEQ 998942112 OPTIONS maxdumps=1; dks0d2s0 0 SIZE -1 amandad: got ack: Amanda 2.4 ACK HANDLE 008-10053470 SEQ 998942112 amandad: pid 13740 finish time Mon Aug 27 22:27:08 2001 Which looks OK. Sendsize.debug reveals the following sendsize: debug 1 pid 13741 ruid 6000 euid 6000 start time Mon Aug 27 22:27:06 2001 /usr/freeware/libexec/sendsize: version 2.4.1p1 calculating for amname 'dks0d2s0', dirname '/' sendsize: getting size via dump for dks0d2s0 level 0 sendsize: running "/usr/freeware/libexec/rundump (xfsdump) -F -J -l 0 - /dev/rroot" running /usr/freeware/libexec/killpgrp rundump: error [must be invoked by root] . (no size line match in above dump output) . asking killpgrp to terminate sendsize: pid 13741 finish time Mon Aug 27 22:27:08 2001 The permissions on the rundump binary look like the ones on the working hosts. -rwsr-x---1 root amanda 14092 aug 8 17:16 rundump Someone who has an idea on this ? Kris, -- Kris Boulez Tel: +32-9-241.11.00 AlgoNomics NV Fax: +32-9-241.11.02 Technologiepark 4 email: [EMAIL PROTECTED] B 9052 Zwijnaarde http://www.algonomics.com/
Re: /etc/inetd.conf
Hello! On Tue, 28 Aug 2001, chandra wrote: > I have finally managed to install the client for the sun box. I suppose > there has to be a entry in /etc/inetd.conf. I have searched and tried to > figure out what to put in there but haven't succeeded. Can someone please > help. I assume you are talking about Solaris. On my backup server there are the following lines in inetd.conf: # Amanda Backup amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped amanda dgram udp waitamanda /usr/local/libexec/amandad amandad On a backup client you only need the following line: # amanda backup client # amanda dgram udp waitamanda /usr/local/libexec/amandad amandad The directory on the end on the lines depend where you installed amanda. Bye, Gaby -- enlog AGDaimlerstr. 15 - 89079 Ulm Dipl. Inf. Gaby Hornik Germany Systems Administrator Tel.: +49 731 2075134 mailto:[EMAIL PROTECTED] Fax: +49 731 2075109
dump to tape failed
Hi,
I'm trying to resolve a problem with amanda, but I don't know why.
Every time I run amdump I receive a report like this:
These dumps were to tape Diaria-001.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
volinux.ay /home/sanzm lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:02 0:00 0:00 (0:00 start,
0:02 idle)
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 0.00.00.0
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --
NOTES:
taper: tape Diaria-001 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s
MMM:SS KB/s
-- --
--
volinux.a /home/sanzm0 FAILED
(brought to you by Amanda version 2.4.1p1)
I have looked at the *.debug files but I haven't seen anything strange.
I have looked too at the file amdump.1 and I have found this:
driver: send-cmd time 3.500 to taper: PORT-WRITE 00-1
volinux.ayto.es
/home/sanzm 0 20010824
driver: result time 3.500 from taper: PORT 1073
driver: send-cmd time 3.500 to dumper0: PORT-DUMP 01-2 1073
volinux.ayto.es /home/sanzm 0 1970:1:1:0:0:0 GNUTAR
|;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;
driver: state time 3.500 free kps: 1970 space: 0 taper: writing
idle-dumpers: 3 qlen tapeq: 0 runq: 0
stoppedq: 0 wakeup: 86400 driver-idle: not-idle
driver: interface-state time 3.500 if : free 570 if LE0: free 1 if
LOCAL: free 1
driver: hdisk-state time 3.500
driver: result time 3.503 from dumper0: FAILED 01-2 [taper port
open: Resource temporarily
unavailable]
driver: result time 123.497 from taper: TAPE-ERROR 00-1 [port
connect timeout]
driver: QUITTING time 123.498 telling children to quit
driver: send-cmd time 123.498 to taper: QUIT
driver: send-cmd time 123.498 to dumper0: QUIT
driver: send-cmd time 123.498 to dumper1: QUIT
driver: send-cmd time 123.498 to dumper2: QUIT
driver: send-cmd time 123.498 to dumper3: QUIT
taper: DONE [idle wait: 0.000 secs]
taper: writing end marker. [Diaria-001 OK kb 0 fm 0]
driver: FINISHED time 128.729
amdump: end at Fri Aug 24 09:54:11 CEST 2001
Is there anybody that know why this occurs? I need help.
Thanks,
Mercedes.
