On 02/21/2013 03:35 PM, Dennis Benndorf wrote:
Hi,
yes they are the same, but and thats the strange thing, if I use
amcheck -c daily HOSTNAME
it works. I thought of not enough socket or a another limit in amanda?!
The connect system call return ECONNREFUSED 'Connection refused'. So it
looks to be an amanda client problem. Do you checked the system log on
the client?
From the debug file, do amcheck try to contact each host more than one
time?
Jean-Louis
Regards,
Dennis
Am 21.02.2013 20:37, schrieb Jean-Louis Martineau:
Dennis,
amcheck try to contact all hosts at the same time which can make big
load on some system services (dns, ...).
Is it always the same 40 hosts that fail?
Can you amcheck them once at a time: amcheck -c daily HOSTNAME
Jean-Louis
On 02/21/2013 10:30 AM, Dennis Benndorf wrote:
Hello,
let me explain this headline. Last night the backup failed and
amcheck shows the following messages for about 40 of our 148 Servers
in backup:
/amanda@dl380-54:~$ amcheck -c daily //
//*** selfcheck request failed: error sending REQ: write error to:
Broken pipe//
//...//
//
//The debug logs show this://
//Thu Feb 21 16:22:59 2013: thd-0x10df200: amcheck-clients:
connect_port: Try port 516: available - Success//
//Thu Feb 21 16:22:59 2013: thd-0x10df200: amcheck-clients:
connect_portrange: Connect from 0.0.0.0:516 failed: Connection
refused//
//Thu Feb 21 16:22:59 2013: thd-0x10df200: amcheck-clients:
connect_portrange: connect to ***:10080 failed: Connection
refused//
//Thu Feb 21 16:22:59 2013: thd-0x10df200: amcheck-clients:
stream_client: Could not bind to port in range 512-1023.//
//
//amanda@dl380-54:~$ amadmin daily hosts |wc -l//
//148//
//
//amanda@dl380-54:~$ amadmin daily dles |wc -l//
//396//
/
If I now comment some dles out, everthing is nice:
/
/
/amanda@dl380-54:~$ amadmin daily hosts |wc -l//
//139//
//
//amanda@dl380-54:~$ amadmin daily dles |wc -l//
//370//
/
What is going wrong?
Thanks in advance,
Dennis/
/
