Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

network connection timed out(41)

Created: 30 Aug 2011 • Updated: 30 Aug 2011 | 2 comments
Pritesh Pisal's picture

We are getting frequent backup failure “network connection timed out(41)” on Alpha base client.

 Master server is NB7.0.

 NB ver. 6.0 client with MP7

1)I have increased the client read timeout 300 to 3000  and backup size is 350gb

but after making changes it fails with error code 40 (network connection broken)

Please find the bpbkar logs

 

Comments 2 CommentsJump to latest comment

Marianne's picture

Seems bpbkar is getting stuck on 'nohup.out' :

07:25:57.886 [9044] <2> bpbkar SelectFile: INF - path = nohup.out
07:39:11.982 [9044] <16> bpbkar sighandler: ERR - bpbkar killed by SIGPIPE
07:39:11.982 [9044] <2> bpbkar sighandler: INF - ignoring additional SIGPIPE signals
07:39:11.982 [9044] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 40: network connection broken

 

Where have you increased the timeout? Time between last 'SelectFile' entry and failure is just short of 15 minutes.

Try to exclude nohup.out as a start.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Pritesh Pisal's picture

I have increased the timeout value on master server as well as respective client host properties timeouts

master server act as media server too

how will I exclude nohup.out as a start.