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_01C12EFF.12BDEEA0
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
We are having similar situation here with 25, 41, 54, 58, 13 etc etc =
errors.
Next day the manual runs fine. Here is a article from Veritas site (It
wasn't under "error 25, status code 25 or status 25" it was under "25"!
Their web site needs a better index or search engine).
=20
I didn't set it as low as they had wanted (1 sec) but just by cutting =
it in
half I reduced the errors I was getting from 20-30 a night down to 2 or =
3. I
went from 4 minutes to 2 and will try going from 2 to 1 to see if that =
fixes
the remaining ones. Hope this helps your problem. Sounds very familiar.
=20
Ours was set to the default 4 minutes (240000 milliseconds). I set it =
to
half that (120000) to try it out. - TRM 24Aug01
------------------------------------------------------------------------=
---
This document (230050) is provided subject to the disclaimer at the end =
of
this document.=20
Symptom:=20
When performing backups, or restores, socket errors are being produced. =
Exact Error Message:=20
Status codes 13, 14, 23, 24, 25 may occur. 13 =3D file read failed, 14 =
=3D file
write failed, 23 =3D socket read failed, 24 =3D socket write failed, 25 =
=3D cannot
connect on socket=20
Solution:=20
Possibly the NetBackup server is getting a lot of traffic from clients;
therefore, sockets are not becoming free soon enough to satisfy the =
demand.
For Solaris 2.6 or previous use the following command:
ndd -get /dev/tcp tcp_close_wait_interval
For Solaris 7 or above use the following command:
ndd -get /dev/tcp tcp_time_wait_interval
For HP-UX 11 use the following command:
ndd -get /dev/tcp tcp_time_wait_interval
(NOTE: The equivalent command on HP-UX 10 is "nettune" instead of =
"ndd".)=20
These commands will produce a large number, like the default 240000 =
(value
is in milliseconds, so 240 seconds or 4 minutes). This is the amount of =
time
to wait after a socket is closed before it can be reused. In most cases =
this
can be shortened to about 1 second (1000) and may alleviate the =
problem.=20
The command to set it to 1000 on Solaris 2.6 and previous versions is:
ndd -set /dev/tcp tcp_close_wait_interval 1000
The command to set it to 1000 on Solaris 7 and later versions is:
ndd -set /dev/tcp tcp_time_wait_interval 1000
or=20
The command to set it to 1000 on HP-UX 11 is:
ndd -set /dev/tcp tcp_time_wait_interval 1000
The "ndd" command makes the change immediately, without a need for a =
reboot.
This setting will go back to default after a reboot. To make it set to =
this
value after each reboot, the command can be added to the appropriate =
TCP/IP
startup script. On Solaris, this is /etc/rc2.d/S69inet or on HP-UX 11 =
see
/etc/rc.config.d/nddconf for examples of how to set it.
-----Original Message-----
From: Jonas Bl=E5berg [mailto:jonas.blaberg AT cellnetwork DOT com]
Sent: Monday, August 27, 2001 12:55 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] a large file, error 41
Hello!=20
We are using netbackup to backup a file of about 40GB which is the only =
file
in that Backup Class. We get error 41 (network connection timed out) =
every
night. When we run a Manual Backup on this Class in daylight it is
successful.
Anyone who has a hint?=20
/jonas=20
Jonas Bl=E5berg=20
Cell Network Sverige AB=20
Kruthusgatan 17,6=20
S-411 04 G=F6teborg=20
jonas.blaberg AT cellnetwork DOT com=20
@office: +46-(0)31-707 69 85=20
not@office: +46-(0)709-95 00 68=20
------_=_NextPart_001_01C12EFF.12BDEEA0
Content-Type: text/html;
charset=iso-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>a large file, error 41</TITLE>
<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=364134713-27082001><FONT face=Arial color=#0000ff size=2>We
are
having similar situation here with 25, 41, 54, 58, 13 etc etc errors. Next day
the manual runs fine. Here is a article from Veritas site (It wasn't under
"error 25, status code 25 or status 25" it was under "25"! Their web site needs
a better index or search engine).</FONT></SPAN></DIV>
<DIV><SPAN class=364134713-27082001><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=364134713-27082001><FONT face=Arial color=#0000ff size=2>I
didn't set it as low as they had wanted (1 sec) but just by cutting it in half
I
reduced the errors I was getting from 20-30 a night down to 2 or 3. I went from
4 minutes to 2 and will try going from 2 to 1 to see if that fixes the
remaining
ones. Hope this helps your problem. Sounds very familiar.</FONT></SPAN></DIV>
<DIV><SPAN class=364134713-27082001><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=364134713-27082001><FONT size=2>
<P>Ours was set to the default 4 minutes (240000 milliseconds). I set it to
half
that (120000) to try it out. - TRM 24Aug01</P>
<P>---------------------------------------------------------------------------</P>
<P>This document (230050) is provided subject to the disclaimer at the end of
this document. </P>
<P>Symptom: </P></FONT>
<TABLE cellSpacing=0 width=780 border=0>
<TBODY>
<TR>
<TD><FONT size=2>
<P>When performing backups, or restores, socket errors are being
produced.
</FONT></P></TD></TR></TBODY></TABLE><B><FONT size=2>
<P>Exact Error Message:</B> </P></FONT><FONT face=Courier size=2>
<P>Status codes 13, 14, 23, 24, </FONT><FONT face=Courier color=#ff0000
size=4>25</FONT><FONT face=Courier size=2> may occur. 13 = file read failed, 14
= file write failed, 23 = socket read failed, 24 = socket write failed,
</FONT><FONT face=Courier color=#ff0000 size=4>25</FONT><FONT face=Courier
size=2> = cannot connect on socket</FONT><FONT size=2> </P>
<P>Solution: </P>
<P>Possibly the NetBackup server is getting a lot of traffic from clients;
therefore, sockets are not becoming free soon enough to satisfy the
demand.<BR><BR>For Solaris 2.6 or previous use the following command:<BR>ndd
-get /dev/tcp tcp_close_wait_interval<BR><BR>For Solaris 7 or above use the
following command:<BR>ndd -get /dev/tcp tcp_time_wait_interval<BR><BR>For HP-UX
11 use the following command:<BR>ndd -get /dev/tcp
tcp_time_wait_interval<BR>(NOTE: The equivalent command on HP-UX 10 is
"nettune"
instead of "ndd".) <BR><BR>These commands will produce a large number, like the
default 240000 (value is in milliseconds, so 240 seconds or 4 minutes). This is
the amount of time to wait after a socket is closed before it can be reused. In
most cases this can be shortened to about 1 second (1000) and may alleviate the
problem. <BR><BR>The command to set it to 1000 on Solaris 2.6 and previous
versions is:<BR>ndd -set /dev/tcp tcp_close_wait_interval 1000<BR><BR>The
command to set it to 1000 on Solaris 7 and later versions is:<BR>ndd -set
/dev/tcp tcp_time_wait_interval 1000<BR><BR>or <BR>The command to set it to
1000
on HP-UX 11 is:<BR>ndd -set /dev/tcp tcp_time_wait_interval 1000<BR><BR>The
"ndd" command makes the change immediately, without a need for a reboot. This
setting will go back to default after a reboot. To make it set to this value
after each reboot, the command can be added to the appropriate TCP/IP startup
script. On Solaris, this is /etc/rc2.d/S69inet or on HP-UX 11 see
/etc/rc.config.d/nddconf for examples of how to set it.<BR></P></FONT><FONT
face=Arial size=2></FONT></SPAN></DIV>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Jonas Blåberg
[mailto:jonas.blaberg AT cellnetwork DOT com]<BR><B>Sent:</B> Monday, August
27, 2001
12:55 AM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT
edu<BR><B>Subject:</B>
[Veritas-bu] a large file, error 41<BR><BR></FONT></DIV><!-- Converted from
text/rtf format -->
<P><FONT face=Arial size=2>Hello!</FONT> </P>
<P><FONT face=Arial size=2>We are using netbackup to backup a file of about
40GB
which is the only file in that Backup Class. We get error 41 (network
connection
timed out) every night. When we run a Manual Backup on this Class in daylight
it
is successful.</FONT></P>
<P><FONT face=Arial size=2>Anyone who has a hint?</FONT> </P>
<P><FONT face=Arial size=2>/jonas</FONT> </P><BR>
<P><FONT face=Arial size=2>Jonas Blåberg</FONT> <BR><FONT face=Arial
size=2> Cell Network Sverige AB</FONT> <BR><FONT face=Arial size=2>
Kruthusgatan 17,6</FONT> <BR><FONT face=Arial size=2> S-411 04
Göteborg</FONT> <BR><FONT face=Arial size=2>jonas.blaberg AT cellnetwork DOT
com</FONT>
<BR><FONT face=Arial size=2>@office: +46-(0)31-707 69 85</FONT> <BR><FONT
face=Arial size=2>not@office: +46-(0)709-95 00 68</FONT> </P><BR></BODY></HTML>
------_=_NextPart_001_01C12EFF.12BDEEA0--
|
