On 9 Apr 2001 [EMAIL PROTECTED] wrote:
While installing on a linux system I got the following error:
...
checking for gcc... gcc
checking whether the C compiler (gcc ) works... no
configure: error: installation or configuration problem: C compiler cannot create
executables.
The
amandad: debug 1 pid 14470 ruid 50 euid 50 start time Mon Apr 9
19:54:21 2001
amandad: pid 14470 finish time Mon Apr 9 22:07:40 2001
The strange thing is that this client has been working fine for months
in the past and is now suddenely failing daily.
Suggestions?
Thanks,
Rob
Alexandre
We are seeing a fairly recent problem with some of our amanda
installation (we have 11 different amanda jobs each night using
from 2.2.6 to 4.2.x).
We have some partitions that amanda is running "direct to tape"
rather than via the spool area even though we have sufficient
spool space.
Hello,
I tested an amdump run manually, it was too long and I stopped the
process, I ran the amcleanup and I had the report below. Can someone
tell me what are the problem ?
Thanks.
Sambot Root wrote:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape DailySet1001.
On Apr 10, 2001, Rob Flory [EMAIL PROTECTED] wrote:
amandad: debug 1 pid 14470 ruid 50 euid 50 start time Mon Apr 9
19:54:21 2001
amandad: pid 14470 finish time Mon Apr 9 22:07:40 2001
Bump etimeout to 9000 seconds or so.
--
Alexandre Oliva Enjoy Guarana', see
On Apr 9, 2001, Jean-Louis Martineau [EMAIL PROTECTED] wrote:
On Mon, Apr 09, 2001 at 02:03:00PM -0300, Alexandre Oliva wrote:
Looks like we need an additional argument in search_fstab, say
check_dev, and get amname_to_devname to call search_fstab first with
check_dev == 1, so as to reject
On Apr 10, 2001, [EMAIL PROTECTED] (Brian Cuttler) wrote:
Wondering if this isn't a "feature" of 2.2.6 and a must upgrade
for performance issue at our site.
The smaller problem partition is only 4 gig, the larger in excess
of 18, both partitions continue to grow.
I'm afraid you'll have to
Paul,
Actually both amanda hosts are Solaris 5.6, one machine is its
own and only client, the other is its own client but also has
both solaris and irix clients.
In both cases its a local file system with the problem.
In both cases output is to a local DLT drive.
Establishing chunksize as a
Thank you. Paul Bort had the same thought.
I'd thought we'd exceeded the 2 gig barrier long ago - perhaps
that was only on some of the newer version amanda servers.
Thank you both - will schedule an upgrade to both amanda systems.
Oh - which release do you recommend. We don't need the latest
On Tue, Apr 10, 2001 at 10:10:57AM +0300, Harri Haataja wrote:
On 9 Apr 2001 [EMAIL PROTECTED] wrote:
While installing on a linux system I got the following error:
...
checking for gcc... gcc
checking whether the C compiler (gcc ) works... no
configure: error: installation or
can't get amrecover to run... run as amanda says must run as root... run as
root says i'm not allowed to access as amanda from root, amandahostauth
problem.. maybe someone will know something aboutthis, it kinda has me in a
bind cause i need this recover badly
Joe
Each of your amanda clients has a file which lists the users and servers
that can access that client for backups and restores. You need to add the
root user. It will be in the home directory of the amanda user. For example,
mine is /home/amanda/.amandahosts, and looks like:
The patch works for me, what's your /proc/mounts and /etc/mtab entry?
/proc/mounts:
/dev/root / ext2 rw 0 0
/etc/mtab:
/dev/hda1 / ext2 rw 0 0
/etc/fstab:
LABEL=/ / ext2 defaults 1 1
./getfsent /:
device of `/': /dev/root
dirname of `/': /
fstype of `/': ext2
./selfcheck:
Hang on guys,
I'm getting directions from a number of people here. Woe Nelly!
Yeah, this got a little confusing. Sorry 'bout that.
My advice is to wait for Alexandre, Jean-Louis and I to stop publicly
arguing with each other :-) and come to an agreement on the fix.
Then I'll put together a
I'm attempting to build Amanda 2.4.2p2 on Solaris 5.6 and finding
the following...
[newton] /local/source/etc/amanda/amanda-2.4.2p2 43 ./configure --with-user=bin
--with-group=sys
which seems to run to completion (we have notes from previous installation
that talk about the --disable-libtool
I tested an amdump run manually, it was too long and I stopped the
process, I ran the amcleanup and I had the report below. Can someone
tell me what are the problem ?
This problem:
192.168.10 /home/dourix lev 0 FAILED [192.168.10.10: [addr 192.168.10.10: hostname
lookup failed]
says that
Hi, I'm having trouble with amanda. Recently it started to send me
emails dated "BogusMonth" and containing the "RESULTS MISSING" error.
That probably says amreport cannot read the log file.
What happens when you run amcheck?
Looking at the logfile directive in amanda.conf, and then looking at
On Tue, Apr 10, 2001 at 01:48:13PM -0500, John R. Jackson wrote:
I'm not sure why you asked about /etc/mtab. While it has the right
value, we don't look at it in Amanda (which might be the real problem).
We look at /proc/mounts (which has the wrong /dev value) and MNTTAB,
which is
I'm attempting to build Amanda 2.4.2p2 on Solaris 5.6 and finding
the following...
output ending with...
checking whether lockf locking works... (cached) no
checking whether lnlock locking works... (cached) no
configure: warning: *** No working file locking capability found!
configure: warning:
I have /dev/hda1 in /etc/fstab.
Ahh, I see. So you cheated. :-) :-)
Try this patch, It look at MOUNTED before MNTTAB.
Looks good to me. Alexandre, can you give this a try on Tru64? If it
works for you, then I'll put together a single patch for Walter to try,
and if that works, Jean-Louis
Ok, everyone, sorry to bother again.
Anyway, I've been working on this for a while (taken a back seat
over the last couple of days) anyway, every time I run amcheck I get
selfcheck request timed out: host down. However, it's not because it's
the tape host or the server. What am I missing?
... every time I run amcheck I get
selfcheck request timed out: host down. However, it's not because it's
the tape host or the server. What am I missing?
This is a very common problem and the FAQ (www.amanda.org) has quite a
bit on it. Have you gone through those steps?
If it doesn't help,
Hang on guys,
I'm getting directions from a number of people here. Woe Nelly!
Yeah, this got a little confusing. Sorry 'bout that.
My advice is to wait for Alexandre, Jean-Louis and I to stop publicly
arguing with each other :-) and come to an agreement on the fix.
Then I'll put
Hang on guys,
I'm getting directions from a number of people here. Woe Nelly!
Yeah, this got a little confusing. Sorry 'bout that.
My advice is to wait for Alexandre, Jean-Louis and I to stop publicly
arguing with each other :-) and come to an agreement on the fix.
Then
24 matches
Mail list logo
