[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

671.0. "2.4 installation hangs" by KERNEL::LOAT (Bored....Bored....BORED!!!!) Tue May 12 1992 14:41

    
    A customer is attempting to install ALL-IN-1 2.4 on VMS 5.4-2, and it
    gets to the part where it attempts to build the shared images modules,
    and the process stops.
    
    The process clocks up no CPU or IO, and is stuck in a HIB state.
    Control-Y'ing the process does nothing, and the only way to kill it is
    to stop/id the process.
    
    He hasn't set interactive logins to zero, so he's not being bitten by
    that bug.
    
    This is a brand new installation, and he's now tried four times to get
    this working, but each time, it does exactly the same thing. There have
    been no other errors up until this bit of the installation, and he';s
    set the process quotas, and SYSGEN parameters as recommended.
    
    Ideas?
    
    Steve.
T.RTitleUserPersonal
Name		DateLines
671.1A link loop without the loop? ;')BUFFER::VICKERSRearranging the DEChairsTue May 12 1992 14:5919
    This certainly does sound like very strange behaviour for a common
    household appliance (or installation).  The HIB process state seems
    quite bizarre.

    A wild guess would be that there is some file system level problem,
    possibly a bad object library or other file used in the link. It would
    be good to do an ANAL/RMS on the various object libraries in SYS$SHARE
    as well as the ones being used more directly by ALL-IN-1 in its area. 

    I would suggest that the ANAL/DISK be done on the system disk and other
    disks being used for the install to see if there are problems at that
    level, as well.

    It might be a bit helpful to do a SHOW PROC/CONT on one other terminal
    and a SHOW DEV/FIL/NOSYS SYS$SYSDEVICE: on another to observe the
    progress of the install.

    Hang in there,
    don
671.2DEBUG, DEBUG, DEBUG!AIMTEC::WICKS_ALiverpool win the F.A Cup again!Tue May 12 1992 15:587
    Or redo the installation with OPTIONS D 
    
    that will tell you what file it is trying to access.
    
    Regards,
    
    Andrew.D.Wicks
671.3Assuming you don't fill the disc with the resulting logfile...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeTue May 12 1992 16:020
671.4VMS bug?IOSG::TALLETTMaking broccoliWed May 20 1992 19:2815
    
    	This reminds me of a bug in SPAWN, something to do with the
    	protection on a mailbox used by DCL to pass info between the
    	parent and sub-process. The footprint was a HIB parent in
    	supervisor mode (don't we just know it) and no subprocess. It
    	was introduced in a recent VMS version, as the protection on the
    	mailbox was "corrected". HIB+super state is normal for a parent
    	spawning a subprocess.
    
    	Sorry I can't be more specific, I didn't really understand the
    	details at the time. You could maybe trawl VMSNOTES, cos that's
    	where I saw it.
    
    Regards,
    Paul