tapetype crashes
This happens after tapetype runs for 5 or so hours. What is wrong or does someone have the tapetype for a for a TR-5 10/20gb tape. Thanks! Will Error as follows: ahc1 target 4 synchronous at 10.0mghz, offset = 0xf Tapetype could not rewind /dev/nst0 Input/Output error . Last message repeated 3383 times. Mt f /dev/nst0 rewind does not seem to work until a reboot. Amanda version 2.4.2p1 OpenBSD 2.8 with most recent patches. Tape Drive: Seagate STT22N-RFT 10/20
Script for tape index
I am looking for a script that someone posted to this list a while ago. It allows you to get a listing of what is on the backup tape. I have problems that since I use 2 tapes per backup, the amtoc that I use either reports just what is on the second tape or reports completely incorrect information. I am using amanda 2.4.1p1 currently and need a way to examine the contents of the tapes. I could not seem to find the script in the mail list archives. Thanks for any assistance. --- "I have not failed. I've just found 10,000 ways that won't work." - Thomas Edison Michael Hendrix [EMAIL PROTECTED] Systems Engineer Logical Net / Capital Net (518) 292-4509
Re: DELL 120T changer on RH 6.2
Attached is the changer script that I have been using successfully on two 120T's for several months at the School of Computer Science & Electrical Engineering at The University of Queensland, Australia. These are attached to Dell PowerEdge 4400's, one running RH6.2 and one running RH7.0. I had also no luck with the original scripts supplied with Amanda on the Dell changer - so set out and modified them. I started with the csee-chg-mtx script in 2.4.1p1 and got it going with the mtx from http://mtx.sourceforge.net/, basically by confirming that the tapes were offline before doing any unload command. Then Joe Rhett released a modified script for the mtx changer that had other things I liked so I adopted and modified his script into what is here. My script fixes major problems we were seeing, that potentially could arise with many changers - like hardcoded bits in the script to load the first slot, but if the first slot was empty so the script would loop forever! This script uses the sensors in the changer to determine which slots are full/empty and automatically skips empty slots, returns to amanda only the number of slots that are full, and so on. We don't run automated cleaning tapes (at the moment) so I haven't tested that part of the script, but my script has been 100% reliable for what it does for us. You've said you have the changer going now, so hopefully in your logs you have lines like: (scsi2:0:0:0) Synchronous at 20.0 Mbyte/sec, offset 8. Vendor: QUANTUM Model: DLT7000 Rev: 2561 Type: Sequential-Access ANSI SCSI revision: 02 Vendor: ADIC Model: FastStor DLT Rev: D116 Type: Medium Changer ANSI SCSI revision: 02 st: bufsize 32768, wrt 30720, max buffers 5, s/g segs 16. Detected scsi tape st0 at scsi2, channel 0, id 0, lun 0 Detected scsi generic sg4 at scsi2, channel 0, id 1, lun 0 For other Linux users who might be watching, if you haven't figured out what devices to use you can determine which tape device and changer device to use from the last two lines above - in this example, the changerdev is /dev/sg4, and the tapedev is /dev/nst0 (the no-rewind version of st0). If you don't have a /dev/sgN or /dev/nstN then use MAKEDEV sgN to create it. Specify the 'changerfile' to be somewhere writable by the amanda user, and the script will generate changerfile-clean, changerfile-access and changerfile-slot files recording number of cleans, number of accesses, current slot (as per the original scripts). Hope this helps and you have as much success with my script as I do. Regards, Chris chg-csee-mtx
tapetype crashes
This happens after tapetype runs for 5 or so hours. What is wrong or does someone have the tapetype for a for a TR-5 10/20gb tape. Thanks! Will Error as follows: ahc1 target 4 synchronous at 10.0mghz, offset = 0xf Tapetype could not rewind /dev/nst0 Input/Output error . Last message repeated 3383 times. Mt –f /dev/nst0 rewind does not seem to work until a reboot. Amanda version 2.4.2p1 OpenBSD 2.8 with most recent patches. Tape Drive: Seagate STT22N-RFT 10/20
No Subject
unsubscribe [EMAIL PROTECTED]
RE:
Did somebody yell, "Fire!"? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel > Sent: Thursday, March 22, 2001 6:10 PM > To: [EMAIL PROTECTED] > Subject: > > > unsubscribe [EMAIL PROTECTED] > >
(no subject)
unsubscribe begin:vcard n:Lott;Miles tel;cell:713-410-5480 tel;work:713-410-5480 x-mozilla-html:FALSE url:http://milosch.net org:Milosch.net adr:;;;Houston;TX;;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Sole-proprietor x-mozilla-cpt:;-12384 fn:Miles Lott end:vcard
scheduling dumps question
Hi ! I'm fairly new to amanda and am stuck with a problem setting up my dumps: I'm using the 'starttime' dumptype parameter to delay one dump to sort of force it to be the last one. That's because I want to backup the amanda database and tar snapshot files to the same tape (with indexing turned off) to keep it all together in one place (or rather tapes ;-) for easy restoring (btw, the online chapter of the unix backup & restore book states incorrectly that this 'starttime' is relative to the amdump start time, but I think I'm not the first one to stumble over it). This works as expected as long as all dumps fit into the holding disk(s) as is the case with levels >=1. But unfortunately when doing a full dump one of partitions is much too big to fit into the holding disk and is dumped directly to tape. In this situation the dump of that big partition is delayed until _after_ the run of the delayed amanda database dump. As far as I understand it (and could verify it with the help of the sources) this is the designed behaviour as the smaller dumps are preferred over the bigger ones and direct dumps to tape (due to 'no-diskspace') are only done, when all delayed dumps have finished. Is this correct and if so, is there any other trick/configuration/whatever that helps me achieve my goal ? What is everybody else doing with their tar incremental snapshot files which are needed for a correct restore ? Thanks a lot for any hints & help! Urban
No Subject
unsubscribe [EMAIL PROTECTED]
Re: user permissions problem
On Thu, 22 Mar 2001, John R. Jackson wrote: > I don't think this would be the problem. LFS would only come into play > if the file went to disk. The only way it would go to disk is in the > holding disk, and you can set the chunksize in amanda.conf for that. > Also, Amanda would have whined mightily if you hit this limit. Right. I figured as much. The Samba users mailing list suggests your assessment below is more correct. > I think the problem is that Samba (or SMB or whatever) cannot do the > large files itself, regardless of OS. I seem to recall other people > having trouble with this, but may be mistaken. results from dd'ing from smbclient (file in question is 2-22-01-all.bkf): --start-- 22:00:07 - prefect:/tmp/backup $ smbclient //wiley/home -W wiley -U backup -E -d0 -Tqc - backups/2-22-01-all.bkf | dd bs=1k | tar tvf - Password: -rw-r--r-- 0/0 7956623360 2001-02-23 01:43:47 ./backups/2-22-01-all.bkf tar: dumped 1 files and directories Total bytes written: 3661656576 3575900+0 records in 3575900+0 records out tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now --end-- Whoops. Looks like samba sees about 8gb of the 11.1gb in the listing. dd gets about 3.5gb, and tar doesn't like it at all. Thoughts? Looks like samba is the culprit. -- http://www.mchang.org/ http://decss.zoy.org/
unsubscribe Jerry.Lawler@dss.ca.gov
unsubscribe [EMAIL PROTECTED]
Amanda
Hello I ftped the following files from amanda site :- amanda-2.4.2p1.tar.gz,autoconf-2.13.tar.gz,automake-1.4.tar.gz,bison-1.2 7.tar.gz,flex-2.5.4a.tar.gz,gawk-3.0.3.tar.gz,gnuplot-3.7.tar.gz,readlin e-2.2.1.tar.gz,and termcap-1.3.tar.gz. and configured ,make,make install it to my SunSolaris Server Ver 5.8 under /export/home/amanda file system as well as MY AIX ver4.3.3.0 server under /home/amanda file system .Both server has a amanada user and a group. My Tape drive is in Sun solaris box. and i want to take my aix box backup through amanda software while using amanda server Tape drive. and i also make changes in /etc/services and /etc/inetd.conf as per your /docs/INSTALL instructions. kindly advice me what is the next step . and how will i configure amanda as a server and a client. Waiting for your reply Anurag
FW: Amanda
> Hello > I ftped the following files from amanda site :- > amanda-2.4.2p1.tar.gz,autoconf-2.13.tar.gz,automake-1.4.tar.gz,bison-1 > .27.tar.gz,flex-2.5.4a.tar.gz,gawk-3.0.3.tar.gz,gnuplot-3.7.tar.gz,rea > dline-2.2.1.tar.gz,and termcap-1.3.tar.gz. and configured ,make,make > install it to my SunSolaris Server Ver 5.8 under /export/home/amanda > file system as well as MY AIX ver4.3.3.0 server under /home/amanda > file system .Both server has a amanada user and a group. My Tape drive > is in Sun solaris box. and i want to take my aix box backup through > amanda software while using amanda server Tape drive. and i also make > changes in /etc/services and /etc/inetd.conf as per your /docs/INSTALL > instructions. kindly advice me what is the next step . and how will i > configure amanda as a server and a client. > > What is the next step for using amanda . kindly help me out.. > > > Waiting for your reply > Anurag > >
Re: user permissions problem
>... Thus amrecover is good, but somehow >things didn't get backed up. Nicely diagnosed. >But I think I've found the problem. The last file in the index is an 11GB >file. The backup server, if you recall, is Linux without the large >filesystem patches. My guess is that it all just died when it tried to get >through 11GB. A quick browse through the samba mailinglist says that large >filesystem support (lfs) isn't enabled by default in the latest 2.0.7 >release for ostype "linux", even if you have the 2.4 kernel or the 2.2 >patches. Anyone else run into this problem? I don't think this would be the problem. LFS would only come into play if the file went to disk. The only way it would go to disk is in the holding disk, and you can set the chunksize in amanda.conf for that. Also, Amanda would have whined mightily if you hit this limit. I think the problem is that Samba (or SMB or whatever) cannot do the large files itself, regardless of OS. I seem to recall other people having trouble with this, but may be mistaken. See if you can just do the smbclient part to nothing (image never hits the disk): smbclient '\\pc\share' -U -E -d0 -Tqc - \ | dd bs=1k \ | tar tvf - The dd will tell you how many blocks it processed, which, as long as they are all full, will be the image size in KBytes. You should also see a size message from smbclient and the "tar t". You might also try this without the "" arg so the whole share is dumped, which is what Amanda is asking. And you might play with different debug levels and the 'q' option to see if you can get it to complain any. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: yep, it's "Selfcheck request timed out. Host down?" again
Well, it's working again. I think that amandad was confused or something. There were some lost items (shown by the ipcs command) that I recovered with ipcrm. Also, I had set up /tmp/amanda as a symbolic link to a different partition with more disk space when I first installed it (and was getting huge debug files), so I moved it back. I'm thinking perhaps there was a permissions problem that had decided to magically appear. After making these changes, and restarting inetd, things were back to normal. Thanks for your ideas, John, they helped me to try the types of things that finally fixed the problem. Using amanda 2.4.1p1 and FreeBSD 4.2 --- Eric "John R. Jackson" wrote: > > >Amanda has been running smoothly for months, then suddenly last night's dump > >failed on all the samba shares (NT boxes) as well as the amanda host and tape > >server (also the samba server). > > That's all because of amandad not working. Once we get it going again, > this will probably all go away. > > >I did a HUP to inetd, and the last line of amandad.debug shows: > >amandad: error receiving message: timeout > > That line must be from after you ran amandad by hand. What happens to > the file if you run amcheck? Does it get updated? > > I know you said you went through the FAQ, but could you confirm that if > you do a "netstat -a | grep amanda" that it shows someone listening? > > When you did the HUP to inetd, did it log anything (/var/adm/messages > or wherever)? > > You might try removing /tmp/amanda and see if it gets recreated. > > What version of Amanda are you using? What type of OS? > > >--- Eric > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
Re: Amanda Issue.
>Now in this stage it gives me an error. >"/usr/local/etc/amanda/Daily/amanda.conf", line 75: duplicate parameter, >prev def on line 74 As Marc Mengel just said, if you look at your amanda.conf you'll see three duplicate lines and comments right above them that explain what to do (you're supposed to pick one or none). This is probably a problem in our release (that amanda.conf has a syntax error) and I'll see about changing that for the future. You're the second person this week that has run into this. >Anurag John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Thanks John,
You know what's sad is, the more sarcasm added to a tech story, the more _believable_ it becomes... On Thu, 22 Mar 2001, John R. Jackson wrote: > >You are always such a great help in this mailing list, do you have a pay > >pal account? ... > > No (don't even know what that is). > > >I'd like to buy you a drink or a pizza or at least send you > >the money for one :) > > Thanks. I don't happen to drink (just a personal choice), my waistline > doesn't tolerate pizza like it did 25 years ago (which really sucks :-), > and Purdue pays me pretty well, but I appreciate the sentiment. > > Tell you what -- next time you're out and blissfully ignoring backups > because you know they're running well due to Amanda, have a drink or > pizza or whatever for me. > > Just don't blame me for the panic attack that happens when, right after > you finish the pizza, you get a phone call: > > Operations: "Was there anything very important on the even numbered > backup tapes?" > > You:(lengthy pause) "Why would you ask that?" > > Operations: "Well, you see, someone brought in this cool magnet. It's > really small and you wouldn't believe the pull that thing > has ..." > > You: "Yeah, yeah, but what about the tapes?" > > Operations: "Ummm, there was this little incident. Well, hardly an > incident, just kind of a tiny problem. Well, maybe not > really a problem, more like ..." > > You: "GET ON WITH IT!" > > Operations: "Oh! Well, see, one of the other Operators (NOT ME!) was > walking around with the magnet and they got near the Pepsi > machine -- we could have sworn that thing was bolted down > -- and there was this big jar of molasses on top of it > and the tapes were sitting next to it and, well, anyway ..." > > "Sorry." > > You:(dead silence -- literally) > > Operations: "Oh, by the way, the boss just accidentally removed all the > files on one of the main servers, then went to two others to > see if the rm command he just read about worked the same way > everywhere. He left to get to the golf course for tee time, > but says you need to restore those machines right away." > > At which point you realize that ignoring backups because you know they're > running well is a really terrible idea, no matter how good the pizza. > > :-) > > >Jeff Bearer > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Jason Hollinden SMG Systems Admin
Re: Amanda Issue.
This question should go to [EMAIL PROTECTED], and I am copying that list for further discussion. >From the error you include, an examination of lines 74..76 of your amanda.conf file would indicate that you either have a repeated line, or different values specified for the same parameter. Following up to [EMAIL PROTECTED] with a copy of your amanda.conf file would be the proper course of action. Marc Mengel <[EMAIL PROTECTED]> On Thu, 22 Mar 2001, Nischal, Anurag wrote: > Now in this stage it gives me an error. > "/usr/local/etc/amanda/Daily/amanda.conf", line 75: duplicate parameter, > prev def on line 74 > "/usr/local/etc/amanda/Daily/amanda.conf", line 76: duplicate parameter, > prev def on line 75
Re: user permissions problem
On Wed, 21 Mar 2001, John R. Jackson wrote: > OK. The first thing to do is look at the actual index files and see > if they have the entries (this is sounding familiar, so if we've gone > down this path before and I've forgotten, my apologies). If the files > are listed, it's an amrecover problem. To rewind the conversation -- gnutar 1.13.19 has been installed and it fixes my solaris backup problem. The only remaining issue is the smb clients. > Once we know which of these is the area responsible, debugging it can > proceed from there. Looking at the index, the files are not listed. Looking at a dump of all the files on the tape (dd style through tar), the missing files were _not_ backed up. Thus amrecover is good, but somehow things didn't get backed up. But I think I've found the problem. The last file in the index is an 11GB file. The backup server, if you recall, is Linux without the large filesystem patches. My guess is that it all just died when it tried to get through 11GB. A quick browse through the samba mailinglist says that large filesystem support (lfs) isn't enabled by default in the latest 2.0.7 release for ostype "linux", even if you have the 2.4 kernel or the 2.2 patches. Anyone else run into this problem? -- http://www.mchang.org/ http://decss.zoy.org/
Re: Thanks John,
>You are always such a great help in this mailing list, do you have a pay >pal account? ... No (don't even know what that is). >I'd like to buy you a drink or a pizza or at least send you >the money for one :) Thanks. I don't happen to drink (just a personal choice), my waistline doesn't tolerate pizza like it did 25 years ago (which really sucks :-), and Purdue pays me pretty well, but I appreciate the sentiment. Tell you what -- next time you're out and blissfully ignoring backups because you know they're running well due to Amanda, have a drink or pizza or whatever for me. Just don't blame me for the panic attack that happens when, right after you finish the pizza, you get a phone call: Operations: "Was there anything very important on the even numbered backup tapes?" You:(lengthy pause) "Why would you ask that?" Operations: "Well, you see, someone brought in this cool magnet. It's really small and you wouldn't believe the pull that thing has ..." You:"Yeah, yeah, but what about the tapes?" Operations: "Ummm, there was this little incident. Well, hardly an incident, just kind of a tiny problem. Well, maybe not really a problem, more like ..." You:"GET ON WITH IT!" Operations: "Oh! Well, see, one of the other Operators (NOT ME!) was walking around with the magnet and they got near the Pepsi machine -- we could have sworn that thing was bolted down -- and there was this big jar of molasses on top of it and the tapes were sitting next to it and, well, anyway ..." "Sorry." You:(dead silence -- literally) Operations: "Oh, by the way, the boss just accidentally removed all the files on one of the main servers, then went to two others to see if the rm command he just read about worked the same way everywhere. He left to get to the golf course for tee time, but says you need to restore those machines right away." At which point you realize that ignoring backups because you know they're running well is a really terrible idea, no matter how good the pizza. :-) >Jeff Bearer John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
GTAR Tape Changer problems
Dear Sirs. For our 250 GBytes RAID array backup on a FBSD 4.3 Server we use AMANDA 2.4.2p1. The tape changer is a HP SureStore 40x6i, which has a 6 cartridges magazine. I configured AMANDA that way to use the first time 8 magazines, each holding 5 tapes and one cleaning tape. For all filesystems GNU tar (GTAR) is used so I do not fall into problems when dumping images bigger than one tape. The first time this runs well, AMANDA saved all the images out to two or three tapes (like the multi volume mechanism when using a simple tar -M backing up a big filesystem ...). Now we changed several parameters (due to the lacking docimentation how to use GTAR we have had to recalibrate all parameters to the right size and want to start from the begining). amlabel labels each used cartridge used by AMANDA and in the manner of using dump as the backup/save tool this means that each run is made to tapes with increasing numbers. At this moment, our magazines are filled up with cartridges each labeled with the same label, means mag one is completely labeled throughout each cartridge with LABEL00, the second mag's tapes LABEL01 ... that means now, whenever GNU tar/AMANDA reaches the end of the first tape to continiue on the next one, it finds the same labeld tape in each slot, greps through the whole magazine and tells that it is out of tape. Well, I'm not very familiar how AMANDA/GTAR signs up each tape to keep in track with each one, but I want it to have 'clean' tapes because I think gtar is not continuing a LABEL00-tape on a second, like LABEL00:1, instead it needs LABEL01 - tape, or I'm wrong? How can I delete each label a fast way? ERASE is not a good idea (using mt) due the fact it takes a long time for each tape to be cleaned and delabeled ... -- MfG O. Hartmann [EMAIL PROTECTED] IT-Administration des Institut fuer Physik der Atmosphaere (IPA) Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532
Fwd: Re: DELL 120T changer on RH 6.2
-- ðÅÒÅÓÌÁÎÎÏÅ ÐÉÓØÍÏ -- Subject: Re: DELL 120T changer on RH 6.2 Date: Wed, 21 Mar 2001 10:56:39 -0500 From: Murat H. Dymov <[EMAIL PROTECTED]> To: "Thomas Hepper" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Hello, > Hi, > - Original Message - > From: "Murat H. Dymov" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, March 15, 2001 10:55 PM > Subject: DELL 120T changer on RH 6.2 > > > Hello All, > > > > I use Amanda 2.4.2p1 on RH Linux 6.2. > > > > we have Dell PowerVault 120T, and the documentation says that it has > > two SCSI devices - one for tape device and second for tape changer. > > Taper is running as /dev/nst0, seems to be OK - at least it make some > > noise . > > > But I couldn't find any way to get the changer working. > > I used /dev/sch0, /dev/sg*(means sg0-sg3) devices, with no respond. > > Last time I set it to /dev/sga, and it doesn't give error messages, but I > > can't force it to do any operation with tapes. > > > Does anybody have PV120T changer working under RH linux ? > > No changer but may be i can help you if you give some more infos. Which > programm did you > try for controlling the changer ?, I tried to use chg-scsi, chg-multi - had no succes. After that I finally downloaded mtx program. Now it can do something - it can load the tape from the changer slot in to the tape recorder, and it can move tapes from one slot to another. But in most cases it can not unload the tape from the tape recorder - reports with something like this "can not move tape from element 82 to element 5" where 5 is the number of the slot from where the tape was loaded into the recorder. I tried botn mtx 1.2 and 1.1 - the same error appears. I have no idea why it thinks of tape recorder as of element 82. The command like "unload 0 5" doesn't work either Any ideas of how to fix this are very welcome ! thanks, Murat > Thomas --- _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: amandahostsauth failed
>ERROR: daphne: [access as amanda not allowed from amanda@daphne] >amandahostsauth failed >*** > >Is this a point of trouble with rsh? No. Amanda does not use rsh. >I create in: > >/export/home/amanda/.amandahosts > >containing: > >daphne.webcom.de amanda >helena.webcom.de amanda Read the amcheck message carefully. The host name it reports is "daphne" rather than "daphne.webcom.de". So you need this in the file: daphne amanda However, this error might indicate a system misconfiguration on daphne. It says that when Amanda (or any other program) does a reverse lookup of the IP address for daphne, it does not get back a fully qualified host name. That's usually a bad thing, and you need to talk to whoever set up your name system (DNS, /etc/hosts or whatever) about why that is happening. >Bernd John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: error message help.
>I will download the latest cvs and compile it. I hope it won't have any >problems working with 2.4.1p1 (the version I'm currently using). ... It will work fine with 2.4.1p1 (I still have some old clients here). However, don't bother. You have a **serious** problem on that machine and it's not (directly) Amanda related ... >Mar 22 18:22:07 dexter amandad[10069]: open debug file >"/tmp/amanda/amandad.debug": File exists >... >2. trying to view the debug information in /tmp/amanda game me the error: >Input/output error. Trying to `rm` `file` gave the same error. You should never, ever, get "I/O error" for something like this. My guess is the disk involved is truly broken. I'd take that machine down for maintenance ASAP. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amandahostsauth failed
Hi All, i did some amcheck getting this message: *** Amanda Backup Client Hosts Check ERROR: daphne: [access as amanda not allowed from amanda@daphne] amandahostsauth failed *** Is this a point of trouble with rsh? what do i have to do with it? I create in: /export/home/amanda/.amandahosts containing: daphne.webcom.deamanda helena.webcom.deamanda tanxs for some hints (not hits) :-) Bernd
Re: error message help.
Hi John I will download the latest cvs and compile it. I hope it won't have any problems working with 2.4.1p1 (the version I'm currently using). The only caveat. It will take me at ;east until middle of next week to finish this (too much real work to do). Guilty as charged, I upgraded the SSH client server from 2.3.0p1 to 2.5.2p2 :) In the mean time I found a couple of other clues: syslog reports the following: Mar 22 18:22:07 dexter amandad[10069]: open debug file "/tmp/amanda/amandad.debug": File exists Mar 22 18:22:07 dexter inetd[10028]: amanda/udp server failing (looping or being flooded), service terminated for 10 min 1. killing inetd and restarting it didn't help. 2. trying to view the debug information in /tmp/amanda game me the error: Input/output error. Trying to `rm` `file` gave the same error. Hope this helps. "John R. Jackson" wrote: > >send req failed: Connection refused > >protocol packet receive: Connection refused > >protocol packet receive: Connection refused > > I can tell you what Amanda is doing, but not why your system is reporting > this error to Amanda. > > Amanda has created a socket and then done a sendto() to ship a UDP packet > from your server to one of the clients, presumably "dexter". That call > reported back "Connection refused", which Amanda retried several times > but eventually gave up on. > > I've added a whole lot more debugging messages in the network code. > Is there any chance I could convince you to get the latest 2.4.2 CVS > sources and at least build them (you would not need to actually install)? > You could "chown root" and "chmod u+s" that version of amcheck and run it > from the build area (make sure you use the binary, not the funny shared > library wrapper script of the same name, but use the wrapper script to > run it, or you can build with --disable-shared to turn all this off just > for testing), then look at /tmp/amanda/amcheck*debug to see what it did. > > >BTW: The isn't a new one and nothing changed in the environment. > > Yeah, right. How often have I heard that story. :-) > > Clearly something related to "dexter" has changed that is causing packets > to not be able to be delivered (in fact, they are being explicitly > refused). I'd start checking that client to make sure inetd is happy > and listening to the Amanda port, that there are no firewall problems, > that the name <-> IP mapping is right from the server, and so on. > > >Paolo > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: error message help.
>send req failed: Connection refused >protocol packet receive: Connection refused >protocol packet receive: Connection refused I can tell you what Amanda is doing, but not why your system is reporting this error to Amanda. Amanda has created a socket and then done a sendto() to ship a UDP packet from your server to one of the clients, presumably "dexter". That call reported back "Connection refused", which Amanda retried several times but eventually gave up on. I've added a whole lot more debugging messages in the network code. Is there any chance I could convince you to get the latest 2.4.2 CVS sources and at least build them (you would not need to actually install)? You could "chown root" and "chmod u+s" that version of amcheck and run it from the build area (make sure you use the binary, not the funny shared library wrapper script of the same name, but use the wrapper script to run it, or you can build with --disable-shared to turn all this off just for testing), then look at /tmp/amanda/amcheck*debug to see what it did. >BTW: The isn't a new one and nothing changed in the environment. Yeah, right. How often have I heard that story. :-) Clearly something related to "dexter" has changed that is causing packets to not be able to be delivered (in fact, they are being explicitly refused). I'd start checking that client to make sure inetd is happy and listening to the Amanda port, that there are no firewall problems, that the name <-> IP mapping is right from the server, and so on. >Paolo John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Thanks John,
John, You are always such a great help in this mailing list, do you have a pay pal account? I'd like to buy you a drink or a pizza or at least send you the money for one :) I cc'd the list in case anyone else would like to express their gratitude but haven't thought of how to do it yet. -- Jeff Bearer, RHCE Webmaster PittsburghLIVE.com
Re: About amlabel
>How to change the tape label with same configure file ? for example, change >label from tape-01 to tape-91. >How to relabel the tape with different configure file? for example, from >tape-01 to backup-01. In either case, you should probably run amrmtape to make sure the old label is not referenced, then you can just run amlabel (with the -f option to force the change) to write a new label. Note that doing either of these may confuse your tape cycle, i.e. what tape Amanda uses next. See my recent posts on how the tapelist file is managed. >--weihai John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
error message help.
Hi I've started getting an error when running amcheck: amcheck weekly Amanda Tape Server Host Check - WARNING: /mnt/amanda/dumps: only 2024816 KB free (4194304 KB requested). NOTE: skipping tape-writable test. Tape week1 label ok. Server check took 8.778 seconds. send req failed: Connection refused < protocol packet receive: Connection refused < protocol packet receive: Connection refused < Amanda Backup Client Hosts Check WARNING: dexter: selfcheck request timed out. Host down? Client check: 7 hosts checked in 30.387 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) Until today I had no problems what so ever with amanda. Can anyone please explain why it started. BTW: The isn't a new one and nothing changed in the environment. Paolo
About amlabel
Hi, How to change the tape label with same configure file ? for example, change label from tape-01 to tape-91. How to relabel the tape with different configure file? for example, from tape-01 to backup-01. Thanks. Regards, --weihai
