Veritas-bu

Re: [Veritas-bu] (no subject)

2007-12-14 10:22:57
Subject: Re: [Veritas-bu] (no subject)
From: "Ed Wilts" <ewilts AT ewilts DOT org>
To: "pcuringa AT parker DOT com" <pcuringa AT parker DOT com>
Date: Fri, 14 Dec 2007 08:51:41 -0600
[root@osiris ~]# bperror -S 24 -r
socket write failed
A write operation to a socket failed.

Try the following:

1.  Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create debug log directories for the processes that could have returned this status code. Then retry the operation and check the resulting debug logs.
2.  A possible cause could be a high network load. For example, this has been seen in conjunction with Cannot write to STDOUT when a Windows system that is monitoring network load has detected a high load and sent an ICMP packet to other systems that says the route being used by those systems was disconnected. The log messages were similar to the following:
01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No route to host
01/31/96 14:05:48 ruble crabtree.null.com successfully wrote backup id crabtree.null.com_0823125016, copy 1, fragment 1, 440864 Kbytes at 628.538 Kbytes/sec
01/31/96 14:05:51 netbackup crabtree.null.com CLIENT crabtree.null.com POLICY Remote3SysFullW  SCHED Sirius  EXIT STATUS 24 (socket write failed)
3.  On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes).
4.  On Windows, verify that the recommended service packs are installed.
5.  This error may occur during a restore to a Novell client. Note the following possible actions:
   *  By default, the value for Novell "Maximum Packet Receive Buffers" may be too low (such as 100). The restore performance may be improved by changing this value to 2000. To change it, issue "SET Maximum Packet Receive Buffers=<value>" at the console, or enter the value in either of the following Novell files: sys:system\startup.ncf or sys:system\autoexec.ncf.
   *  Change to or add the following settings in the Novell sys:system\autoexec.ncf file:
   SET Maximum Packet Receive Buffers = 4000
   SET Maximum Directory Cache Buffers = 4000
   SET Maximum Concurrent Disk Cache Writes = 2000
   SET Maximum Concurrent Directory Cache Writes = 2000
   SET Maximum Physical Receive Packet Size = 1514
[root@osiris ~]#



On 12/14/07, pcuringa AT parker DOT com <pcuringa AT parker DOT com> wrote:

Does anybody know why a job fails  for a socket write failed(24) ? The server us up and can be pinged



--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu