| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Noticed the following in the OAFC$SERVER.LOG. The system manager had been looking at a problem on the system - a number of processes hanging. He thought the OAFC server had stopped. In fact, the process (WARBLY$SRV73) was still there (connect time 17 days). He killed the process and restarted the server which seems to have cured the processes hanging. Can anyone shed light on the following errors (the problem appeared at about 11am on the 26th, last entry at 18:30 on 25th) - especially the ACCVIOs ??? Cheers, Andy 25-JAN-1994 18:11:23.32 Server: WARBLY::"73=" Error: %MCC-E-EXISTENCE_ERROR, object does not exist Message: CsiCacheFlushDrawerAccess; Error from mcc_mutex_try_lock 25-JAN-1994 18:11:23.55 Server: WARBLY::"73=" Error: %SYSTEM-E-ACCVIO, access violation, reason mask=!XB, virtual address=!XL, PC=!XL, PSL=!XL Message: CsiCacheFlushDrawerAccess; Error from mcc_mutex_try_lock 25-JAN-1994 18:14:15.22 Server: WARBLY::"73=" Error: %MCC-E-EXISTENCE_ERROR, object does not exist 25-JAN-1994 18:18:54.71 Server: WARBLY::"73=" Error: %SYSTEM-E-ACCVIO, access violation, reason mask=!XB, virtual address=!XL, PC=!XL, PSL=!XL 25-JAN-1994 18:30:30.31 Server: WARBLY::"73=" Error: %SYSTEM-F-IVLOCKID, invalid lock id Message: CsiCacheReleaseVMSLock; deq failed in lost DAB loop 25-JAN-1994 18:30:30.80 Server: WARBLY::"73=" Error: %SYSTEM-F-IVLOCKID, invalid lock id Message: CsiCacheBlockAstService; Error releasing VMS lock 26-JAN-1994 13:15:01.91 Server: WARBLY::"73=" Message: Startup for File Cabinet Server V1.0-2 complete
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3813.1 | Not much to go on I'm afraid... | IOSG::STANDAGE | Wed Jan 26 1994 16:04 | 19 | |
Andy,
Question. What version of ALL-IN-1 are they running ? There were a few
problems which caused ACCVIOs that were fixed in the server with MUPA.
From the log file alone it is impossible to determine the exact cause
of a given accvio.
Also, is this a one-off event or have there been other accvios in the
past ?
Thanks,
Kevin.
| |||||
| 3813.2 | V3.0-1? | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Wed Jan 26 1994 16:55 | 8 |
Kev,
looks like a v3.0-1 FCS to me - see the startup message at the bottom.
but thos !XB things look really weird.
Regards,
Andrew.D.wicks
| |||||
| 3813.3 | Some more info.. | NUKVXA::Andy_Doran | Mine's a pint of Ruddles | Wed Jan 26 1994 17:11 | 15 |
Oops... I normally put in versions!!! ALL-IN-1 V3.0-1 VMS V5.5-2 Also (should have said!) its part of a 3 node cluster - all running the same stuff (ie ALL-IN-1). The other 2 nodes do not have similar entries in the server log file, and these 2 ACCVIOs are the only ones in the log file for this node (the log file is now 3 months old). Cheers, Andy | |||||
| 3813.4 | IOSG::STANDAGE | Thu Jan 27 1994 08:43 | 12 | ||
Those !XB things I've seen a few times before, and as I said, the MUP I
know fixes some instances where they might appear.
I suggest you keep an eye on this and let me know if it happens again,
particularly once you have upgraded to MUPA.
Thanks,
Kevin.
| |||||
| 3813.5 | When is spring coming? | CHRLIE::HUSTON | Thu Jan 27 1994 14:03 | 10 | |
To me this looked like the background thread that manages the
CSI drawer cache table barfed, or some control structures for it got
nicely stomped into an unusable mess. No way to be sure from the
lgo file, but the mutex for that thread seems to be the start of the
problem, and the thread acc vio APPEARS to be that background thread.
--Bob (who could be way off, my brain could be frozen after the
wakeup to -16 deg F this morning)
| |||||