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

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4188.0. "PW5.0c server goes down automatically.." by QCAV02::KPREM () Tue Mar 04 1997 04:48

    Hi,
    
    I am facing the following problem in the PW server.
    What could be the problem here ?? 
    
Problem Description..

	Pathworks Server shuts down automatically after machine boot.

	The pathworks server startup is included in the system startup
	file. The server starts up at the time of booting and then shuts
	down automatically. Once the server is started manually, it
	starts running. At times, after a random time period, the server
	goes down by itself. 

	There is one error logged in the error log file. It say 
        CMTEXTRACTPWRKVALUE in module CMTCONFIGINT PCM_WARNING_ACTION.
        But there is no message in the OPERATOR.LOG file also. This indicates 
        that the DECnet in the system is working ok. There is no message 
        logged for a DECnet disturbance or a UCX disturbance. 
	There is no disturbance in the network hardware as all the terminals
	connected to the DECserver are working OK without any disturbance.
	
	The problem started occuring only from last Tuesday. Till then, the
	server was working fine.
        
        The server has been configured with only DECnet. TCP/IP, Netbieu
        and IPX is not running on the server.
    
Hardware config...
	Alpha Server 1000A 5/300 with
	128 MB RAM
	1 * RZ29B-VA 4GB HDD (Narrow) in SBB
	1 * CD-ROM
	1 * FDD
	1 * TLZ07 DAT Drive
	1 * DE-435 Ethernet card

Software details...

	OVMS 6.2-1H3
	Pathworks 5.0C running on DECnet
	UCX 3.3
        ORACLE	

Network details...

	The system is connected on the network with the following.

		1 * DECserver 700
		3 * DECserver 90L+
		1 * 8 port Synoptics hub
		1 * Cisco Route

    
    Tks n regards,
    
    Prem
T.RTitleUserPersonal
Name
DateLines
4188.1VMSNET::P_NUNEZTue Mar 04 1997 09:2320
    Prem,
    
    Start by looking in usual places:
    
    Process dump (*.dmp) files in either PWRK$LOGS: or PWRK$LMLOGS: and, if
    found, their corresponding .log file. 
    
    $ ADMIN/ANALYZE/SINCE=<date:time>
    
    how do you know the server has "gone down"?  Do you see specific
    processes missing or simply that when you try to use it, it returns an
    error indicating it's not running, etc?
    
    If you're really running v5.0C, highly recommend upgrading to latest
    version - v5.0E.  To see what version you have:
    
    $ @sys$startup:pwrk$define_commands
    $ pwver ! Note the Image Version column
    
    Paul
4188.2Server going down..QCAV02::KPREMWed Mar 05 1997 00:5120
    Hi,
    
    There is no process dump file and no proper trace of any  errors
    in the  error logs. 
    
    The server is configured for 7 users only. Only DECnet has been
    configured, Netbieu and TCP/IP has been eliminated. The users
    get connected thru DECnet. We noticed that the server is down
    only when a new user tries to connect or when we run ADMIN/PATHWORKS.
    The message we get is "Server is not running". The processes 
    remain on the system. We have to manually start the server and
    it runs for the entire day. This problem is intermittent. 
    
    1. Can this problem be due to Netbieu not running ??
    2. The version 5.0c cld be giving this problem ??
    
    Regards,
    
    Prem
    
4188.3UTRTSC::EISINKNo Kipling apes todayThu Mar 06 1997 02:1736
    Prem,

>>    1. Can this problem be due to Netbieu not running ??
    
    	No, more likely that decnet starts to fail and PATHWORKS
    	startup dies.
    
>>    2. The version 5.0c cld be giving this problem ??
    
    	Can be, wild guess but I strongly recomend to upgrade to V50E.
    	Its not a hard job, easy to do and when you escalate to the CSC
    	people or to engineering they will ask you to upgrade anyway 
    
    
    	Back to the problem. 
    
    	1) Is decnet started before PATHWORKS
    
    	2) Does systartup terminates before it even call pwrk$startup.com ?
    	   You know, $ set noon?
    
    	3) What does admin/analyze give you. DO you see the startup from
    	   pwrk$lmmcp process which starts the lmdmn and lmsrv process ?
    	   It must be there....
    
    	4) What does accounting gives you. This is an indication that the
           processes are started, thus pwrk$startup called.
    	   What do you see when image accounting is turned on.
    
    	5) What do you see in the log files when you submit decnet startup
    	   in batch _and_ pathworks in batch too.
    
    	6) You can start pathworks manualy so look in the startup phase.
    
    		Rob.