Conference csc32::consolemanager

453.0. "Notify daemon none existent process" by OPCO::TSG_SJM (Coming live to you from Rosebery) Thu Oct 27 1994 07:32

    PCM V1.5-002
    7000-620 VMS V6.1
    
    Twice now in the past week I have had PCM go into a state in which it
    doesn't respond.  Like when you attempt to connect to a console,
    nothing happens.  I have tried to connect to consoles on various
    control processes only to have the same thing happen.
    
    I then have issued the CONSOLE SHUTDOWN command, and all appears to
    shutdown successfully.  Except one (1) control process is still hanging
    around in LEF state.  I then did the STOP/ID on it, and it went away,
    which is expected.
    
    Then I tried to restart PCM, the logfile indicates successful startup
    of PCM, but PCM still will not respond.  I then looked at the console
    processes running on the system, and the Notify daemon wasn't found. 
    Attempting another shutdown fails, and when you answer YES to the
    shutdown confirmation, it just sits there and blinks at you.
    
    When I did the CONSOLE STATUS, it showed me that ENS was running, but
    the process ID shown doesn't exist on the system.  The only way to
    restart PCM has been to reboot, which is extremely inconvenient.
    
    Any thoughts on this..
    
    Cheers
    Steve

    Just did a reboot of this system, and as soon as the system was up the
    Notify and two control processes were in the RWMBX state.  After
    stopping OSCint and the PSW consolidator, PCM went on its merry way. I
    gather that this is not expected behaviour.
    
    Steve

Steve,

  Which version of OSCint are you using, we did have a problem like
  this early on which I fixed for the OSCint folks. The fix involved
  you installing the PCM ECO1 kit and a couple of extra images I
  provided to the OSCint folks. Maybe you should check with them.

Cheers,
Phil

Steve,

   Which version are you using? ($ OSCINT SHOW VERSION)
   You should use the V2.0 version which is now in the OSCINT$KIT
   directory on node AZUR. (The doc is in OSCINT$DOC)

Cheers,
Christian.
    

    Yep, using OSCint X2.0-03.  Will drop the OSCint folks a line.
    
    Thanks for help
    
    Steve