Error Bpbrm Bpcd Exited Status 23
Contents |
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 CommunityCategoryBoardResourcesUsers turn
Socket Read Failed 23 Netbackup Windows
on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible netbackup error code 24 matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : netbackup error opening the snapshot disks status 23 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
Netbackup Error Code 25
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 19:51:27 - Error bpbrm (pid=5551) bpcd on client
Netbackup Socket Write Failed
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 Backup and Recovery NetBackup 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! 08:57:27.974 [
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community bpclntcmd 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 General Error: Status code 23, socket read failed, during client https://vox.veritas.com/t5/NetBackup/socket-read-failed-23/td-p/525966 backups or restores, 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 Logout Sign in to Subscribe Please sign in to set up your https://www.veritas.com/support/en_US/article.TECH57100 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
de domaine. La liaison entre le master server et le serveur en question marche très bien, les https://randrianiriana.wordpress.com/2011/08/31/netbackup-status-code-23-socket-read-failed/ ports ouverts vers le serveur master sont : tcp/1521 pour https://support.symantec.com/en_US/article.TECH205899.html le backup Oracle tcp/1556 pour le java admin client tcp/udp 13720,13722,13724,13782,13783 La résolution de nom sur les 2 serveurs marche aussi !! L’erreur que j’ai : 8/31/2011 9:47:41 AM - Error bpbrm(pid=8060) bpcd on winsrv-ifrX exited with status 23: socket read failed netbackup error 8/31/2011 9:47:46 AM - Error bpbrm(pid=8060) cannot send mail because BPCD on winsrv-ifrX exited with status 23: socket read failed 8/31/2011 9:47:49 AM - end writing socket read failed(23) D’après la doc de symantec il faut forcer la résolution du nom ( vraiment bizarre ), donc il faut éditer votre fichiers hosts netbackup error code comme ici : http://www.symantec.com/business/support/index?page=content&id=TECH54563 Évaluez ceci :Share this:TwitterLinkedInImprimerEmailPinterestFacebookGoogleJ'aime:J'aime chargement… Sur le même thème Cette entrée, publiée dans tips, est taguée netbackup. Bookmarquez ce permalien. Navigation des articles ← my nagios check_ftpplugin Play! framework +GAE → Laisser un commentaire Annuler la réponse. Entrez votre commentaire... Entrez vos coordonnées ci-dessous ou cliquez sur une icône pour vous connecter: Adresse de messagerie (obligatoire) (adresse strictement confidentielle) Nom (obligatoire) Site web Vous commentez à l'aide de votre compte WordPress.com. (Déconnexion/Changer) Vous commentez à l'aide de votre compte Twitter. (Déconnexion/Changer) Vous commentez à l'aide de votre compte Facebook. (Déconnexion/Changer) Vous commentez à l'aide de votre compte Google+. (Déconnexion/Changer) Annuler Connexion à %s Avertissez-moi par email des nouveaux commentaires. Avertissez-moi par email des nouveaux articles. Recherche Pages et Articles Phares squid + active directory + dansguardian + sarg Configurer sur un routeur Cisco avec Minicom Envoyer des sms sur debian gnu/linux vpnc-connect: hash comparison failed: (ISAKMP_N_AUTHENTICATION_FAILED)(24) check group password! Moov 3G+
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 SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' NDMP backups are failing with socket read failed(23) TECH205899 August 16th, 2015 http://www.symantec.com/docs/TECH205899 Support / NDMP backups are failing with socket read failed(23) 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 NDMP backups are failing with socket read failed(23) Error EXIT STATUS 23: socket read failed Cause Checked the bptm, bpbrm logs and below is the findings Detailed Status:- 03/05/2013 12:21:20 - Info ndmpagent(pid=2056) 470000 entries sent to bpdbm 03/05/2013 12:22:24 - Info ndmpagent(pid=2056) 475000 entries sent to bpdbm 03/05/2013 12:23:42 - Info ndmpag