Netbackup Error 25 Cannot Connect On Socket Linux
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 netbackup cannot connect on socket linux Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal
Netbackup Cannot Connect On Socket 25 Windows
Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet netbackup error 58 can't connect to client STATUS CODE 25: Troubleshooting procedures for client Status 25 errors. Article:000009351 Publish: Article URL:http://www.veritas.com/docs/000009351 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? bptestbpcd cannot connect on socket 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 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
Bppllist Cannot Connect On Socket 25
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 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 net
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 bptestbpcd main: function connecttobpcd failed: 25 In CommunityCategoryBoardResourcesUsers bptestnetconn turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you
Bpcd Port Number
type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect on soc... VOX : https://www.veritas.com/support/en_US/article.TECH141839 Backup and Recovery : NetBackup : 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 MaykelF0209 Level 3 01-30-2013 01:51 PM Options Mark https://vox.veritas.com/t5/NetBackup/bptestbpcd-EXIT-status-25-cannot-connect-on-socket/td-p/569792 as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I'm currently runnning NB 7.5.0.4. I'm getting the "bptestbpcd: EXIT status = 25 cannot connect on socket" error when running the commands as specified by Symantec. I'm able to resolve from the master/media server (which is the same) see below C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn hcndc02 host hcndc02: hcndc02 at 192.168.100.226 aliases: hcndc02 192.168.100.226 However I get the following when running the command and checking the logs 16:35:39.583 [3948.3296] <2> bpcd main: accept sock = 380 16:35:39.598 [3660.3528] <2> setup_debug_log: switched debug log file for bpcd 16:35:39.598 [3660.3528] <2> bpcd main: VERBOSE = 0 16:35:39.598 [3660.3528] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpcd.exe -standalone 16:35:39.598 [3660.3528] <2> process_requests: offset to GMT 18000 16:35:39.614 [3660.3528] <2> logconnections: BPCD ACCEPT FROM 192.168.100.226.61837 TO 192.168.100.226.13782 fd = 380 16:35:39.614 [3660.3528] <2> process_requests: setup_sockopts complete 16:35:39.614 [3660.3528] <2> bpcd peer_hostname: Connection from host HCNDC02.hcnetwork.org (192.168.100.226) port 61837 16:35:39.614 [3660.3528] <2> bpcd valid_server: comparing hcntape01 and HCNDC02.hcnetwork.org 16:35:39.614 [3660.3528] <
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 http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/status-25-cannot-connect-on-socket-62611/ mean VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect on soc... VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot cannot connect 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 cannot connect on 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.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]
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » Symantec NetBackup » Status 25 - Cannot Connect On Socket The time now is Thu Oct 20, 2016 6:18 pm View previous topic | View next topic Page 1 of 1 Status 25 - Cannot Connect On Socket Author Message Randy Samora Guest Status 25 - Cannot Connect On Socket I have gone through the steps outlined in the In-depth Troubleshooting Guide for Exit Status Code 25 in Veritas NetBackup (tm) Server / NetBackup Enterprise Server 6.0 but I have one client that continues to fail with a status 25. The client was backing up fine until last Friday. I was told that the server crashed as if someone had unplugged it but it came back up after a reboot. Ever since that time, the backups have failed. All other types of communication are fine except for the actual attempt to backup data. 1. I can bpclntcmd -pn, -hn, -self, -ip and I get proper responses to and from the Master, Media Server and Client. 2. I can nslookup, nbtstat and ping in both directions. 3. I can telnet to bpcd on the client successfully. 4. I uninstalled and reinstalled the client. I even typed in a fake server name along with the other Media Server names and the installation recognized that the server name was bad. 5.