Video Screencast Help

Cannot connect on socket(25)

Created: 28 Feb 2013 • Updated: 29 May 2013 | 6 comments
This issue has been solved. See solution.

Some restores suddenly returning error 25.  Services are running on all servers and name resolution is not a problem.

2/28/2013 9:38:03 AM - begin Restore
2/28/2013 9:38:08 AM - 11 images required
2/28/2013 9:38:09 AM - media 3303L5 required
2/28/2013 9:38:09 AM - media 3312L5 required
2/28/2013 9:38:09 AM - media 81D813 required
2/28/2013 9:38:09 AM - media 81D816 required
2/28/2013 9:38:09 AM - media 81D806 required
2/28/2013 9:38:09 AM - media 81D7F0 required
2/28/2013 9:38:09 AM - media 81D7FF required
2/28/2013 9:38:09 AM - media 81D7F4 required
2/28/2013 9:38:09 AM - media 81D817 required
2/28/2013 9:38:09 AM - media 81D80F required
2/28/2013 9:38:09 AM - media 81D80D required
2/28/2013 9:38:09 AM - media 81D812 required
2/28/2013 9:38:09 AM - media 81D818 required
2/28/2013 9:38:09 AM - media 81D81C required
2/28/2013 9:38:09 AM - media 81DA4B required
2/28/2013 9:38:09 AM - media 81DA56 required
2/28/2013 9:38:09 AM - media 81DA59 required
2/28/2013 9:38:09 AM - media 81DA55 required
2/28/2013 9:48:18 AM - restoring image lon-ish-fvs01_1356051602
2/28/2013 9:48:20 AM - Error bpbrm(pid=5820) bpcd on lon-ishare-01a.group.shlroot.local exited with status 48: client hostname could not be found
2/28/2013 9:48:21 AM - Info bpbrm(pid=5820) telling media manager to start restore on client     
2/28/2013 9:48:24 AM - Info bpbrm(pid=5820) Sending SIGHUP to media manager 2156       
2/28/2013 9:48:24 AM - Info bpbrm(pid=5820) terminating bpbrm child 4896 jobid=294456        
2/28/2013 9:48:24 AM - Error bpbrm(pid=5820) could not open event Global\NetBackup Terminate Event, pid: 4896, The system cannot find the file specified.
2/28/2013 9:48:24 AM - Warning bptm(pid=2156) failure logging message to client lon-ishare-01a.group.shlroot.local in log /C/Programà€ Files/Veritas/NetBackup/logs/user_ops/hank000/logs/NBWIN003:  client hostname could not be found (48)
2/28/2013 9:48:25 AM - Error bpbrm(pid=4896) bpcd on lon-ishare-01a.group.shlroot.local exited with status 48: client hostname could not be found
2/28/2013 9:48:26 AM - connecting
2/28/2013 9:48:26 AM - Error bpbrm(pid=4896) bpcd on lon-ishare-01a.group.shlroot.local exited with status 48: client hostname could not be found
2/28/2013 9:48:27 AM - requesting resource 3303L5
2/28/2013 9:48:27 AM - granted resource 3303L5
2/28/2013 9:48:27 AM - granted resource THD_TL_D2
2/28/2013 10:12:21 AM - Warning bprd(pid=11836) Restore must be resumed prior to first image expiration on 02/03/2013 14:52:55
2/28/2013 10:12:24 AM - end Restore; elapsed time: 00:34:21
cannot connect on socket(25)

Operating Systems:

Comments 6 CommentsJump to latest comment

HankHill's picture

No because this one returned 25 cannot connect on socket and the other was partially successful.  May be some errors in common in the details, but that doesn't mean the same solution would apply.

Nagalla's picture

both are from the same client, if you could fix 48 First, proablty that would help to this error also...

lets isolate from one error first... 

Vickie's picture

Error from logs, shows that NBU is not able to find the server name configured.

"2/28/2013 9:48:26 AM - Error bpbrm(pid=4896) bpcd on lon-ishare-01a.group.shlroot.local exited with status 48: client hostname could not be found"

Check the connectivity of client with media server and master server.Share output of below commands,

bpgetconfig -g clientname

bpclntcmd -pn

bpplclients | grep -i clientname (run on master server)

lets Hope this may help us to get some way towards resolution.

Mark_Solutions's picture

The restore fails after 10 minutes

I assume with the number of media involved that it is a large restore so by the time it has prepared its file list it has timed out

Increase the client connect and client read timeouts on your master and media servers to a larger figure (try 1800 or 3600) and see if that resolves it for you

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.