Conference azur::mcc

6447.0. "MCC_EVC_SINK logfile fills systemdisk..." by STKHLM::BERGGREN (Nils Berggren,SI Sweden 876-8287) Mon May 13 1996 22:55

Hi all,

I've a problem with the MCC_EVC_SINK logfile....
It tends to fill the system disk.  The SINK-process was restarted 
last thursday, May 9:th and today, 4 days later the logfile has 
filled 587000 blocks on the system disk.....

The customer is using the MCC_EVC_SEND program heavliy, but *NOT THAT MUCH*!

Is there any way to disable the logging from the MCC_EVC_SINK process?
The logfile is kind of useless anyway, noone checks it....

We don't want to disable the sink-process to close the file and have it 
deleted.  All their alarming depends on the sink-process being up so that the
alarms may be distributed between all their DECmcc nodes.  So disabling the 
sink could cause some distributed alarms not to come thru.


Environment is VMS V6.1, DECnet V and DECmcc V1.3.

We're not sure if can upgrade to DECmcc V1.4 since they're using the SNA-AM
and we haven't been able to get any answer from anywhere if it will work
with DECmcc V1.4...  (there's no support for that product any more, so we'll
end up trying on one of their machines to see if it works.)

	Thanks for any input.
	
	rgds,
	Nils

Some more info....

I've found that aprox half the files contains the following error-message:

    >>Error translating MCC event 3, status = 1000, <Date&Time stamp>

Doing a search in one of the logfiles gives:

$ SEARCH/STAT/WIND=0 SYS$MANAGER:MCC_EVC_SINK.LOG -
">>Error translating MCC event 3, status = 1000,"

SYS$SYSROOT:[SYSMGR]MCC_EVC_SINK.LOG;12

Files searched:                 1       Buffered I/O count:         6
Records searched:          111891       Direct I/O count:         986
Characters searched:      7483793       Page faults:               58
Records matched:            55228       Elapsed CPU time:  0 00:00:06.05
Lines printed:                  1       Elapsed time:      0 00:00:12.35

This particular logfile was created 13-MAY-1996 01:35:25.66, so it's 
been alive for aprox 22 hours which gives the rate of 1.4 error-lines/second!

No wonder the system disk gets filled up.

Now, what does this message mean?  How do I get rid of it?

	/Nils