15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

Chapter 4, <strong>NetBackup</strong> Status Codes and Messages 77<br />

Status Codes<br />

For detailed troubleshooting in<strong>for</strong>mation, create a debug log directory <strong>for</strong> the process that<br />

returned this status code, retry the operation, and check the resulting debug log.<br />

<strong>NetBackup</strong> Status Code: 27<br />

Message: child process killed by signal<br />

Explanation: A child of the process reporting this error was killed. This can occur because<br />

the backup job was terminated or the child process was terminated by another error. This<br />

problem can also occur if a <strong>NetBackup</strong> process was terminated through Task Manager or<br />

another utility.<br />

Recommended Action: Check the <strong>NetBackup</strong> All Log Entries report <strong>for</strong> clues on where<br />

and why the failure occurred. For detailed troubleshooting in<strong>for</strong>mation, create a debug<br />

log directory <strong>for</strong> the process that you suspect of returning this status code. Then, retry the<br />

operation and check the resulting debug log.<br />

<strong>NetBackup</strong> Status Code: 28<br />

Message: failed trying to <strong>for</strong>k a process<br />

Explanation: A CreateProcess failed. This may be due to:<br />

◆ An overloaded system<br />

◆ Insufficient swap space or physical memory<br />

◆ Too many processes running on the system<br />

Recommended Action: Check the <strong>NetBackup</strong> All Log Entries report <strong>for</strong> clues on where<br />

and why the failure occurred. For detailed troubleshooting in<strong>for</strong>mation, create debug log<br />

directories <strong>for</strong> the processes that you suspect of returning this status code. Then, retry the<br />

operation and check the resulting debug logs.<br />

<strong>NetBackup</strong> Status Code: 29<br />

Message: failed trying to exec a command<br />

Explanation: A command could not be executed. This can occur because the permissions<br />

of the command do not allow it to be executed, or there is lack of system resources such as<br />

memory and swap space.<br />

Recommended Action:<br />

1. Check the <strong>NetBackup</strong> All Log Entries report <strong>for</strong> clues on where and why the failure<br />

occurred.<br />

2. Check the permissions on the command to be executed.<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!