| 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 | 
	Hi,
	OpenVMS AXP V6.1, Polycenter Console Manager V1.6 + ECO kit.
	A customer reported this problem :
		Yesterday around 4 PM no more messages(events) were
		notified. The Console Notify process stayed in LEF.
		Today around 8 AM the notification started again
		without any intervention by the customer. Below I have
		included the mail received from the customer.
	Questions:
	1) Is this a known problem ?
	2) Do I have to activate CONSOLE$DEBUG (ENS or TRUE) ?
	   What's the difference between TRUE and ALL ?
	3) Do you have a procedure to troubleshoot a LEF process on an AXP ?
	   This would be nice for the customer to get as much information
	   as possible when it comes back.
	Any help/feedback is welcome.
	Thanks in advance.
	Rgds,
	Geert
PS	This problem looks like the one reported in note 993 !
==============================================================================
The process Console Notify is there but stay with a priority of 9 and stat LEF.
No events since 11-Oct-1995 16:07.
But at 12-Oct-1995 08:20 the process Console Notify was in full speed executing
(COM) to give the events since the stop.
The information is :
PCMAXB_SYSTEM> sho proc/id=0000011F/cont
                             Process Console Notify             08:18:39
                                                                08:18:40
    State               LEF                 Working set              166
    Cur/base priority   9/4                 Virtual pages           1065
    Current PC          8008796C            CPU time       0 00:00:33.26
    Current PSL         0000001B            Direct I/O             12840
    Current user SP     7F959040            Buffered I/O           22105
    PID                 0000011F            Page faults              333
    UIC                 [SYSTEM]            Event flags         E0000001
                                                                00000000
    PCMAXB$DKA100:[CONSOLE.][IMAGES]CONSOLE$ENS_DAEMON.EXE;4
PCMAXB_SYSTEM> sho proc/id=0000011F/acc
12-OCT-1995 08:18:45.35   User: SYSTEM           Process ID:   0000011F
                          Node: PCMAXB           Process name: "Console Notify
"
Accounting information:
 Buffered I/O count:     22105  Peak working set size:       3360
 Direct I/O count:       12840  Peak virtual size:          17024
 Page faults:              333  Mounted volumes:                0
 Images activated:           1
 Elapsed CPU time:          0 00:00:33.26
 Connect time:              0 21:01:35.39
ty CONSOLE$ENS_DAEMON.LOG;1
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! For interactive processes, turn on Control T, and set the terminal type
$!
$ mode = f$mode()
$ tt_devname = f$trnlnm("TT")
$ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  -
    (f$locate("WSA",tt_devname) .ne. f$len(tt_devname))
$ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -
    (f$locate("MBA",tt_devname) .ne. f$len(tt_devname))
$ unknown_devtyp = (mode .eqs. "INTERACTIVE") .and. -
    (f$getdvi("sys$command","devtype") .eq. 0)
$!
$ if (mode .eqs. "INTERACTIVE") .and. unknown_devtyp .and. .not. -
     (session_mgr_login .or. session_detached_process)
$ endif
$!
$ if (mode .eqs. "INTERACTIVE") .and. .not. -
     (session_mgr_login .or. session_detached_process)
$ endif
$!
$! MicroVAX Support Removed from OpenVMS Alpha
$!
$! Place your site-specific LOGIN commands below
$!
$ !
$ ! Start Parent Controller process, this has child index of "0"$ !
$ DAEMON :== $CONSOLE$IMAGE:CONSOLE$ENS_DAEMON.EXE
$ DAEMON
POLYCENTER Console Manager
Event Notification Services Version V1.6-110
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket ENS_C3
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket SECURITY____001
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket MANAGER_____001
         msg2 : error 0
Error deleting Log file - CONSOLE$TMP:SECURITY____001.LOG
     errno = 98954
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket ENS_C3
         msg2 : error 0
Error deleting Log file - CONSOLE$TMP:NETWORK_____002.LOG
     errno = 98954
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket SECURITY____003
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket ENS_C3
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket ENS_C3
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket NETWORK_____002
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket ENS_C3
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket ENS_C3
         msg2 : error 0
CONSOLE$ENS_DAEMON: eventport_error Callback
    errno_val : 0
         msg1 : Read error on Local socket ENS_C3
         msg2 : error 0
ty CONSOLE$DAEMON.LOG;1
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! For interactive processes, turn on Control T, and set the terminal type
$!
$ mode = f$mode()
$ tt_devname = f$trnlnm("TT")
$ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  -
    (f$locate("WSA",tt_devname) .ne. f$len(tt_devname))
$ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -
    (f$locate("MBA",tt_devname) .ne. f$len(tt_devname))
$ unknown_devtyp = (mode .eqs. "INTERACTIVE") .and. -
    (f$getdvi("sys$command","devtype") .eq. 0)
$!
$ if (mode .eqs. "INTERACTIVE") .and. unknown_devtyp .and. .not. -
     (session_mgr_login .or. session_detached_process)
