Manualshelf

Troubleshooting guide

ManualsBrandsVERITAS ManualsConsumer electronicsNetBackup
101102103104105106107108109110
Chapter 4, Status Codes and Messages 93
Status Codes
Status Code: 26
Message: client/server handshaking failed
Explanation: A process on the server encountered an error when communicating with the
client. This error indicates that the client and server were able to initiate communications,
but encountered difficulties in completing them. This problem can occur during a backup
or a restore.
Recommended Action: Determine which activity encountered the handshake failure by
examining the All Log Entries report for the appropriate time period. Determine the client
and server that had the handshake failure.
For detailed troubleshooting information, create an activity log directory for the process
that returned this status code, retry the operation, and check the resulting activity log.
Status Code: 27
Message: child process killed by signal
Explanation: A child of the process reporting this error was killed. This can occur because
the backup job was terminated or the child process was terminated by another error. This
problem can also occur if a NetBackup process was terminated through Task Manager or
another utility.
Recommended Action: Check the NetBackup All Log Entries report for clues on where
and why the failure occurred. For detailed troubleshooting information, create an activity
log directory for the process that you suspect of returning this status code. Then, retry the
operation and check the resulting activity log.
Status Code: 28
Message: failed trying to fork a process
Explanation: A fork of a child process failed (on UNIX) or a CreateProcess failed (on
Windows NT/2000). This may be due to:
◆ An overloaded system
◆ Insufficient swap space or physical memory
◆ Too many processes running on the system
Recommended Action: Check the NetBackup All Log Entries report for clues on where
and why the failure occurred. For detailed troubleshooting information, create activity log
directories for the processes that you suspect of returning this status code. Then, retry the
operation and check the resulting activity logs.