Veritas-bu

[Veritas-bu] My 2 cents on "socket write failed (24)"

2004-03-29 13:04:21
Subject: [Veritas-bu] My 2 cents on "socket write failed (24)"
From: DMoses AT leviton DOT com (Moses, Darby)
Date: Mon, 29 Mar 2004 13:04:21 -0500
This is a multi-part message in MIME format.

------_=_NextPart_001_01C415B8.4324C48C
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Let me preface this by stating "I am very new to the Unix/Linux
platform"
=20
    After several weeks of not being able to perform a backup on one of
my Linux servers and intermittent failures on a UNIX box we've found the
problem.  It has nothing to do with protocols or sockets.  I have also
been working with Veritas for a month.  It is embarrassing but here is
the true problem.  If the disk used by Veritas to generate logs on the
client is full the "socket write failed(24)" is generated.  Veritas was
completely unaware of the condition.  My question is why would a disk
full condition generate a socket error?
=20
Thanks
Darby
=20
=20

------_=_NextPart_001_01C415B8.4324C48C
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial size=3D2>Let me =
preface this=20
by stating "I am very new to the Unix/Linux =
platform"</FONT></SPAN></DIV>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;=20
After several weeks of not being able to perform a backup on one of my =
Linux=20
servers and intermittent failures on a UNIX box we've found the =
problem.&nbsp;=20
It has nothing to do with protocols or sockets.&nbsp; I have =
also&nbsp;been=20
working with Veritas for a month.&nbsp; It is embarrassing but here is =
the true=20
problem.&nbsp; If the disk used by Veritas to generate logs on the =
client is=20
full the "socket write failed(24)" is generated.&nbsp; Veritas was =
completely=20
unaware of the&nbsp;condition.&nbsp;&nbsp;My question is why would a =
disk full=20
condition generate a socket error?</FONT></SPAN></DIV>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial=20
size=3D2>Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial=20
size=3D2>Darby</FONT></SPAN></DIV>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D809585417-29032004><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C415B8.4324C48C--

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] My 2 cents on "socket write failed (24)", Moses, Darby <=