Forum Discussion

cnx_anup's avatar
cnx_anup
Level 4
10 years ago

socket write failed(24)

Hi Folks,

Below is the logs(details tab) generated when the backup of one of the server fails.

6/30/2015 8:42:26 PM - connecting
6/30/2015 8:42:27 PM - Info bptm(pid=17396) setting receive network buffer to 263168 bytes      
6/30/2015 8:42:28 PM - Info bpbrm(pid=19244) start bpbkar32 on client         
6/30/2015 8:42:28 PM - connected; connect time: 0:00:02
6/30/2015 8:42:28 PM - begin writing
6/30/2015 8:42:29 PM - Info bpbkar32(pid=10516) Backup started           
6/30/2015 8:42:29 PM - Info bpbrm(pid=19244) Sending the file list to the client      
6/30/2015 8:42:29 PM - Info bpbkar32(pid=10516) change time comparison:<disabled>          
6/30/2015 8:42:29 PM - Info bpbkar32(pid=10516) archive bit processing:<enabled>          
6/30/2015 8:42:29 PM - Info bpbkar32(pid=10516) not using change journal data for <D:\>: not enabled    
6/30/2015 8:56:42 PM - Critical bpbrm(pid=19244) from client phsqlserve.gm.net: FTL - socket write failed     
6/30/2015 8:56:42 PM - Info bpbrm(pid=19344) child done, status 24         
6/30/2015 8:56:42 PM - Info bpbrm(pid=19344) sending message to media manager: STOP BACKUP phsqlserve.gm.net_1435654829     
6/30/2015 8:56:55 PM - Info bpbrm(pid=19344) media manager for backup id phsqlserve.gm.net_1435654829 exited with status 150: termination requested by administrator
6/30/2015 8:56:55 PM - end writing; write time: 0:14:27
socket write failed(24)

Issue is intermittent.

Why it says "status 150: termination requested by administrator" ? I'm not cancelling the job.

I am trying to find Root cause. Can somebody give me steps to debug this issue ...

  • There is about 10 minutes between these 2 time stamps: 

    6/30/2015 8:42:29 PM -   
    6/30/2015 8:56:42 PM -

    To know where the break in communication is and if any data was transferred in this period, you will need to have a look at logs.

    Level 0 logs will not help - you will need to increase logging level on media server and client to at least level 3.

    Logs that are needed:

    On client: bpbkar

    On media server: bptm and bpbrm.

     

8 Replies

Replies have been turned off for this discussion
  • Status 150 when no one cancled the jobs, indicate a resource limit of the system, check RAM or swap/page file settings on the master server.

  • There is about 10 minutes between these 2 time stamps: 

    6/30/2015 8:42:29 PM -   
    6/30/2015 8:56:42 PM -

    To know where the break in communication is and if any data was transferred in this period, you will need to have a look at logs.

    Level 0 logs will not help - you will need to increase logging level on media server and client to at least level 3.

    Logs that are needed:

    On client: bpbkar

    On media server: bptm and bpbrm.

     

  • RAM is 16 GB on the master server. It's a Win 2008 R2 64 bit. It's a branch office and backing up some 5 servers. 

  • Forget about the status 150. The real error is the status 24: Critical bpbrm(pid=19244) from client phsqlserve.gm.net: FTL - socket write failed You will need logs as per my post of yesterday.
  • Hi Marianne, thank you. This one makes sense.

     

    I want to confirm if I'm doing it right about the increasing debug level. So this is what I have done.

     

    On the media server and on the client machines, Opened BAR(backup, archive and restore) window, made the following change :

    debug level.JPG

    And on Media server created folders for bptm and bpbrm.

    On client machine created folder for bpbkar.

     

    Is that all I have to do ?

  • The above should be done for Client only.
    Maybe a good idea to increase TCP logging level on the client as well (since the error is network related).

    For the Media server, open Host Properties on the master server, select Media Servers -> Media server name -> Logging.
    Here you can select only bptm and bpbrm to increase logging.

  • Ok.. I reverted it back on Master server. and made the changes as you suggested. We have media server and master server the same since this is a branch office. May be that's why I dont see media servers under Host properties. So I chose Master Servers > master server name > Logging.