Error Bpbrm Bpcd On Exited With 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
Netbackup Error 23 Socket Read Failed
Developers Blogs Groups Vision 2016 Sign In netbackup error code 24 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your netbackup error opening the snapshot disks status 23 search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : socket
Netbackup Error Code 25
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) mantu2a Level 3 ‎01-13-2013 06:50 PM Options
Netbackup Socket Write Failed
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 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 *.*
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 bpclntcmd 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 backups or restores, or when loading client properties. Article:000090314 Publish: Article URL:http://www.veritas.com/docs/000090314 Support https://vox.veritas.com/t5/NetBackup/socket-read-failed-23/td-p/525966 / 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 General https://www.veritas.com/support/en_US/article.TECH57100 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 https://randrianiriana.wordpress.com/2011/08/31/netbackup-status-code-23-socket-read-failed/ en question marche très bien, les ports ouverts vers le serveur master sont : tcp/1521 pour le backup Oracle tcp/1556 pour le java http://www.tremka.com/archive/index.php/t-49664.html 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 - netbackup error Error bpbrm(pid=8060) bpcd on winsrv-ifrX exited with status 23: socket read failed 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 netbackup error code il faut forcer la résolution du nom ( vraiment bizarre ), donc il faut éditer votre fichiers hosts 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
Lösung 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 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 Weiterlesen... (http://www.symantec.com/connect/de/forums/socket-read-failed-23)