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