[Veritas-bu] Error 54 - client connect timeout

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C47FA4.8090ECA3
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi folks...

the 52's can be also by cause of the drive path... I have this problem =
in
one customer... and only with regenerate the path we solve this...

regards,
nacho

-----Mensaje original-----
De: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]En nombre de Weber,
Philip
Enviado el: mi=E9rcoles, 11 de agosto de 2004 14:08
Para: 'Mark.Donaldson AT cexp DOT com'; 'veritas-bu AT mailman.eng.auburn DOT 
edu'
Asunto: RE: [Veritas-bu] Error 54 - client connect timeout


We had a lot of problems with 50s and 54s on RMAN backups a while back, =
and
fixed by bringing the NB client and NB database client software up to =
the
same patch levels as the master and media servers.

I seem to remember 52s can be caused by having the
/usr/openv/volmgr/DISABLE_RESOURCES_BUSY flag set on your master =
server.  I
think this is a hangover from 3.4 but now strongly dis-recommended by
Veritas (see support.veritas.com).  This flag was pointed out to us by
Veritas on a support call for performance issues, although we weren't
getting 52s.

regards, Phil

-----Original Message-----
From: Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT com]=20
Sent: 09 August 2004 16:16
To: Mark.Donaldson AT cexp DOT com; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Error 54 - client connect timeout


Well - I've changed the symptoms.

I'm getting Error 52's now.  Timeouts on Media Mounts.

I've changed the storage unit to a fixed unit from the former storage =
group
and set my media mount timeouts to zero per this document:

http://seer.support.veritas.com/docs/263989.htm

-M

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Donaldson,
Mark - Broomfield, CO
Sent: Friday, August 06, 2004 1:47 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Error 54 - client connect timeout


Well - what I've done so far:

First off, the storage units are already set to a fixed storage group &
their bp.conf files contain the MUST_USE_LOCAL_DRIVES directive so the =
media
servers are using their locally defined storage unit as the =
destination.

My CLIENT_READ_TIMEOUT was already set to 7200 but =
CLIENT_CONNECT_TIMEOUT
was only 500 so I upped it to 1800 (Thanks, Penelope & Glenda).

I've set my Netbackup max-jobs/client for these clients to 99 (from 12 =
- a
mistake but it was still there) since they're media servers and I =
pretty
much let the media servers run wide open.  (The change to 12 =
jobs/client was
only recent and we've been plagued by these type of errors for longer =
than
this so I don't think this is too relevant.)

My master server's tcp time wait interval was still at default (120000 =
ms)
so I dropped it to 10000.  I also increased the default window sizes to =
64K
(tcp_xmit_hiwat & tcp_recv_hiwat) from their defaults.  This matches my
master server's settings to these clients' already set values.  I also
increased the master server's TCP queue size (tcp_conn_req_max_q) to =
2048
from 1024.

Backups are running now and I'm monitoring. =20

They'd start before - no problem - but would often have trouble =
completing
after hours of running.  I'll see where they are this weekend and =
update
this note on Monday.

Thanks to all who replied.

-M

-----Original Message-----

I'm being plagued by these on my RMAN backups:

ERROR: 54
timed out connecting to client
The server could not complete the connection to the client. The accept
system or winsock call timed out after 60 seconds.

I've got an open ticket with Veritas but have any of you defeated this
dragon?

-M

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
 (2B|^2B) =3D=3D ?
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
 Mark Donaldson - SA - Corporate Express
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
is authorised and regulated by the Financial Services Authority. Egg
Investments Ltd. is entered in the FSA register under number 190518.=20

Registered in England and Wales. Registered offices: 1 Waterhouse
Square, 138-142 Holborn, London EC1N 2NA.

If you are not the intended recipient of this e-mail and have received
it in error, please notify the sender by replying with 'received in
error' as the subject and then delete it from your mailbox.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

------_=_NextPart_001_01C47FA4.8090ECA3
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.73">
<TITLE>RE: [Veritas-bu] Error 54 - client connect timeout</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi folks...</FONT>
</P>

<P><FONT SIZE=3D2>the 52's can be also by cause of the drive path... I =
have this problem in one customer... and only with regenerate the path =
we solve this...</FONT></P>

