>We're trying to get SL4NT to work on a new server but it crashes with an error that says "An error occurred in allocating a memory block of 235 bytes from the heap."
this message means that the SL4NT service ran out of available memory:
When does the crash occur? Immediately after service startup or after running for some time? I suspect that for some reasons (failure/timeout writing the received syslog messages to the action targets, like file, DB, etc.) the service queues the received messages in RAM till all RAM is used up.
- Please monitor the RAM resource usage of the SL4NT service after a new service startup: Is it continously increasing till the next crash?
- Are received syslog messages written to all the targets (file, DBs) specified in the configured actions?
- Are there any other relevant event log entries indicating a problem with a specific action target?