Error Cannot Connect To Socket Netbackup
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 25 Windows
Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español netbackup cannot connect on socket linux USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Cannot connect to socket (25) and Backup fails with Status code 58: Can't
Bptestbpcd Cannot Connect On Socket
connect to client. Article:000007335 Publish: Article URL:http://www.veritas.com/docs/000007335 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 bppllist cannot connect on socket 25 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 Error : "Cannot connect to socket (25)"Backup fails with Status code 58: Can't connect to client. Cause The problem turned out to be the Windows Firewall Service in Windows 2008 Server. Solution DETAILS:
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
Bptestbpcd Main: Function Connecttobpcd Failed: 25
Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch netbackup cannot connect on socket 25 solaris Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Unable to connect to a NetBackup client. Exit
Netbackup Error 58 Can't Connect To Client
Status 25 - cannot connect on socket. 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 https://www.veritas.com/support/en_US/article.000007335 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 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 https://www.veritas.com/support/en_US/article.000008360 the Host Properties tree in the NetBackup Administration Console. Error Message Exit 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 noGovernance 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 https://www.experts-exchange.com/questions/25863586/netbackup-cannot-connect-on-socket-error.html mean VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect on soc... VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect 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 Print Email to a Friend Report Inappropriate Content Hi I'm cannot connect on 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.828 [4106] <2> bptestbpcd: VERBOSE = 0 10:49:29.830 [4106] <2> copy_preferred_network_list: ../../libvlibs/nbconf.c.1796: pseudo PN for : chiapp510 10:49:29.830 [4106] <2> copy_preferred_network
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > netbackup cannot connect on socket error Want to Advertise Here? Solved netbackup cannot connect on socket error Posted on 2010-04-13 Storage Software Storage 2 Verified Solutions 4 Comments 4,406 Views Last Modified: 2013-12-01 I am getting this error when I got clients and "connect' or "properties" I get "cannot connect on socket " I can connect to the server that has the netbackup server running on it , I am guessing the first thing would be to restart the sevices on the client or reboot , and then check to see if the ports are open for comuunitcation , anything else ? 0 Question by:NAMEWITHELD12 Facebook Twitter LinkedIn Google LVL 4 Best Solution byjeb If you have upgraded the clients you cant connect to, to a version higher than you backup server this will cause that to happen and will having the wrong master server name on the clients. if you have Go to Solution 4 Comments LVL 4 Overall: Level 4 Storage Software 2 Storage 1 Message Accepted Solution by:jeb2010-04-13 If you have upgraded the clients you cant connect to, to a version higher than you backup server this will cause that to happen and will having the wrong master server name on the clients. if you have reinstalled or moved the master server to a new box with a different name they wont connect. 0 LVL 1 Overall: Level 1 Message Active today Author Comment by:NAMEWITHELD122010-04-13 thanks , I will check this out when i get to work , I have no access from here , thanks again for the reply 0 LVL 31 Overall: Level 31 Storage Software 21 Storage 9 Message Active 1 day ago Assisted Solution by:Rodney Barnhardt2010-04-14 I have seen th