Greetings;
I just had to get up and discovered no report in the printer output tray.
On inspection with htop, most of the amanda stuff seems to be sleeping or
waiting. An amstatus says its hung on the first dump, and I'm seeing
broken pipe stuff in the logs.
The only thing that comes to mind
Greetings;
I just unpacked the 2.5.1p3-20070220 src tree and ran a grep
for 'amanda-dbg', finding it only in my gh.cf file that drives
the ./configure step. I expected that result as it hasn't been
configured yet, just unpacked.
Then I backed up to the 2.5.1p3-20070216 tree which is running
Gene,
You found a bug.
Old debug files are not removed, this bug exist since we created subdir
for debugging files, only the root is cleaned.
Jean-Louis
Gene Heskett wrote:
Greetings;
I just unpacked the 2.5.1p3-20070220 src tree and ran a grep
for 'amanda-dbg', finding it only in my
On 2007-02-21 11:15, Gene Heskett wrote:
Greetings;
I just had to get up and discovered no report in the printer output tray.
On inspection with htop, most of the amanda stuff seems to be sleeping or
waiting. An amstatus says its hung on the first dump, and I'm seeing
broken pipe stuff
On Wednesday 21 February 2007, Paul Bijnens wrote:
On 2007-02-21 11:15, Gene Heskett wrote:
Greetings;
I just had to get up and discovered no report in the printer output
tray. On inspection with htop, most of the amanda stuff seems to be
sleeping or waiting. An amstatus says its hung on the
On Wednesday 21 February 2007, Jean-Louis Martineau wrote:
Gene,
You found a bug.
Old debug files are not removed, this bug exist since we created subdir
for debugging files, only the root is cleaned.
Jean-Louis
I'd assume that similar code for the amanda-dbg assignment could be
patched in
Gene,
Try the attached patch.
Jean-Louis
Gene Heskett wrote:
On Wednesday 21 February 2007, Jean-Louis Martineau wrote:
Gene,
You found a bug.
Old debug files are not removed, this bug exist since we created subdir
for debugging files, only the root is cleaned.
Jean-Louis
I'd
On Wednesday 21 February 2007, Jean-Louis Martineau wrote:
Gene,
Try the attached patch.
Jean-Louis
Its building now. I guess I'm getting slow, but I don't see the magic in
that simple a patch. If it works, I assume that it won't leave behind
any dbg files in that tree after tonight's run
Debug files are kept 4 days by default (can be configured with
'--with-debug-days').
Only the files from the same program will get deleted.
eg. amcheck will only delete the amcheck.*.debug files
Jean-Louis
Gene Heskett wrote:
On Wednesday 21 February 2007, Jean-Louis Martineau wrote:
On Wednesday 21 February 2007, Jean-Louis Martineau wrote:
Debug files are kept 4 days by default (can be configured with
'--with-debug-days').
Oh, goodie! I agree, when you need them they're current much easier to
find instead of wading through a directory that may have a thousand files
On 2/21/07, Stefan G. Weichinger [EMAIL PROTECTED] wrote:
FL schrieb:
A host check reports no slots available, when there are slots available.
What causes this, and what is the remedy? Thanks.
Changer problem: no slots available
In my case it helped to change the group of the used
Hello,
Does anybody run Amanda on AIX 5.2 ?
I try different binary packages, I compile the 2.5.1p3 sources, but the
result is always the same : segmentation fault.
I am not an AIX guru, so I have no idea about the problem :
all amanda modules I try crashed immediately,
is it a lib problem ? I
Hi Pozzi,
On 02/22/2007 12:29 AM, [EMAIL PROTECTED] wrote:
Hello,
Does anybody run Amanda on AIX 5.2 ?
5.2.0.0 or above ? What is the output of oslevel -r ?
I try different binary packages, I compile the 2.5.1p3 sources, but the
result is always the same : segmentation fault.
Have you
Hi Pozzi,
On 02/22/2007 12:29 AM, [EMAIL PROTECTED] wrote:
Does anybody run Amanda on AIX 5.2 ?
just another question, how have you compiled amanda on AIX ?
I've just tried to do so with amanda-2.5.1p2 (we use Solaris as main
environment, and there is no need to backup our AIX boxes yet).
Now that this problem is overcome, have I run out of tape? Perhaps I need to
split directiories up (200 GB tape_
These dumps were to tape Daily-12.
*** A TAPE ERROR OCCURRED: [No more writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush to flush them to
Hello,
I am trying to find out the parameters of my tape unit using amtapetype but it
looks like something is failing. When I run amtapetype -f /dev/nst0 I always
get this message:
Estimate phase 1...amtapetype: could not write any data in this pass: short
write
Then amtapetype finishes. The
16 matches
Mail list logo