On Mon, Aug 02, 2004 at 10:03:53AM -0700, Jann Toole wrote:
>
>
>
> Anyone know of any known issues with 4.5 FP6? I upgraded my master
> (Solaris9) last Monday and got exit status 213 errors for 334 backup
> policies, and exit status 0 for 408. So, it's not like the storage
> unit wasn't really available. I've seen hundreds of error code 13
> come in email, but the activity monitor doesn't show any error 13,
> but hundreds of error 50.
> Thinking this may all be a compatilbity issue between the 2 SAN servers
> and the master, I upgraded one SAN server on wednesday, the other on
> thrusday. Veritas support has had me change timeout parameters, do the
> ndd -set /dev/tcp tcp_time_wait_interval 1000
> and change some of the system file settings - which I resisted because
> of the tech note 264867 recommendations.
> Of course the system changes brought about shared memory allocation errors -
> I changed them back - no more shared memory errors, but the 213 errors came
> back. I did the ndd -set /dev/tcp tcp_time_wait_interval 1000 and last night
> for the first night in a week I did not have 213 or 13 errors, but there were
> some 50 errors in the activity monitor..
> ALSO, another very weird thing, one backup policy (according to the activity
> monitory) started at 22:06 last night, but got error code 50 (aborted) -
> this morning that policy was running (they get 2 tries) - but there were 2
> active backups doing the same policy. OH, and another weirdness, the
> bpdbjobs report did not show any active backups.. but there were 2 tapes
> in the drives - I hadn't looked at the GUI yet - but they probably would
> have shown the jobs to be active since the completion time was 8:45am
> I'm losing confidence in FP6. FP5 was a breeze.
> Any ideas??
Sorry, I posted a wrong link, the correct one is
http://seer.support.veritas.com/docs/264802.htm
Regards,
--
Konstantin 'Kastus' Shchuka
Unix System Administrator
ePocrates Inc.
tel 650.227.1786
fax 650.592.6995
|