Netbackup Error 54 Unix Client
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 Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status Code 54: Timed out connecting to client. Article:000032603 Publish: Article URL:http://www.veritas.com/docs/000032603 Support / Article Sign In Remember me Forgot Password? 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 Article Languages Subscribe to this Article Manage your Subscriptions Problem Status Code 54: Timed out connecting to client. Error Message Status code 54: Timed out connecting to client. Solution Overview:Status Code 54: Timed out connecting to client.Troubleshooting:After bpcd is started by the inbound connection from the bpbrm, it needs to complete a second socket connection to bpbrm before starting bpbkar, tar, or other client processes. Prior to attempting to complete the second connection, bpcd has to obtain a source port from the operating system from which to originate the connection. If ports are not available, the bpcd log will show a message similar to this. 15:20:30 [19683] <2> bpcd main: offset to GMT 25200 15:20:30 [19683] <2> bpcd main: setup_sockopts complete 15:20:30 [19683] <2> bpcd main: output socket port number = 1020 15:20:30 [19683] <2> bpcd peer_hostname: Connection from host nitro (192.168.101.212) port 1022 15:20:30 [19683] <2> bpcd main: Peer hostname is nitro 15:20:30 [19683] <16> bpcd main: Couldn't reserve output port. Errno = 11: Resource temporarily unavailable Reservation, bind, or resource busy/unavailable log entr
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 Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet In-depth Troubleshooting Guide for Exit Status Code 54 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 5.0 / 5.1 Download Attachments Article:000029205 Publish: Article URL:http://www.veritas.com/docs/000029205 Support / Article Sign In Remember https://www.veritas.com/support/en_US/article.000032603 me Forgot Password? 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 Download Attachments Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem In-depth Troubleshooting Guide for Exit Status https://www.veritas.com/support/en_US/article.TECH38514 Code 54 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 5.0 / 5.1 Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful? Email Address (Optional) Your feedback has been submitted successfully! Thank You! Sorry, we couldn't post your feedback right now, please try again later. Create/Manage Case QUESTIONS? CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud HealthcFAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/error-54-client-connect-timeout-49785/ AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • https://support.symantec.com/en_US/article.TECH20449.html Log in Backup Central Forums Forum Index » Symantec NetBackup » Error 54 - client connect timeout The time now is Thu Oct 20, 2016 6:30 pm View previous topic | View next topic Page 1 of 1 netbackup error Error 54 - client connect timeout Author Message Mark.Donaldson Guest Error 54 - client connect timeout I'm being plagued by these on my RMAN backups: ERROR: 54 timed out connecting to client The server could not complete the connection to the client. The accept system or winsock netbackup error 54 call timed out after 60 seconds. I've got an open ticket with Veritas but have any of you defeated this dragon? -M ================================================= (2B|^2B) == ? ================================================= Mark Donaldson - SA - Corporate Express ================================================= Fri Aug 06, 2004 7:32 am Mark.Donaldson Guest Error 54 - client connect timeout Here's some more detail - the brpd logs for this error on my master server. The TCP timewait interval on the client is set to 10000, by the way. Master server is 120000. -M 22:46:07.256 [29912] <2> logconnections: BPRD ACCEPT FROM 10.128.16.175.45349 TO 10.128.24.183.13720 22:46:07.257 [29912] <2> connected_peer: Connection from host ub-23.cexp.com, 10.128.16.175, on non-reserved port 45349 22:46:07.260 [29912] <2> db_valid_master_server: ub-23.cexp.com is not a valid server 22:46:07.260 [29912] <2> db_valid_master_server: ub-23.cexp.com is a valid media server 22:46:07.265 [29912] <2> process_request: command C_USER_BPBACKUP_3_0 (53) received 22:46:07.268 [29912] <2> logconnections: BPDBM CO
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' STATUS CODE 54: Oracle restores may fail with a NetBackup Status Code 54 (timed out connecting to client) if RMAN simultaneously requests un-multiplexed restores to different RMAN channels of a backup set that are on the same media. TECH20449 October 24th, 2013 http://www.symantec.com/docs/TECH20449 Support / STATUS CODE 54: Oracle restores may fail with a NetBackup Status Code 54 (timed out connecting to client) if RMAN simultaneously requests un-multiplexed restores to different RMAN channels of a backup set that are on the same media. Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation STATUS CODE 54: Oracle restores may fail with a NetBackup Status Code 54 (timed out connecting to client) if RMAN simult