Veritas-bu

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

2002-03-11 15:53:10
Subject: [Veritas-bu] Error 96 due to Socket read error?
From: gbos AT uoguelph DOT ca (Gerrit Bos)
Date: Mon, 11 Mar 2002 15:53:10 -0500
Thanks, Kevin and Ang, for the responses so far.  The file systems are not
filled, and the drives hadn't gone down, or away from TLD control.  Many
backups went since, and the same machines backed up succesfully in the same
class the following night.  One more unusual thing I just noticed, is that
in the activity monitor the jobs show up as not assigned to a media
server.  I'm thinking I'll leave it as a network hiccup, unless it happens
again....Gerrit

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


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