Status Code: 57

Client connection refused

The client refused a connection on the port number for bpcd. This can occur when the client has not been properly configured to accept connections from the master server. This can also occur due to name resolution issues or due to a misconfiguration of the client services.

Status Code 57: client connection refused

Page 1 of 7

Table of Contents
1 Detailed explanation............................................................................................................................... 3 2 Verify client software is installed and running ....................................................................................3 2.1 Windows clients.................................................................................................................................. 3 2.2 UNIX clients....................................................................................................................................... 3 2.3 Linux clients....................................................................................................................................... 4 2.4 Standalone clients.............................................................................................................................. 4 3 Windows Privileges and Rights............................................................................................................. 4 4 Name Resolution.................................................................................................................................... 5 4.1 Windows forward and reverse lookups............................................................................................... 5 4.2 UNIX forward and reverse lookups..................................................................................................... 5 5 Verify bpcd port configuration.............................................................................................................. 5 5.1 Windows services entries................................................................................................................... 5 5.2 UNIX services entries ........................................................................................................................ 6 5.2.1 UNIX and Linux systems.............................................................................................................. 6 5.2.2 Client using bpcd in standalone mode......................................................................................... 6 6 Verifying connectivity to bpcd............................................................................................................... 6 6.1 Telnet test from a Windows server..................................................................................................... 6 6.2 Telnet test from a UNIX server........................................................................................................... 6 7 Non-windows or UNIX considerations.................................................................................................. 7 7.1 NDMP policy type............................................................................................................................... 7 7.2 Catalog backup file list....................................................................................................................... 7 8 Enabling logging..................................................................................................................................... 7 9 Links........................................................................................................................................................ 7

Status Code 57: client connection refused

Page 2 of 7

1 Detailed explanation
A NetBackup process was unable to connect to the NetBackup Client Service process bpcd. The NetBackup Client Service (bpcd) listens vicariously through the local service manager (like inetd in UNIX or bpinetd in Windows) on port 13782 for other NetBackup processes to contact it. The bpcd process could also be run standalone without a service manager like xinetd running. This contact can be host-to-host communication or IPC communication within a single host. If the requesting process fails to successfully connect to bpcd through port 13782, a Status 57 is generated. This can occur because there is no bpcd process listening on port 13782 or there are more connections to the bpcd port then the network subsystem can handle with the listen() call. In Figure 1, you can see how the NetBackup processes connect through bpinetd during a normal backup:

Figure 1. Windows process flow

2 Verify client software is installed and running

2.1 Windows clients
Make sure that NetBackup Client Service is installed and running. From the Start menu select Settings > Control Panel > Administrative Tools > Services to launch the Services tool. Scroll through the Windows Services list and verify the NetBackup Client Service exists and has a Status of Started. If the client service is running, the Process tab within the Windows Task Manager will show bpinetd.exe is running.

2.2 UNIX clients

Check the process table to make sure that bpcd is running. From a shell window, run the command:
# netstat a | grep bpcd *.bpcd *.* 0 0 49152 0 LISTEN

Status Code 57: client connection refused

Page 3 of 7

If bpcd is not in LISTEN status then check the startup configuration. Check the /etc/inetd.conf file to ensure that inetd has been configured to find and start bpcd. Also verify the /etc/services file has the bpcd service defined. In /etc/inetd.conf, there should be an entry similar to this:
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

In /etc/services, look for a line like the following:

bpcd 13782/tcp bpcd

If these entries are missing, reinstall the client software. This should add the bpcd and other required services to the inetd.conf and services file.

2.3 Linux clients

Linux clients use the xinetd service to start bpcd and other client services. Each service will have a file in the /etc/xinetd.d directory. Check to see that the file /etc/xinetd.d/bpcd is present and correct. Here is an example of a typical /etc/xinetd.d/bpcd file:
{ disable socket_type protocol wait user server } = = = = = = no stream tcp no root /usr/openv/netbackup/bin/bpcd

If this file does not exist try reinstalling the client software. This should add the bpcd and other required services to the /etc/xinetd.d directory. Check the NetBackup OS Compatibility Guide to ensure the client is running a supported version.

2.4 Standalone clients

For clients that have been configured to manually start bpcd at startup, ensure the standalone flag is being passed. This would only apply to clients where inetd and xinetd have been disabled and bpcd is started from a startup script. Make sure that theres a system startup file for bpcd, and check the syntax of the command in that file. The startup line in the script should read something like:
/usr/openv/netbackup/bin/bpcd -standalone

The standalone flag is used to make bpcd run as a persistent daemon, rather than being started automatically by inetd or xinetd.

3 Windows Privileges and Rights

Make sure the NetBackup Client Service is using an account with appropriate Local administrator or root privileges. Some situations require the NetBackup Administrator to change the NetBackup Client Service to start using an account with Domain Administrator rights. This can lead to problems if the specified account is deleted or the password is changed and the NetBackup Client Service is not updated accordingly.

Status Code 57: client connection refused

Page 4 of 7

The default account for the NetBackup Client Service is LocalSystem. To verify what user is set go to the Start menu and select Settings > Control Panel > Administrative Tools > Services to launch the Services tool. Scroll through the Windows Services list and check what user is listed under Log On As for the NetBackup Client Service.

