cancel
Showing results for 
Search instead for 
Did you mean: 

Linux client backup getting code 13

Hello,

 We have a Linux SUSE client backup is continuously getting a code 13 file read failed.

 Netbackup Client 7.6.0.1

Netbackup Master Server 7.6.0.3 running on Linux

Below is a portion of the the bpbkar log

From the bpbkar log

 00:34:04.650 [7028] <16> bpbkar: ERR - bpbkar killed by SIGPIPE

00:34:04.651 [7028] <16> bpbkar: ERR - bpbkar FATAL exit status = 40: network co

00:34:04.651 [7028] <16> bpbkar: reached 11885

00:34:04.651 [7028] <4> bpbkar: INF - EXIT STATUS 40: network connection broken

00:34:04.651 [7028] <16> bpbkar: reached 11935

00:34:04.651 [7028] <8> bpbkar: WRN - Error closing stdout

 

From the bpbkar log

 00:34:04.650 [7028] <16> bpbkar: ERR - bpbkar killed by SIGPIPE

00:34:04.650 [7028] <16> bpbkar: reached 11627

00:34:04.650 [7028] <16> bpbkar: reached 11633

00:34:04.650 [7028] <16> bpbkar: reached 11698

00:34:04.650 [7028] <16> bpbkar: reached 11811

00:34:04.650 [7028] <16> bpbkar: reached 11839

00:34:04.651 [7028] <16> bpbkar: ERR - bpbkar FATAL exit status = 40: network connection broken

00:34:04.651 [7028] <16> bpbkar: reached 11885

00:34:04.651 [7028] <4> bpbkar: INF - EXIT STATUS 40: network connection broken

00:34:04.651 [7028] <16> bpbkar: reached 11935

00:34:04.651 [7028] <8> bpbkar: WRN - Error closing stdout

  I increased the timeout to =40000

 CLIENT_READ_TIMEOUT = 40000

 Is there anything else I should be looking at to resolve this error?

 Thanks in advance!

Tags (2)
8 Replies

Re: Linux client backup getting code 13

Please make sure your network configuration setting is correct, your bp.conf file is accurate and host resolution is perfect (either DNS or /etc/hosts).  Try to traceroute from client to media server and see if its as expected. Please check ifconfig setting matches with the any other working client.

Run all the network troubleshooting command to check if you are getting the correct output like - you may use bptestbpcd and bpclntcmd (on client).

Re: Linux client backup getting code 13

I would also check the file system(s), as a problem there can give status 13 too.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Re: Linux client backup getting code 13

Snippets like these do not help to troubleshoot.

This might be a Client Read Timeout, but we need all of the following (as .txt file attachments):

On media server - bpbrm and bptm (level 3 logs)

On client: full bpbkar log (level 3)

As well as all text in Job Details.

PS: 
Are you aware that support for all NBU versions up to 7.6.1.x ended on 1 Feb 2017?

Re: Linux client backup getting code 13

Hello,

Thanks, sorry this took a while another admin was working on this, however the issue remains.

Marianne, yes we know 7.6.1.x ended on 1 Feb 2017. There are reasons that an 7.7.x upgrade has not occurred for this server.

I have uploaded the log files.

 

 

Re: Linux client backup getting code 13

Hello,

Thanks, sorry this took a while another admin was working on this, however the issue remains.

Marianne, yes we know 7.6.1.x ended on 1 Feb 2017. There are reasons that an 7.7.x upgrade has not occurred for this server.

I have uploaded the log files.

 

 

Re: Linux client backup getting code 13

Hello,

Thanks, sorry this took a while another admin was working on this, however the issue remains.

Marianne, yes we know 7.6.1.x ended on 1 Feb 2017. There are reasons that an 7.7.x upgrade has not occurred for this server.

I have uploaded the log files.

 

 

Re: Linux client backup getting code 13

Here is the Media Server log file, sorry there seem to be no option to upload this at the same time. Unlike the previous webpage.

 

Thanks

Re: Linux client backup getting code 13

We need ALL of the info requested in my previous post.