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

hcl-bot · July 5, 2004, 3:14pm

Keep getting the following message on my console:

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

I’ve already changed the EVENT_POOL_SIZE to 5.

sh ta

  Task                 Description

Database Server Perform console commands

Database Server Listen for connect requests on TCPIP

Database Server Load Monitor is idle

Database Server Database Directory Manager Cache Refresher is idle

Database Server Organization Name Cache Refresher is idle

Database Server Idle task

Database Server Perform Database Cache maintenance

Database Server Idle task

Database Server Platform Stats is idle

SMTP Server Providing service for 200.186.217.130

SMTP Server Providing service for 200.223.188.65

SMTP Server Providing service for 127.0.0.1

Router Dispatching messages

SMTP Server Listen for connect requests on TCP Port:25

SMTP Server Utility task

SMTP Server Control task

Agent Manager Executive ‘2’: Idle

Agent Manager Executive ‘3’: Idle

Agent Manager Executive ‘1’: Idle

Calendar Connector Idle

Schedule Manager Idle

Admin Process Idle

Agent Manager Idle

Directory Indexer Idle

Maps Extractor Idle

Indexer Idle

Replicator Idle

Event Monitor Idle

Strangely, HTTP doesn’t show up. If I do a “load http” it says “HTTP Server: already running”

Any ideas?

Thanks,

Daniel

hcl-bot · July 8, 2004, 10:36am

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

If got exactly the problem. EVENT_POOL_SIZE error and no HTTP Task.Setting the event pool to 5 or even higher does make a difference.

I didn’t find a solution until now and restarting the server doesn’t help.

Please inform me if you find out anything.

Thanx

hcl-bot · July 13, 2004, 9:53am

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

Hi Dennis,this problem is related to the events task, which is “configured” by events4.nsf .

What I did was to stop the events task, and rename events4.nsf to events4.old and restart Domino server. This way, Domino created a events4.nsf f/ scratch, w/o any parameters defined there. The previous events4.nsf (now events4.old) had way too much stuff configured there, and Domino was having a hard time keeping up with all the stuff to log.

You could delete the docs in events4.nsf but we decided no to because this is an “emergency” situation and I want to eventually have a look at the old config to better “tune” it.

Hope this helps.

Best Regards,

Daniel

hcl-bot · August 18, 2004, 3:19am

Subject: 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:

Stop the Domino server
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)
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