[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

1321.0. "PCM 1.6 ENS connection failing on DUNIX 3.2d" by CSC32::B_GRUBBS () Wed Jun 12 1996 10:10

    
    UNIX 3.2d2
    PCM 1.6 - eco 2 
    
    When I start c3 I can't get anything to start because the ENS
    connection is failing. I turned on the debug info and restarted c3 
    and I see this repeating over and over:
    
    CMCreateEventPort: Opening local transport event port </var/opt/console/tmp
    /CONSOLE_EVT_ENS_C3>
    CMCreateEventPort: Open failure
    CMCloseEventPort: Closing Event Port <ENS_C3>
    C3: Wed Jun 12 09:00:21 1996:  Failed to connect to ENS
    C3: adding ENS connect timer
    
    
    The permissions on /var/opt/console/tmp:
    
    drwxrwxrwx   2 root     system       512 Jun 12 07:58 /var/opt/console/tmp
    
    
    I never see any sockets get created in that directory either.  the 
    only file in that directory is console_cfg.dat.
    
    I've tried deleting all the subsets and deleting the /var/opt/console
    and /usr/opt/DCR160 dirs and reinstalling and still the same thing.
    
    I'm starting to thing there is something wrong about 3.2d and PCM 1.6
    togethor.
    
    ideas?
    
    --Bert Grubbs
      Colorado CSC
T.RTitleUserPersonal
Name
DateLines
1321.1CSC32::BUTTERWORTHGun Control is a steady hand.Wed Jun 12 1996 12:0733
    Bert,
      If there are no sockets and you don't find any files
    other than the config then the daemons must not be starting
    as well. After you start PCM from root do
    
    console -d -c
    
    Find the fields that give you the process id's for the ENS and parent 
    daemon. Next do a ps and grep for the pids and see if they are still 
    there. If they are not do
    
    console -s -y
    
    at least twice. Repeat the console -d -c command and hopefully 
    the CM pid and ENS pid will be 0 as well as all the other fields.
    Now do console_startup and hopefull it'll start. The goal of this
    exercise is to make sure the shared memory section is cleaned
    up. There seems to be a real problem with the way PCM uses
    shared-mem with 3.2D. I do not know anything about Unix memory
    management to take this too much further.
    
    I have also had your problem even when the sockets are present and the 
    daemons are alive and well. The sockets get created and then their 
    protection is changed via a call to chmod using a mask of 0700. This 
    protection mask grants only owner access and the owner is typically
    root. What bothers me is that I would have expected connections to 
    these sockets to have *always* failed except for the root user yet
    everything has worked *fine* up to version 3.2D! So something has 
    changed. I posed this question in the Digital Unix conference but noone
    has replied.
    
    Regs,
      Dan
1321.2CSC32::B_GRUBBSWed Jun 12 1996 12:38155
    
    PCM is major league broken.
    
    I did a reboot with no console script set to start at reboot.
    
    First time to try /sbin/console_startup gets a shared memory error.
    console -d -c showed all 0 for the PID....guess they NEVER started.
    
    I tried multiple times with console -s -y and it failed everytime.
    
    # console -s -y
    CMShm: Failed to get shared memory section
    Console Manager shutting down, Please Wait...
    
    
    I did notice that there is at least one new file in
    /var/opt/console/tmp that is a socket file called ENS_CONTROL.
    
    Here's the debug output of console_startup being run:
    Realize this is the FIRST attempt to start console manager after having
    	just rebooted the system.
    
    # /sbin/console_startup
    
    CMShm: Failed to get shared memory section
    
     Clearing out Temporary Directory
    
     Starting Console Manager Processes.
    
    POLYCENTER Console Manager
    Console Controller Daemon Version V1.6-127
    Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
    
    # CMShm: Initialize done
    CMShm: Returning HEADER record
    CMShm: Reset system count
    CMShm: Returning HEADER record
    CMShm: Set CM PID
    CMShm: Returning CM record
    CMShm: Set CM version
    CMShm: Returning CM record
    CMShm: Set CM start time
    CMShm: Returning CM record
    POLYCENTER Console Manager
    Event Notification Services Version V1.6-127
    Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
    
    console_ensd: Starting
      Event Sequencing starts at 746,1 (48889857)
    
    CMShm: Returning HEADER record
    CMShm: Mapped to section, reference count = 1
    CMShm: Set ENS start time
    CMShm: Returning ENS record
    CMShm: Set ENS PID
    CMShm: Returning ENS record
    CMShm: Reset ENS event source count
    CMShm: Returning ENS record
    CMShm: Reset ENS C3 count
    CMShm: Returning ENS record
    CMShm: Reset ENS monitor count
    CMShm: Returning ENS record
    CMShm: Reset ENS active actions count
    CMShm: Returning ENS record
    CMShm: Reset ENS despatched actions count
    CMShm: Returning ENS record
    CMShm: Reset ENS failed actions count
    CMShm: Returning ENS record
    CMShm: Set ENS version
    CMShm: Returning ENS record
    CMCreateEventListener: Creating Event listener
    </var/opt/console/tmp/CONSOLE_EVT
    _ENS>
    CMCreateEventListener: Create succeeded
    CMCreateEventListener: Creating Event listener
    </var/opt/console/tmp/CONSOLE_EVT
    _ENS_MONITOR>
    CMCreateEventPort: Opening local transport event port
    </var/opt/console/tmp/CONS
    OLE_EVT_ENS>
    CMCreateEventListener: Create succeeded
    CMCreateEventListener: Creating Event listener
    </var/opt/console/tmp/CONSOLE_EVT
    _ENS_C3>
    CMCreateEventListener: Create succeeded
    console_ensd: Event Preprocessing enabled
    CMCreateEventListener: Creating Event listener
    </var/opt/console/tmp/CONSOLE_EVT
    _ENS_PREPROCESSOR>
    CMCreateEventListener: Create succeeded
    CMCreateEventListener: Creating Event listener
    </var/opt/console/tmp/CONSOLE_EVT
    _ENS_POSTPROCESSOR>
    CMCreateEventListener: Create succeeded
    console_ensd: Establishing exit handler
    console_ensd: Establishing signal handlers
    console_ensd: Starting garbage collection at 30 second intervals
    console_ensd: Entering CMMainLoop
    console_ensd: Event port Connected - Event Source
    CMShm: Increment ENS event source count
    CMShm: Returning ENS record
    CMCreateEventPort: Open succeeded
    Console Manager shutting down at user request
    total_completion is 0, telling ens to shutdown...
    
    console_ensd: Message received via control socket
    
    console_ensd: Requesting MainLoop exit
    Waiting for ENS to exit...
    Waiting for ENS to exit...
    
    console_ensd: Message processing complete.
    
    console_ensd: Performing Exit Handler cleanup ...
    CMShutdownEventListener: Shutting down listener <ENS_MONITOR>
    CMShutdownEventListener: Shutting down listener <ENS_C3>
    CMShutdownEventListener: Shutting down listener <ENS_PREPROCESSOR>
    CMShutdownEventListener: Shutting down listener <ENS_POSTPROCESSOR>
    console_ensd: Closing Source event port  - 1073773504
    CMCloseEventPort: Closing Event Port <ENS>
    CMCloseEventPort: Closing socket associated with event port ...
                      closed.
    CMShutdownEventListener: Shutting down listener <ENS>
    CMShm: Set ENS start time
    CMShm: Returning ENS record
    CMShm: Set ENS PID
    CMShm: Returning ENS record
    CMShm: Reset ENS active actions count
    CMShm: Returning ENS record
    CMShm: Reset ENS despatched actions count
    CMShm: Returning ENS record
    CMShm: Reset ENS event source count
    CMShm: Returning ENS record
    CMShm: Set ENS version
    CMShm: Returning ENS record
    CMShm: Reference count == 0, deleting shared memory from process space
    
    console_ensd: Exiting Now!!!
    CMCloseEventPort: Closing Event Port <ENS>
    CMCloseEventPort: Closing socket associated with event port ...
                      closed.
    Parent waiting for children to exit
    Waiting for the Grim Reaper to come for them
    All children exited, continuing with shutdown...
    CMShm: Set CM version
    CMShm: Returning CM record
    CMShm: Set CM PID
    CMShm: Returning CM record
    CMShm: Set CM start time
    CMShm: Returning CM record
    CMShm: Searching for FIRST system record
    CMShm: Returning NULL record, system not found
    CMShm: Reference count == 0, deleting shared memory from process space
    
1321.3CSC32::BUTTERWORTHGun Control is a steady hand.Wed Jun 12 1996 17:158
    Bert,
      V1.6-127 isn't ECO 2! ECO 2 is V1.6-201!! V1.6-127 was a "field test"
    build of ECO 2.
    
    Is this system in the CSC?
    
    Regs,
      Dan
1321.4CSC32::B_GRUBBSWed Jun 12 1996 19:0021
    
    ok, I wiped it and went back to version 110 (eco 1).
    
    this time I did 3 things different and got it started.  It's a miracle.
    
    1) I titially disabled netview so PCM said 'no netview detected' when
    	installing
    
    2) I logged in as root instead of my regular account and su'ing to root
    	
    
    3) The first command I did was /sbin/console_startup and it failed
       I then tried console_startup restart, and it gave me a message
    	saying the word 'clean' was the only valid parameter.
    
    	I did /sbin/console_startup clean and the whole darn thing came
    	up running!
    
    	Just exactly what did 'clean' do, that couldn't be done before?
    
    
1321.5CSC32::B_GRUBBSThu Jun 13 1996 09:5211
    
    I still can't quite figure out WHAT I did to make this start working
    but it will start and stop ok everytime now.  IT had something to
    do either with the database or with 'console_startup clean'.
    
    Interestingly enough, when I look at the debug of a successful
    start there is still a message like this:
    
    CMShm: Failed to get shared memory section
    
    That must have not been the original problem.
1321.6CSC32::BUTTERWORTHGun Control is a steady hand.Thu Jun 13 1996 12:304
    Now upgrade to the real ECO 2 and see what happens. 
    
    Regs,
      Dan
1321.7CSC32::B_GRUBBSThu Jun 13 1996 13:427
    
    >> Now upgrade to the real ECO 2 and see what happens.
    
    where is it?  the reason I was using rev 127 is that was the last
    kit we had around after pcm engineering fell of the digital planet.