Re: Request timed out...
> GIC MLs wrote: > > > Having problems with getting Amanda working on one machine... > > > > OS: FreeBSD > > Version: Amanda 2.4.2p2 (installed as tarball, not as FreeBSD port) > > Problem: > > - amcheck daily: looks great > > - amdump daily : Request to client.domain.com timed out. > > > > I've set this up as close as I can tell to the config of a working > > machine... > > I realize that most time-outs are the result of amandad not listening on the > > client machine, but I have set it up in inetd.conf and restarted inetd a > > couple of times with no luck. Can anyone see what I'm missing here? > > Specific information follows... > > > > Thanks, > > > > Shawn > > > > > > /etc/hosts > > xxx.xxx.xxx.xxx client.domain.com client > > xxx.xxx.xxx.xxx host.domain.com host > > > > /etc/inetd.conf > > amanda dgram udp waitamanda /usr/local/libexec/amandad > > amandad > > > > /etc/services > > amanda 10080/udp #Dump server control > > amandaidx 10082/tcp #Amanda indexing > > > > /home/amanda/.amandahosts > > host.domain.com amanda > > client.domain.com amanda > > > I have found that if I use a FQDN for the client name in the clients > .amandahosts file I get timeouts. server Linux, client IRIX > > on client maybe try > > clientname amanda > Tried this with no luck. Also, I am using gtar: # gtar --version tar (GNU tar) 1.13.25 My configuration options were: --without-server --with-user=amanda --with-group=operator --with-tape-server=server.domain.com --with-gnutar=/usr/local/bin/gtar --with-config=daily Any further thoughts/suspicions appreciated. Thanks, Shawn
Request timed out...
Having problems with getting Amanda working on one machine...
OS: FreeBSD
Version: Amanda 2.4.2p2 (installed as tarball, not as FreeBSD port)
Problem:
- amcheck daily: looks great
- amdump daily : Request to client.domain.com timed out.
I've set this up as close as I can tell to the config of a working
machine...
I realize that most time-outs are the result of amandad not listening on the
client machine, but I have set it up in inetd.conf and restarted inetd a
couple of times with no luck. Can anyone see what I'm missing here?
Specific information follows...
Thanks,
Shawn
/etc/hosts
xxx.xxx.xxx.xxx client.domain.com client
xxx.xxx.xxx.xxx host.domain.com host
/etc/inetd.conf
amanda dgram udp waitamanda /usr/local/libexec/amandad
amandad
/etc/services
amanda 10080/udp #Dump server control
amandaidx 10082/tcp #Amanda indexing
/home/amanda/.amandahosts
host.domain.com amanda
client.domain.com amanda
Email Report:
These dumps were to tape daily001.
The next tape Amanda expects to use is: daily001.
FAILURE AND STRANGE DUMP SUMMARY:
client.domain. /usr lev 0 FAILED [Request to client.domain.com timed out.]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:15
Run Time (hrs:min) 0:15
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk client.domain.com:/usr.
driver: WARNING: got empty schedule from planner
taper: tape daily001 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
client.agic.ne /usr0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
Re: Getting My Data Back Off The Tape
Thanks very much for the help... > First make a scratch directory like this: > mkdir /var/tmp/testing/ > Then, from inside that directory, run the same dd command, but > with "gtar -tvf -" so you can see exactly which files got into > the archive. This also shows what the file names look like. They > won't start with a slash, because tar strips those, but they > probably will start with ./ depending on how tar was called. > > Ultimately, you'll probably need to use "gtar -xf - ./usr.dump" > > > And if the data transferred, where did it go to? Not to the directory wher I > > ran the dd command from... Did it get sent back to the client automagically? > > I wouldn't take the chance of overwritting something accidentally. > That's why I suggest you run the dd and tar commands from within > a new, empty directory. I had originally make the scratch directory so as to avoid problems, and had been running the command from inside that directory. I followed your advice and ran the command with the -tvf - flags, which seemed to only give me a listing of directories.: # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -tvf - I grepped this for amanda, but only got the directories containing amanda then, of course, so finally I got on the ball and : # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf - ./home/user/amanda-2.4.2p2.tar.gz which gave me just what I wanted - THANKS! John LaBadie wrote: > It is a common unix convention to use "-" as a file name placeholder > meaning "standard input". For example: "ls | cat foo - bar" puts > the ls output between the contents of the files foo and bar. Didn't know that - that was one of the things that was confusing me, thanks for the clarification. Cheers much, Shawn
Re: Getting My Data Back Off The Tape
> Yeah, it's right here in the SYNOPSIS section of the man page: > > SYNOPSIS >tar [ - ] A --catenate --concatenate | c --create | d > Ok, see it now? (Neither do I :-) :-))) > But you need a - after the -xf, > otherwise tar is trying to read its input from usr.dump, which it can't > find. a - after the -f option says to read from stdin. So try changing > that to read: > > # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf - usr.dump > > and let us know how it goes. > > -Mitch Ok, that is exactly what I was missing - thanks! Now my problem is this... # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf - usr.dump 0+0 records in 0+0 records out 0 bytes transferred in 0.040918 secs (0 bytes/sec) /usr/local/bin/gtar: usr.dump: Not found in archive /usr/local/bin/gtar: Error exit delayed from previous errors Hmm... usr.dump *does* exist in /usr on the client... wonder why it didn't get anything... I tried to recover another file which exists on the client as /usr/home/user/amanda-2.4.2p2.tar.gz # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf - amanda-2.4.2p2.tar.gz 53741+0 records in 53741+0 records out 1760985088 bytes transferred in 594.278274 secs (2963233 bytes/sec) /usr/local/bin/gtar: amanda-2.4.2p2.tar.gz: Not found in archive /usr/local/bin/gtar: Error exit delayed from previous errors This time it looks like there was something there, data transferred... but then why would it say "Not found in archive?" And if the data transferred, where did it go to? Not to the directory wher I ran the dd command from... Did it get sent back to the client automagically? Thanks, Shawn
Getting My Data Back Off The Tape
Hi, Ok, so I have finally got Amanda to write a partition to tape. Now I want to grab a file off of the tape. I'm using Amanda-2.4.2p2 on FreeBSD. After a successful amcheck and amdump, I run # mt rewind # mt fsf 001 to position the tape at the beginning of where I wrote daily001. I'm following the instructions in Unix Backup & Recovery here - Chapter 4 page 183. I have backed up /usr on the client machine, and in /usr I have a file called usr.dump that I would like to recover. I am trying to do this with the following command: # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf usr.dump ... but I get: /usr/local/bin/gtar: usr.dump: Cannot open: (null) /usr/local/bin/gtar: Error is not recoverable: exiting now What am I doing wrong here? Am I using the gtar command incorrectly? I read through the tar manpage trying to find my mistake, but can't seem to see what I'm doing wrong. Any advice appreciated, Shawn
Re: selfcheck request timed out.
Ok, I figured out the permissions problem that was preventing amcheck from working, as per below. amcheck now finishes with no errors. When I run amdump, "top" on the client shows gtar working away, so it data compression seems to be happening. amdump finishes with no errors, but in the report email, I get: > These dumps were to tape daily001. > The next tape Amanda expects to use is: daily001. > > FAILURE AND STRANGE DUMP SUMMARY: > client.agic. /usr lev 0 FAILED [Request to client.agic.ne.jp timed out.] > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)0:15 > Run Time (hrs:min) 0:15 > Dump Time (hrs:min)0:00 0:00 0:00 > Output Size (meg) 0.00.00.0 > Original Size (meg) 0.00.00.0 > Avg Compressed Size (%) -- -- -- > Filesystems Dumped0 0 0 > Avg Dump Rate (k/s) -- -- -- > > Tape Time (hrs:min)0:00 0:00 0:00 > Tape Size (meg) 0.00.00.0 > Tape Used (%) 0.00.00.0 > Filesystems Taped 0 0 0 > Avg Tp Write Rate (k/s) -- -- -- > > > NOTES: > planner: Adding new disk client.agic.ne.jp:/usr. > driver: WARNING: got empty schedule from planner > taper: tape daily001 kb 0 fm 0 [OK] > > > DUMP SUMMARY: > DUMPER STATSTAPER STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > client.agic.ne /usr0 FAILED --- > > (brought to you by Amanda version 2.4.2p2) Can anyone help me end this nightmare? Shawn - Original Message - From: "Jonathan Murray" <[EMAIL PROTECTED]> To: "GIC MLs" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, May 11, 2002 1:55 AM Subject: Re: selfcheck request timed out. > check .amandahosts file. > also make sure that you don't use FQDN in .amandahosts. > > GIC MLs wrote: > > > Hi, > > > > I'm running Amanda 2.4.2p2, and when I run "amcheck daily", I get: > > > > Amanda Tape Server Host Check > > - > > NOTE: skipping tape-writable test > > Tape daily001 label ok > > NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist > > NOTE: it will be created on the next run > > Server check took 5.219 seconds > > > > Amanda Backup Client Hosts Check > > > > WARNING: client.agic.ne.jp: selfcheck request timed out. Host down? > > Client check: 1 host checked in 30.078 seconds, 1 problem found > > > > The client machine is pingable and configured with amandad running off of > > inetd. > > Can anyone tell me where I should start looking for the root of this > > problem? > > > > Thank you for any assistance. > > > > Shawn > > > > > > > > >
selfcheck request timed out.
Hi, I'm running Amanda 2.4.2p2, and when I run "amcheck daily", I get: Amanda Tape Server Host Check - NOTE: skipping tape-writable test Tape daily001 label ok NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist NOTE: it will be created on the next run Server check took 5.219 seconds Amanda Backup Client Hosts Check WARNING: client.agic.ne.jp: selfcheck request timed out. Host down? Client check: 1 host checked in 30.078 seconds, 1 problem found The client machine is pingable and configured with amandad running off of inetd. Can anyone tell me where I should start looking for the root of this problem? Thank you for any assistance. Shawn
Couple of Log File Questions
A couple of questions from my log file: planner:RDEV_PREFIX="/dev/r" DUMP="/sbin/dump" planner:RESTORE="/sbin/restore" GNUTAR="/usr/bin/tar" Should I be using gtar instead? (http://www.amanda.org/cgi-bin/fom?_recurse=1&file=7#file_10) How do I change this setting? planner:DEFAULT_CONFIG="DailySet1" My amanda.conf has labelstr "^daily[0-9][0-9]$*" - where is this DailySet1 coming from? planner:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM My amanda.conf has tapedev "/dev/nrsa0" ... what gives? got result for host client.agic.ne.jp disk /usr: 0 -> -1K, -1 -> -1K, -1 -> -1K Is this bad? And the failure that I've been getting: getting estimates took 0.183 secs FAILED QUEUE: 0: client.agic.ne.jp /usr DONE QUEUE: empty ANALYZING ESTIMATES... planner: FAILED client.agic.ne.jp /usr 0 [disk /usr offline on client.agic.ne.jp?] Any suggestions? Shawn
Re: disk offline
> >My amdump email report starts out: > > > >These dumps were to tape daily001. > >The next tape Amanda expects to use is: daily001. > > This in itself, is odd, very odd. Your amanda.conf seems to be > out of whack somehow. Well, that could very well be, I suppose... > >(brought to you by Amanda version 2.4.2p2) > > Was this an rpm installed version? No. I am running FreeBSD ports. I installed Amanda in January... I think it was done using the FreeBSD ports collection. > And whats an 'amcheck /config/' report? %amcheck daily Amanda Tape Server Host Check - NOTE: skipping tape-writable test Tape daily001 label ok NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist NOTE: it will be created on the next run Server check took 5.145 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.114 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) > >I'm not really sure where to start looking for answers here. > >Can anyone suggest a starting point? > > Building your own from scratch has always worked here. I have a > short script that I use for the ./configure step so that each > succeeding version remains compatible with the previous one by > having the exact same options each time, and I'm currently > running the 2.4.3b3-20020422 snapshot with a seagate changer. I have no changer... A script sounds like a good idea. Thanks, Shawn
disk offline
I would expect this to be a frequently asked question, but after looking
through Google, I didn't see much specifically on it, so...
My amdump email report starts out:
These dumps were to tape daily001.
The next tape Amanda expects to use is: daily001.
FAILURE AND STRANGE DUMP SUMMARY:
client.agic. /usr lev 0 FAILED [disk /usr offline on client.agic.ne.jp?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk client.agic.ne.jp:/usr.
driver: WARNING: got empty schedule from planner
taper: tape daily001 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
client.agic.ne /usr0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
I'm not really sure where to start looking for answers here.
Can anyone suggest a starting point?
Thanks,
Shawn
Re: Holding disk
Thank you for the pointers...
> >I'm having the same problem here, also running Amanda 2.4.2p2.
>
> Actually, you're having a different problem. But be that as it may ...
>
> >ERROR: /export/dumps/amanda: rewinding tape: Inappropriate ioctl for
device
> > (expecting a new tape)
> >...
> >I had set tapedev "/export/dumps/amanda" in amanda.conf with the
(obviously
> >mistaken) understanding that Amanda would just dump to that dir. ...
>
> The 2.4.2p2 version of Amanda only writes to tapes. If you want to store
> your images in a disk area, you need what's called the "tapeio" feature.
> You can get that either via the amanda-242-tapeio CVS branch (see the
> FAQ for details on how to check out and build from CVS), or it's also
> part of 2.4.3, which is now in beta.
>
> Are you planning on leaving the images in that disk area, i.e. treating it
> like a pseudo tape, or are you planning on flushing them to tape later on?
I plan to buy a tape setup, but the kind I want wont be available in Japan
until March, so I am trying to test the system by dumping to hard disk for
the time being. It will also make the boss feel better to be able to see
backed up data physically on another machine. :-)
> If you plan to eventually flush them, then you want to do things
> differently (and 2.4.2p2 support this). Just set "reserve" to zero in
> the holding disk declaration so Amanda will go ahead and do full dumps,
> then set tapedev to something like "/no/such/device". The tape writing
> portion of Amanda will fail, but the dumping to the holding disk part
> will work. Then change tapedev and run amflush as needed (and set
> tapedev back after the amflush).
>
> In fact, the above might do what you want even without the flushing.
> It depends on what the goal is.
I set tapedev to literally "/no/such/device" :-)
and set reserve to 0.
I then ran:
# su amanda -c "amcleanup daily"
# su amanda -c "amcheck daily"
# su amanda -c "amdump daily"
I then checked the dump directory to see what happened:
# ls -l /export/dumps/amanda/
total 1
drwx-- 2 amanda backup 512 Feb 5 11:21 20020205/
and saw that a new directory with today's date has been created.
I then looked in that directory for backed up data, but:
# ls -al /export/dumps/amanda/20020205/
total 2
drwx-- 2 amanda backup 512 Feb 5 11:21 ./
drwxrwxr-x 3 1 backup 512 Feb 5 11:21 ../
hmm... nothing...
Any idea what I'm missing?
The error mail I get from Amanda follows.
Thanks,
Shawn
*** A TAPE ERROR OCCURRED: [no tape online].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
mydom.co. /usr lev 0 FAILED [disk /usr offline on mydom.co.jp?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk mydom.co.jp:/usr.
driver: WARNING: got empty schedule from planner
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
mydom.co /usr0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
Re: Holding disk
> >Before running amcleanup I checked the content of my > >holding disk. It contained a subfolder with the date > >of the normal run, but the folder was empty. > > There's not enough information yet to know what's going on with your > setup. You need to get through a complete amdump without it aborting > before we deal with the holding disk situation. > > The datestamp directory is normal in the sense that that's created early > in the amdump run to hold the images. But my guess is something else > happened to cause the run to abort, hence the empty holding disk and > amcheck whining about amdump still running. > > Check to see if amdump is still running (ps -u ). Assuming > it isn't, run amcleanup. Run amcheck and make sure it's happy. Then run > amdump and if it fails, report everything it had to say. If it does > not fail, look in your holding disk area again. > > >I'm running Amanda version 2.4.2p2 > > Thanks for that info. At least we'll know what set of code to be > looking at. Hi, I'm having the same problem here, also running Amanda 2.4.2p2. I run # su amanda -c "amdump daily", which finishes with no errors. I get an email report saying: *** A TAPE ERROR OCCURRED: [rewinding tape: Inappropriate ioctl for device]. I do a ps to make sure amdump is not running, then # su amanda -c "amcleanup daily", which gives me: amcleanup: no unprocessed logfile to clean up. Scanning /export/dumps/amanda... # I then run # su amanda -c "amcheck daily", and get: Amanda Tape Server Host Check - Holding disk /export/dumps/amanda: 4784640 KB disk space available, using 4774400 KB ERROR: /export/dumps/amanda: rewinding tape: Inappropriate ioctl for device (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/local/etc/amanda/daily/index: does not exist Server check took 30.118 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.112 seconds, 0 problems found I had set tapedev "/export/dumps/amanda" in amanda.conf with the (obviously mistaken) understanding that Amanda would just dump to that dir. Should I be setting this differently or commenting out something else in amanda.conf to prevent it from mistaking this for a tape? Any help appreciated. Thanks, Shawn
