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

Netbackup client failing with 23 error continously - Need a solution

Created: 17 Nov 2013 • Updated: 19 Nov 2013 | 18 comments
This issue has been solved. See solution.

Hi All,

The Netbackup client is failing continously with 23 error (SOCKET read failed)

Ping, connections from client properties evrything fine!!

Tried bpcd -client - clientname -verbose - debug from master server and got the below details.... where i could find error in Vnet section...

Help me out guyzz!!!!!

Error log SS.PNG

Thanks in Advance!!!

Robert

Operating Systems:

Comments 18 CommentsJump to latest comment

Marianne's picture

The screenshot is too small to read.

Please copy the text and post here.

Ensure bpcd log folder exists on the client before you run bptestbpcd again.
Is anything logged in the file in bpcd folder?
Do you have a single master/media server or additional media server(s)?
If addtional media server(s), do bptestbpcd from there as well.

Please also copy all text in Details tab of failed job and post here.

Please tell us all versions on master, media server and client:
OS version and patch level
NBU version and patch level

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

Robert R A's picture

Hi Marianne,

I have replied you with logs in private message.. Please check.. Thank You yes

RamNagalla's picture

Vnetd_catched_getaddrinfo() failed.

looks like some name resolution issue on the client end..

make sure Media server and master server is resolving the Correct name and IP in the clinet end

check the below commands in client

bpclntcmd -ip <MasterserverIP>

bpclntcmd -hn <masterservername>

bpclntcmd -ip <Media server ip>

bpclntcmd -hn <media server name>

Robert R A's picture

Hi Nagalla,

All the above commands is looking fine when i tested!!

So i think this is someother issue..! :O

Thank You!!

nesel's picture

Hi Robert,

Kindly issue this command on master server

<NBU install path>\Netbackup\bin\admincmd\ bptestbpcd -client <clientname>

Try to put clientname on master server host file, then rerun bptestbpcd command

Thanks,

Nesel

Robert R A's picture

Hi Nesel,

I have checked that and found few errors like below,

21:20:55.879 [28574062] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1529: 0: in failed file cache: 8 0x00000008

Thank You

Guduru's picture

check if file systems have any issues(file system capacity or is it in read-only mode...etc) on client server...

Robert R A's picture

Hi Guduru,

I have checked the file systems capacity and they showed no issues!!

Thank You

Ah45's picture

Robert,

In most of the cases error 23 due to host name resolution

please do the follwing

<installed path>/netbackup/bin/bpclntcmd -pn

<installed path>/netbackup/bin/bpclntcmd -self

and check the CLIENT_NAME in

HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config

Robert R A's picture

Hi,

The second command which you have given

"<installed path>/netbackup/bin/bpclntcmd -self" is showing two different IP address with same host name in client,

Will that be an issue?????

Thank You

Ah45's picture

Robert,

Yes I think that is the issue,

please check the hosts entries

hosts.PNG

do

nslookup <clientname>

--> try adding entries in hosts file

--> work with your dns team..

Yogesh.Jadhav's picture

Rob,

1. Make sure netbackup client is successfully installed and does not have any installation issue

2. Check the connectivity from the both client and media server or master end using the connectivity commands already mentioned in the post above

3. Also check if there is enough space on server drive if its windows client

4. Check if you find something in bpcd logs.

Thanks

Yogesh

Thanks & Regards

Yogesh Jadhav
Robert R A's picture

Hi Yogesh,

First three steps you recommended are normal

And the bpcd logs shows some error as below,

21:20:55.879 [28574062] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1529: 0: in failed file cache: 8 0x00000008

Thank You

Marianne's picture

Thanks for output in PM.

We see in Activity Monitor that MediaServer=xxxx003.
 
Have you tried bptestbpcd from this Media server?
 
Is anything logged in bpcd log after connection attempt from media server xxxx003?
We need to see full bpcd log.
The snippet in your post above is not enough.
 
Have you tested name lookup between media server  xxxx003 and the client?
 

On Media server:
bpclntcmd -hn <Client-name>
bpclntcmd -ip <Client-IP>

On Client:
bpclntcmd -hn <media server name>
bpclntcmd -ip <Media server ip>

Yes, 2 IP addresses with one hostname has been known for causing problems - Connection attempt is received on one IP address and Connect Back is attempted on other IP address.

Best to add hosts entries on the client to bind the different IP addresses to different hostnames.

Bind the hostname to the IP address that must be used for backups and 2nd IP to different hostname.

*** EDIT ***

Small steps to solve - start with this media server (xxxx003).
Check forward and reverse lookup between media server and client using bpclntcmd.
If good, use bptestbpcd on media server to test connection.
Check client's bpcd log to see if connection request is received.
 
Only when resolved, perform same steps for next media server.

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

Marianne's picture

Thank you for bpcd log file via PM.

Double-check SERVER list on Client. You should be able to use Host Properties from master server to do that.
 
Firstly, it seems client does not have Server entries for media server xxx001, xxx002 or xxx003.
 
Secondly, the Server list looks WAY too big - Client cannot resolve some of those hostnames.
You can see in bpcd log how client is comparing resolved hostname with current Server list and also try to perform forward hostname lookup for each of these server names.
Example of failed lookup:
 
hosts_equal: gethostbyname failed for aaaaaaa.FQDN: The requested name is valid, but no data of the requested type was found.
 
There are WAY too many of these errors. Either remove these Server entries from Client's server list, or fix hostname lookup via hosts files or DNS.

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

SOLUTION
Marianne's picture

I was hoping that Robert would give final feedback in this forum discussion.

This was the last PM that he sent:

As you requested i have removed all Media servers from the Host properties of client. Kept only four needed media servers...

And atlast Backup started now...! :)

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

Robert R A's picture

Yes sure!!

Backups are still in progress!!
 

I will update once its done completely!!

Rob :)

Robert R A's picture

Backups went on successfully for this issue.. So that is resolved..

Thanks all for your support!!