Warning: Cannot record event

I’m receiving the following error message on my server.

Warning: Cannot record event - cannot keep up with event occurrence rate!

The EVENT_POOL_SIZE param in NOTES.INI can be set up to 5Mb. It defaults to 3Mb.

According to the following LDD document

http://www-10.lotus.com/ldd/today.nsf/a2535b4ba6b4d13f85256c59006bd67d/6c90831bedbfb01085256d71006576b9?OpenDocument

The max setting is EVENT_POOL_SIZE=20

I’ve tried using this parameter but have not had any success. I started seeing this message with 6.02 CF1 and hoped that 6.03 would help, it has not. I’ve reviewed my log levels in notes.ini and not found anything unusual. I also don’t want to turn off events since I make use of this information. Any suggestions to stop this annoying message would be very welcome.

Subject: Possible Solution: event pool size

Lotus states, that the setting for “EVENT_POOL_SIZE” is set in MBytes as of version 6.x.

Through our tests we have established, that this is not correct (at least on Linux and AIX vers. 6.5.1/2). The setting should still be set in Bytes!

To check this, one can simply call a “tell event dump” and will be returned the size of the event pool. This will be maximum 65536 Bytes when the size is set in MBytes.

To correct this:

  1. Stop the Domino server

  2. Change the Notes.ini setting from MB to Bytes (or in config doc, but this then needs to be checked if it has been written into the Notes.ini)

  3. restart the Domino Server

To check if working correctly:

  • call the “tell event dump” - you will see that a greater size has been allocated (than 64Kb).

  • check if errors concerning event monitor log still occur. If so, increase the size (in Bytes)

I’m going to write Lotus Support as well.

Hope that helps.

Andreas Hechler

Magirus International GmbH

Stuttgart - Germany

Subject: Warning: Cannot record event

After a significant amount of trial and error, I solved the problem - I hope. These are the things that I had to do.

  1. Made sure that events4.nsf was using the latest template. DB is now called Monitoring Configuration.

  2. Made sure that any replication conflicts and other unneeded documents were removed from Monitoring Configuration.

  3. Made sure that there was only a single “Statistics Collection” document in Monitoring Configuration. (You can have multiple servers in this document.

  4. Delete statrep.nsf and restart server. StatRep.nsf will recreate it self when it is needed. Database is called Monitoring Results now.

  5. Cleaned out old V3 Stats and Events from NAB.

No guarantee, but this seems to have solved the problem. I’m fairly sure that step 4 is what solved my problem, but the other things are worth doing also.

Hope this actually helps…