Can you also post the amdump.? log file and the chunker.*.debug for the
failed dle.
Jean-Louis
Marc Muehlfeld wrote:
First two more information:
* It changes, which DLE on which client fails/retries. Every backup
between 1 and 3 of about 130 DLEs fail. I very less cases, none fails.
* The problem disappears directly when I downgrade amanda back to
2.6.1p2. So should be no config/firewall issue.
Am 27.10.2010 12:23, schrieb Jean-Louis Martineau:
What amanda version on the client that failed?
All clients run versions between 2.5.0 and 3.2.0. Most are 2.5.0p2. I
checked the reports of the last 30 days. During that time it never
appeared on a client >= 3.x.
Which auth are you using?
bsd
On server, what's the output of: amgetconf CONF unreserved-tcp-port
This was the first I had checked.
# amgetconf KDD unreserved-tcp-port
1025,65535
This was not changed when switching from 2.6.1p2 to 3.1.1.
On client, what's the output of: amgetconf --client CONF
unreserved-tcp-port
My 2.5.0 clients (CentOS5) don't have amgetconf. It's only in the
amanda-server package, that is not installed.
My 2.5.2 clients (openSUSE 11.1) don't know the '--client' parameter
and without it complains, that no "/etc/amanda/{CONF}/amanda.conf" was
found, what is right.
Do the port are open on the firewall?
There are no firewalls between server and clients. Not even on the
server/clients itself.
Can you post the dumper.*.debug files from server and amandad.*.debug
and
sendbackup.*.debug from the client.
Find the files attached.
