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

Conference clarid::dasc

Title:	DASC Tool, Problems & Suggestions
Notice:	Latest kit: see note 85.0
Moderator:	CLARID::KREYER

Created:	Mon Mar 26 1990
Last Modified:	Fri May 23 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	208
Total number of notes:	848

203.0. "VAX CRASHED loading FYDRIVER!!!" by DEBUG::GALLO (Fast/Good/Cheap... Pick 2!) Wed Feb 19 1997 22:35

    Just had a BAD customer situation happen.  I installed DASC V4.1 on a
    VAX 6430 running OpenVMS VAX V5.5-2.  It installed fine.  When I
    invoked DASC.COM, and it started to run...
    
    	       -- Collect system info --
    	%SYSMAN-I-TIMEVAL, timeout value is  00:06:00.00
    	%SYSMAN-I-ENV, current command environment:
    	        Clusterwide on local cluster
    	        Username DAWSON       will be used on nonlocal nodes
    	
    	%SYSMAN-I-OUTPUT, command execution on node VENUS
    	%DASC-I-Collect     :  14:51:07.58
    	%DASC-I-License     :  14:51:14.94
    	%DASC-I-LIFE_start  :  14:51:33.12
    	%SYSTEM-W-NOSUCHDEV, no such device available
    	%SYSTEM-W-NOSUCHDEV, no such device available
    	%DASC-I-NOFYA0  Loading FYDRIVER...
    	
    	Xyplex -206- Connection to EARTH terminated
    	             No response within timeout period
    	Xyplex>
    
    You guessed it.  The VAX crashed while loading FYDRIVER!!!
    When it came back up. I looked at the version of FYDRIVER.EXE out there
    and found...
    
    	FYDRIVER.EXE;2                File ID:  (2516,75,0)
    	Size:           13/21         Owner:    [SYSTEM]
    	Created:   8-JUL-1992 01:21:43.62
    	Revised:   8-NOV-1992 18:03:21.36 (37)
    
    This is a 2 node cluster.
    Any reason why this machine should CRASH????
    
    Thanks.  Paul Gallo

T.R Title User Personal
Name Date Lines

203.1 bogus copy at sys$specific:[sys$ldr]fydriver.exe VELI::KORKKO Veli K�rkk� @FNO, 879-5512 Thu Feb 20 1997 19:59 28

T.R	Title	User	Personal Name	Date	Lines
203.1	bogus copy at sys$specific:[sys$ldr]fydriver.exe	VELI::KORKKO	Veli K�rkk� @FNO, 879-5512	`Thu Feb 20 1997 19:59`	28
	Seems that your (customer's) FYDRIVER.EXE is outdated. On my V5.5-2 system FYDRIVER info is: Directory SYS$COMMON:[SYS$LDR] FYDRIVER.EXE;4 File ID: (7299,2,0) Size: 13/16 Owner: [SYSTEM] Created: 2-OCT-1993 19:39:11.92 Revised: 10-MAR-1994 11:12:12.13 (15) Expires: 21-MAY-1997 20:56:39.59 Backup: 8-FEB-1997 00:15:55.46 File organization: Sequential File attributes: Allocation: 16, Extend: 0, Global buffer count: 0, No version limit Record format: Fixed length 512 byte records Record attributes: None RMS attributes: None Journaling enabled: None File protection: System:RWED, Owner:RWED, Group:RWED, World: Access Cntrl List: None Total of 1 file, 13/16 blocks. Is your FYDRIVER.EXE at the sys$common:[sys$ldr] or is there a "bogus" copy at SYS$SPECIFIC:[SYS$LDR]? _veli

        Seems that your (customer's) FYDRIVER.EXE is outdated. On my
        V5.5-2 system FYDRIVER info is:
        

Directory SYS$COMMON:[SYS$LDR]

FYDRIVER.EXE;4                File ID:  (7299,2,0)         
Size:           13/16         Owner:    [SYSTEM]
Created:   2-OCT-1993 19:39:11.92
Revised:  10-MAR-1994 11:12:12.13 (15)
Expires:  21-MAY-1997 20:56:39.59
Backup:    8-FEB-1997 00:15:55.46
File organization:  Sequential
File attributes:    Allocation: 16, Extend: 0, Global buffer count: 0, No version limit
Record format:      Fixed length 512 byte records
Record attributes:  None
RMS attributes:     None
Journaling enabled: None
File protection:    System:RWED, Owner:RWED, Group:RWED, World:
Access Cntrl List:  None

Total of 1 file, 13/16 blocks.
        
        
        Is your FYDRIVER.EXE at the sys$common:[sys$ldr] or is there a
        "bogus" copy at SYS$SPECIFIC:[SYS$LDR]?
        
        _veli