Backup Central

Hello,

since switching the server from 2.6.1p2 to 3.1.1 and then to 3.2.0, every
report mail shows up 1-n DLEs on 1-n clients have been failed and then
successfully retried. Sample:

storage-01.mr.lfmg.de /tmp lev 0 FAILED [Can't open data output stream:
Connection refused]
storage-01.mr.lfmg.de /tmp lev 0 was successfully retried

Switching the server back to 2.6.1p2 and the message is gone. Going to 3.1.1
or higher again, the message is back. It's reproducable here.

We have about 20 clients with version between 2.5.0 and 3.2.0.

Any idea?

Regards,
Marc

--
Marc Muehlfeld (IT-Leiter)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78
http://www.medizinische-genetik.de

What amanda version on the client that failed?
Which auth are you using?
On server, what's the output of: amgetconf CONF unreserved-tcp-port
On client, what's the output of: amgetconf --client CONF unreserved-tcp-port
Do the port are open on the firewall?

Can you post the dumper.*.debug files from server and amandad.*.debug
and sendbackup.*.debug from the client.

Jean-Louis

Marc Muehlfeld wrote:
Hello,

since switching the server from 2.6.1p2 to 3.1.1 and then to 3.2.0,
every report mail shows up 1-n DLEs on 1-n clients have been failed
and then successfully retried. Sample:

storage-01.mr.lfmg.de /tmp lev 0 FAILED [Can't open data output
stream: Connection refused]
storage-01.mr.lfmg.de /tmp lev 0 was successfully retried

Switching the server back to 2.6.1p2 and the message is gone. Going to
3.1.1 or higher again, the message is back. It's reproducable here.

We have about 20 clients with version between 2.5.0 and 3.2.0.

Any idea?

Regards,
Marc

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.

I'm seeing a similar issue to Marc's.

Server 3.1.2, client was 2.6.1, just updated the client to 3.1.2
so we will see what tonight's run brings.

In this case client and server are both Solaris 10x86.

thanks - Brian


On Wed, Oct 27, 2010 at 08:29:03AM -0400, Jean-Louis Martineau wrote:
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.





---
Brian R Cuttler brian.cuttler < at > wadsworth.org
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.