> > -Original Message-
>
> Just to follow up on this: after making sure a default route
> was included with the second ethernet jack, I rebooted
> the server machine on the private network, and then ran an
> amcheck. It came back properly this time. If the backup
> doesn't work corre
> -Original Message-
> I have a very weird problem with my amanda system, that maybe others
> may be able to help. Here's my issue:
>
> I have a server and two clients. The server and one client are
> RedHat 9, while the other client is RHEL 4. The problem I'm having
> is with the t
> -Original Message-
>
>
> > The server and the client in question are directly connected via
> > second ethernet jacks and a crossover cable.
>
> First, I would check if the crossover connection is perfectly
> working with some network test tool.
>
Been working with netperf an
> The server and the client in question are directly connected via
> second ethernet jacks and a crossover cable.
First, I would check if the crossover
connection is perfectly working with some network test tool.
I have a very weird problem with my amanda system, that maybe others
may be able to help. Here's my issue:
I have a server and two clients. The server and one client are
RedHat 9, while the other client is RHEL 4. The problem I'm having
is with the two RH9 boxes. The server had been doing a ch
Edson Noboru Yamada schreef:
Thank you, Paul. You´re absolutely right.
I´ve configured SOlaris tcp stack to decrease the keep alive interval
("ndd -set /dev/tcp tcp_time_wait_interval 24") and everything runs fine now.
I guess you mean:
ndd -set /dev/tcp tcp_keepalive_interval 24
em: terça-feira, 21 de março de 2006 19:58
Para: Edson Noboru Yamada; Mailing List Amanda User
Assunto: Re: dumper issue - timeout problem?
Edson Noboru Yamada schreef:
>
> I´ve been facing a problem when trying to backup one of our clients.
> The backup starts normally, but after some
On Tuesday 21 March 2006 12:22, Edson Noboru Yamada wrote:
> One important thing I´ve noticed is that the error allways occurs after 300
> seconds. Is there some tunable timeout I´m forgetting?
>
> Additional info: strangely, the backup appears successful, even when this
> message shows up. The sa
Edson Noboru Yamada schreef:
I´ve been facing a problem when trying to backup one of our clients.
The backup starts normally, but after some time, the following message shows up
in the taper log:
dumper: stream_client: our side is 0.0.0.0.45740
driver: result time 553.824 from dumper0: FAILED
Hi,
I´ve been facing a problem when trying to backup one of our clients.
The backup starts normally, but after some time, the following message shows up
in the taper log:
dumper: stream_client: our side is 0.0.0.0.45740
driver: result time 553.824 from dumper0: FAILED 01-2 [mesg read:
Conne
- Mensagem Original
De: Matt Hyclak <[EMAIL PROTECTED]>
Para: amanda-users@amanda.org
Assunto: Re: Planner timeout problem
Data: 10/06/05 19:39
> I'd be willing to be that there is a firewall running on matriz. amcheck
can
> usually pass a firewall where amdump
On Fri, Jun 10, 2005 at 09:05:10PM +, Aazevedo enlightened us:
> Please, help a newbie in amanda.
>
> I have amanda up and running backups from several machines on my network.
> Amanda version is 2.4.5 for both server and clients. The server
>
> runs Linux 2.6.9-1.
>
> Everything runs fine,
Please, help a newbie in amanda.
I have amanda up and running backups from several machines on my network.
Amanda version is 2.4.5 for both server and clients. The server
runs Linux 2.6.9-1.
Everything runs fine, except from one machine.
The mail report says:
FAILURE A
> > I might be making progress; I'm not sure.
> >
>[ snip ]
> >
> > So... Why does the server close (FIN) all three connections only 1 second
> > after opening them? I can find no messages in the server logs as to why
> > this might have happened.
>
> Don't know my networking and tcpdump, so
I might be making progress; I'm not sure.
For those who haven't been following... The amanda client under cygwin will
reset the data connection without sending the final "goodbye" message and
thus the server ignores all the backup data.
To fix this, I removed the "aclose" of the various sockets
Zhen Liu
Via Webmail
[EMAIL PROTECTED]
-- Forwarded message ---
From: Zhen Liu <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: Fri, 29 Mar 2002 09:09:14 -0500
Hi,
Thanks for your suggestions, I did change the etimeout from 300
(5minutes by default) to 3600 (1 hour
Zhen Liu
Via Webmail
[EMAIL PROTECTED]
-- Forwarded message ---
From: Zhen Liu <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: Fri, 29 Mar 2002 09:09:14 -0500
Hi,
Thanks for your suggestions, I did change the etimeout from 300
(5minutes by default) to 3600 (1 hour
Hi,
Thanks for your suggestions, I did change the etimeout from 300
(5minutes by default) to 3600 (1 hour). Meanwhile, I changed the
"localhost" to the FQDN...and my holding disk in amanda.conf to
2Mb... But I still got some kind of timeout issue...I tried to
back up 5 file systems and got 3
>I am working on the amanda backup project now. ...
Welcome!
>When enter "su amanda -c amdump daily", my dump for the localhost
>/scsi9-data failed... I check the logs and debugs, it said "FAIL
>planner localhost /scsi9-data 0 [Request to localhost timed out.]
As Mark Schoonover said, please d
My first guess would be that you don't have amandad in your
inetd.conf on your backup server machine, or that service is
not running for some other reason. amdump talks to the amandad
even on localhost.
On Fri, 22 Mar 2002, Zhen Liu wrote:
> Hi, Everyone:
>
> I am working on the amanda backup
I think you have a DNS issue. You should also not use the localhost as the
name of the backup server. Use the real name of the server in your disklist
file(s). That way if some time in the future your backup server should
change, there won't be a name conflict...
HTH
.mark
Hi, Everyone:
I am working on the amanda backup project now. I have some problem
with my amdump... HELP!!!
The OS I am working on is Linux RH7.1, the tape changer we have is
Adic Fastor, Quantum 7000 tape drive.
When enter "su amanda -c amdump daily", my dump for the localhost
/scsi9-data faile
22 matches
Mail list logo