4 Name Resolution
NetBackup is fully dependent on accurate forward and reverse hostname resolution. Incorrect name resolution can lead to a Status Code 57 if the address resolved is that of a reachable machine that happens to not be running bpcd. Use the bpclntcmd command to test forward and reverse name resolution from the server side of the connection.

4.1 Windows forward and reverse lookups

The following commands can be run to test both forward and reverse hostname lookups in Windows. The following commands can be used to test the short name alias and the fully qualified long name of the system.
% <install path>\netbackup\bin\bpclntcmd hn <ShortName> % <install path>\netbackup\bin\bpclntcmd hn <LongName>

The following command can be used to test reverse IP lookup of the system.
% <install path>\netbackup\bin\bpclntcmd ip <IP Address returned by hn command>

These commands should be run from the master server and also the media server that is handling the backup. The results should display the correct hostname and IP address for the host.

4.2 UNIX forward and reverse lookups

The following commands can be run to test both forward and reverse hostname lookups in UNIX. The following commands can be used to test the short name alias and the fully qualified long name of the system.
# /usr/openv/netbackup/bin/bpclntcmd hn <name exactly as it is in the policy>

The following command can be used to test reverse IP lookup of the system.
# /usr/openv/netbackup/bin/bpclntcmd ip <IP Address returned by hn command>

These commands should be run from the master server and also the media server that is handling the backup. The results should display the correct hostname and IP address for the host.

5 Verify bpcd port configuration

It is possible to change the port bpcd and other processes listen on. By default bpcd listens on port 13782. Check to see if these default values have been changed. These settings can be verified by looking at the services file in UNIX or Windows.

5.1 Windows services entries

Open the services file <install path>\system32\drivers\etc\services and find the lines that begin bpcd and bprd and see what port they are set to. By default they look like this:
bpcd bprd 13782/tcp 13720/tcp

If these entries are missing, reinstall the client software.

Status Code 57: client connection refused

Page 5 of 7

5.2 UNIX services entries

The following files can be checked on UNIX and Linux clients to verify the port number being used for bpcd.

5.2.1 UNIX and Linux systems

For UNIX and Linux systems check the /etc/services file for a listing of NetBackup services.
bpcd vnetd vopied bpjava-msvc 13782/tcp 13724/tcp 13783/tcp 13722/tcp bpcd vnetd vopied bpjava-msvc

5.2.2 Client using bpcd in standalone mode

For systems running bpcd standalone check the bpcd startup line in the system startup files to see if the default port (13782) has been modified on the command line.

6 Verifying connectivity to bpcd

A status 57 is an active refusal by the client to accept a connection on port 13782. This means that a packet was sent from the master server to the client, and that no bpcd process was listening on the requested port. A perimeter security device, such as a firewall, will not cause a status 57. Local security services (such as tcpwrappers) might. Check connectivity to bpcd on the client from the master using telnet.

6.1 Telnet test from a Windows server

Open a command prompt and type:
% telnet <hostname> 13782

If bpinetd/bpcd is listening, the screen will turn blank with a blinking cursor in the top left corner. Press Ctrl-c to return to a command prompt. If bpinetd/bpcd is not listening, the following message will be received:
Connecting To <hostname>...Could not open connection to the host, on port 13782 : Connect failed

This will automatically return to a prompt since a connection to bpcd could not be established.

6.2 Telnet test from a UNIX server

Open a shell and enter the command:
# telnet <hostname> 13782

If bpcd is listening, the following lines will appear:

# telnet <hostname> 13782 Trying x.x.x.x... Connected to <hostname>. Escape character is '^]'.

The cursor will flash, press [Enter] to return to a command prompt. If bpcd is not listening, the following message will be received:
# telnet <hostname> 13782 Trying x.x.x.x... telnet: Unable to connect to remote host: Connection refused

This will automatically return to a prompt since a connection to bpcd could not be established.

Status Code 57: client connection refused

Page 6 of 7

7 Non-windows or UNIX considerations

There are additional causes for a Status 57 that can occur based on policy configuration.

7.1 NDMP policy type

When using the NDMP protocol make sure that the Policy Type of the policy being used is set to NDMP. This is set in the Attributes tab of the policy. Having the Policy Type set to something other then NDMP, such as Standard or MS-Windows-NT, will result in a status code 57 when a backup job is initiated.

7.2 Catalog backup file list

For catalog backups, make sure the file paths are valid entries. In the Java GUI go to the Catalog section and select Actions > Configure NetBackup catalog. The Files tab will list the files that will be backed up as part of the catalog backup. Ensure these are pointing to the correct path names.

8 Enabling logging
There is no client logging information that will help in troubleshooting a status 57 issue. The bpcd log on the client will show nothing as thats the process that cannot be connected to. Sometimes, the system log on the client may show why bpcd is having problems starting up. Enable the bpbrm daemon the media server that is handling the backup. This will show the connection to the client. The logconnections line can be used to verify the IP address that is being connected to.
<2> logconnections: BPCD ACCEPT FROM x.x.x.x.607 TO y.y.y.y.113782

Verify the sending and receiving IP addresses match the expected hosts. These IP addresses can also be used in the bpclntcmd testing in Section 4 of this document.

9 Links
Click here to Search for other documents on Status 57
Also, click below to perform a search on the following relevant items: Status Code 57 client connection refused

Status Code 57: client connection refused

Page 7 of 7