Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.
Status Code: 25 Message: cannot connect on socket Explanation: 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 NT, 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. Recommended Action: 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 a Windows NT 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 are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred. o 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 daemon (or service) is running. Then, create an activity log directory for bpdbm, retry the operation, and check the resulting activity log. o If you can view the report and have not found an entry related to this problem, create activity 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 activity logs. 2. Verify that the server list specifies the correct master server. o On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). o On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file. o On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file. 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 NT). 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. On Windows NT, verify that the %SystemRoot%\system32\drivers\etc\services 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 Configuration dialog box match the settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). 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" on page 31. 4. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 5. On Windows NT, verify that the recommended service packs are installed.
|Doing a DR (Disaster Recovery) Test on Red Hat Linux Servers.||2||44|
|help pulling data string using Awk||9||44|
|need to remove or skip grub protection password in ubuntu on boot time||2||31|
|Boot external USB drive using MDT Media||20||36|
Join the community of 500,000 technology professionals and ask your questions.
Connect with top rated Experts
15 Experts available now in Live!