On 2008-01-23 04:40, Kermit Short wrote:
Hey gurus!
I've checked many many resources about this error and I've done just
about everything they've asked, but I can't get rid of it, and I don't
really even know if it's a show stopper or not. Here's my situation:
[...]
backup set name. In
Hi,
Kermit Short schrieb:
The client check mewls and cries, indicating
the selfcheck request timed out, and asks if the host is down.
Are all services through xinetd are running on your client/server?
# netstat -taun | egrep :1008.
tcp0 0 192.168.29.2:10082 0.0.0.0:*
Hi all
Amanda-2.5.2p1 on both the server and client.
The backup devices are vtapes on the server.
I ran amdump on the server.
The backup would be full dump (Lv0).
After I ran amdump, I found the vtape directory not being correctly set.
I Thought that the backup was failure.
When I checked the
Hello all,
I've been having a problem with incremental dumps on a NFS mounted
Netapp. AMANDA runs great until I reboot the client (or remount the
NFS shares on the client). At that point, while calcsize predicts what
I believe is the correct incremental dump size, tar proceeds to do a
Thanks, Paul, for your helpful responses! As you requested, I've tried
to run the amadmin command but it seems this version doesn't know that
parameter of amadmin:
[EMAIL PROTECTED]:~$ amadmin DailySet1 config
amadmin: unknown command config
However, as this is a binary package, I'm not
Hi Marc, thanks for your ideas!
The system does indeed resolve it's full FQDN both through dig/nslookup,
but pinging the IP address does not resolve the hostname. Not sure if
this is an issue?
The output from your netstat command does indeed list the correct ports
and services listening
Takashi Kurakata wrote:
Hi all
Amanda-2.5.2p1 on both the server and client.
The backup devices are vtapes on the server.
I ran amdump on the server.
The backup would be full dump (Lv0).
After I ran amdump, I found the vtape directory not being correctly set.
I Thought that the backup was
Kermit Short wrote:
Thanks, Paul, for your helpful responses! As you requested, I've tried
to run the amadmin command but it seems this version doesn't know that
parameter of amadmin:
[EMAIL PROTECTED]:~$ amadmin DailySet1 config
amadmin: unknown command config
Oops, my mistake... I
Kermit Short wrote:
Hi Marc, thanks for your ideas! The system does indeed resolve it's full
FQDN both through dig/nslookup, but pinging the IP address does not
resolve the hostname. Not sure if this is an issue?
The output from your netstat command does indeed list the correct ports
and
Jordan Desroches wrote:
Hello all,
I've been having a problem with incremental dumps on a NFS mounted
Netapp. AMANDA runs great until I reboot the client (or remount the NFS
shares on the client). At that point, while calcsize predicts what I
believe is the correct incremental dump size,
I agree the problem is with gnutar, and also agree that the root cause
of my problem, and the cause of the problem that Paul described and
linked to, are the same: some attribute (either major/minor with a
file system, or with NFS, FSID) is changing that is fooling gnutar
into thinking
I've dug further into the gnutar-lists directory, and I think I know
what is causing the problem, but I don't quite know what to do about
it. I have a NFS mounted directory /mnt/thayerfs/home
Here is a section of the incremental file from 1/19/08:
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
Paul-
I'm still tracking down some of the things you mentioned I should
check...However, I've just had a brainstorm. This specific server is
bound via winbind to a Windows 2003 Active Directory controller. Now,
while Windows doesn't specify a user specifically named backup (the
amadmin
13 matches
Mail list logo
