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

Conference csc32::consolemanager

Title:	POLYCENTER Console Manager
Notice:	Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:	CSC32::BUTTERWORTH

Created:	Thu Aug 06 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1541
Total number of notes:	6564

863.0. "Console Daemon dies at once" by SWETSC::WESTERBACK (Mai pen rai!) Wed Jul 12 1995 13:41

    Hi, I have an urgent problem: I can't start PCM at all!
    
    PCM 1.5, VMS/AXP 6.1.
    
    After a system crash the other night PCM didn't start. The process
    Console Notify was there, but not Console Daemon. After that I have
    tried different ways to get it going, but no luck. From what I see
    in the manual I do a CONSOLE SHUTDOWN, then a @CONSOLE$STARTUP. It
    tells me there are still processes running, use RESTART. I can see
    that Console Notify is still there. I use @CONSOLE$STARTUP RESTART
    instead, and now a Daemon process is created, but goes away at once.
    
    Accounting shows:
    
    DETACHED Process Termination
    ----------------------------
    
    Username:          SYSTEM            UIC:               [SYSTEM]
    Account:           SYSTEM            Finish time:       12-JUL-1995
    13:26:42.54
    Process ID:        0000013F          Start time:        12-JUL-1995
    13:26:32.33
    Owner ID:                            Elapsed time:                0
    00:00:10.21
    Terminal name:                       Processor time:              0
    00:00:03.39
    Remote node addr:                    Priority:          4
    Remote node name:                    Privilege <31-00>: FFFFFFFF
    Remote ID:                           Privilege <63-32>: FFFFFFFF
    Queue entry:                         Final status code: 00000001
    Queue name:
    Job name:
    Final status text: %SYSTEM-S-NORMAL, normal successful completion
     
    Page faults:              521        Direct IO:                 59
    Page fault reads:         122        Buffered IO:              233
    Peak working set:        5312        Volumes mounted:            0
    Peak page file:         37392        Images executed:            5
    
    
    I have tried various ways of rebooting the system without PCM, then 
    starting it interactively, or in batch, but no luck. 
    
    This is urgent, since this PCM covers all our internal IS systems,
    and all our PCM expertise is on vacation...
    
    Rgds,
    Hans Westerback
    IS Stockholm

T.R	Title	User	Personal Name	Date	Lines
863.1	A log file	SWETSC::WESTERBACK	Mai pen rai!	`Wed Jul 12 1995 14:10`	28
	I just found the command: $ define/sys CONSOLE$DEBUG DAEMON and tried again. Here is the log: $ SET MESSAGE /FACILITY /IDENTIFICATION /SEVERITY /TEXT $ SET DEFAULT CONSOLE$TMP: $ SET PROCESS /DUMP $ RUN CONSOLE$IMAGE:CONSOLE$DAEMON.EXE POLYCENTER Console Manager Console Controller Daemon Version V1.5-006 Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved System 'GRETA' is disabled, NO verify performedSystem 'PORLA' is disabled, NO verify performedSystem 'REMS' is disabled, NO verify performedSystem 'STKIN' is disabled, NO verify performedSystem 'SUV01' is disabled, NO verify performedSystem 'SUV02' is disabled, NO verify performedCMChildControlSocketErrorCB: Start Unable to create/map shared memory section error 0 Console Manager shutting down at user request Unable to create control listener Console Manager shutting down at user request ISOPER job terminated at 12-JUL-1995 13:49:26.82 Accounting information: Buffered I/O count: 229 Peak working set size: 4400 Direct I/O count: 23 Peak page file size: 37520 Page faults: 560 Mounted volumes: 0 Charged CPU time: 0 00:00:03.31 Elapsed time: 0 00:00:08.74 Does this shared memory section mean anything to you? Hans
863.2		OPG::PHILIP	And through the square window...	`Wed Jul 12 1995 15:28`	16
	Hans, The inability to create the shared memory section is almost certainly the cause of your problem. As for the reason for the problem, I dont know. Before the system crash, were any system parameters changed (such as gblsections/gblpages)? This may cause quota problems making it impossible for PCM to create the mapped section. I would suspect that if it worked before but not now then something someone has changed broke it (I doubt a system crash would cause this behaviour). Cheers, Phil
863.3	autogen fixed it	SWETSC::WESTERBACK	Mai pen rai!	`Wed Jul 12 1995 16:20`	22
	Phil, Thanks for your advice. There were no changes in MODPARAMS lately, maybe the system manager has made some changes in SYSGEN because of the recent crashes. We have had three crashes at night during the last two weeks. Anyway I ran an AUTOGEN and rebooted, and now it seems to be working OK. The only notable entries in AGEN$PARAMS.REPORT was GBLPAGES parameter information: Feedback information. Old value was 100816, New value is 122000 RESHASHTBL parameter information: Feedback information. Old value was 32768, New value is 8192 Rgds, Hans