| QAR # Status Sev Category Component Date in Date out
----- ------ --- -------- -------------- ------------ -------------
00486 AK M SG DECNET_IV 28-SEP-1992 1-OCT-1992
MCC_DNA4_EVL DIES OCCASIONALLY
Reproducible at will: N
CPU Memory System device
VAXSTATION 32MB RZ24
Once in a while the MCC DNA4 event logger process dies. Here is the
log file:
$! TXNET::SYS$MANAGER:SYLOGIN.COM - System-wide login command file
$! Modification history comments are at the bottom
$!
Declared network object MCC_DNA4_EVL,25-SEP-1992 14:51:57.43
Wait for EVL link,25-SEP-1992 14:51:57.44
Connected to EVL,25-SEP-1992 14:59:33.11
Terminated mcc_dna4_evl_main,28-SEP-1992 08:15:20.52
%ERF-W-NOMSG, Message number 00089C68
SYSTEM job terminated at 28-SEP-1992 08:15:21.62
Accounting information:
Buffered I/O count: 168744 Peak working set size: 2064
Direct I/O count: 54 Peak page file size: 7354
Page faults: 3158 Mounted volumes: 0
Charged CPU time: 0 00:40:20.65 Elapsed time: 2 17:23:30.58
NET>
...also - I have noticed that now I need to STOP and START LOGGING from
DECnet for the EVL process to connect to the MCC_DNA4_EVL logger. If
I don't it just waits for the EVL link to come up. Any ideas?
Bill
Answer for QAR #00486:
------ --- ------- -------
Sept-30-1992
Please check sys$manager:evl.log for any information indicating
that EVL has dropped the link to monitor mcc_dna4_evl.
mcc_dna4_evl serves as an event sink to system's EVL. It is EVL
that initiates and maintains the network connection to the sink.
EVL occasionally drops the link to local sink(s) for various reasons,
sometimes unpredictably. The monitor mcc_dna4_evl is implemented to cope
with this behavior by staying alive for five re-trials. In other words,
when the sink was dropped by EVL, it does NOT exit and dies immediately. It
waits until EVL fails to re-connect to it five times, the sink then
terminates itself. The user at this point should examine the EVL.log and
find out why EVL is not able to re-connect to the monitor. Very often the
cause is environmental, like accessibility and security.
Yes, once after the sink process terminates itself, you will have to
DISABLE and ENABLE the sink so that it makes itself known to EVL again
(by declaring a network object again).
If this problem is occuring frequently and predicably, we may need
to work together to figure out whether EVL on your system returns unexpected
status when it drops the link or whether there is any system specific
behavior that the sink can't deal with.
The engineer who works on DNA4 Access Module can be contacted at:
took::D_BALL or DTN: 226-5345.
Thank you for your feedback. Hope this helps.
Jean (took::jean_lee DTN: 226-5528)
|