[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

4229.0. "Edits hang, FCS loops" by GIDDAY::BURT (Scythe my dandelions down, sport) Fri Jun 03 1994 08:10

Hello and greetings,

ALL-IN-1 V3.0A

Users getting "hung" when editing, Filecabinet Server appears to be looping.

On several occasions, the filecabinet server has been observed to be using 
excessive amounts of CPU. Users have complained that they are 'hung' when 
attempting to edit a document.

Stopping and restarting the server usually fixes the immediate problem.

I've looked here & in Stars, but have not seen anything similar reported.

Any thoughts on what is happening here?


Thanks & regards,

Chele

FCS log extract follows formfeed


The Filecabinet Server log contains the following :

29-MAY-1994 04:18:50.12  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete

30-MAY-1994 02:45:20.63  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiCacheBlockAstService; Error from
mcc_astevent_receive

30-MAY-1994 02:59:56.36  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete

31-MAY-1994 02:46:26.76  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiCacheBlockAstService; Error from
mcc_astevent_receive

31-MAY-1994 03:02:41.26  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete

31-MAY-1994 20:09:07.10  Server: PER2::"73="  Error: %DSL-W-SHUT, Network
shutdown  Message: Shutting Down server, network failure.

31-MAY-1994 20:09:08.49  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: SrvBufferProcess; receive alert to
terminate thread

31-MAY-1994 20:09:09.15  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: SrvMemoryScavenge; receive alert to
terminate thread

31-MAY-1994 20:09:09.40  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiCacheBlockAstService; Error from
mcc_astevent_receive

31-MAY-1994 20:22:37.06  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete

 1-JUN-1994 02:45:13.95  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: SrvBufferProcess; receive alert to
terminate thread

 1-JUN-1994 02:59:25.56  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete

 2-JUN-1994 02:46:20.50  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiCacheBlockAstService; Error from
mcc_astevent_receive

 2-JUN-1994 03:01:14.88  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete


 2-JUN-1994 13:43:22.05  Server: PER2::"73="  Error: %OAFC-E-THREADACCVIO, An
FCS thread access violated, please submit an SPR  Message: FCS has access
violated, please submit an SPR.

 3-JUN-1994 02:46:17.31  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiCacheBlockAstService; Error from
mcc_astevent_receive

 3-JUN-1994 03:01:13.72  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete

 3-JUN-1994 11:57:21.14  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiOpenRmsFC; error opening filecab:
DISK$USER14:[USER_AL
 3-JUN-1994 11:57:45.69  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiOpenRmsFC; error opening filecab:
DISK$SYS3:[ALLIN1.MGR]

 3-JUN-1994 11:57:48.75  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiOpenRmsFC; error opening filecab:
DISK$USER18:[USER_ALLIN1.WOPLAOAI1.A1]


 3-JUN-1994 11:57:50.24  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiOpenRmsFC; error opening filecab:
DISK$USER14:[USER_ALLIN1.WOPMW3AI1.A1]

 3-JUN-1994 11:58:02.89  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiOpenRmsFC; error opening filecab:
DISK$USER19:[USER_ALLIN1.WOPTT2AI1.A1]

 3-JUN-1994 11:58:16.39  Server: PER2::"73="  Error: %MCC-E-EXISTENCE_ERROR,
object does not exist  Message: CsiEndFunction; Error from ReturnDRCBs

 3-JUN-1994 11:58:20.38  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiOpenRmsFC; error opening filecab:
DISK$USER14:[USER_ALLIN1.WOPGC3AI1.A1]

 3-JUN-1994 11:58:24.37  Server: PER2::"73="  Error: %MCC-E-ALERT_TERMREQ,
thread termination requested  Message: CsiOpenRmsFC; error opening filecab:
DISK$USER13:[USER_ALLIN1.CALGS9AI1.A1]

 3-JUN-1994 12:01:17.04  Server: PER2::"73="  Message: Startup for File
Cabinet Server V3.0A complete

T.RTitleUserPersonal
Name
DateLines
4229.1HERO::LOCKWOODZZZZzzzz....Fri Jun 03 1994 09:5415
    
    	Hi,
    
    	We've had several similar reports of the server suddenly going into
    	a 100% CPU loop.  As far as we can tell the problem seems to be
    	being caused in RMS, which the server is using all the time.  We've
    	been told that the actual RMS problem has been fixed in VMS 6.1 (I
    	think - don't quote me on that ;-) ), but we're trying to prevent
    	the loop by modifying the way we call RMS from the server.
    	Hopefully tests later today will tell us if we've been successful,
    	but obviously this fix will be in the new server and I don't know
    	if there'll be a patch available for MUP servers...
    
    	Pete.
    
4229.3IOSG::STANDAGETue Jun 07 1994 10:2714
    
    Chele,
    
    Yes, we do have some news. It would appear as though we have resolved
    the 100% CPU loop we were reproducing here. This will appear in a PFR
    of ALL-IN-1 and TLC.
    
    However, I should probably point out that this might not be necessarily
    the cause of your CPU loop, but we haven't seen any others so
    statistically the chances have been dramatically reduced :-).
    
    Kevin.
    
    
4229.5HERO::LOCKWOODIt must be a ThursdayTue Jul 05 1994 10:188
    
    	Currently in the PFRs known as TLC V2.1 and ALL-IN-1 V3.1
    
    	I don't know of any plan for a patch right now.
    
    
    	Pete