[Orca-users] Out of memory during request for 1016 bytes error

[Michael O'Dea]

After a bunch of tinkering, I got it running - but ended up taking the descriptors way way down, from unlimited to 1024 - it seems to be cranking along

here is that output:


$ ulimit -Ha
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        unlimited
coredump(blocks)     unlimited
nofiles(descriptors) 4096
vmemory(kbytes)      unlimited


But, now for some reason the index.html is being written as 'index.html.htm' -- it didn't before, i'll take a look in the configs...

also:
>I'm suspecting your system admin has 
>imposed a 30,000 KByte data seg size limit on your account.

I am the sysadmin -- and as far as I know I have done nothing of the sort. If anything the kernel is tuned for max user performance. 

I cleared up a few of the path related issues, I also dumped a years worth of data to speed along the process.

-m 

-----Original Message-----
From: Steve Waltner [mailto:swaltner at lsil.com]
Sent: Thursday, December 19, 2002 4:54 PM
To: orca-users at orcaware.com
Cc: Michael O'Dea
Subject: Re: [Orca-users] Out of memory during request for 1016 bytes
error


On Thursday, December 19, 2002, at 02:31 PM, Blair Zajac wrote:

> Michael O'Dea wrote:
>>
>> I bumped the limits down:
>>
>> bash-2.05$ ulimit -a
>> core file size (blocks)     0
>> data seg size (kbytes)      unlimited
>> file size (blocks)          unlimited
>> open files                  512
>> pipe size (512 bytes)       10
>> stack size (kbytes)         8192
>> cpu time (seconds)          unlimited
>> max user processes          29995
>> virtual memory (kbytes)     51200
>>
>> 512 open files -- it was 4096 before. I am still getting the errors
>
> No, no, no!!!  Wrong way!!!  You want to raise the limits.
>
> Try increasing your stack size, the pipe size and the virtual memory
> to unlimited.

What does "ulimit -Ha" display. In the output above, the system reports 
an unlimited data seg size, but I'm curious if the system hard limit 
has been set to something besides unlimited. The data seg size is the 
amount of memory that a single process can allocate. When a system 
needs a larger memory block to increase the total RAM size, it uses the 
brk() system call. Since you are getting errors with brk() system call, 
I would look at this option. I'm suspecting your system admin has 
imposed a 30,000 KByte data seg size limit on your account.

Once you get these errors related to open files and RAM usage resolved, 
I would start looking at resolving the bzip and defunct processes. I 
suspect these failures are somehow related to the process limits 
imposed on your system.

Steve