Netbackup Socket Read Error
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 Profile Corporate Leadership Newsroom Research Exchange Investor Relations error code 24 in netbackup Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português bpcd on client exited with status 23 socket read failed Español USA Site: Veritas Veritas PartnerNet General Error: Status code 23, socket read failed, during client backups or restores,
Netbackup Error Opening The Snapshot Disks Status 23
or when loading client properties. Article:000090314 Publish: Article URL:http://www.veritas.com/docs/000090314 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile
Netbackup Error Code 25
Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem General Error: Status code 23, socket read failed, during client backups or restores, or when loading client properties. Error Message Status code 23, socket read failed Cause The keyfile.dat file in the
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
Clear Host Cache Netbackup
Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us bpclntcmd English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet NetBackup status bpclntcmd pn 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? https://www.veritas.com/support/en_US/article.TECH57100 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 How to troubleshoot backups that fail with status 23 "socket read https://www.veritas.com/support/en_US/article.000089930 failed". Error Message socket read failed Solution Overview:This document discusses how to troubleshoot backups that fail with status 23 "socket read 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
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In https://vox.veritas.com/t5/NetBackup/socket-read-failed-23/td-p/525966 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results http://blogs.dlt.com/status-code-23-socket-read-failed/ by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : 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 socket read Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution socket read failed (23) mantu2a Level 3 01-13-2013 06:50 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, We are facing issue with a media server. Many jobs running on various client servers for that media server are failing with error : 01/13/2013 netbackup socket read 19:51:27 - Error bpbrm (pid=5551) bpcd on client exited with status 23: socket read failed 01/13/2013 19:51:28 - Error bpbrm (pid=5551) cannot send mail because BPCD on client exited with status 23: socket read failed 01/13/2013 19:51:29 - end writing socket read failed (23) We checked and found : bptestbpcd -client client name Command is working when we try it from master for media server but not for client Again , when we try vmoprcmd, vmoprcmd -d -h (media server) The Media Manager device daemon (ltid) is not active on host (media server). Again,for media server : netstat -a |grep bp *.bpcd *.* 0 0 49152 0 LISTEN *.bpjava-msvc *.* 0 0 49152 0 LISTEN 30054418cd8 stream-ord 300211cf480 00000000 /usr/openv/var/vnetd/bpcompatd.uds When we try bpclntcmd from media server for client, we get : bpclntcmd -hn client host cleint: client at 199.37.184.185 (0xc725b8b9) aliases: From master for media: master: bpclntcmd -hn media host media: media at 135.153.168.80 aliases: media 135.153.168.80 From media for master : bpclntcmd -hn master host master: master at 135.53.28.54 (0x87351c36) host master: master at 135.53.28.53 (0x87351c35) aliases: Please advice, Regards Samrat Chowdhury Solved! Go to Solution. Labels: 7.1.x and Earlier Ba
Read Failed” Juan Maldonado September 21, 2010 No Comments Facebook Twitter LinkedIn I am sure you have run into a status code 23 “Socket Read Failed”. This stinks because the code can lead you to troubleshooting a multiple of things in your environment. Let’s see the recommended action by Symantec would you check the NetBackup problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problem report, then you are to create a debug log directory for the process that could have returned this status code (YAY for Legacy Logging!!) Then, retry the operation and check the resulting debug log. Also corrupt binaries are one possible cause for this error. So make sure you load a fresh “bptm” from the install media to try to resolve the problem. On Sun Solaris systems you must first verify that all operating systems patches are installed. See the Operating Notes sections of the NetBackup Release Notes. For Windows you need to verify that the recommended service packs are installed. Also this error can occur during a restore to a Novell client. The following may be a possible action to take: • By default, the value for Novell “Maximum Concurrent Disk Cache Writes” may be too low (for example, 50); Novell recommends setting it to 100. A value of 100 increases the speed and efficiency of the disk cache writes. It increases the number of write requests to be run at one time • Change to or add the following settings in the Novell sys:system\autoexec.ncf file:SET Maximum Packet Receive Buffers = 4000SET Maximum Directory Cache Buffers = 4000 SET Maximum Concurrent Disk Cache Writes = 2000SET Maximum Concurrent Directory Cache Writes = 2000SET Maximum Physical Receive Packet Size = 1514 On Windows master servers, check the LIST_FILES_TIMEOUT value and ensure that this value is at least 1800. NetBackup Share This: Facebook Twitter LinkedIn Previous AutoCAD for Mac Next Open Source in the DoD Juan Maldonado Related Posts Smart Records Retention for Government Social Media Content July 20, 2016 6 Steps to Giving Data Backup the Respect It Deserves June 28, 2016 All-Flash Storage Goes Mainstream, but Only Some Offer Enterprise-Grade Parity June 17, 2016 Don’t Miss: Feds Discuss Forward Thinking Approach to Data Backup and Recovery June 16, 2016 Follow DLT Facebook Twitter Linkedin Youtube About Technically Speaking Technically Speaking is a blog dedicated to providing the latest public sector IT industry news. Written by leading industry professionals, this blog is designed to stimulate discussion, drive thought, and suggest best