I'm having problems with amstatus on machines that I have upgraded to
relativly new versions of perl:
Script started on Thu Mar 1 03:04:13 2001
amanda@debian:~$ amstatus DailyDump
Name "main::exec_prefix" used only once: possible typo at
/usr/local/amanda/sbin/amstatus line 15.
Modification
I'm trying to get chg-zd-mtx to work with my HP tapechanger.
I't not working and I am trying to debug where the problem lies. I would
like to just run the changer script by hand, and see what results I get.
Unfortuantely I can't seem to figure out how to do this. I would have
thought oone of the
Hello, all,
Amanda 2.4.2 running on two HP 735 servers running HP-UX 10.20 servers.
I'm using gnutar 1.3.18 with the Amanda-recommended patches. The tape
drives are an Exabyte 8505XL on one system and an Ecrix VXA-1 on the
other.
The problem: On occasion, intermittently and not always on the
On the fileserver (Tapeserver) amrecover give me no output ...
Huh? No output at all???
The file has 0 Bytes :-( ...
What file? The amrecover program?
The first place to look is /tmp/amanda/amindexd*debug on the server.
The result of this run is :
amindexd: debug 1 pid 3228 ruid 560
Hello.
I am trying to help out a friend of mine. His
company is Rational Professionals.
A long time ago, I was doing alot of research on
rational clearcase. I collected alot of research
materials and had your email address on the
discussion. If you are interested, please respond
with a
See my other e-mail -- the shipping version of chg-zd-mtx doesn't work with
modern versions of mtx. Use either the barcode-enabled version someone
posted, or the version at
http://www.noc.isite.net/?Projects
I keep meaning to integrate the two versions into one, but just haven't had
time
As others have said, it uses the TAPE environment variable. I wish we could
convince the maintainer to use CHANGER instead, so it doesn't conflict with
mt's TAPE environment variable sigh
Anyway, make sure you are using either the version we made
http://www.noc.isite.net/?Projects
or
The problem: On occasion, intermittently and not always on the same tape,
both servers will abort the backup almost as soon as it begins with a
complaint that the tape is full. ...
Details, please. What **exactly** did Amanda say? Did it say it got
an I/O error, for instance?
In any case,
The owner and group was amanda and disk respectively. The amanda services is
setup to run as user amanda and as group disk in xinetd.d/amanda. When I
chown root.root amandates sendsize works. But now sendbackup.debug is
giving: error [opening /etc/amandates: Permission denied]. ...
Here's how I
"Jonathan" == Jonathan Dill [EMAIL PROTECTED] writes:
Jonathan In case you haven't heard, don't open that Snow White attachment! I'll
Jonathan send more details shortly so you know this isn't a hoax...
I would have thought that by now, users would have been sufficiently
slapped around the
IMHO, anyone who insists on using the software that's vulnerable to such
attacks deserves to lose.
"Anthony A. D. Talltree" wrote:
IMHO, anyone who insists on using the software that's vulnerable to such
attacks deserves to lose.
OTOH the amanda-users list doesn't deserve to lose if someone is dumb
enough to open the attachment, gets infected, and sends all kinds of
crap back to the list.
I'll change it in the chg-zd-mtx.sh.in tomorrow, and post a patch
against the current CVS tree to here and amanda-hackers. The last one I
posted was based off the one you listed below, and I did my best not to
alter how it worked with non-barcode drives and whatnot. If you want to
build off
Just noticed that the barcode enabled chg-zd-mtx.sh.in has been added to
the CVS tree, so if you can test it sometime soon, I'll post any errors
you find along with the $TAPE - $CHANGER naming from the last message.
The drive I had to test with worked with or without the barcode, but
better safe
On Mar 1, 2001, Darin Dugan [EMAIL PROTECTED] wrote:
At 07:27 AM 3/1/2001, Stan Brown wrote:
amanda@debian:~$ amstatus DailyDump
Name "main::exec_prefix" used only once: possible typo at
/usr/local/amanda/sbin/amstatus line 15.
Modification of a read-only value attempted at
Well this did not seem to work either. I ran up2date to get all of the
latest updates then reinstalled the amanda package. This now worked. It
appears that something was in the way. Wish I knew what is was so this could
be more helpful.
James
-Original Message-
From: [EMAIL PROTECTED]
Don't know if this problem has been solved for you, but if you are using
hosts.allow/deny, you may find it necessary to permit aanda access in
hosts.allow.
For me, simply adding to hosts.allow
amandad: (ip of backup host)
worked a treat.
On Wed, 21 Feb 2001, John R. Jackson wrote:
...
Hi!
Huh? No output at all???
The file has 0 Bytes :-( ...
What file? The amrecover program?
Yes, and i don't know why amrecover has 0 Byte. Bu i have a copy :-)
The first place to look is /tmp/amanda/amindexd*debug on the server.
The result of this run is :
amindexd: debug 1 pid
Hi. I am having a chronic problem with some file systems which are
active all of the time. I am running gnu-tar 1.13.19 with amanda
2.4.1p1, and it returns 2, which causes amanda to fail.
In looking over the archives of mail messages on the subject, it seems
like there are two solutions. I
19 matches
Mail list logo
