Steven,
Let me know if the patch works or not.
Jean-Louis
On 01/06/2014 01:13 PM, Jean-Louis Martineau wrote:
Try this patch, chg-robot retry the mtx command if it failed with 'No
Sense'.
Jean-Louis
On 01/06/2014 01:04 PM, Steven Backus wrote:
The complete output of mtx is not logged, run
running amcheck
2. amtape-shows-slot-empty-but-mtx-doesn-t
3. chg-robot retry the mtx command if it failed with 'No Sense'
--
All the patches worked great, I'm all fixed up now. Thanks
Jean-Louis.
Steve
Jean-Louis writes:
Let me know if the patch works or not.
There were 3 patches:
1. Transient data-path errors when running amcheck
2. amtape-shows-slot-empty-but-mtx-doesn-t
3. chg-robot retry the mtx command if it failed with 'No Sense'
--
All the patches worked great, I'm all fixed up now
Amanda can't fix bug in the scsi hardware/firmware.
It's possible there's a scsi bug but since it always works the
2nd time hopefully more of a timing issue.
Post the amtape debug file when it fail.
amtape.20140106091626.debug:
Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: pid 12109 ruid
Steven,
The complete output of mtx is not logged, run it on the command line to
get the complete output:
/usr/sbin/mtx -f /dev/changer nobarcode status
'it always works the 2nd time', Did it always works the 3rd and 4th
time? When is the first time?
Jean-Louis
On 01/06/2014 12:27 PM,
The complete output of mtx is not logged, run it on the command line to
get the complete output:
/usr/sbin/mtx -f /dev/changer nobarcode status
Storage Changer /dev/sg6:1 Drives, 7 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded)
Storage Element
Try this patch, chg-robot retry the mtx command if it failed with 'No
Sense'.
Jean-Louis
On 01/06/2014 01:04 PM, Steven Backus wrote:
The complete output of mtx is not logged, run it on the command line to
get the complete output:
/usr/sbin/mtx -f /dev/changer nobarcode status
Huh! I had a couple of instances of it's empty / no it isn't and deleted
my changerfile. This fixed it, but perhaps I should also try your patch. I was
sharing the drive and the changerfile between 2 configurations (a daily and an
archive) and thought I might have caused my problems by doing
On 12/30/2013 10:46 AM, Steven Backus wrote:
The problem I'm having with both chg-zd-mtx and chg-robot is the
drive doesn't become ready in time. The first amcheck alwayws
fails but the 2nd one succeeds. I've tried various delay settings
to both without success. It' an Ultrium robot, any
Since upgrading to 3.3.5 I occasionally get errors of this nature:
ERROR: whimsy.med.utah.edu sdc1: data-path is AMANDA but device do not support
it
upon re-running amcheck the errors go away. When they do appear,
there are errors of this type generated for each entry in my
disklist. Any
On Thu, 11 Oct 2012 Toomas Aas wrote:
On Wed, 10 Oct 2012, Charles Curley wrote:
I believe running amcheck during an amdump run is a harmless error.
It doesn't probably do any harm, but it turns out that in this case
the mail report is still sent, containing these warnings:
WARNING
On Thu, Oct 11, 2012 at 08:15:15PM +0300, Toomas Aas wrote:
On Thu, 11 Oct 2012 Toomas Aas wrote:
On Wed, 10 Oct 2012, Charles Curley wrote:
I believe running amcheck during an amdump run is a harmless error.
It doesn't probably do any harm, but it turns out that in this
case
On Thu, Oct 11, 2012 at 20:15:15 +0300, Toomas Aas wrote:
Which leads me to next question - what is the best way to detect, in
a script, that amdump or amflush is running? Off the top of my head
I can only think of something like 'ps | grep amdump', but that
doesn't seem very elegant. I tried
On Wed, 10 Oct 2012, Charles Curley wrote:
I believe running amcheck during an amdump run is a harmless error.
It doesn't probably do any harm, but it turns out that in this case
the mail report is still sent, containing these warnings:
WARNING: skipping tape test because amdump
I'm thinking about setting up an 'amcheck -m' run for early morning.
This is a remote site doing backups to external USB hard disk, and
they tend to forget to replace the disk once a week, so I'd like to
have the FIX BEFORE RUN IF POSSIBLE e-mail waiting for them first
thing in the
On Wed, 10 Oct 2012 Charles Curley wrote:
However, I suspect that swapping out the vtape drive will cause
problems for amanda. For example, if you try a restore but the file to
be restored is on the swapped out disk, amanda will likely get
confused. It will be looking for a vtape that isn't
Greetings;
This doesn't look terribly comforting, and occurred apparently at the amcheck
phase of a script I wrote to install new amanda snapshots:
Aug 24 10:35:34 coyote xinetd[2394]: Starting reconfiguration
Aug 24
On Monday 24 August 2009, Gene Heskett wrote:
Greetings;
This doesn't look terribly comforting, and occurred apparently at the
amcheck phase of a script I wrote to install new amanda snapshots:
Aug 24 10:35:34 coyote xinetd[2394]: Starting reconfiguration
Aug 24 10:35:34 coyote xinetd[2394]:
Hello All-
I am running into another issue while running 'amcheck' on one of my
sets; I've checked msg boards and the wiki for the answer to this, but
I'm still not sure where the problem is.
The error is on the client (which is the same machine as the server):
WARNING: ottawa: selfcheck
I should probably also say that I'm working with version 2.5.2.
And that I verified the Amanda services are in the /etc/services file.
Thanks again!
Jeanna Geier wrote:
Hello All-
I am running into another issue while running 'amcheck' on one of my
sets; I've checked msg boards and the wiki
Jeanna Geier wrote:
Thanks
for the reply.
I'm running './amcheck DailySet3', so I looked in the
/tmp/amanda/server/DailySet3 file, but it's emptyit's there, but
nothing in it.
Any ideas on how to proceed?
Thanks again!
-j.g.
Mario Silva wrote:
Check
while running 'amcheck' on one of my
sets; I've checked msg boards and the wiki for the answer to this, but
I'm still not sure where the problem is.
The error is on the client (which is the same machine as the server):
WARNING: ottawa: selfcheck request failed: timeout waiting for ACK.
I've
running into another issue while running 'amcheck' on one of my
sets; I've checked msg boards and the wiki for the answer to this, but
I'm still not sure where the problem is.
The error is on the client (which is the same machine as the server):
WARNING: ottawa: selfcheck request failed: timeout
On Friday 24 August 2007, Jeanna Geier wrote:
Sure, sorry for leaving that information out!
./configure --with-index-server=ottawa --with-user=amanda
--with-group=amanda --prefix=/usr/local/amanda_2.5.2 --sysconfdir=/etc
And, I did a search for the '.amandahosts' file, and it doesn't seem to
be
Hello all:
Problem:
Running amcheck, all hosts on one subnet timeout:
host selfcheck request failed: timeout waiting for ACK
Things I thought were odd: (common to all hosts in this subnet)
1. none of them ever created the /tmp/amanda folder or any debug info.
1a. I created them by hand
Hi,
Running amcheck, all hosts on one subnet timeout:
host selfcheck request failed: timeout waiting for ACK
I don't see you mentionning any .amandahosts on the clients... As
/tmp/amanda was not created, maybe .amandahosts was not either.
Best regards,
Olivier
the gateway to the /etc/hosts file on all servers in
the subnet, (they read the file before the DNS) and everything works.
-Peter Farrell
On 23/08/06, Peter Farrell [EMAIL PROTECTED] wrote:
Hello all:
Problem:
Running amcheck, all hosts on one subnet timeout:
host selfcheck request failed: timeout
Hi all,
I just added a few more items to back up from a particular server (that
has, up 'til now, been working fine), but running amcheck now causes
/usr/lib/amanda/selfcheck to hang on the server in question. I see the
following in the process listing:
16255 ?Ss 0:00 /usr/sbin
Hi I am running SuSE Linux Enterprise server 9.
I will install from the default amanda rpm I would prefer to use the
source though.
I have read a dit about readline and it is required if I intend to use
amrecover.
Cheers
On Mon, 2005-05-16 at 13:44 -0400, Matt Hyclak wrote:
On Mon, May 16,
On Tue, May 17, 2005 at 09:57:08AM +0100, Chuck Amadi Systems Administrator
enlightened us:
I am running SuSE Linux Enterprise server 9.
I will install from the default amanda rpm I would prefer to use the
source though.
I have read a dit about readline and it is required if I intend to
Hi, Matt Hyclak,
on Dienstag, 17. Mai 2005 at 13:55 you wrote to amanda-users:
MH On Tue, May 17, 2005 at 09:57:08AM +0100, Chuck Amadi Systems Administrator
enlightened us:
I am running SuSE Linux Enterprise server 9.
I will install from the default amanda rpm I would prefer to use the
Hi I run make distclean and reconfigured and I noticed the following
which running ./configure I choose the following where Amanda will live.
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-gnu-ld \
--prefix=/local/sw/amanda/bckup \
On Mon, May 16, 2005 at 05:31:03PM +0100, Chuck Amadi enlightened us:
I run make distclean and reconfigured and I noticed the following
which running ./configure I choose the following where Amanda will live.
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
Hi cheers for that
I have less less /local/sw/src/amanda-2.4.4p4/config.log
here is part of the /readline arguments.
And as you are aware hell of alot of data mostly stating no file or
directory found and last but not least READLINE_LIBS=
configure:27608: checking readline.h usability
On Mon, May 16, 2005 at 06:31:34PM +0100, Chuck Amadi Systems Administrator
enlightened us:
cheers for that
I have less less /local/sw/src/amanda-2.4.4p4/config.log
here is part of the /readline arguments.
And as you are aware hell of alot of data mostly stating no file or
directory
Hi When I run ./configure
I got these errors
checking readline.h usability... no
checking readline.h presence... no
checking for readline.h... no
checking readline/history.h usability... no
checking readline/history.h presence... no
checking for readline/history.h... no
checking
--On Monday, May 16, 2005 17:31:03 +0100 Chuck Amadi [EMAIL PROTECTED] wrote:
Hi I run make distclean and reconfigured and I noticed the following
which running ./configure I choose the following where Amanda will live.
./configure --with-user=amanda \
--with-group=disk \
On Mon, 16 May 2005 at 6:31pm, Chuck Amadi Systems Administrator wrote
And as you are aware hell of alot of data mostly stating no file or
directory found and last but not least READLINE_LIBS=
configure:27608: checking readline.h usability
configure:27620: gcc -c -D_FILE_OFFSET_BITS=64 -g
Hi, Matt,
on Montag, 16. Mai 2005 at 19:04 you wrote to amanda-users:
configure: WARNING: *** No terminal library, no history and command line
editing in amrecover!
configure: WARNING: *** vtblc headers not found - no QIC volume table
support!
You only need that with QIC-tapes.
I have
I hope this is encouraging
myserver:/local/sw/amanda/bckup/libexec # su amanda -c
/local/sw/amanda/bckup/sbin/amcheck DailySet1
Amanda Tape Server Host Check
-
WARNING: program /local/sw/amanda/bckup/libexec/planner: not setuid-root
WARNING: program
Hi again
I am getting somewhere after a battle of some sorts but I have a few
more errors. I have
myserver:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck DailySet1
Amanda Tape Server Host Check
-
WARNING: program /usr/sbin/amcheck: not setuid-root
Holding disk
On Thu, Apr 14, 2005 at 02:13:35PM +0100, Chuck Amadi wrote:
Hi again
I am getting somewhere after a battle of some sorts but I have a few
more errors. I have
myserver:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck DailySet1
Amanda Tape Server Host Check
-
hi,
I just reported this to a gentoo-linux bugtracker and think you might also be
interested ;)
Thanks in advance for having a look.
http://bugs.gentoo.org/show_bug.cgi?id=72919
Summary: amandad segfaults (via inetd) while running amcheck
Product: Gentoo Linux
Version
Hello
I have encountered the error below while testing the amanda backup software.
Amanda Backup Client Hosts Check
ERROR: osama: [could not access hda6 (hda6): No such file or directory]
Client check: 1 host checked in 0.026 seconds, 1 problem found
Excerpt of
while running amcheck/amdump
Hello
I have encountered the error below while testing the amanda backup
software.
Amanda Backup Client Hosts Check
ERROR: osama: [could not access hda6 (hda6): No such file or directory]
Client check: 1 host checked in 0.026
Subject: Re: Fw: Error while running amcheck/amdump
Madhvi Gokool wrote:
The client is running Linux 8.0 (ext3 filesystem) as shown below :
LABEL=/ / ext3defaults
1 1
LABEL=/boot /boot ext3defaults
1 2
LABEL=/home
Madhvi Gokool wrote:
The /dev/hda6 mountpoint is /
I have added the mount point to the disklist file . The dumptype was set to
tar and then dump. amcheck detected no errors on the client host.
When amdump was run , a level 0 dump was done on /dev/hda6 ( as seen in
/etc/dumpdates).
So, you mean,
On Mon, 17 Mar 2003 at 4:56pm, Madhvi Gokool wrote
The /dev/hda6 mountpoint is /
I have added the mount point to the disklist file . The dumptype was set to
tar and then dump. amcheck detected no errors on the client host.
When amdump was run , a level 0 dump was done on /dev/hda6 ( as seen
Hi :-) - I have installed amanda 2.4.2p2 on my SuSE 7.2, just like I have
read in the
docu.
I want it to run with my onstream DI-30 tape-drive.
After installation I tried to run ./amcheck Daily, and it returned:
---
On Tue, 30 Apr 2002 [EMAIL PROTECTED] wrote:
Hi :-) - I have installed amanda 2.4.2p2 on my SuSE 7.2, just like I have
read in the
docu.
I want it to run with my onstream DI-30 tape-drive.
After installation I tried to run ./amcheck Daily, and it returned:
On Thu, 2 Nov 2000, Denise Ives wrote:
Looks like there is no problem with client connections -
but the subject header does have this BOLD warning message.
Can this be ignored?
No! You don't have a problem with your client connections, as you
realized. But have a look at the server
... the subject header does have this BOLD warning message.
Can this be ignored?
...
Subject: daily AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE
Amanda is not meant to be run without a tape and that's what it is
warning you about. Since you plan to work that way, it doesn't apply.
Note that
O.k. - I ran amcheck against my configuration file just to check things
out before tonights scheduled dump.
Looks like there is no problem with client connections -
but the subject header does have this BOLD warning message.
Can this be ignored?
Subject: daily AMANDA PROBLEM: FIX
53 matches
Mail list logo
