Veritas-bu

[Veritas-bu] socket write failed (24)

2003-05-08 22:05:15
Subject: [Veritas-bu] socket write failed (24)
From: gtan AT microsoft DOT com (Gabriel Tan)
Date: Thu, 8 May 2003 19:05:15 -0700
This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
        boundary="----_=_NextPart_001_01C315CF.6F4BA659"

------_=_NextPart_001_01C315CF.6F4BA659
Content-Type: text/plain;
        charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hello there,

I have a Solaris 2.8 backup client that is failing with status 24 (
socket write failed ).

Master: Sol 2.8 - Netbackup 3.4
Client: Sol 2.8 - Netbackup 3.4

05/08/2003 00:06:14 master client  from client client: ERR - Cannot
write to STDOUT. Errno =3D 32: Broken pipe
05/08/2003 00:06:14 master client  media manager terminated during mount
of media id 001053, possible media mount timeout
05/08/2003 00:06:16 master client  media manager terminated by parent
process
05/08/2003 00:06:17 master client  backup of client client exited with
status 24 (socket write failed)
05/08/2003 00:06:50 master client  from client client: ERR - Cannot
write to STDOUT. Errno =3D 32: Broken pipe
05/08/2003 00:06:50 master client  media manager terminated during mount
of media id 001053, possible media mount timeout
05/08/2003 00:06:52 master client  media manager terminated by parent
process
05/08/2003 00:06:54 master client  backup of client client exited with
status 24 (socket write failed)
05/08/2003 00:06:54 master -  scheduler exiting - socket write failed
(24)  =20

Bpbkar output is something like:
...
15:01:45 [24894] <4> bpbkar PrintFile: /dev/dsk/c7t4d0s4
15:02:17 [24894] <16> flush_archive(): ERR - Cannot write to STDOUT.
Errno =3D 32: Broken pipe
15:02:17 [24894] <16> bpbkar Exit: ERR - bpbkar FATAL exit status =3D =
24:
socket write failed
15:02:17 [24894] <4> bpbkar Exit: INF - EXIT STATUS 24: socket write
failed
15:02:17 [24894] <2> bpbkar Exit: INF - Close of stdout complete


Truss output is something like:

write(1, " /\0\0\0\0\0\0\0\0\0\0\0".., 524288) (sleeping...)
write(1, " /\0\0\0\0\0\0\0\0\0\0\0".., 524288) Err#32 EPIPE
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
time() =3D 1052428541
write(4, " 1 4 : 1 5 : 4 1 E R R".., 63) =3D 63
time() =3D 1052428541
getpid() =3D 22879 [1]
write(3, " 1 4 : 1 5 : 4 1 [ 2 2".., 93) =3D 93
write(2, " E R R - ", 6) =3D 6
write(2, " C a n n o t w r i t e".., 47) =3D 47
write(2, "\n", 1) =3D 1
sigaction(SIGHUP, 0xFFBE2E20, 0xFFBE2EA0) =3D 0
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
time() =3D 1052428541
getpid() =3D 22879 [1]
write(3, " 1 4 : 1 5 : 4 1 [ 2 2".., 92) =3D 92
sigaction(SIGPIPE, 0xFFBE2E20, 0xFFBE2EA0) =3D 0
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
time() =3D 1052428541
getpid() =3D 22879 [1]
write(3, " 1 4 : 1 5 : 4 1 [ 2 2".., 76) =3D 76
write(2, " I N F - ", 6) =3D 6
write(2, " E X I T S T A T U S ".., 35) =3D 35
write(2, "\n", 1) =3D 1
close(1) =3D 0
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
open("/usr/openv/msg/C/netbackup/PrgMsgs", O_RDONLY) Err#2 ENOENT
time() =3D 1052428541
getpid() =3D 22879 [1]
write(3, " 1 4 : 1 5 : 4 1 [ 2 2".., 65) =3D 65
sigaction(SIGALRM, 0xFFBE2E20, 0xFFBE2EA0) =3D 0
alarm(300) =3D 0
access("/usr/openv/netbackup/bin/bpend_notify.ouroboros.fullbkps", 0)
Err#2 ENOENT
access("/usr/openv/netbackup/bin/bpend_notify.ouroboros", 0) Err#2
ENOENT
access("/usr/openv/netbackup/bin/bpend_notify", 0) Err#2 ENOENT
alarm(0) =3D 300
sigaction(SIGALRM, 0xFFBE2E20, 0xFFBE2EA0) =3D 0
llseek(0, 0, SEEK_CUR) Err#29 ESPIPE
llseek(6, 0, SEEK_CUR) =3D 0
_exit(24)=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D
    =20

Has anyone encountered this type of errors before? I've changed tcp
abort interval and wait interval as suggested in some of the knowledge
base I saw. But, none seems to work.

This client backup was running fine till this past weekend when the
client crash while backup was running. When the system came back up, it
retry'd and backup completed successfully. Any backup that was initiated
after that led to a socket write failed.

Any Ideas???


Cheers,
Gabriel
                            =20

