Re: Dump Program Not available
On Sat, Jun 01, 2002 at 02:08:30PM -0400, Kaan Saldiraner wrote: > Hello, > > Thanks for the responce .. I ran this command while su - to amanda > > export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin > > Now amanda user can infact run the dump and restore without doing /sbin/dump > ..etc. > > But when i do amcheck on my server It is still giving me the same error. > > DUMP Porgram not available > RESTORE program not available > >>> End of included message <<< Amcheck and friends do not use the PATH variable for find "dump" or "tar". They are hardcoded as absolute paths at compile time. To see what has been compiled in, look at the file /config/config.h There will be two line #define DUMP and #define GNUTAR. These defines are where amcheck is failing to find the programs. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Dump Program Not available
On Sat, Jun 01, 2002 at 06:09:07PM -0500, Frank Smith wrote: > Amanda uses the full path to all the backup/restore programs that it was > configured with (and are fixed at compile time). So if Amanda was built > with your dump program as /usr/sbin/dump. but now it is /sbin/dump or > /usr/local/bin/dump, then you will get the 'program not available' error > even though 'dump' is somewhere in the Amanda user's path. (Disclaimer: > I'm a 'tar' user, and am assuming Amanda deals with ufsdump, vxdump, and > other variants of dump in a similar way to the way it finds GNU tar.) >Somewhere near the beginning of /tmp/amanda/amandad.*.debug you can > find the full command path that Amanda is trying to run. You can then > either make a link from there to the real program, or (probably better > for the long term) rebuild Amanda with the correct path. > > Good luck, > Frank > > --On Saturday, June 01, 2002 14:08:30 -0400 Kaan Saldiraner <[EMAIL PROTECTED]> >wrote: > > > Hello, > > > > Thanks for the responce .. I ran this command while su - to amanda > > > > export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin > > > > Now amanda user can infact run the dump and restore without doing /sbin/dump > > ..etc. > > Look in your config header file, /config/config.h, for the path compiled in for the "#define's" of DUMP and GNUTAR. These absolute paths are what amcheck and friends are using. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Dump Program Not available
Amanda uses the full path to all the backup/restore programs that it was configured with (and are fixed at compile time). So if Amanda was built with your dump program as /usr/sbin/dump. but now it is /sbin/dump or /usr/local/bin/dump, then you will get the 'program not available' error even though 'dump' is somewhere in the Amanda user's path. (Disclaimer: I'm a 'tar' user, and am assuming Amanda deals with ufsdump, vxdump, and other variants of dump in a similar way to the way it finds GNU tar.) Somewhere near the beginning of /tmp/amanda/amandad.*.debug you can find the full command path that Amanda is trying to run. You can then either make a link from there to the real program, or (probably better for the long term) rebuild Amanda with the correct path. Good luck, Frank --On Saturday, June 01, 2002 14:08:30 -0400 Kaan Saldiraner <[EMAIL PROTECTED]> wrote: > Hello, > > Thanks for the responce .. I ran this command while su - to amanda > > export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin > > Now amanda user can infact run the dump and restore without doing /sbin/dump > ..etc. > > But when i do amcheck on my server It is still giving me the same error. > > DUMP Porgram not available > RESTORE program not available > > Thanks, > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Saturday, June 01, 2002 8:07 AM > To: Kaan Saldiraner > Subject: RE: Dump Program Not available > > > It sounds like your environment for the amanda user does not have the path > to > the dump command. "su -" to the amanda user account and see if you can run > dump from the command line. If not you need to add it to the path for the > amanda user. > > Just my 2 cents. > > Wade > > > >> Hello, >> >> Thanks for the response but i think that the solution that you have gave > me >> is for something else... Thanks for your response .. >> My problem is that amanda doesn't see that the machine has Dump already.. >> Maybe permission problem >> >> -Original Message- >> From: Gene Heskett [mailto:[EMAIL PROTECTED]] >> Sent: Friday, May 31, 2002 8:37 PM >> To: Kaan Saldiraner; [EMAIL PROTECTED] >> Subject: Re: Dump Program Not available >> >> >> On Friday 31 May 2002 05:21 pm, Kaan Saldiraner wrote: >> > Hello, >> > >> > I just installed a client and when i do amcheck for the Server it >> > gives me this error >> > >> > ERROR: machine.domain.com: [DUMP program not available] >> > ERROR: machine.domain.com: [RESTORE program not available] >> > >> > I rpmed the dump program and recompiled amanda on the client after >> > and still the same error >> > >> > Any ideas?? >> > >> > Thanks >> > >> > Kaan Saldiraner >> > Steltor Inc. >> > (514)733-8500 x6503 >> > www.steltor.com >> >> Either see if its listed in inetd.conf if your system usesd inetd, >> or see if there is an amanda in /etc/xinetd.d. If so, edit it to >> change the disable = yes line to disable = no, then restart >> /etc/rc.d/int.d/xinetd. >> >> -- >> Cheers, Gene >> AMD K6-III@500mhz 320M >> Athlon1600XP@1400mhz 512M >> 98.96+% setiathome rank, not too shabby for a hillbilly >> >> >> >> > > > - > This message was sent using Endymion MailMan. > http://www.endymion.com/products/mailman/ > > > > -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Dump Program Not available
Hello, Thanks for the responce .. I ran this command while su - to amanda export PATH=$PATH:/usr/sbin/:/usr/local/bin:/sbin:/bin Now amanda user can infact run the dump and restore without doing /sbin/dump ..etc. But when i do amcheck on my server It is still giving me the same error. DUMP Porgram not available RESTORE program not available Thanks, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 01, 2002 8:07 AM To: Kaan Saldiraner Subject: RE: Dump Program Not available It sounds like your environment for the amanda user does not have the path to the dump command. "su -" to the amanda user account and see if you can run dump from the command line. If not you need to add it to the path for the amanda user. Just my 2 cents. Wade > Hello, > > Thanks for the response but i think that the solution that you have gave me > is for something else... Thanks for your response .. > My problem is that amanda doesn't see that the machine has Dump already.. > Maybe permission problem > > -Original Message- > From: Gene Heskett [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 31, 2002 8:37 PM > To: Kaan Saldiraner; [EMAIL PROTECTED] > Subject: Re: Dump Program Not available > > > On Friday 31 May 2002 05:21 pm, Kaan Saldiraner wrote: > >Hello, > > > >I just installed a client and when i do amcheck for the Server it > > gives me this error > > > >ERROR: machine.domain.com: [DUMP program not available] > >ERROR: machine.domain.com: [RESTORE program not available] > > > >I rpmed the dump program and recompiled amanda on the client after > > and still the same error > > > >Any ideas?? > > > >Thanks > > > >Kaan Saldiraner > >Steltor Inc. > >(514)733-8500 x6503 > >www.steltor.com > > Either see if its listed in inetd.conf if your system usesd inetd, > or see if there is an amanda in /etc/xinetd.d. If so, edit it to > change the disable = yes line to disable = no, then restart > /etc/rc.d/int.d/xinetd. > > -- > Cheers, Gene > AMD K6-III@500mhz 320M > Athlon1600XP@1400mhz 512M > 98.96+% setiathome rank, not too shabby for a hillbilly > > > > - This message was sent using Endymion MailMan. http://www.endymion.com/products/mailman/
ftape error or Amanda error
HI, I am running Amanda-2.4.2p2 and it works fine. I am also currently running ftape-4.x-2002_03_21 that I expanded from a tar ball. It runs fine. My problem is that just recently I get the following errors in my syslog: May 28 18:26:49 stud kernel: [210] 0 ftape-io.c (ftape_report_error) - ftape_report_operation(ftape, &code, QIC_REPORT_ERROR_CODE, 16) failed: -5. May 28 18:26:49 stud kernel: [211] 0 ftape-ctl.c (ftape_get_drive_status) - report_error_code failed: -5. May 28 18:26:51 stud kernel: [220] 0 ftape-io.c (ftape_report_raw_drive_status) - report_operation failed after 4 trials. May 28 18:26:51 stud kernel: [221] 0 ftape-io.c (ftape_wakeup_drive) - ftape_report_raw_drive_status(ftape, &status) failed: -5. May 28 18:26:51 stud kernel: [222] 0 ftape-io.c (ftape_reset_drive) - Wakeup failed !. May 28 18:26:53 stud kernel: [231] 0 ftape-io.c (ftape_report_raw_drive_status) - report_operation failed after 4 trials. May 28 18:26:53 stud kernel: [232] 0 ftape-io.c (ftape_ready_wait) - ftape_report_raw_drive_status(ftape, status) failed: -5. Unusual System Events =-=-=-=-=-=-=-=-=-=-= May 28 18:26:27 stud kernel: fdc-internal.c: fdc_internal_register @ 0xf0862c40. May 28 18:26:27 stud kernel: [154] 0 fdc-internal.c (fdc_int_detect) - fdc[0] base: 0x03f0, irq: 6, dma: 2. May 28 18:26:27 stud kernel: [160] 0 fdc-io.c (fdc_probe) - Type 82077AA FDC found. May 28 18:26:28 stud kernel: [161] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:29 stud kernel: [164] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:30 stud kernel: [166] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:31 stud kernel: [168] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:32 stud kernel: [170] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:33 stud kernel: [172] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:34 stud kernel: [174] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:34 stud kernel: [176] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:35 stud kernel: [178] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:36 stud kernel: [180] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:37 stud kernel: [182] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:38 stud kernel: [184] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:39 stud kernel: [186] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:40 stud kernel: [188] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:40 stud kernel: [190] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:41 stud kernel: [192] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:42 stud kernel: [194] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:43 stud kernel: [196] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:44 stud kernel: [198] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:45 stud kernel: [200] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:46 stud kernel: [202] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:46 stud kernel: [204] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:47 stud kernel: [206] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:48 stud kernel: [208] 0 ftape-ctl.c (ftape_get_drive_status) - error status set. May 28 18:26:49 stud kernel: [209] 0 ftape-io.c (ftape_report_operation) - missing status stop bit. May 28 18:26:49 stud kernel: [210] 0 ftape-io.c (ftape_report_error) - ftape_report_operation(ftape, &code, QIC_REPORT_ERROR_CODE, 16) failed: -5. May 28 18:26:49 stud kernel: [211] 0 ftape-ctl.c (ftape_get_drive_status) - report_error_code failed: -5. May 28 18:26:50 stud kernel: [212] 0 ftape-io.c (ftape_report_operation) - No acknowledge after 300 msec. (96 iter). May 28 18:26:50 stud kernel: [213] 0 ftape-io.c (ftape_report_operation) - timeout on Acknowledge. May 28 18:26:51 stud kernel: [214] 0 ftape-io.c (ftape_report_operation) - No acknowledge after 300 msec. (96 iter). May 28 18:26:51 stud kernel: [215] 0 ftape-io.c (ftape_report_operation) - timeout on Acknowledge. May 28 18:26:51 stud kernel: [216] 0 ftape-io.c (ftape_report_operation) - No acknowledge after 300 msec. (96 iter). May 28 18:26:51 stud kernel: [217] 0 ftape-io.c (ftape_report_operation) - timeout on Acknowledge. May 28 18:26:51 stud kernel: [218] 0 ftape-io.c (ftape_report_operation) - No acknowledge after 300 msec. (96 iter). May 28 18:26:51 stud kernel: [219] 0 ftape-io.c (ftape_report_