$ endif
$!
$ if (mode .eqs. "INTERACTIVE") .and. .not. -
     (session_mgr_login .or. session_detached_process)
$ endif
$!
$! MicroVAX Support Removed from OpenVMS Alpha
$!
$! Place your site-specific LOGIN commands below
$!
$ !
$ ! Start Parent Controller process, this has child index of "0"$ !
$ DAEMON :== $CONSOLE$IMAGE:CONSOLE$DAEMON.EXE
$ DAEMON
POLYCENTER Console Manager
Console Controller Daemon Version V1.6-110
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
CONSOLE$DAEMON: Termination Mailbox created (status = 1), channel = 240
CONSOLE$DAEMON: Termination Mailbox unit = 27
Read error on Local socket CONSOLE_CTRL
Read error on Local socket CONSOLE_CTRL
Read error on Local socket CONSOLE_CTRL
Read error on Local socket CONSOLE_CTRL
Read error on Local socket CONSOLE_CTRL
Read error on Local socket CONSOLE_CTRL
===============================================================================
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 1033.1 | LEF troubleshoot | 54625::WILLEMSG | Geert Willems MCS-Belgium | Fri Oct 13 1995 11:08 | 10 | 
|     
    
    	Hi,
    
    	Do I have to open an IPMT ? 
    	Can someone give advise for the CONSOLE$DEBUG (TRUE versus ALL) ?
    
    	Rgds,
    
    	Geert 
 | |||||
| 1033.2 | 29067::BUTTERWORTH | Gun Control is a steady hand. | Fri Oct 13 1995 16:21 | 42 | |
|     I'm trying Geert but theres only so much for me to go around.
    
    >       OpenVMS AXP V6.1, Polycenter Console Manager V1.6 + ECO kit.
    >       A customer reported this problem :
    >               Yesterday around 4 PM no more messages(events) were
    >               notified. The Console Notify process stayed in LEF.
    >               Today around 8 AM the notification started again
    >               without any intervention by the customer. Below I have
    >               included the mail received from the customer.
    
    Thats a new one!!
    
    >       Questions:
    >       1) Is this a known problem ?
    
    No.
    
    >       2) Do I have to activate CONSOLE$DEBUG (ENS or TRUE) ?
    
    Since I suspect a communication problem here it would be nice to
    set debug to ENS and IPC but this could consume some disk space
    if theres event a moderate amount of event going on. 
    
    >          What's the difference between TRUE and ALL ?\
    
    LOTS!! TRUE really only gets us a logfile. If you turn on ALL, there 
    will be some much debugging code turned on causing so many messages to
    be logged that the product is practically unuseable in my opinion.
    
    >       3) Do you have a procedure to troubleshoot a LEF process on an
    >AXP?
    
    It's not much different than VAX. What you need to do is use SDA to see
    what the process was doing. Once you've set your process context 
    to the process in question via SDA do a SHOW PROC/CHANNEL and 
    do a SHOW CALL followed by a couple SHOW CALL/NEXT commands.
    
    Regs,
     Dan
               This would be nice for the customer to get as much
    information
    
 | |||||
| 1033.3 | I can't believe I left that out ;-} | 29067::BUTTERWORTH | Gun Control is a steady hand. | Fri Oct 13 1995 16:21 | 1 | 
| And post the results of those commands.. | |||||
| 1033.4 | status ? | 50242::MUELLER | Mon Dec 04 1995 03:49 | 16 | |
| Hallo, is there any news on the reported problem? I experienced the same problem: process Console Notify was in state 'LEF' - no events came through. After approx. 30 Minutes the process went back to state HIB and the messages got displayed. environment: VAX/VMS V6.1 / PCM V1.6-111 / OSCint V2.1 Regards, - Sabine | |||||
| 1033.5 | 29067::BUTTERWORTH | Gun Control is a steady hand. | Tue Dec 05 1995 10:48 | 19 | |
|     Sabine,
       This problem is related to several inter-process communication
    problems that I fixed just last week. The images may be found at
    
    CSC32::DUMPS:[BUTTERWORTH.PCM]CSC_116.BCK
    
    This is not a kit but rather a saveset with the images in it. To
    restore it, use these commands:
    
    BACK/LOG CSC_116.BCK/SAVE/SEL=(CONSOLE$BROAD*.EXE,CONSOLE$EVENT*.EXE) -
       CONSOLE$ROOT:[ACTIONS.SYSTEM]/NEW
    
    BACK/LOG CSC_116.BCK/SAVE/EXCL=(CONSOLE$BROAD*.EXE,CONSOLE$EVENT*.EXE)-
       CONSOLE$IMAGE:/NEW
    
    Once restored, restart PCM.
    
    Regards,
       Dan
 | |||||
| 1033.6 | 52336::STRATMAN | Peter Stratman @VBO | Tue Dec 12 1995 04:50 | 4 | |
|     Re. .5, is this VAX or AXP. Is this patch in 111_SMG ?
    Thanks,
    Peter.
 | |||||