| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Customer has the following problem, when opening the iconic map he
gets to messages windows:
1) Request from another PM not processed
%MCC-E-INSEVTPOOLMEM Insuffient event pool memory to post event
2) Unexpected condition returned to Notification FM
%MCC-E-INSEVTPOOLMEM Insuffient event pool memory to post event
DECmcc-BMS V1.2, VMS 5.5-1
Vaxstation 3100 Model 80, 72 MB of memory
Running MCC_AUDIT says his system/process is ok. We rebooted the system
now messages are not appearing.
Any Ideas where to go from here?
Steve Woestemeyer
CSC/CS
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3615.1 | same error, an answer please | EVTAI1::TRICHET | E4e5Cf3Cc6Fc4Cf6Cg5? | Mon Oct 05 1992 11:11 | 10 |
Here, DEF , Evry Headquaters , Control Center Telecom & Network
are getting exactly the same error messages at the same level.
The only difference is VMS version , which is 5.4-2
Please, Would you be great to give an input .
Thanks.
| |||||
| 3615.2 | Did you reboot, too? | TOOK::GUERTIN | It fall down, go boom | Mon Oct 05 1992 12:38 | 16 |
RE:.1
Does this mean that when you rebooted, the problem went away, (as in
.0)? It may be that a process which made a request to the event
manager for events and then was kill in a non-graceful way, and the
event manager could not flush out the unwanted events. Rebooting was
simply an industrial strength way of re-initializing the event pool.
Another less severe way is to take down MCC by exiting all processes
which are using MCC shared images and restarting them. The source of
these kinds of problems are generally users who $STOP/ID mcc processes
which are listening for events. On VMS, we rely on the exit handlers
(which do not get called on $STOPs) to tell the event manager that the
events are no longer of interest.
-Matt.
| |||||
| 3615.3 | TAke down MMC and restart it | EVTAI1::TRICHET | E4e5Cf3Cc6Fc4Cf6Cg5? | Tue Oct 06 1992 05:11 | 8 |
As explained , we took down MCC this morning;
and restarted the processes ...
And it solved the problem.
Thanks for your help.
| |||||