How to fix this ERROR: (8011-323-1057)?

[Bono]

It started to happen after cPanel rolled out 11.25 version of their
software. Anyone has idea how to fix it, before that everything worked
perfectly.

[Bono]

This is complete error:

ERROR: (8011-323-1057) Failed to allocate memory
DETAIL: : Cannot allocate memory

[Jeremy Aube]

Try this:

1. On profile level set the DB Memory Usage (under Profile\Storage DB)
to 'Keep all in memory' and set the DB Table limit to a value you
would normally use, such as 100,000.
2. Run profile and watch memory usage on the box. Once box starts
swapping, cancel processing and use a lower setting for DB Table
limit. Find a setting that will work without using file swap.
3. Once you've found a setting that works, check your maximum memory
allocation. That's your desired RAM size setting that you should use
for processing your kind of logs.
4. If all fails, that means there's just not enough memory on the box
for your type of logs. For example, 2 Gb may not be quite enough for
100Mb-1Gb logs. Urchin can allocate up to 2 Gb of RAM for log
processing, but don't forget about the OS itself, MySQL/PostgreSQL,
and other processes you have on the box.

Jeremy Aube
http://www.roirevolution.com/urchin

[Bono]

On Dec 21, 1:13 pm, Jeremy Aube <ja...@roirevolution.com> wrote:
> Try this:
>
> 1. On profile level set the DB Memory Usage (under Profile\Storage DB)
> to 'Keep all in memory' and set the DB Table limit to a value you
> would normally use, such as 100,000.
> 2. Run profile and watch memory usage on the box. Once box starts
> swapping, cancel processing and use a lower setting for DB Table
> limit. Find a setting that will work without using file swap.
> 3. Once you've found a setting that works, check your maximum memory
> allocation. That's your desired RAM size setting that you should use
> for processing your kind of logs.
> 4. If all fails, that means there's just not enough memory on the box
> for your type of logs. For example, 2 Gb may not be quite enough for
> 100Mb-1Gb logs. Urchin can allocate up to 2 Gb of RAM for log
> processing, but don't forget about the OS itself, MySQL/PostgreSQL,
> and other processes you have on the box.
>
> Jeremy Aubehttp://www.roirevolution.com/urchin

I suspect that is related to cpanel update and I have more than enough
memory. My DB table limit is set to 100.000 and so far I had limit at
1GB. Now I have tried to process profile with 32MB memory limit and I
get same error.

My memory status:

total used free shared buffers
cached
Mem: 4053 3835 218 0 327
2747
-/+ buffers/cache: 759 3294
Swap: 2047 209 1837

I get same error for all profiles and my biggest log i need to process
is around ~350MB and smallest is around 15MB. In total I have 5
profiles and my Urchin version is 6.601.

[Bono]

I have upgraded to latest version but this problem is still there.

Here is more info:

When trying to run profile i see this:
2046 nobody 16 0 491m 453m 964 R 79 11.2 0:00.79 urchin

and then process dies and in profile logs I got this:

[17:22:30] Logfile: /usr/local/apache/domlogs/domain.net
data lines: 0 (0%)
ERROR: (8011-577-2137) Failed to allocate memory
DETAIL: : Cannot allocate memory

[Bono]

Looks like urchin 6.602 task processor is in the loop, maybe this is
why I get error "cannot allocate memory"

[2009/12/23 02:24:25] urchind 1599: Starting Slave Scheduler
[2009/12/23 02:24:25] urchind 1599: Checking for jobs in queue
[2009/12/23 02:24:25] urchind 1599: Selecting next task in queue
[2009/12/23 02:24:30] urchind 1599: Checking for jobs in queue
[2009/12/23 02:24:30] urchind 1599: Selecting next task in queue
[2009/12/23 02:24:35] urchind 1599: Checking for jobs in queue
[2009/12/23 02:24:35] urchind 1599: Selecting next task in queue
[2009/12/23 02:24:40] urchind 1599: Checking for jobs in queue
[2009/12/23 02:24:40] urchind 1599: Selecting next task in queue
[2009/12/23 02:24:45] urchind 1599: Checking for jobs in queue
[2009/12/23 02:24:45] urchind 1599: Selecting next task in queue
[2009/12/23 02:24:50] urchind 1599: Checking for jobs in queue
[2009/12/23 02:24:50] urchind 1599: Selecting next task in queue
[2009/12/23 02:24:55] urchind 1599: Checking for jobs in queue
[2009/12/23 02:24:55] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:00] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:00] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:05] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:05] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:10] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:10] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:15] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:15] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:20] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:20] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:25] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:25] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:30] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:30] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:35] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:35] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:40] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:40] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:45] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:45] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:50] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:50] urchind 1599: Selecting next task in queue
[2009/12/23 02:25:55] urchind 1599: Checking for jobs in queue
[2009/12/23 02:25:55] urchind 1599: Selecting next task in queue
[2009/12/23 02:26:00] urchind 1599: Checking for jobs in queue
[2009/12/23 02:26:00] urchind 1599: Selecting next task in queue
[2009/12/23 02:26:05] urchind 1599: Checking for jobs in queue
[2009/12/23 02:26:05] urchind 1599: Selecting next task in queue

[Bono]

Fixed by Red Hat restart.