Netbackup Message 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 Profile Corporate Leadership error code 24 in netbackup Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English
Netbackup Error Opening The Snapshot Disks Status 23
Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 23: Schedule initiated Client bpcd on client exited with status 23 socket read failed 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? Don't have a Veritas Account? Create netbackup error code 25 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 Status Code 23 (socket read failed). Error Message
Clear Host Cache Netbackup
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. %
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 bpclntcmd -pn Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us bpclntcmd pn 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 https://www.veritas.com/support/en_US/article.TECH54563 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 failed". Error https://www.veritas.com/support/en_US/article.000089930 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.3. In this instance,
Read Failed” Juan Maldonado September 21, 2010 No Comments Facebook Twitter LinkedIn I am sure you have run into a status code 23 “Socket http://blogs.dlt.com/status-code-23-socket-read-failed/ 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 socket read 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 socket read failed 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 valu