------_=_NextPart_001_01C315CF.6F4BA659
Content-Type: text/html;
        charset="US-ASCII"
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.6895.3">
<TITLE>[Veritas-bu] socket write failed (24)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello there,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a Solaris 2.8 backup client that =
is failing with status 24 ( socket write failed ).</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Master: Sol 2.8 - Netbackup 3.4</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Client: Sol 2.8 - Netbackup 3.4</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:14 master client&nbsp; =
from client client: ERR - Cannot write to STDOUT. Errno =3D 32: Broken =
pipe</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:14 master =
client&nbsp; media manager terminated during mount of media id 001053, =
possible media mount timeout</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:16 master client&nbsp; =
media manager terminated by parent process</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:17 master =
client&nbsp; backup of client client exited with status 24 (socket write =
failed)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:50 master =
client&nbsp; from client client: ERR - Cannot write to STDOUT. Errno =3D =
32: Broken pipe</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:50 master =
client&nbsp; media manager terminated during mount of media id 001053, =
possible media mount timeout</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:52 master client&nbsp; =
media manager terminated by parent process</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:54 master =
client&nbsp; backup of client client exited with status 24 (socket write =
failed)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">05/08/2003 00:06:54 master -&nbsp; =
scheduler exiting - socket write failed (24)&nbsp;&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Bpbkar output is something like:</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">...</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">15:01:45 [24894] &lt;4&gt; bpbkar =
PrintFile: /dev/dsk/c7t4d0s4</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">15:02:17 [24894] &lt;16&gt; =
flush_archive(): ERR - Cannot write to STDOUT. Errno =3D 32: Broken =
pipe</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">15:02:17 [24894] &lt;16&gt; bpbkar =
Exit: ERR - bpbkar FATAL exit status =3D 24: socket write failed</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">15:02:17 [24894] &lt;4&gt; bpbkar =
Exit: INF - EXIT STATUS 24: socket write failed</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">15:02:17 [24894] &lt;2&gt; bpbkar =
Exit: INF - Close of stdout =
complete&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Truss output is something like:</FONT>
</P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">write(1, &quot; =
/\0\0\0\0\0\0\0\0\0\0\0&quot;.., 524288) (sleeping...)<BR>
write(1, &quot; /\0\0\0\0\0\0\0\0\0\0\0&quot;.., 524288) Err#32 =
EPIPE<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
time() =3D 1052428541<BR>
write(4, &quot; 1 4 : 1 5 : 4 1 E R R&quot;.., 63) =3D 63<BR>
time() =3D 1052428541<BR>
getpid() =3D 22879 [1]<BR>
write(3, &quot; 1 4 : 1 5 : 4 1 [ 2 2&quot;.., 93) =3D 93<BR>
write(2, &quot; E R R - &quot;, 6) =3D 6<BR>
write(2, &quot; C a n n o t w r i t e&quot;.., 47) =3D 47<BR>
write(2, &quot;\n&quot;, 1) =3D 1<BR>
sigaction(SIGHUP, 0xFFBE2E20, 0xFFBE2EA0) =3D 0<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
time() =3D 1052428541<BR>
getpid() =3D 22879 [1]<BR>
write(3, &quot; 1 4 : 1 5 : 4 1 [ 2 2&quot;.., 92) =3D 92<BR>
sigaction(SIGPIPE, 0xFFBE2E20, 0xFFBE2EA0) =3D 0<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
time() =3D 1052428541<BR>
getpid() =3D 22879 [1]<BR>
write(3, &quot; 1 4 : 1 5 : 4 1 [ 2 2&quot;.., 76) =3D 76<BR>
write(2, &quot; I N F - &quot;, 6) =3D 6<BR>
write(2, &quot; E X I T S T A T U S &quot;.., 35) =3D 35<BR>
write(2, &quot;\n&quot;, 1) =3D 1<BR>
close(1) =3D 0<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
open(&quot;/usr/openv/msg/C/netbackup/PrgMsgs&quot;, O_RDONLY) Err#2 =
ENOENT<BR>
time() =3D 1052428541<BR>
getpid() =3D 22879 [1]<BR>
write(3, &quot; 1 4 : 1 5 : 4 1 [ 2 2&quot;.., 65) =3D 65<BR>
sigaction(SIGALRM, 0xFFBE2E20, 0xFFBE2EA0) =3D 0<BR>
alarm(300) =3D 0<BR>
access(&quot;/usr/openv/netbackup/bin/bpend_notify.ouroboros.fullbkps&quo=
t;, 0) Err#2 ENOENT<BR>
access(&quot;/usr/openv/netbackup/bin/bpend_notify.ouroboros&quot;, 0) =
Err#2 ENOENT<BR>
access(&quot;/usr/openv/netbackup/bin/bpend_notify&quot;, 0) Err#2 =
ENOENT<BR>
alarm(0) =3D 300<BR>
sigaction(SIGALRM, 0xFFBE2E20, 0xFFBE2EA0) =3D 0<BR>
llseek(0, 0, SEEK_CUR) Err#29 ESPIPE<BR>
llseek(6, 0, SEEK_CUR) =3D 0<BR>
_exit(24)</FONT>=20
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Has anyone encountered this type of =
errors before? I've changed tcp abort interval and wait interval as =
suggested in some of the knowledge base I saw. But, none seems to =
work.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This client backup was running fine =
till this past weekend when the client crash while backup was running. =
When the system came back up, it retry'd and backup completed =
successfully. Any backup that was initiated after that led to a socket =
write failed.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Any Ideas???</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Cheers,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Gabriel</FONT>

<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C315CF.6F4BA659--

--------------InterScan_NT_MIME_Boundary--


<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] socket write failed (24), Gabriel Tan <=