| 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 |
Could someone clarify the status of the ens notify lef problem reported in
several earlier notes (eg 933, 1033,1130,1211). Ie I would like to know if this
is still a known problem in 1.6 in the later ecos. From the earlier notes it
seems that this was a problem pre eco2, but have not seen anything in the
subsequent release notes about this so wonder what ecos contains fixes for
these problems.
Of course I have a customer who has just reported this problem. I would just
like to know the current status of this as I have not seen any notes on it for
a while.
Also in note 1033 the following errors are reported in the log file. Are these
part of the problem or part of normal operation..
Thanks for any help.
dave gledhill
ty CONSOLE$ENS_DAEMON.LOG;1
$!
etc ...
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
$!
etc ....
$ 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 |
|---|---|---|---|---|---|
| 1528.1 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue Apr 29 1997 13:05 | 7 | |
The fix to this problem evolved over a period of time. There were some
design flaws in the interprocess-communications code that manifested
themselves in a variety of different ways. You should install ECO 4 from
CSC32::PCM$KITS:.
Regs,
Dan
| |||||
| 1528.2 | thanks... | COMICS::GLEDHILL | Wed Apr 30 1997 17:48 | 9 | |
Thanks for the reply dan, we have the customer restoring eco 4 shortly. Can someone confirm if the error messages I mentioned are part of the problem. Thank very much. dg. | |||||
| 1528.3 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri May 02 1997 12:07 | 8 | |
The ones in the ENS daemon log were indicative of the problem. bear in
mind that you can induce those kinds of erros by doing a STOP/ID on an
action routine process, terminating your decwindows session or using the
Motif Window manager menu picks such as File->Exit. The same is
true for the messages in the CONTROLLER_xx.LOG.
Regs,
Dan
| |||||