Вы находитесь на странице: 1из 3

Problem

NetBackup status code 82: media manager killed by signal

Solution
Message: media manager killed by signal Explanation: Another process or a user terminated the tape manager (bptm) or disk manager (bpdm). Recommended action: This error should not occur in normal operation. If you want to terminate an active backup, use the NetBackup Activity Monitor. When backing up a DomainOS client, this error occurs after the server has not received anything on the socket for at least 300 seconds. It causes a client read timeout and breaks the connection. The bpbkar debug log has an entry similar to the following:
13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESETConnection reset by peer (UNIX/errno status)

To resolve the problem, increase the CLIENT_READ_TIMEOUTvalue (in this instance to 900).

Problem
Status Code 82: Media Manager killed by signal

Solution
ISSUE: The majority of backups Fail with Status 82 :Media Manager killed by signal ERROR CODE/MESSAGE: Status 82: Media Manager killed by signal The bpbkar log may also show Network Related Errors. For example: Error status = 24: socket write failed OR status = 40: network connection broken. bpbkar Log 02:10:17.785 [23278] <16> flush_archive(): ERR - Cannot write to STDOUT. Errno = 32: Broken pipe 02:10:17.786 [23278] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 24: socket write failed 02:10:17.786 [23278] <4> bpbkar Exit: INF - EXIT STATUS 24: socket write failed

02:10:17.786 [23278] <2> bpbkar Exit: INF - Close of stdout complete 02:10:17.786 [23278] <4> bpbkar Exit: INF - setenv FINISHED=0 Fails after 4 mins bpbrm Log: 02:07:50.040 [10446] <2> bpbrm send_parent_msg: POSITION ABC123 211 0 02:09:15.208 [10446] <2> bpbrm read_media_msg: read from media manager: POSITION SSP441 31 1 02:09:15.209 [10446] <2> bpbrm send_parent_msg: POSITION ABC123 31 1 02:09:28.468 [10446] <2> bpbrm read_media_msg: read from media manager: BEGIN_BACKUP abc.xyz.123.com_1244613988 ABC123 02:09:28.468 [10446] <2> bpbrm send_parent_msg: BEGIN_BACKUP abc.xyz.123.com_1244613988 ABC123 02:09:28.469 [10446] <2> bpbrm read_media_msg: read from media manager: BEGIN_BACKUP abc.xyz.123.com_1244613989 ABC123 02:09:28.469 [10446] <2> bpbrm send_parent_msg: BEGIN_BACKUP abc.xyz.123.com _1244613989 ABC123 02:09:53.968 [10446] <2> bpbrm read_media_msg: read from media manager: ERROR 82 02:09:53.968 [10446] <2> bpbrm send_parent_msg: ERROR 82 02:09:53.968 [10446] <2> bpbrm process_media_msg: got ERROR 82 from media manager 02:09:53.968 [10446] <2> bpbrm kill_bpbrm_child: killing bpbrm child 10455. 02:09:53.968 [10446] <2> bpbrm kill_bpbrm_child: killing bpbrm child 10463. 02:09:53.969 [10455] <2> Bpbrm_siginfo_print: 0: delay 0 signo SIGHUP:1 code 0 pid 10446 02:09:53.969 [10463] <2> Bpbrm_siginfo_print: 0: delay 0 signo SIGHUP:1 code 0 pid 10446 02:09:53.969 [10446] <2> bpbrm Exit: ERROR 82 sent to parent process CAUSE: There could be Possibility of a Network Communication Issue or a DNS Forward/Reverse Lookup Issue. TROUBLESHOOTING: Make sure all of the following are correct: IP Addresses, Shortnames, FQDN in the /etc/host files for Master, Media Servers, especially if you suspect there are issues with your DNS. Short name and the FQDN in the SERVER = entry in the bp.conf. Name Servers & IP Addresses listed in the correct order in the resolve.conf Make sure you have files first and then the dns and not the other way round in the nsswitch.conf file, especially if you suspect there are issues with your DNS. Check and Confirm with the bpclntcmd command for forward & reverse name resolution. Both are important.) From Client to Server and Server to Client # bpclntcmd -ip <IP_Address> # bpclntcmd -hn <hostname> From Client to Server only

# bpclntcmd -pn If the above steps do not work then you can Test the Communication with any Third Party Utility and check for packet Reordering or Network Packet dropouts/timeouts. Eg. apparNet