Snapshot 2.5.2-20070523 runs fine last night, on Solaris8 (client only).
amrecover works as expected, too.
Peter
I posted to the web -- but I don't know that it will find its
way back to amanda-users. Besides, the thread was 2 years old...
but its come back to haunt me.
--- In [EMAIL PROTECTED], Jon LaBadie [EMAIL PROTECTED] wrote:
On Thu, Feb 24, 2005 at 09:04:49AM -0500, Gil Naveh wrote:
Hello,
--- In [EMAIL PROTECTED], Jon LaBadie [EMAIL PROTECTED] wrote:
On Thu, Feb 24, 2005 at 09:04:49AM -0500, Gil Naveh wrote:
Hello,
Amanda is successfully running on our Solaris Servers. But on Amanda's
report (the E-mail it sends after amdump) I get the following STRANGE
message:
My amanda is the following:
amandad: time 0.170: security_getdriver(name=bsd) returns ff2d8f20
amandad: version 2.5.2-20070523
amandad: time 0.170: build: VERSION=Amanda-2.5.2-20070523
amandad: time 0.170:BUILT_DATE=Thu May 24 10:07:47 EDT 2007
amandad: time 0.170:
On Fri, May 25, 2007 at 10:32:28AM -0400, Brian Cuttler wrote:
I posted to the web -- but I don't know that it will find its
way back to amanda-users. Besides, the thread was 2 years old...
but its come back to haunt me.
--- In [EMAIL PROTECTED], Jon LaBadie [EMAIL PROTECTED] wrote:
On
Hi all,
I've been having troubles with Amanda on my new box (an eMachines
desktop running Fedora Core 6).
I have four machines being backed up to vdisks with about 500Gb total
being backed up with two clients active at the time of the crash. All
three are running builds of 2.5.2.
I
Can you try latest 2.5.2 snapshot from
http://www.zmanda.com/community-builds.php?
Do: AMANDA_CFLAGS=-g
before you configure
Add the following lines to amanda.conf:
debug_auth 1
debug_protocol 1
debug_dumper 1
Send me the Backtrace and the dumper.*.debug if it still crash.
Jean-Louis
Bruce
Jon,
I'm confused, apparently not parsing this correctly.
I believe you are saying that using strings you confirmed that
the message is generated from ufsdump, but that you would not
expect ufsdump to create /tmp/amanda, you would have expected
that from an amanda binary.
Is this a request to
When I run amstatus --config daily --date
zorn-[13] amstatus --config daily --date
Using /var/amanda/daily/amdump from Fri May 25 07:51:23 EDT 2007
20070525075123 bers:/ 0 4649m
finished (9:20:41)
20070525075123 bessel:/
Amanda is not reusing tapes in my library. I have them setup to overwrite when
it reaches the last tape but now I am getting this tape error. Any ideas?
Thanks in advance.
*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush
On Fri, May 25, 2007 at 03:33:34PM -0400, Brian Cuttler wrote:
Jon,
I'm confused, apparently not parsing this correctly.
I believe you are saying that using strings you confirmed that
the message is generated from ufsdump, but that you would not
expect ufsdump to create /tmp/amanda,
On Fri, May 25, 2007 at 04:26:46PM -0500, James Wilson wrote:
Amanda is not reusing tapes in my library. I have them setup to overwrite
when it reaches the last tape but now I am getting this tape error. Any
ideas? Thanks in advance.
*** A TAPE ERROR OCCURRED: [No writable valid tape
James Wilson wrote:
Amanda is not reusing tapes in my library. I have them setup to overwrite
when it reaches the last tape but now I am getting this tape error. Any
ideas? Thanks in advance.
*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the
Sorry, I will post my configs this time. I have them split up into 2
separate backups. DailyTapes run from Monday-Saturday and WeeklyTapes
run on Sunday which are always full backups. I meant the conf files by
Them.
Here is my amanda.conf from DailyTape only.
dumpcycle 7 # the number of
On Fri, May 25, 2007 at 05:47:33PM -0400, Jon LaBadie wrote:
ISTR, from your original message, that the Strange message said
unable to create temporary directory under, /tmp, /var/tmp, and /.
I don't recall it saying anything about /tmp/amanda. I don't
understand why you are fixed on that
List,
I'm new to Amanda. It's running on a Fedora Core 2 server. Below is
the message I receive from an amanda:
DailyBackup1 AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE
Amanda Tape Server Host Check
-
WARNING: holding disk /AmandaBackup/HoldingDisk: only 476156
Hi David,
whenever i would get this message from amanda, i would:
1. put tape DailyBackup1-A003 into my changer
2. if DailyBackup1-A003 is offsite or unavailable, amlabel
a new tape media and leave it in the changer
3. run amflush config to dump files left on holding disk
onto
On Fri, May 25, 2007 at 05:40:00PM -0500, Dustin J. Mitchell wrote:
On Fri, May 25, 2007 at 05:47:33PM -0400, Jon LaBadie wrote:
ISTR, from your original message, that the Strange message said
unable to create temporary directory under, /tmp, /var/tmp, and /.
I don't recall it saying
On Fri, May 25, 2007 at 05:23:22PM -0500, James Wilson wrote:
Sorry, I will post my configs this time. I have them split up into 2
separate backups. DailyTapes run from Monday-Saturday and WeeklyTapes
run on Sunday which are always full backups. I meant the conf files by
Them.
Here is my
On Fri, May 25, 2007 at 04:58:15PM -0700, David Lynum wrote:
List,
I'm new to Amanda. It's running on a Fedora Core 2 server. Below is
the message I receive from an amanda:
DailyBackup1 AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE
Amanda Tape Server Host Check
20 matches
Mail list logo
