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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

3488.0. "Fatal server bug error..." by KERNEL::CROOKS () Thu Oct 18 1990 12:35

    Hello folks,
    DECwindows v1.0 DECwrite v1.0 Vaxstation 3100 VMS 5.2
    
    A customer reported following error which occurs
    when editing a file or even opening file from DECwrite.
    The error was actually logged in DECW$SERVER_0_ERROR.LOG

    Dixmain address=253fa
    Now attach all known txport images
    in SetFontPath
    out SetFontPath
    Monochrome Frame Buffer support loaded
    mfb$InitOutput address=133200
    Connection Prefix: len==36
    Now I call scheduler/dispatcher
    Connection  b6310 is closed by Txport
       "    	b6248 "   "      "   "
       "    	b6248 "   "      "   "
    		b83a8
    		b9c40
    		b62b8
    		34a860
    		34a860
    		b62b8
    		c2950
    		
    Fatal server bug
    Resource db corruption found(head=1807bc,drawld=5243000)
    
    Request opcode 70 is ignored due to internal runtime error c for
    client 5(#error =1)
    Exception Call stack dump follows:
    		aa6f5
    		24f55
    		3510d
    		207d2
    		23f5d
    		23ab9
    		256b4
    *************marking the end of call stack dump ******************
    ******************************************************************
    
    Fatal server bug
    Resource db corruption found(head=1807bc,drawld=5243000)
    
    Client 5 has made too many runtime errors(2), its connection is
    marked for termination
        Exception Call stack dump follows:
    		aa6f5
    		24f55
    		3510d
    		207d2
    		23f5d
    		23ab9
    		256b4
    *************marking the end of call stack dump ******************
    ******************************************************************
    ..ddx layer returns bad status(17)
    ..Dispatcher close down connection 5

    Do these errors make any sense to anyone out there...?
    
    Thanks in advance for any input at all...

    Alan Crooks UK CSC
    
    
T.RTitleUserPersonal
Name
DateLines
3488.1DECWIN::NORCROSSThu Oct 18 1990 16:495
    The resource manager database in the server has been corrupted for
    some reason.  We fixed similar problems in DECwindows in V2.
    I suggest the customer upgrade if possible.
             
    -AnnMarie
3488.2In the meantime.....KERNEL::CROOKSMon Oct 22 1990 10:228
    Thanks for the reply AnnMarie,
    
    Just one thing, is it possible to recover the resource manager
    database in any way if an immediate upgrade is not possible?
    
    Regards 
    Alan ( who knows little about Decwindows servers)
    
3488.3DECWIN::NORCROSSTue Oct 23 1990 10:4610
    No, the resource manager database can not be recovered.
    
    The resource manager database is a basically a hash table
    maintained by the server to keep track of resources (like pixmaps
    and GCs) for clients. 
    
    The only solution is to upgrade.
    
    -AnnMarie