Hi Since upgrading our Administration server to 8.5 from 6.5.6 FP3 we are getting frequent occurrences of 2 error messages.
The first is:
Warning: Cannot record event - cannot keep up with event occurrence rate!
Decrease logging levels or increase the event pool size by setting EVENT_POOL_SIZE in NOTES.INI. Default size is 10,485,760 bytes. Ma
ximum size is 104,857,600 bytes.
The logging levels are no different than they were in 6.5.6 and are not very high. I couldn’t find any references to this in the 8 or 8.5 forums, only in the 6 and 7 forums, and there seems to be some confusion over whether the levels should be set in Bytes or MB. There is currently no line in the notes.ini for evnt pool size - should I create one and if so whatt value should I use? If I restart Domino the error messages stop - but not for long!
Also getting this error
17/04/2009 16:55:28 Event: Error loading domain monitoring configuration view ‘($DDMFilters)’: Entry not found in index
-I am wondering if there is any connection between the 2 messages?
Would really appreciate any help as we cannot upgrade any more servers until we are sure this one is OK
Many thanks, Anne
Subject: “view ‘($DDMFilters)’: Entry not found in index” due to events4.nsf design being out-of-sync
When upgrading to Domino 8.5, the design of events4.nsf is refreshed from events4.ntf. The first remediation to try is to insure you’ve referencing the correct ntf, manually refresh the design of the nsf and then restart the event task.
Subject: $DMM Filters view
Hi Harry
Many thanks for your suggestions - you were correct - the template had reverted to the old 6.5 template, so have updated it and switched off replication - all other servers in domain are still on 6.5 templates. After restarting domino the $DMM view error stopped, and events started being logged in the DMM db - Also saw on consolecthat we had a memory dump programe for nserver.exe that did a memory dump every 60 mins . Have switched that to start up only so that may be the source of the event pools szie problem. Not sure why this wasn’t appearing on the log before. Well fingers crossed - thank you so much for your help, Anne
Subject: re: “Cannot record event - cannot keep up with event occurrence rate”
Perhaps the following events are also being logged:Event: Error posting event to event queue ‘EVENTLOG’: Insufficient memory - event pool is full. You can increase it’s size via the NOTES.INI setting EVENT_POOL_SIZE.
Event: Error posting event to event queue ‘PROBEMGR’: Insufficient memory - event pool is full. You can increase it’s size via the NOTES.INI setting EVENT_POOL_SIZE.
When these errors occur, you should also see the following message on the server console, which more fully explains the problem:
“Event correlation cache is full, too many Event documents in DDM.NSF for this server. You can increase the cache size by setting the EVENT_CORRELATION_POOL_SIZE setting in NOTES.INI. Default size is %,d bytes. Maximum size is %,d bytes.”
The event process on each server keeps a cache of all of the events that get logged to DDM for that server. On startup, this cache is loaded with all of the events in DDM.NSF for the given server. As new events get logged, they get added to the cache. Duplicate events get correlated in this cache.
The default size of this cache is 10 MB, max size is 100 MB, and you can tweak the size using the EVENT_CORRELATION_POOL_SIZE NOTES.INI parameter.
You can also avoid this problem by decreasing the number of events DDM is generating, or by deleting old or obsolete events in DDM.NSF for the given server. When we have seen this error in our domain, it was usually due to a misconfigured DDM probe that generated thousands of events. Fixing the probe configuration and deleting the bogus events solved the problem for us.