Leslie,
Can you try the attached patch?
Amanda already have a lot of timeout, see 'man amanda-changers'
But Amanda immediately fail on a 'SCSI error; Sense Key=Aborted
Command', try the attached patch.
Jean-Louis
On 04/01/2014 12:43 PM, leslie wrote:
Hello,
Have been using amanda for
Hello,
Have been using amanda for approximately 3 years and am delighted with
the software.
I have a problem which I believe is related to device sharing.
The OS is CentOS 5.10 and I am running amanda 3.3.3.
Have a SUN SL500 with three LT05 drives, a 90 tape library, and a 15
ecv(dgram=0xd40004, timeout=0,
fromaddr=0xd4fff0)
amandad: time 9.916: (sockaddr_in *)0xd4fff0 = { 2, 708, 202.53.250.162 }
amandad: time 19.913: dgram_recv(dgram=0xd40004, timeout=0,
fromaddr=0xd4fff0)
amandad: time 19.913: (sockaddr_in *)0xd4fff0 = { 2, 708, 202.53.250.162 }
amandad: time 29.912: pid
Are you sure the server receive the request?
Did amandad get execute on the server? Post its debug log.
Check your firewall/network log.
Jean-Louis
fedora wrote:
hi all,
I am having problem with amrecover..
amrecover DailySet1
AMRECOVER Version 2.5.1p3. Contacting server on server.com ...
[re
curity_close(handle=0x8c04660, driver=0x50a0e0 (BSD))
any helps would be appreciated. :-D
--
View this message in context:
http://www.nabble.com/amrecover-failed---time-out-contacting-to-server-itself-tf4717399.html#a13485325
Sent from the Amanda - Users mailing list archive at Nabble.com.
Hello,
I would first try to increase the "timeout" parameter in amanda.conf .
And if this doesn't help you can change the "estimate" parameter in you
dumptype definition to either "server" or "calcsize". Also look in
/var/log/messages for any hardware errors/warnings.
Pavel Pragin
Hi,
I ha
Hi,
I have a nagging problem with a client machine running 2.5.1p2,1. Two
of the disk slices are being backed up without any problem but one
continues to fail. The Amanda server is running 2.5.1.p1 and backups
are completing on other hosts without similar problems.
FAILURE AND STRANGE DUMP SUMM
On Thu, Mar 20, 2003 at 10:50:42AM +0100, anne enlightened us:
> hello
>
> I'm trying amanda. But amcheck doesn't work :
> Amanda Backup Client Hosts Check
>
> WARNING: helium: selfcheck request timed out. Host down?
> WARNING: carbone.edge-it.subnet: selfcheck re
On Thu, 2003-03-20 at 01:50, anne wrote:
> I'm trying amanda. But amcheck doesn't work :
> Amanda Backup Client Hosts Check
>
> WARNING: helium: selfcheck request timed out. Host down?
> WARNING: carbone.edge-it.subnet: selfcheck request timed out. Host down?
> Cl
hello
I'm trying amanda. But amcheck doesn't work :
Amanda Backup Client Hosts Check
WARNING: helium: selfcheck request timed out. Host down?
WARNING: carbone.edge-it.subnet: selfcheck request timed out. Host down?
Client check: 2 hosts checked in 30.005 seconds,
On Thu, Mar 06, 2003 at 10:43:36AM +0100, Jeroen Heijungs wrote:
>
> The error is always the same in amandad.debug:
> Amanda 2.4 REP HANDLE 009-80FD0708 SEQ 1046914809
> OPTIONS maxdumps=1;
> /etc 0 SIZE 1260
> /etc 1 SIZE 30
> /home 0 SIZE 15710
> /home 1 SIZE 40
> /usr/local 0 SIZE 63730
> /usr/
e backed up fine, it really
is trouble free, except for one of the servers behind the firewall. That
one (mailrelay server) was backed-up fine untill it became a production
server, suddenly it had every night a time-out error:
"mailrelay. /var lev 0 FAILED [Request to mailrelay..xx timed out.]&
> 'make install' is always the best way to make sure all the permissions are
> correct.
OK, I was a good boy and installed amanda anew on the machine :)
It seems that the problem is the same. So I join a complete
/tmp/amanda/amanda.20030115.log, the problem seems to be a network problem.
Amchec
On Mon, 13 Jan 2003 at 3:47pm, Olivier Nicole wrote
> I set-up a new machine, and basically copied everything in /usr/local,
'make install' is always the best way to make sure all the permissions are
correct.
> recreated the /amanda directopry for amanda user and amanda group,
> created .amanda
Hi,
I am stuck with a problem with Amanda since I updated this
machine. Before everything was running very smoothly.
I set-up a new machine, and basically copied everything in /usr/local,
recreated the /amanda directopry for amanda user and amanda group,
created .amandahosts. I double checked tha
it.
"Look at ' # man amcheck' to see how you can run
amcheck on only the client or only the host."
- Original Message -
From:
DALLAS
CHEE
To: [EMAIL PROTECTED]
Sent: Friday, July 12, 2002 12:36
PM
Subject: localhost request time-out error
Hi there,
I am currently trying to configure Amanda version 2.4.2p2, using
Linux Redhat 7.3. The storage device used is HP Surestore DLT8000,
using tape HP DLT-IV.
I ran "amcheck DailySet1/" as user amanda on the localhost and I
encountered the following error message: "Self-check request
I'm running an Amanda server on a Linux (RH 7.2) machine to backup about
twenty client.
Every time a Win client fail *for some wrong share permission* (smbclient
can enter but not browse the network resource) and not for a time out, a
time-out of an Irix 6.5.15 client, waiting for an ack fro
Ok, I'm getting the selfcheck time out message for two of my 12 amanda
clients. They all have exactly the same configuration, as far as I can
tell. I have installed the latest amanda source on each client system,
using the same config settings. I have checked, double checked and
triple ch
> Again...running RH7.1 with kernel upgraded to 2.4.6.
^
The all important fact. Redhat 7.1 (and 7.0, IIRC) use xinetd, not inetd.
Rather than a single .conf file, xinetd uses a number of files in the
/etc/xinetd.d directory. I've attached 3 files -- amanda, amandaidx and
a
On Thu, 30 Aug 2001 at 9:23am, Rebecca Pakish wrote
> sure what the syntax is for xinetd.conf as far as that information is
> concerned. Here's what it has:
>
> #
> # Simple configuration file for xinetd
> #
> # Some defaults, and include /etc/xinetd.d/
>
> defaults
> {
> instances
>... I would like to know if
>etimeout and dtimeout are the same thing. ...
They are not. Etimeout determines how long Amanda waits on a client when
it is asking for the estimates. Dtimeout is how long it waits when the
client is actually doing a dump.
>I have amanda 2.4.2 so i don;t know
HI everybody:
I'm sorry if my question is too silly but I would like to know if
etimeout and dtimeout are the same thing. I ask you because i have
problem with a machine that today reported data time out. I check
the mailing list if somebody have had the same problem and i
23 matches
Mail list logo
