Re: FAILURE AND STRANGE DUMP SUMMARY
Thanks Marc. Marc Muehlfeld wrote: > > 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 > > > > -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11170958 Sent from the Amanda - Users mailing list archive at Nabble.com.
timeout waiting for ACK on amanda server
Hi NG, I use amanda 5 years and now I have mystical problem. My amanda server do backup from all my servers, PC's and notebooks except self backup. This happened few days ago. After amcheck I see this message: planner: ERROR Request to asnserv1 failed: timeout waiting for ACK In /tmp/amanda and /var/log/amanda have no files. Directories have modes: drwx--S--- 2 backup disk 1024 Jun 18 01:37 /tmp/amanda/ drwxrwx--- 4 backup backup 12288 Jun 10 09:28 /var/log/amanda/ drwx--S--- 2 backup backup 45056 Jun 10 09:37 /var/log/amanda/amandad/ In /etc/services I have: amanda 10080/tcp # amanda backup services amanda 10080/udp kamanda 10081/tcp # amanda backup services kamanda 10081/udp amandaidx 10082/tcp # amanda backup services amidxtape 10083/tcp # amanda backup services amanda.conf work for all computers except amanda server asnserv1. Thanks for help, Leonid
Re: timeout waiting for ACK on amanda server
> After amcheck I see this message: > planner: ERROR Request to asnserv1 failed: timeout waiting for ACK What system is Amanda server runnig on? What did you change few days ago? Did you reboot the machine and the problem is still there? What is the result of the following command: netstat -na |grep 10080 ping asnserv1 Best regards, Olivier
Re: timeout waiting for ACK on amanda server
Hi Oliver, asnserv1 runnig on Debian Linux 2.6.18-4-amd64 with Amanda-2.5.1p1. netstat -na |grep 10080 - do nothing. ping on asnserv1 is normal: asnserv1:/etc/amanda# ping asnserv1 PING asnserv1.localdomain (192.168.0.253) 56(84) bytes of data. 64 bytes from asnserv1.localdomain (192.168.0.253): icmp_seq=1 ttl=64 time=0.014 ms 64 bytes from asnserv1.localdomain (192.168.0.253): icmp_seq=2 ttl=64 time=0.023 ms 64 bytes from asnserv1.localdomain (192.168.0.253): icmp_seq=3 ttl=64 time=0.021 ms --- asnserv1.localdomain ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.014/0.019/0.023/0.005 ms I don't reboot server because my staff is all time work on it. On Mon, 2007-06-18 at 15:04 +0700, Olivier Nicole wrote: > > After amcheck I see this message: > > planner: ERROR Request to asnserv1 failed: timeout waiting for ACK > > What system is Amanda server runnig on? What did you change few days > ago? > > Did you reboot the machine and the problem is still there? > > What is the result of the following command: > > netstat -na |grep 10080 > > ping asnserv1 Leonid
Re: timeout waiting for ACK on amanda server
> netstat -na |grep 10080 - do nothing. Hummm, I don't use debian, but if you get nothing it would tend to mean that amandad is not running on that machine, so when the server call, nobody answers. Olivier
Re: timeout waiting for ACK on amanda server
Hi, Leonid Shulov schrieb: netstat -na |grep 10080 - do nothing. Then the service is not running. Is it running, when you restart (x)inetd? If not, then check the system logfile if there are any compliants about that service entry. If you can't fix it, then please post the error of the (x)inetd-logfile and your amanda (x)inetd configuration. 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: Virtual tape to Real tape cycles
On Fri, Jun 15, 2007 at 04:23:57PM -0400, Charlie Reitsma wrote: > As I read through the man pages I am finding hints that it has been thought > of. In the amdd man page "This may be used for debugging or to convert from > one format to another." > > I began looking at the contents of various directories and files based on > comments found in Gene's Amanda Helper scripts. The index is just a list of > files contained in the images > contained on the the tape. It wouldn't change at all as the images aren't > being modified. I couldn't find anything that maps an image file to a > particular location on a tape. It > appears that the contents of a virtual tape need no further processing before > moving them to a real tape. Copying those images onto a tape and moving the > index, curinfo and > tapelist date to another cycle seems like it might be straightforward. Since > all the image sizes are known in advance they might even be reordered more > optimally to fit on tape. I > didn't like Gene's suggestion that the virtual tape size and the real tape > size should be kept the same. We might even choose to put different file > systems on different tapes as > they may go to different offsite locations for security reasons. > > Restores appear to collect the images associated with a particular file > system and give them back to the appropriate program to extract the file(s) > requested. That process wouldn't > change just because the media changed. > > I'll take a look at the Developer Documentation to continue my exploration. Charlie -- This sounds like a great project, and I'm excited you're working on it. Please feel free to consult amanda-hackers with any further technical questions or musings you might have. The functionality you're thinking about is a form of hierarchical storage management, with data migrating between storage media based on enterprise policies and needs. It's a kind of functionality that would be welcome in Amanda, and that has been in the back of most developers' minds for some time. The new Device API will be an important step in this direction, since (among other benefits) it will allow us to treat all storage media the same way. With a little reworking, taper can then become a generic data migration tool. The major unresolved issues are: - policy (how does Amanda know when to migrate what, and where) - metadata updates (which you mentioned above) Device API: http://wiki.zmanda.com/index.php/Device_API Once the Device API is released, the immediate next step is to treat holding disk as a device. This represents Amanda's existing functionality -- dumping to holding, then spooling to tape -- as a data migration, opening the door to more complex migrations down the road. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: Virtual tape to Real tape cycles
Le lundi 18 juin 2007, vous avez écrit : [...] > > Device API: http://wiki.zmanda.com/index.php/Device_API > I've just had a look at this API. Why don't you use an API ala Linux VFS, ie, you insert your "methods" and data into a struct and then can do: gboolean mydev->start_file(Device * /* must be mydev, that's the limit */, const dumpfile_t *); instead of: gboolean device_start_file(Device *, const dumpfile_t *); ? I've used this technique quite a few times and found it to be very practical. -- Francis Galiegue, [EMAIL PROTECTED] 12bis rue de la Pierre Levée, 75011 PARIS +33143381980, +33683877875
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] 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 Olivier notes that the network connection failed, at least before the estimate was finished. Also note the third line: "Successfully retried". Check out what happens after that, as it may have gone on to successfully backup cpu.ind.com:/var/lib/mysql Rob -- Rob Echlin Software Development Environment Prime Espial IPTV rechlin -at- espial.com Phone: +1 613-230-4770 ext 1150 www.espial.com Espial Group Inc. Confidential Important Notice: This communication is intended to be received only by the individual or entity to whom or to which it is addressed and may contain information that is privileged, confidential and/or subject to copyright. Any unauthorized use, copying, review or disclosure of this communication is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender by reply email. Thank you for your cooperation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of fedora Sent: Monday, June 18, 2007 12:23 AM To: amanda-users@amanda.org Subject: 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#a1 1169793 Sent from the Amanda - Users mailing list archive at Nabble.com.