<P><FONT SIZE=3D2>regards,</FONT>
<BR><FONT SIZE=3D2>nacho</FONT>
</P>

<P><FONT SIZE=3D2>-----Mensaje original-----</FONT>
<BR><FONT SIZE=3D2>De: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu">mailto:veritas-b=
u-admin AT mailman.eng.auburn DOT edu</A>]En nombre de Weber,</FONT>
<BR><FONT SIZE=3D2>Philip</FONT>
<BR><FONT SIZE=3D2>Enviado el: mi=E9rcoles, 11 de agosto de 2004 =
14:08</FONT>
<BR><FONT SIZE=3D2>Para: 'Mark.Donaldson AT cexp DOT com'; =
'veritas-bu AT mailman.eng.auburn DOT edu'</FONT>
<BR><FONT SIZE=3D2>Asunto: RE: [Veritas-bu] Error 54 - client connect =
timeout</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>We had a lot of problems with 50s and 54s on RMAN =
backups a while back, and</FONT>
<BR><FONT SIZE=3D2>fixed by bringing the NB client and NB database =
client software up to the</FONT>
<BR><FONT SIZE=3D2>same patch levels as the master and media =
servers.</FONT>
</P>

<P><FONT SIZE=3D2>I seem to remember 52s can be caused by having =
the</FONT>
<BR><FONT SIZE=3D2>/usr/openv/volmgr/DISABLE_RESOURCES_BUSY flag set on =
your master server.&nbsp; I</FONT>
<BR><FONT SIZE=3D2>think this is a hangover from 3.4 but now strongly =
dis-recommended by</FONT>
<BR><FONT SIZE=3D2>Veritas (see support.veritas.com).&nbsp; This flag =
was pointed out to us by</FONT>
<BR><FONT SIZE=3D2>Veritas on a support call for performance issues, =
although we weren't</FONT>
<BR><FONT SIZE=3D2>getting 52s.</FONT>
</P>

<P><FONT SIZE=3D2>regards, Phil</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Mark.Donaldson AT cexp DOT com [<A =
HREF=3D"mailto:Mark.Donaldson AT cexp DOT com">mailto:Mark.Donaldson AT cexp 
DOT com</=
A>] </FONT>
<BR><FONT SIZE=3D2>Sent: 09 August 2004 16:16</FONT>
<BR><FONT SIZE=3D2>To: Mark.Donaldson AT cexp DOT com; =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Error 54 - client connect =
timeout</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Well - I've changed the symptoms.</FONT>
</P>

<P><FONT SIZE=3D2>I'm getting Error 52's now.&nbsp; Timeouts on Media =
Mounts.</FONT>
</P>

<P><FONT SIZE=3D2>I've changed the storage unit to a fixed unit from =
the former storage group</FONT>
<BR><FONT SIZE=3D2>and set my media mount timeouts to zero per this =
document:</FONT>
</P>

<P><FONT SIZE=3D2><A =
HREF=3D"http://seer.support.veritas.com/docs/263989.htm"; =
TARGET=3D"_blank">http://seer.support.veritas.com/docs/263989.htm</A></F=
ONT>
</P>

<P><FONT SIZE=3D2>-M</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu">mailto:veritas-b=
u-admin AT mailman.eng.auburn DOT edu</A>]On Behalf Of Donaldson,</FONT>
<BR><FONT SIZE=3D2>Mark - Broomfield, CO</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, August 06, 2004 1:47 PM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Error 54 - client connect =
timeout</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Well - what I've done so far:</FONT>
</P>

<P><FONT SIZE=3D2>First off, the storage units are already set to a =
fixed storage group &amp;</FONT>
<BR><FONT SIZE=3D2>their bp.conf files contain the =
MUST_USE_LOCAL_DRIVES directive so the media</FONT>
<BR><FONT SIZE=3D2>servers are using their locally defined storage unit =
as the destination.</FONT>
</P>

<P><FONT SIZE=3D2>My CLIENT_READ_TIMEOUT was already set to 7200 but =
CLIENT_CONNECT_TIMEOUT</FONT>
<BR><FONT SIZE=3D2>was only 500 so I upped it to 1800 (Thanks, Penelope =
&amp; Glenda).</FONT>
</P>

