I'm having serious problems with full restore of a GNUTAR dump. Simply
put, if I do amrestore, then tar xvf dump file, tar will exit with
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
tar: Error exit delayed from previous errors
after extracting most, but not
Again, if you need any help with the xml stuff, feel free to hand some over :-)
-Original Message-
From: [EMAIL PROTECTED] on behalf of Stefan G. Weichinger
Sent: Wed 10/13/2004 12:40 AM
To: [EMAIL PROTECTED]
Cc:
Subject:Re: newb: getting started
Hi, Frank,
on
Toralf Lund wrote:
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
37800+0 records in
37800+0 records out
gzip: stdin: invalid compressed data--crc error
tar: Child returned status 1
tar: Error exit delayed from previous errors
I've had the same message
Alexander Jolk wrote:
Toralf Lund wrote:
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
37800+0 records in
37800+0 records out
gzip: stdin: invalid compressed data--crc error
tar: Child returned status 1
tar: Error exit delayed from previous errors
I've had
* Toralf Lund [EMAIL PROTECTED] [20041013 09:43]:
Alexander Jolk wrote:
Toralf Lund wrote:
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
37800+0 records in
37800+0 records out
gzip: stdin: invalid compressed data--crc error
tar: Child returned
+[ Jon LaBadie [EMAIL PROTECTED] (12.Oct.2004 19:21):
|
| this is the runtar executable
| pi# ls -l /usr/local/libexec/amanda/runtar
| -r-sr-x--- 1 root operator 4636 Sep 28 12:22 /usr/local/libexec/amanda/runtar
|
| My guess is an incorrect installation.
| runtar is supposed to be
On Wed, Oct 13, 2004 at 11:42:33AM -0300, Fernan Aguero enlightened us:
I did the installation as root, of course. I'm not using the
amanda sources 'as is', however, but through the added layer
of the FreeBSD ports system. I doubt this can cause any
trouble, I've already checked the port's
FYI: RedHat is release 7.2 (Enigma)
Ok, some good news. Turns out that whatever our initial problem was
the solution involved our ability to read and understand the man pages.
Redhat, perhaps linux in general, does not use SIG HUP to reload its
configuration, it uses that to dump it. SIG USR2
Jean-Francois Malouin wrote:
[ snip ]
Actually, I'm starting to suspect that gzip itself is causing the
problem. Any known issues, there? The client in question does have a
fairly old version, 1.2.4, I think (that's the latest one supplied by
SGI, unless they have upgraded it very recently.)
+[ Matt Hyclak [EMAIL PROTECTED] (13.Oct.2004 11:58):
|
| On Wed, Oct 13, 2004 at 11:42:33AM -0300, Fernan Aguero enlightened us:
| I did the installation as root, of course. I'm not using the
| amanda sources 'as is', however, but through the added layer
| of the FreeBSD ports system. I
On Wed, Oct 13, 2004 at 12:13:02PM -0300, Fernan Aguero enlightened us:
+[ Matt Hyclak [EMAIL PROTECTED] (13.Oct.2004 11:58):
|
| On Wed, Oct 13, 2004 at 11:42:33AM -0300, Fernan Aguero enlightened us:
| I did the installation as root, of course. I'm not using the
| amanda sources 'as
Fernan Aguero wrote:
Hmm ... this is what I have in inetd.conf:
amandaidx stream tcp nowait amanda /usr/local/libexec/amanda/amindexd amindexd
amidxtape stream tcp nowait amanda /usr/local/libexec/amanda/amidxtaped amidxtaped
amandadgram udp wait amanda /usr/local/libexec/amanda/amandad
On Wed, 13 Oct 2004 at 11:03am, Brian Cuttler wrote
Redhat, perhaps linux in general, does not use SIG HUP to reload its
configuration, it uses that to dump it. SIG USR2 however will reload
the configuration.
The right way on redhat to start and stop services is
/sbin/service $NAME restart,
Brian Cuttler wrote:
We are running the amanda client as amanda:disk, we are able to successfully
backup the (relatively small) root partition but not the larger user
partition.
From and client machine's /tmp/amanda files it looks like the dump is starting
but the debug file is incomplete.
I will
Paul,
Josh,
I'll check on the timeout issue.
Restarting xinetd - yes, I guess services would have provided
a clean restart but I wasn't really looking to shutdown xinetd,
just to change one of the socket behaviours. Its not unusual for
us (my site) to HUP inetd on Solaris and Irix so I didn't
On Wednesday 13 October 2004 10:42, Fernan Aguero wrote:
+[ Jon LaBadie [EMAIL PROTECTED] (12.Oct.2004 19:21):
| this is the runtar executable
| pi# ls -l /usr/local/libexec/amanda/runtar
| -r-sr-x--- 1 root operator 4636 Sep 28 12:22
| /usr/local/libexec/amanda/runtar
|
| My guess is
On Wednesday 13 October 2004 11:07, Toralf Lund wrote:
Jean-Francois Malouin wrote:
[ snip ]
Actually, I'm starting to suspect that gzip itself is causing the
problem. Any known issues, there? The client in question does have
a fairly old version, 1.2.4, I think (that's the latest one
supplied
+[ Matt Hyclak [EMAIL PROTECTED] (13.Oct.2004 12:30):
|
| Why is amandad owned by operator and not amanda? I'm not sure that's making
| a big difference assuming amanda is in the operator group, but it looks like
| some permissions are a little wonky.
I dunno. Amanda is in the operator
+[ To Matt Hyclak [EMAIL PROTECTED] (13.Oct.2004 14:05):
|
| Attached is the output collected during installation.
|
| Fernan
|
+]
Sorry, forgot to add the attach. Here it is,
Fernan
--
Fernan Aguero - fernan at iib.unsam.edu.ar
Phone: +54 11 4580-7255/7 ext 310, Fax: +54 11
Brian Cuttler wrote:
Redhat, perhaps linux in general, does not use SIG HUP to reload its
configuration, it uses that to dump it. SIG USR2 however will reload
the configuration.
Actually, the signal used, if any at all, is a function of the
application's implementation. Some applications use
Fernan Aguero [EMAIL PROTECTED] wrote:
Is there any place where permissions on files, directories,
etc are listed so I can check what a right installation
should look like?
Greetings from a fellow FreeBSD/Amanda sysadmin :-) Maybe we can use my
system (which works fine) as some kind of
Fernan Aguero wrote:
+[ Matt Hyclak [EMAIL PROTECTED] (13.Oct.2004 11:58):
|
| On Wed, Oct 13, 2004 at 11:42:33AM -0300, Fernan Aguero enlightened us:
| I did the installation as root, of course. I'm not using the
| amanda sources 'as is', however, but through the added layer
| of the
Bob,
I understand, I'd just expected more uniformity across unix like
platforms. I realize also that much of what people this of as unix
are contributed utilities that have nothing to do with the kernel.
I'm surprised to learn that older signal utilities didn't have a
larger number of signals
+[ Toomas Aas [EMAIL PROTECTED] (13.Oct.2004 15:11):
|
| Fernan Aguero [EMAIL PROTECTED] wrote:
|
| Is there any place where permissions on files, directories,
| etc are listed so I can check what a right installation
| should look like?
|
| Greetings from a fellow FreeBSD/Amanda sysadmin
24 matches
Mail list logo
