NetBackup status code: 24
Message: socket write failed
Explanation: A write operation to a socket failed.
Recommended Action: Do the following, as appropriate:
Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create debug log directories for the processes that could have returned this status code. Then retry the operation and check the resulting debug logs.
A possible cause is a high network load. For example, this problem occurs with Cannot write to STDOUT when a Windows system that monitors network load detects a high load. It then sends an ICMP packet to other systems to inform them that the route they use is disconnected. The log messages were similar to the following:
01/31/22 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No route to host 01/31/22 14:05:48 ruble crabtree.null.com successfully wrote backup id crabtree.null.com_1643637900, copy 1, fragment 1, 440864 Kbytes at 628.538 Kbytes/sec 01/31/22 14:05:51 netbackup crabtree.null.com CLIENT crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT STATUS 24 (socket write failed)
The following information applies only to Sun Solaris:
Verify that all operating system patches are installed.
See the Operating Notes section of the NetBackup Release Notes.
The following information applies only to Windows systems:
Verify that the recommended service packs are installed.
Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.