<P><FONT SIZE=3D2>I've set my Netbackup max-jobs/client for these =
clients to 99 (from 12 - a</FONT>
<BR><FONT SIZE=3D2>mistake but it was still there) since they're media =
servers and I pretty</FONT>
<BR><FONT SIZE=3D2>much let the media servers run wide open.&nbsp; (The =
change to 12 jobs/client was</FONT>
<BR><FONT SIZE=3D2>only recent and we've been plagued by these type of =
errors for longer than</FONT>
<BR><FONT SIZE=3D2>this so I don't think this is too relevant.)</FONT>
</P>

<P><FONT SIZE=3D2>My master server's tcp time wait interval was still =
at default (120000 ms)</FONT>
<BR><FONT SIZE=3D2>so I dropped it to 10000.&nbsp; I also increased the =
default window sizes to 64K</FONT>
<BR><FONT SIZE=3D2>(tcp_xmit_hiwat &amp; tcp_recv_hiwat) from their =
defaults.&nbsp; This matches my</FONT>
<BR><FONT SIZE=3D2>master server's settings to these clients' already =
set values.&nbsp; I also</FONT>
<BR><FONT SIZE=3D2>increased the master server's TCP queue size =
(tcp_conn_req_max_q) to 2048</FONT>
<BR><FONT SIZE=3D2>from 1024.</FONT>
</P>

<P><FONT SIZE=3D2>Backups are running now and I'm monitoring.&nbsp; =
</FONT>
</P>

<P><FONT SIZE=3D2>They'd start before - no problem - but would often =
have trouble completing</FONT>
<BR><FONT SIZE=3D2>after hours of running.&nbsp; I'll see where they =
are this weekend and update</FONT>
<BR><FONT SIZE=3D2>this note on Monday.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks to all who replied.</FONT>
</P>

<P><FONT SIZE=3D2>-M</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
</P>

<P><FONT SIZE=3D2>I'm being plagued by these on my RMAN backups:</FONT>
</P>

<P><FONT SIZE=3D2>ERROR: 54</FONT>
<BR><FONT SIZE=3D2>timed out connecting to client</FONT>
<BR><FONT SIZE=3D2>The server could not complete the connection to the =
client. The accept</FONT>
<BR><FONT SIZE=3D2>system or winsock call timed out after 60 =
seconds.</FONT>
</P>

<P><FONT SIZE=3D2>I've got an open ticket with Veritas but have any of =
you defeated this</FONT>
<BR><FONT SIZE=3D2>dragon?</FONT>
</P>

<P><FONT SIZE=3D2>-M</FONT>
</P>

<P><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>&nbsp;(2B|^2B) =3D=3D ?</FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>&nbsp;Mark Donaldson - SA - Corporate Express</FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2>This private and confidential e-mail has been sent to =
you by Egg.</FONT>
<BR><FONT SIZE=3D2>The Egg group of companies includes Egg Banking =
plc</FONT>
<BR><FONT SIZE=3D2>(registered no. 2999842), Egg Financial Products Ltd =
(registered</FONT>
<BR><FONT SIZE=3D2>no. 3319027) and Egg Investments Ltd (registered no. =
3403963) which</FONT>
<BR><FONT SIZE=3D2>is authorised and regulated by the Financial =
Services Authority. Egg</FONT>
<BR><FONT SIZE=3D2>Investments Ltd. is entered in the FSA register =
under number 190518. </FONT>
</P>

<P><FONT SIZE=3D2>Registered in England and Wales. Registered offices: =
1 Waterhouse</FONT>
<BR><FONT SIZE=3D2>Square, 138-142 Holborn, London EC1N 2NA.</FONT>
</P>

<P><FONT SIZE=3D2>If you are not the intended recipient of this e-mail =
and have received</FONT>
<BR><FONT SIZE=3D2>it in error, please notify the sender by replying =
with 'received in</FONT>
<BR><FONT SIZE=3D2>error' as the subject and then delete it from your =
mailbox.</FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C47FA4.8090ECA3--