Were any of these the parameters you changed?
Ours was set to the default 4 minutes (240000 milliseconds). I set it to 1/4
that (60000) and it works.
Veritas says set it to 1 sec but Sun says don't go below 1 minute.
ndd -set /dev/tcp tcp_time_wait_interval 60000
>From Veritas' Web Site:
-----------------------------
This document (230050) is provided subject to the disclaimer at the end of
this document.
Symptom:
When performing backups, or restores, socket errors are being produced.
Exact Error Message:
Status codes 13, 14, 23, 24, 25 may occur. 13 = file read failed, 14 = file
write failed, 23 = socket read failed, 24 = socket write failed, 25 = cannot
connect on socket
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.
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
-----Original Message-----
From: David A. Chapa [mailto:david AT xbpadm-commands DOT com]
Sent: Friday, September 21, 2001 10:34 AM
To: Veritas NBU_Q&A
Subject: [Veritas-bu] bpduplicate & bpverify
Importance: High
I hope this gets to someone high up in NetBackup development...I am
struggling with a problem concerning bpduplicate and a socket write failure
(24). This case has been logged (150120468). I did some further testing
and found that I get the same error when I run a bpverify and I would assume
bpimport, but I haven't tested that as of yet.
from STDOUT after running bpverify command.
INF - failure logging message to client bakup189 in log /tmp/verify.output:
socket write failed (24)
INF - Verifying class special, schedule Full (bakup189_1001080401), media id
000353, created 09/21/2001 08:53:21.
What does bpduplicate and bpverify do differently for loggin that bpbackup?
I can issue that command from the command line with -L /tmp/mylogfile and it
works just fine.
If it helps this is being run from the master and the master as about eleven
media servers (mixture of NT and Unix)
Any help would be appreciated.
David
PS...yes this is the same problem I posted last week...it was not fixed with
the kernel parameter changes afterall. This is not your typical problem,
from what I can tell.
<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
NetBackup Consultant
DataStaff, Inc.
http://www.consulting.datastaff.com
847 413 1144
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
