Netbackup Error 25 Cannot Connect On Socket
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 Careers
Netbackup Cannot Connect On Socket Linux
Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español netbackup cannot connect on socket 25 windows USA Site: Veritas Veritas PartnerNet Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on socket. bppllist -l cannot connect on socket (25) Article:000008360 Publish: Article URL:http://www.veritas.com/docs/000008360 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
Netbackup Error 58 Can't Connect To Client
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 Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on socket. For example, if an attempt is made to connect to the client from the Host Properties tree in the NetBackup Administration Console. Error Message Exit
Bptestbpcd Cannot Connect On Socket
Status 25 - cannot connect on socket. Cause Examine the bpcd log from the client for evidence of the following 10:44:50.087 [9501] <2> bpcd main: setup_sockopts complete10:44:50.091 [9501] <8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)10:44:50.091 [9501] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 110:44:50.091 [9501] <16> bpcd main: Couldn't get peer hostname Solution This condition is indicative of a problem with host name resolution via either DNS or the hosts file. Verify that the client's hostname resolves correctly to its IP address and that the reverse is true. That is, that the IP address reverse lookup corresponds to the client's hostname. Perform this verification on both the client and the master server. 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 informaSERVICES 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 bptestbpcd main: function connecttobpcd failed: 25 Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español
Error Code 25 In Netbackup
USA Site: Veritas Veritas PartnerNet STATUS CODE 25: Backup jobs fail with Status 25 "cannot connect on socket". Article:000030592 Publish: bpcd port number Article URL:http://www.veritas.com/docs/000030592 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 https://www.veritas.com/support/en_US/article.000008360 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 25: Backup jobs fail with Status 25 "cannot connect on socket". Error Message error connecting to oprdcannot connect to VMD(70)network protocol error(39)cannot connect on socket Solution Overview:Backup jobs fail with Status 25 "cannot connect on socket". Connection errors are https://www.veritas.com/support/en_US/article.TECH45382 also seen when clicking items in the Administration Console.When clicking "Devices" in the console, the following error may be seen:Error connecting to oprd on
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/bptestbpcd-EXIT-status-25-cannot-connect-on-socket/td-p/761977 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect on soc... VOX : Backup and Recovery : NetBackup : cannot connect bptestbpcd: EXIT status = 25 cannot connect on soc... 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 bptestbpcd: EXIT status = 25 cannot connect on socket alisdad Level 2 10-16-2015 03:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight cannot connect on Print Email to a Friend Report Inappropriate Content Hi I'm getting EXIT status = 25 cannot connect on socket error when I use the following command from the master server (Linux) to the client (Linux) /opt/openv/netbackup/bin/admincmd/bptestbpcd -verbose -debug -client s56upapp620-bak DNS resolves both ways on both boxes, I can ping both ways with host name and ip, traceroute works from either box. The client is listening for forvnetd and bpcd ok tcp 0 0 *:vnetd *:* LISTEN unix 2 [ ACC ] STREAM LISTENING 128287610 /usr/openv/var/vnetd/terminate_vnetd.uds unix 2 [ ACC ] STREAM LISTENING 128287644 /usr/openv/var/vnetd/terminate_bpcd.uds unix 2 [ ACC ] STREAM LISTENING 128287661 /usr/openv/var/vnetd/bpcd.uds unix 3 [ ] STREAM CONNECTED 128287623 /tmp/PBXPIPEvnetd tcp 0 0 *:bpcd *:* LISTEN unix 2 [ ACC ] STREAM LISTENING 128287644 /usr/openv/var/vnetd/terminate_bpcd.uds unix 2 [ ACC ] STREAM LISTENING 128287661 /usr/openv/var/vnetd/bpcd.uds unix 3 [ ] STREAM CONNECTED 128287677 /tmp/PBXPIPEbpcd there is no firewall between these 2 boxes nor do either of them have a local firewall running. The output from the bptestbpcd command from the master server is as follows: root@upnma02b# /opt/openv/netbackup/bin/admincmd/bptestbpcd -verbose -debug -client s56upapp620-bak 10:49:29