Netbackup Error Socket Read Failed
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate exited with status 23 socket read failed Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us error code 24 in netbackup English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE netbackup error opening the snapshot disks status 23 23: Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed). Article:000089429 Publish: Article URL:http://www.veritas.com/docs/000089429 Support / Article Sign In Remember me Forgot Password?
Netbackup Error Code 25
Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 23: Schedule initiated Client backups fail with a NetBackup clear host cache netbackup Status Code 23 (socket read failed). Error Message socket read failed Solution Overview: Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed). Troubleshooting: Use the bpclntcmd command to test the connectivity between the master server and the client. Specifically, be sure to use the bpclntcmd -pn command. The following commands can be run to test both forward and reverse hostname lookups in Windows & Unix The following commands can be used to test the short name alias and the fully qualified long name of the system. %
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision bpclntcmd 2016 Developers Blogs Groups Vision 2016 Sign In
Bpclntcmd Pn
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : https://www.veritas.com/support/en_US/article.TECH54563 NetBackup : socket read failed 23 VOX : Backup and Recovery : NetBackup : socket read failed 23 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution socket read failed 23 ndt Level 4 https://vox.veritas.com/t5/NetBackup/socket-read-failed-23/td-p/516291 03-14-2013 08:19 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, Please help me to solve this problem with error code 23 ==== netbackup client version==== root@dr3 # cat /usr/openv/netbackup/bin/version NetBackup-Solaris10 6.5.5 ====server version===================== root@Nbmaster2 # cat /usr/openv/netbackup/bin/version NetBackup-Solaris10 6.5.5 root@Nbmaster2 # ====bptestbpcd============= root@Nbmaster2 # ./bptestbpcd -client dr3 -debug 10:07:18.625 [7375] <2> bptestbpcd: VERBOSE = 0 10:07:18.628 [7375] <2> ParseConfigExA: Option (VERBOSE) redefined on line 20, discarding definition on line 8. 10:07:18.706 [7375] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006 10:07:18.706 [7375] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpcd 10:07:18.774 [7375] <2> logconnections: BPCD CONNECT FROM 10.151.89.172.49549 TO 10.xxx.xx.220.13724 10:07:18.776 [7375] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.182: msg: VNETD CONNECT FROM 10.xxx.xx.172.49552 TO 10.xxx.xx.220.13724 fd = 5 10:07:18.853 [7375] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.535: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a 10:07:18.857 [7375] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.552: ipc_string: /tmp/vnet-05761363316838848138000000000-ahaiql 10:07:18.860 [7375] <2> get_short: (2) premature end of file (byte 1) 10:07:18.860 [7375] <2> bpcr_put_vnetd_forward_socket: get
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor https://www.veritas.com/support/en_US/article.000089930 Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet NetBackup status code: 23 - How to troubleshoot backups that fail with status 23 "socket read failed". Article:000089930 Publish: Article URL:http://www.veritas.com/docs/000089930 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your netbackup error Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem How to troubleshoot backups that fail with status 23 "socket read failed". Error Message socket read failed Solution Overview:This document discusses how to troubleshoot backups that fail with status 23 "socket read socket read failed failed". Backups may fail with a status 23 when the client is unable to resolve the connecting media server's ip address. Client Log Files:Examine the client's bpcd log for issues related to host name or address resolution:12:44:38.619 [4804.5184] <2> logconnections: BPCD ACCEPT FROM 10.1.2.3.47204 TO 10.1.2.37.1372412:44:38.619 [4804.5184] <2> bpcd main: setup_sockopts complete12:44:43.134 [4804.5184] <8> bpcd peer_hostname: gethostbyaddr failed : The requested name is valid, but no data of the requested type was found.(0)12:44:43.134 [4804.5184] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 012:44:43.134 [4804.5184] <16> bpcd main: Couldn't get peer hostnameTroubleshooting:In the above case, the initial connection from the media server (IP=10.1.2.3) is made to the client (IP=10.1.2.37). The first indication of a failure can be seen in the line containing the following message: <8> bpcd peer_hostname: gethostbyaddr failedThis indicates that the client in this case is unable to resolve the media server's IP address, 10.1.2.3. In this instance, it is likely that an nslookup of 10.1.2.3 will fail, as will running 'bpclntcmd -ip 10.1.2.3'Run the name resolution test using the 'bpclntcmd -hn [host name]' to ensure the hostname is resolving correctly.Resolution: Correct the hostname resolution issue