planner: ERROR Request to servername timed out.
Hello List, i followed this howto: http://ubuntuforums.org/showthread.php?p=2470030 to set up amanda on ubuntu. Now i get the error: -- These dumps were to tape DailySet1-10. The next tape Amanda expects to use is: a new tape. The next new tape already labelled is: DailySet101. FAILURE AND STRANGE DUMP SUMMARY: servername /usr RESULTS MISSING planner: ERROR Request to servername timed out. amcheck shows: -- Amanda Tape Server Host Check - Holding disk /tmp: 8679924 kB disk space available, that's plenty amcheck-server: slot 12: date 20070617 label DailySet1-12 (active tape) amcheck-server: slot 13: date Xlabel DailySet1-13 (new tape) NOTE: skipping tape-writable test Tape DailySet1-13 label ok NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run. NOTE: index dir /var/lib/amanda/DailySet1/index/servername: does not exist NOTE: it will be created on the next run. Server check took 0.046 seconds Any idea why i get this error? What could i do to debug this? Cheers, Mario
Re: planner: ERROR Request to servername timed out.
Hi,
[EMAIL PROTECTED] schrieb:
> FAILURE AND STRANGE DUMP SUMMARY:
> servername /usr RESULTS MISSING planner: ERROR Request to servername
> timed out.
- Is amandad running?
Check with "netstat -an | grep 10080".
- Is the server allowed to connect to the client?
Check if there`s a line like
servername amanda amdump
in .amandahosts
- Any errors in debug* files in /tmp/amanda?
- Do you have multiple interfaces and bind it to the one amanda wants to
connect.
> amcheck shows
Did you run amcheck -c or -s?
Maybe if you run -s (server only) then amanda did not connect to the
client (even if it runs on the same host, like in your environment).
Can you send the output of "amadmin {config} disklist"? Which auth are you
using? Also please send your xinetd configuration for amanda services.
Regards
Marc
--
Marc Muehlfeld (Leitung Systemadministration)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78
http://www.medizinische-genetik.de
Re: Amanda Backup fails possible card errors
Hi Olivier and Jon, > > > > Hi, > > > > Are the tape new? > > > > Did you try different tape? > > > > Did you try to write to the tape "by hand": tar cf /dev/st0 ... > > > > I see that your SCSI card is Ultra 160 but your tape drive is only > > fast wide, do you have any disk pluged in that SCSI interface? It > > should work, but who knows, if you can (have 2 SCSI interface) > > separate fast disks, from slow tape. > > > The SCSI cards I've used will just go the speed of the slowest device. So if you have a 15K RPM Drive and a backup tape drive attached. The tape drive is going to make that hard drive lag. The hard drive is a SATA drive so only the tape drive is attached to the the SCSI card. > > > So i'm finally left with the proverbial question: is it hardware or > > > software? > > The log messages don't sound like software to me, > except maybe the scsi driver. > > Continuing Oliver's train > > > > The tape drive is a few years old the rest of the hardware is brand new. > > I'd guess the SCSI terminator was left on the tape drive from the old > configuration. Is a fast/wide terminator appropriate for the current > Ultra 160 configuration? > > Time to sacrifice a goat to the scsi gods and check all the cables, > terminators, board seatings & settings, and driver & firmware updates. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) I'll try sending some data direct, as i can do that from my office. >From what you have both said re: the different SCSI types. I think I remember the onsite tech used the old cable. I'll most likely need to schedule a visit and check the cables and terminator. Thanks for the pointers. ram. --- ram smith, systems manager tilda communications a division of software holdings pty ltd p (02) 9280 0258 f (02) 9280 0259 e [EMAIL PROTECTED] w http://www.tilda.com.au level 1, 10 grafton st chippendale nsw 2008
Re: FAILURE AND STRANGE DUMP SUMMARY
fedora wrote: > > Hi guys. I am newbie here. I got problem with my Amanda. > > here is the result in mail report: > > FAILURE AND STRANGE DUMP SUMMARY: > ind.ayo.com/var/lib/mysql lev 0 STRANGE > > > STATISTICS: All OK. Showed the progress > > > FAILED AND STRANGE DUMP DETAILS: > > /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE > sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] > sendbackup: info BACKUP=/bin/tar > sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... > sendbackup: info COMPRESS_SUFFIX=.gz > sendbackup: info end > | gtar: ./mysql.sock: socket ignored > ? gtar: ./mysql/general_log.CSV: file changed as we read it > | Total bytes written: 562432000 (537MiB, 7.7MiB/s) > sendbackup: size 549250 > sendbackup: end > > > NOTES: > planner: Full dump of ind.ayo.com:/var/lib/mysql promoted from 5 days > ahead. > taper: tape DailySet1-04 kb 2727712 fm 10 [OK] > > DUMP SUMMARY: >DUMPER STATS TAPER > STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS > KB/s > -- - > - > ind.ayo -/lib/mysql 0 549250 301765.51:10 429.8 0:00 > 154753.5 > > Nothing errors in debug files. Can u guys tell me how come Amanda still > complaining failed and strange whereas dump summary looks OK even I can > recover the backup files. > > Any ideas guys?? > > > I got new problem: These dumps were to tape DailySet1-13. The next tape Amanda expects to use is: DailySet1-14. FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] cpu.ind.com /var/lib/mysql lev 0 was successfully retried can anyone explain to me? -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11169793 Sent from the Amanda - Users mailing list archive at Nabble.com.
Re: FAILURE AND STRANGE DUMP SUMMARY
> FAILURE AND STRANGE DUMP SUMMARY: > cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by > peer] Means that Amanda client on cpu.ind.com closed connection with Amanda server before the dump (or estimate was finished). Olivier
Re: FAILURE AND STRANGE DUMP SUMMARY
Hi, fedora schrieb: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] Maybe the client was rebooted during the backup or xinetd restarted. cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0 instead of 32768] The server didn't send an estimate or backup, because of a maybe reboot. cpu.ind.com /var/lib/mysql lev 0 was successfully retried Everything was done fine. Amanda retried successfully. Regards Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
