Veritas-bu

[Veritas-bu] Error 96 due to Socket read error?

2002-03-11 11:10:07
Subject: [Veritas-bu] Error 96 due to Socket read error?
From: kdavis AT aol DOT net (Kevin Davis)
Date: Mon, 11 Mar 2002 11:10:07 -0500
Gerrit

Check to see if you have a full file system on the media server.

~Kevin

Gerrit Bos wrote:
> 
> I had a weird error this weekend.  We had three error 96's in one class
> even though there were tapes in the scratch pool (and scratch pool is
> defined, and the tapes in the scratch pool are not assigned.)  We are
> running 3.2GA on Solaris 2.7.  Is it possible that the available_media
> script encountered a socket error?  If it is, is it this likely to be a
> blip, which I don't have to worry about?  In looking though the various
> log files, the only thing which stands out is this error from the
> bpsched log.  Thanks for any help anyone can shed....Gerrit
> 
> 23:50:01 [1518] <2> sighdl: timed out
> 23:50:01 [1518] <16> readline: fgets failed:  Interrupted system call
> (4)
> 23:50:01 [1518] <8> available_media: readline failed:  socket read
> failed (23)
> 23:50:02 [1518] <16> log_in_errorDB: backup of client titan.nw exited
> with status 96 (unable to allocate new media for backup, storage unit
> has none available)
> 23:50:02 [1518] <2> getsockconnected: Connect to wayback on port 989
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

--
*             Kevin Davis  -  Systems Admin  -  AOL             *
*         Office: (703) 265-4392   Pager: 1-877-344-3241        *
*          It's insane, to be sane in an insane world.          *

<Prev in Thread] Current Thread [Next in Thread>