STATUS CODE: 5, 49 A restore fails with a Status 5 in the GUI and a Status 49 "Client did not start" is received in the logs.

Article:TECH32332  |  Created: 2004-01-27  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH32332
Article Type
Technical Solution

Product(s)

Environment

Issue



STATUS CODE: 5, 49 A restore fails with a Status 5 in the GUI and a Status 49 "Client did not start" is received in the logs.

Error



<2> bpbrm readline: EOF detected on NAME socket
<16> bpbrm handle_restore: client didn't start
<2> bpbrm brm_sigcld: bpbrm child 6835 exit_status = 49, signal_status = 0
<2> bpbrm brm_sigcld: child 6835 exited with status 49: client did not start

Solution



Overview:
Restore jobs queue and do not go active.  These eventually fail with a Status 5 in the Activity monitor.  A closer look at the bpbrm log will show the job failed with a Status 49 (client did not start).  This can be caused when the tar binary has been removed on the client.


Troubleshooting:
Verify the tar binary is installed on the client.  If the tar binary is missing, the following error will be displayed:
# ls -l /usr/openv/netbackup/bin/tar
/usr/openv/netbackup/bin/tar: No such file or directory


Media Server Log Files:
The /usr/openv/netbackup/logs/bpbrm/log.<date> will show the child bpbrm process failing with an error:
17:54:24.673 [6835] <2> bpbrm handle_restore: received bpcd success message
17:54:24.680 [6835] <2> bpbrm readline: EOF detected on NAME socket
17:54:24.680 [6835] <16> bpbrm handle_restore: client <hostname> didn't start

The corresponding bpbrm parent process then fails with a status 49.
17:54:24.960 [6822] <2> bpbrm brm_sigcld: bpbrm child 6835 exit_status = 49, signal_status = 0
17:54:24.960 [6822] <2> bpbrm brm_sigcld: child 6835 exited with status 49: client did not start


Resolution:
To reinstall the client binaries use the update_clients command.  This will reload any binaries that are missing or that may be corrupt.

1) Create a /tmp/client_list file with a list of clients to update and add the entry.
Solaris Solaris9 <hostname>
Where Solaris is the hardware platform, Solaris9 is the OS version and <hostname> is the client hostname to update.

2) Then run the update_clients command to reinstall the client software:
# /usr/openv/netbackup/bin
# ./update_clients -ForceInstall -ClientList /tmp/client_list

As a workaround, the tar binary can be copied from a working client that is running the same Operating System and hardware platform as the failing client.  Once the tar binary is copied to the nonworking client, verify the correct ownership and permissions are set properly.  

# chmod 555 tar
# chown root tar
# chgrp bin tar
# ls -la tar
-r-xr-xr-x   1 root  bin   462028 May 14 13:34 tar

Note:  The exact size of the tar binary will vary depending on the NetBackup version, operating system version and hardware platform.

Supplemental Materials

SourceError Code
Value49
DescriptionNetBackup Error 49: client did not start

SourceError Code
Value5
DescriptionNetBackup Error 5: the restore failed to recover the requested files

Legacy ID



268347


Article URL http://www.symantec.com/docs/TECH32332


Terms of use for this information are found in Legal Notices