cancel
Showing results for 
Search instead for 
Did you mean: 

Error bpbrm (pid=12433) socket read failed: errno = 62 - Timer expired

Avinash
Level 2
Certified
I am getting error 13 with the following details. Can anyone help with the cause/resolution of this error ?


04/17/2009 13:54:51 - requesting resource NTTA-Shared-Onsite-CDL1
04/17/2009 13:54:51 - requesting resource iadehbkwhms.NBU_CLIENT.MAXJOBS.srvr19031-be
04/17/2009 13:54:51 - requesting resource iadehbkwhms.NBU_POLICY.MAXJOBS.GMP-46002469-sol-os-enc-01
04/17/2009 13:54:52 - granted resource iadehbkwhms.NBU_CLIENT.MAXJOBS.srvr19031-be
04/17/2009 13:54:52 - granted resource iadehbkwhms.NBU_POLICY.MAXJOBS.GMP-46002469-sol-os-enc-01
04/17/2009 13:54:52 - granted resource AI0063
04/17/2009 13:54:52 - granted resource Drive025
04/17/2009 13:54:52 - granted resource iadehbkmd04-be-hcart2-robot-tld-6
04/17/2009 13:54:52 - estimated 58333401 kbytes needed
04/17/2009 13:54:53 - started process bpbrm (pid=12426)
04/17/2009 13:54:58 - connecting
04/17/2009 13:54:59 - connected; connect time: 0:00:00
04/17/2009 13:54:59 - mounting AI0063
04/17/2009 13:55:06 - mounted AI0063; mount time: 0:00:07
04/17/2009 13:55:06 - positioning AI0063 to file 55
04/17/2009 13:55:06 - positioned AI0063; position time: 0:00:00
04/17/2009 13:55:06 - begin writing
04/17/2009 13:59:51 - current media AI0063 complete, requesting next media Any
04/17/2009 13:59:52 - granted resource AI0090
04/17/2009 13:59:52 - granted resource Drive023
04/17/2009 13:59:52 - granted resource iadehbkmd04-be-hcart2-robot-tld-6
04/17/2009 13:59:53 - mounting AI0090
04/17/2009 14:00:00 - mounted AI0090; mount time: 0:00:07
04/17/2009 14:00:00 - positioning AI0090 to file 1
04/17/2009 14:00:00 - positioned AI0090; position time: 0:00:00
04/17/2009 14:00:00 - begin writing
04/17/2009 15:31:17 - Error bpbrm (pid=12433) socket read failed: errno = 62 - Timer expired
04/17/2009 15:31:18 - end writing; write time: 1:31:18
file read failed (13)

3 REPLIES 3

scorpy_582
Level 6
There are many reasons for this error:


This is most likely a network issue. 
-> Check the NIC speed. (Have full duplex all over)
->  If the client is a unix client with multiple interfaces, user REQUIRED_INTERFACE
-> Enable the bpbkar logs on the client to see if it is not dying unexpectedly.
-> Enable bpcd logs on the media server and the client t get more specific error message


Srikanth_Gubbal
Level 6
Certified
i agree with Scorpy, i feel it is due to non availabilty of ports on the client side, run netstat -a on client and check for TIME_WAIT,  if they are more then, apart from his suggestions try these.

update the NIC drivers to latest.
if you are facing problem with all clients, increase the Client read timeout in host properties of master server
or if you face problem with a single client, increase the client read timeout and file browse time out in host properties of client.

let me know if this solves your problem.

Taqadus_Rehman
Level 6
 Mostly this error occure due to shortage of sockets for a particular backup. when all open socktes are in use and backup has to wait for longer for socket to get free.

You can check tcp/ip TIME_WAIT_INTERVAL, by default in unix it is 60000 sec, this can be set to 10sec or less with no adverse effect on performance.