Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
cannot connect on socket
- Thread starter Gaskin69
- Start date
- Thread starter
- #3
To provide good help, you need to offer a bit more in terms of configuration, media, versions, environment etc. The generic error troubleshooting is as per the help files - Further than that, you need to explain/elaborate etc further ...
cannot connect on socket
A process timed out while connecting to another process for a particular operation. This problem can occur when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. (On Windows, these daemons are the NetBackup Request Manager and NetBackup Database Manager services.) It can also occur if the network or server is heavily loaded and has slow response time, or if an evaluation license key for NetBackup BusinesServer or DataCenter has expired.
Try the following:
1. On a UNIX NetBackup master server, verify that the bprd and bpdbm processes are running. If these processes are not running, start them. On aWindows master server, verify that the NetBackup Request Manager and NetBackup Database Manager services are running. If these services are not running, start them.
If the above processes or services are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred.
* If you cannot view the report, or you get a cannot connect on socket error when trying to view it, verify again that the NetBackup Database Manager service or daemon is running. Then, create a debug log directory for bpdbm, retry the operation, and check the resulting debug log.
* If you can view the report and have not found an entry related to this problem, create debug log directories for the related processes that were running when the error first appeared (this process will frequently be bpbrm). Then, retry the operation and check the resulting debug logs.
2. Verify that the server list specifies the correct master server.
* On Windows systems, the master server is designated as CURRENT on the Servers tab in the Specify NetBackup Machines dialog. To display this dialog box, start the Backup, Archive, and Restore interface and click Specify NetBackup Machines on the Actions menu.
* On UNIX, andMacintosh systems, the master server is the first SERVER entry in the bp.conf file.
* On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file.
* Make sure all recommended NetBackup patches have been installed. Check the VERITAS support web site for current patch information. (Go to then select "NetBackup" followed by "files and updates".)
* If failure occurs when executing a user-directed backup from a client, make sure a user-directed backup schedule exists at the master server.
* When working with NetBackup database extensions, make sure that the applicable database product has the correct permissions allowing NetBackup to write to the progress log on the client.
* On UNIX systems, if bpdbm is dying when the shutdown script is executed on a media server, carefully read the K77netbackup script (in /usr/openv/netbackup/bin/goodies) for details on how to prevent this problem.
If you change the server list on a master server, stop and restart the NetBackup database manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows).
3. Check the services file.
On UNIX, verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and bprd.
Run the NetBackup Configuration Validation Utility (NCVU) and note the services port checks in section one. Note the NetBackup daemon running and listening check and the bpps check in section three.
On Windows, verify that the %SystemRoot%system32driversetcservices file has the correct entries for bpcd, bpdbm, and bprd.
Also, verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog match the settings in the services file. To display this dialog, start the Backup, Archive, and Restore interface and click NetBackup Client Properties on the File menu. The values on the Network tab are written to the services file when the NetBackup Client service starts.
Also, see "Verifying Host Names and Services Entries" in the Troubleshooting Guide.
4. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes).
5. On Windows, verify that the recommended service packs are installed.
6. When the base NetBackup BusinesServer or DataCenter license key expires, daemons (such as bprd and bpdbm) will terminate on the NetBackup server. If these daemons are not running, you are likely to encounter status code 25 errors in the Administration GUIs. Install a valid base NetBackup license key, restart the daemons, and restart the GUI.
7. For NetBackup ServerFree Agent:
When many devices are configured on a media server, it may take a long time for the bptpcinfo command to generate the 3pc.conf file. When the backup is run for the first time, the backup may fail with status 25. Make sure that the /usr/openv/volmgr/database/3pc.conf file exists. If it does, rerun the backup. If the backup fails again, run the bptpcinfo manually to generate the 3pc.conf file, then try the backup again.
cannot connect on socket
A process timed out while connecting to another process for a particular operation. This problem can occur when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. (On Windows, these daemons are the NetBackup Request Manager and NetBackup Database Manager services.) It can also occur if the network or server is heavily loaded and has slow response time, or if an evaluation license key for NetBackup BusinesServer or DataCenter has expired.
Try the following:
1. On a UNIX NetBackup master server, verify that the bprd and bpdbm processes are running. If these processes are not running, start them. On aWindows master server, verify that the NetBackup Request Manager and NetBackup Database Manager services are running. If these services are not running, start them.
If the above processes or services are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred.
* If you cannot view the report, or you get a cannot connect on socket error when trying to view it, verify again that the NetBackup Database Manager service or daemon is running. Then, create a debug log directory for bpdbm, retry the operation, and check the resulting debug log.
* If you can view the report and have not found an entry related to this problem, create debug log directories for the related processes that were running when the error first appeared (this process will frequently be bpbrm). Then, retry the operation and check the resulting debug logs.
2. Verify that the server list specifies the correct master server.
* On Windows systems, the master server is designated as CURRENT on the Servers tab in the Specify NetBackup Machines dialog. To display this dialog box, start the Backup, Archive, and Restore interface and click Specify NetBackup Machines on the Actions menu.
* On UNIX, andMacintosh systems, the master server is the first SERVER entry in the bp.conf file.
* On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file.
* Make sure all recommended NetBackup patches have been installed. Check the VERITAS support web site for current patch information. (Go to then select "NetBackup" followed by "files and updates".)
* If failure occurs when executing a user-directed backup from a client, make sure a user-directed backup schedule exists at the master server.
* When working with NetBackup database extensions, make sure that the applicable database product has the correct permissions allowing NetBackup to write to the progress log on the client.
* On UNIX systems, if bpdbm is dying when the shutdown script is executed on a media server, carefully read the K77netbackup script (in /usr/openv/netbackup/bin/goodies) for details on how to prevent this problem.
If you change the server list on a master server, stop and restart the NetBackup database manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows).
3. Check the services file.
On UNIX, verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and bprd.
Run the NetBackup Configuration Validation Utility (NCVU) and note the services port checks in section one. Note the NetBackup daemon running and listening check and the bpps check in section three.
On Windows, verify that the %SystemRoot%system32driversetcservices file has the correct entries for bpcd, bpdbm, and bprd.
Also, verify that the NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog match the settings in the services file. To display this dialog, start the Backup, Archive, and Restore interface and click NetBackup Client Properties on the File menu. The values on the Network tab are written to the services file when the NetBackup Client service starts.
Also, see "Verifying Host Names and Services Entries" in the Troubleshooting Guide.
4. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes).
5. On Windows, verify that the recommended service packs are installed.
6. When the base NetBackup BusinesServer or DataCenter license key expires, daemons (such as bprd and bpdbm) will terminate on the NetBackup server. If these daemons are not running, you are likely to encounter status code 25 errors in the Administration GUIs. Install a valid base NetBackup license key, restart the daemons, and restart the GUI.
7. For NetBackup ServerFree Agent:
When many devices are configured on a media server, it may take a long time for the bptpcinfo command to generate the 3pc.conf file. When the backup is run for the first time, the backup may fail with status 25. Make sure that the /usr/openv/volmgr/database/3pc.conf file exists. If it does, rerun the backup. If the backup fails again, run the bptpcinfo manually to generate the 3pc.conf file, then try the backup again.
- Thread starter
- #6
Master server (Netbackup 4.5 Datacenter) is Win 2k not Unix and it is on a SSO environment, it acts as a media server also.
I have 14 media servers connected to the libraries also. When I try and restore on a particular server it fails with the cannot connect on socket error. These servers are all NT4 or 2000. They backup with no errors.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question