Netbackup Error Code 58 In Solaris
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 netbackup cannot connect on socket Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 netbackup error code 59 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 netbackup error code 58 in windows client errors. Article:000037729 Publish: Article URL:http://www.veritas.com/docs/000037729 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
Bptestbpcd: Exit Status = 25
in to Subscribe Please sign 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 58: Can't connect to client. Troubleshooting procedures for Status 58 errors. Error Message Status Code: 58 Solution Overview: A status 58 error can occur during connections to legacy processes; bpcd, bprd, bpdbm, netbackup port numbers bpjobd, vmd, etc. typically from master or media server to client, but alsofrom master server to media server, orfrom media servers to master, orfrom client to master servers, orin very rare cases from client to media server. The cause is that either a TCP SYN request did not reach the destination host, orthe expected processes were not listening on the destination host, orthe TCP SYN+ACK returned by the destination host did not reach the source host, orthe destination host could not validate that the inbound connection was from a valid NetBackup (NB) host, orthat PBX or vnetd on the destination host could not transfer the connection the desired daemon, orin rare instances that the destination host could not create a connection to the source host - for the same reasons as noted above. The majority of these situations are due to the TCP port(s) not being open through the firewall, daemon processes not running and listening on the destination host, the destination host being unable to resolve the IP address of the source host to a hostname, or the destination host not being configured to recognize the resolved hostname as a valid NB host. Checking Connectivity from the Master Server to the Client When troubleshooting status 58 errors
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 status: failed, (42) connect_refused Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas
Connect Failed Status (18) Connect_failed
Veritas PartnerNet STATUS CODE 25: Troubleshooting procedures for client Status 25 errors. Article:000009351 Publish: Article URL:http://www.veritas.com/docs/000009351 Support / Article Sign
Netbackup Status Code 13
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 https://www.veritas.com/support/en_US/article.TECH68832 Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The master server is getting a status code 25 (cannot connect on socket) error when attempting to bring up the client host properties using the GUI or remote admin console. Cause A status 25 error results from either a TCP SYN request sent to a client from the NetBackup server that was https://www.veritas.com/support/en_US/article.TECH141839 not acknowledged or the server was not resolvable so a TCP SYN request was not sent. The majority of the causes of this issue are due to the client not listening on the bpcd or vnetd ports, the master server failing to resolve the client by hostname, or the client can not resolve the NetBackup server by its IP address. For NetBackup clients running 6.x release, although the vnetd daemon is used for incoming connections, it is still required that bpcd perform the hostname compare to authenticate the NetBackup server. Solution Troubleshooting: Step 1: When troubleshooting status 25 errors on a NetBackup client, verify that the client was working prior to the issue. If it had been working try to determine what changes may have been made to the client server's OS or the network links. Step 2: In 6.x and above environments you can use the command- bptestbpcd to verify you can connect to both the vnetd and bpcd ports on the client server. e.g. bptestbpcd -verbose -debug -client
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM http://unix.ittoolbox.com/groups/technical-functional/solaris-l/netbackup-error-58-cant-connect-to-client-5560887 Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX VoIP_News Inside-ERP I_am_the_dragon Inside-CRM maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Craig Borysowich Dennis Stevenson mircea_luca Richard DukeGanote iudithm Clinton Jones bracke Nikki Klein AbhaiTripathi Iqbalyk jakarman netbackup error Adrian_Grigoriu knowscognosdoi COMPANIES GeoTrust Juniper Networks Silver Peak Sophos View All Topics View All Members View All Companies Toolbox for IT Topics UNIX Groups Ask a New Question Solaris The Solaris group is a forum where peers share technical expertise, solve problems, and discuss issues related to the Solaris operating system, including OS-related malfunctions, security issues, and network performance. Home | Invite netbackup error code Peers | More UNIX Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Netbackup - Error '(58) Can't Connect to Client" olakunleoj asked Aug 7, 2014 | Replies (3) I was using netbackup for my backup, the netbackup was on Solaris 10 and I have several Windows 8 server as a client recently one of my client severs displays error "(58) can't connect to client " 08/06/2014 09:02:23 - Info nbjm (pid=7874) starting backup job (jobid=25267) for client UNION-211, policy iRegisters, schedule Full 08/06/2014 09:02:23 - Info nbjm (pid=7874) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=25267, request id:{FF3DB246-1D3F-11E4-96C0-00
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 04:54:09 GMT by s_wx1011 (squid/3.5.20)