Looks and sounds like there is some other issue with the network and it's
not NetBackup here. Try doing file transfers from the problem machine to
somewhere else, taking NBU out of the picture. Check switch and NIC logs
and stats for the whole path. It may be an issue with the NIC driver, too.
If you need more definitive assistance, Symantec Support has a tool called
Apparenet that will probe the network, end to end, and provide
recommendations on what needs to be fixed. I've used it many times to
prove to networking that there was a problem.
Thank you,
Rusty
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of adgwytc
Sent: Friday, August 05, 2011 5:53 AM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] Netbackup fail issue (FTL - Socket 24)
Hi
We have an issue where is we utilise netbackup it works under 2mb but when
it goes above that speed it fails. Here is a section of the client trace
and also the Server:
Client:
14:08:26.482: [7216.6592] <32> TransporterRemote::write[2](): FTL -
SocketWriteException: send() call failed, could not write data to the
socket, possible broken connection.
14:08:26.482: [7216.6592] <16> NBUException::traceException(): ( An
Exception of type [Symantec::NetBackup::Ncf::OperationFailedException] was
thrown. Details about the exception follow...:
Error code = (-1008).
Src file = (D:\654\src\cl\clientpc\util\tar_tfi.cpp).
Src Line = (275).
Description = (%s getBuffer operation failed).
Operation type=().
)
14:08:26.498: [7216.6592] <16> NBUException::traceException(): ( An
Exception of type [Symantec::NetBackup::Ncf::SocketWriteException] was
thrown. Details about the exception follow...:
Error code = (-1027).
Src file = (TransporterRemote.cpp).
Src Line = (310).
Description = (send() call failed, could not write data to the socket,
possible broken connection).
Local IP=(). Remote IP=(). Remote Port No.=(0).
No. of bytes to write=(32768) while No. of bytes written=(0).
Server
14:08:26.371 [4696.6196] <32> bpbrm main: from client csspow03: FTL -
socket write failed
14:08:26.386 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4035:
connect in progress: 0 0x00000000
14:08:26.402 [4696.6196] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048:
VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
14:08:26.402 [4696.6196] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062:
service: bpjobd
14:08:26.589 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4221: in
progress connect: 0 0x00000000
14:08:26.589 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4224:
connect: async CONNECT FROM xxx.xxx.xxx.xxx.2241 TO xxx.xxx.xxx.xxx.13724
fd = 668
14:08:26.589 [4696.6196] <2> job_connect: SO_KEEPALIVE set on socket 668
for client csbkupv01
14:08:26.589 [4696.6196] <2> logconnections: BPJOBD CONNECT FROM
xxx.xxx.xxx.xxx.2241 TO xxx.xxx.xxx.xxx.13724
14:08:26.589 [4696.6196] <2> vauth_authentication_required:
vauth_comm.c.749: no methods for address: no authentication required
14:08:26.589 [4696.6196] <2> vauth_connector: vauth_comm.c.182: no methods
for address: no authentication required
14:08:26.589 [4696.6196] <2> job_authenticate_connection: no
authentication required
14:08:26.589 [4696.6196] <2> job_authenticate_connection: ignoring VxSS
authentication check for now...
14:08:26.589 [4696.6196] <2> job_connect: Connected to the host csbkupv01
contype 10 jobid <69122> socket <668>
14:08:26.589 [4696.6196] <2> job_connect: Connected on port 2241
14:08:26.589 [4696.6196] <2> set_job_details: Sending Tfile jobid (69122)
14:08:26.589 [4696.6196] <2> set_job_details: LOG 1312463306 32 bpbrm 4696
from client csspow03: FTL - socket write failed
14:08:26.589 [4696.6196] <2> set_job_details: Done
14:08:26.808 [4696.6196] <2> job_monitoring_exex: ACK disconnect
14:08:26.808 [4696.6196] <2> job_disconnect: Disconnected
14:08:26.808 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4035:
connect in progress: 0 0x00000000
14:08:26.839 [4696.6196] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048:
VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
14:08:26.839 [4696.6196] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062:
service: bpdbm
14:08:27.027 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4221: in
progress connect: 0 0x00000000
14:08:27.027 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4224:
connect: async CONNECT FROM xxx.xxx.xxx.xxx.2242 TO xxx.xxx.xxx.xxx.13724
fd = 644
14:08:27.027 [4696.6196] <2> logconnections: BPDBM CONNECT FROM
xxx.xxx.xxx.xxx.2242 TO xxx.xxx.xxx.xxx.13724
14:08:27.027 [4696.6196] <2> vauth_authentication_required:
vauth_comm.c.749: no methods for address: no authentication required
14:08:27.027 [4696.6196] <2> vauth_connector: vauth_comm.c.182: no methods
for address: no authentication required
14:08:27.027 [4696.6196] <2> check_authentication: no authentication
required
14:08:27.027 [4696.6196] <2> vnet_check_vxss_client_magic_with_info:
vnet_vxss_helper.c.770: Ignoring VxSS authentication: 2 0x00000002
14:08:27.027 [4696.6196] <2> vnet_check_vxss_client_magic_with_info:
vnet_vxss_helper.c.926: Not using VxSS authentication: 2 0x00000002
14:08:27.574 [4696.6196] <2> bpbrm main: client csspow03 EXIT STATUS = 24:
socket write failed
14:08:27.574 [4696.6196] <2> bpbrm kill_child_process_Ex: start
14:08:58.120 [4696.6196] <2> bpbrm wait_for_child: start
14:08:58.120 [4696.6196] <2> bpbrm wait_for_child: child exit_status = 150
14:08:58.120 [4696.6196] <2> inform_client_of_status: INF - Server status
= 24
14:08:58.120 [4696.6196] <2> put_long: (11) network write() error: An
existing connection was forcibly closed by the remote host. ; socket = 700
14:08:58.120 [4696.6196] <16> inform_client_of_status: could not send
server status message
14:08:58.120 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4035:
connect in progress: 0 0x00000000
14:08:58.152 [4696.6196] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048:
VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
14:08:58.152 [4696.6196] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062:
service: bpjobd
14:08:58.308 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4221: in
progress connect: 0 0x00000000
14:08:58.308 [4696.6196] <2> vnet_async_connect: vnet_vnetd.c.4224:
connect: async CONNECT FROM xxx.xxx.xxx.xxx.2249 TO xxx.xxx.xxx.xxx.13724
fd = 644
14:08:58.308 [4696.6196] <2> job_connect: SO_KEEPALIVE set on socket 644
for client csbkupv01
14:08:58.308 [4696.6196] <2> logconnections: BPJOBD CONNECT FROM
xxx.xxx.xxx.xxx.2249 TO xxx.xxx.xxx.xxx.13724
14:08:58.308 [4696.6196] <2> vauth_authentication_required:
vauth_comm.c.749: no methods for address: no authentication required
14:08:58.308 [4696.6196] <2> vauth_connector: vauth_comm.c.182: no methods
for address: no authentication required
14:08:58.308 [4696.6196] <2> job_authenticate_connection: no
authentication required
14:08:58.308 [4696.6196] <2> job_authenticate_connection: ignoring VxSS
authentication check for now...
14:08:58.308 [4696.6196] <2> job_connect: Connected to the host csbkupv01
contype 10 jobid <69122> socket <644>
14:08:58.308 [4696.6196] <2> job_connect: Connected on port 2249
I am not a netbackup person so please excuse me if the answer is obvious
Thanks
+----------------------------------------------------------------------
|This was sent by adgwytc AT lycos DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
