It seems when this starts happening, I find at least one job who's
detailed status is many lines of "Error bpbrm could not write
KEEPALIVE to COMM_SOCK". Maybe that gives a clue to what's going on?
I'm still looking for thoughts on this.

-Charlie


---------- Forwarded message ----------
From: Charles Ballowe <cballowe AT gmail DOT com>
Date: Wed, 16 Feb 2005 13:34:35 -0600
Subject: Error 24 problems and trouble shooting
To: veritas-bu AT mailman.eng.auburn DOT edu


It seems that every couple of weeks one of my media servers will
completely forget how to talk to the world and every backup that tries
to use it will fail with a 24. Reboots can clear this, but there has
to be a better way.

A network sniff at the time a backup gets kicked off doesn't show any
traffic to the clients involved so I believe that the problem is on
the server. Outside of backup processes, I'm able to send traffic
through the interface, but backups stop working. In progress backups
seem to continue on to completion.

The environment is NB 5.1 MP2, many of the clients are still 4.5 of
some form. This problem seemed to exist in 4.5 as well. The servers
are all solaris, clients are a mix of unix and windows.
Any idea where to look to start troubleshooting this one?

-Charlie