Re: Too Many Files Open?

I did it now and the command worked... but, the problem's still there.

The sudo lsof | grep VREG  command showed up a total of 989 opened 
files. The original limit was 1024, I raised it to 6000 and created and 
added a line to ".cshrc" file (limit descriptors 6000). Apparently 
worked fine, but eventually the problem showed up again. I repeated the 
lsof command and those old 989 opened files appeared again, checked my 
limit and was the 6000 established before.

Still on the fight... thanks!

-Carlos

On 4, Jun/2004, at 3:48 PM, Sumit Suman wrote:

> It seems you are using csh
>
> [Sumit-Sumans-Computer:~] sumit% ps
>   PID  TT  STAT      TIME COMMAND
>  3307 std  S      0:00.05 -tcsh
>
> With the above command you will know the shell you are using.
> In csh you need to use the other command.
>
> Regards,
> Sumit
>
> On Jun 4, 2004, at 1:12 PM, Carlos Maldonado wrote:
>
>> Thanks a lot list!... I'm working on it, but it seems something is 
>> not allowing me to set such limit. Pascal Robert contributed to this 
>> problem with the lsof command to check what is the number of opened 
>> files... I couldn't interpret the output.
>> With respect to the limit command I didn't find a useful "man" 
>> neither help "limit worked". Here's the output to those commands:
>>
>> [orion:~] admin% limit -S -n 6000
>> tcsh: limit: No such limit.
>> [orion:~] admin% limit
>> cputime         unlimited
>> filesize        unlimited
>> datasize        6144 kbytes
>> stacksize       8192 kbytes
>> coredumpsize    0 kbytes
>> memoryuse       unlimited
>> descriptors     1024
>> memorylocked    unlimited
>> maxproc         100
>> [orion:~] admin% lsof | grep VREG
>> COMMAND  PID  USER   FD   TYPE     DEVICE   SIZE/OFF     NODE NAME
>> lsof    4196 admin    5r  VREG       14,9    3858620   655079 
>> /mach_kernel
>>
>>
>> -Carlos
>>
>> On 4, Jun/2004, at 12:45 PM, Sumit Suman wrote:
>>
>>> It will not. By default the lower version of OS X had higher value 
>>> (probably 2000) for ulimit.
>>> In the latest ones this value is less.
>>> If your application needs to open lot more, set it to value higher 
>>> than 6000.
>>>
>>> Regards,
>>> Sumit
>>>
>>> On Jun 4, 2004, at 10:36 AM, Carlos Maldonado wrote:
>>>
>>>> But this solution is definitely?... I mean, isn't this just will 
>>>> delay the problem?... besides, I never had to do this before I did 
>>>> this server upgrade (grrr!!), I was a happy WOAdmin before, with 
>>>> jaguar 10.2.8 and WO5.2.2
>>>>
>>>> thanks anyway for your comments
>>>> -Carlos
>>>>
>>>> On 4, Jun/2004, at 12:30 PM, Sumit Suman wrote:
>>>>
>>>>> Hi Carlos,
>>>>>
>>>>> You need to set the ulimit to a higher value.
>>>>> If you are using "sh" shell use the following command. It is 
>>>>> recommended to put it in .profile in the home directory.
>>>>>
>>>>> ulimit -S -n 6000
>>>>>
>>>>> If you are using "csh" shell use the following command. It is 
>>>>> recommended to put it in .cshrc in the home directory.
>>>>>
>>>>> limit descriptors 6000
>>>>>
>>>>> This works for me.
>>>>>
>>>>> Regards,
>>>>> Sumit
>>>>>
>>>>> On Jun 3, 2004, at 3:15 PM, Carlos Maldonado wrote:
>>>>>
>>>>>> Hi list,
>>>>>>
>>>>>> I have just installed Panther server and had some problems in 
>>>>>> doing so but finally got it work. The thing is that now I have 
>>>>>> severe problems with my WO installed.
>>>>>>
>>>>>> First of all, the installer didn't upgrade because it scrambled 
>>>>>> everything and I realized by trial and error that I had to do a 
>>>>>> Software Update, some MacOSX 10.3.4 upgrade made through the 
>>>>>> SystemPreferences. When I did it, *everything* started to work 
>>>>>> fine.
>>>>>> At the next day my inbox was floded with mails saying that 
>>>>>> couldn't start my woapps because of an exception: "Too may open 
>>>>>> files". Checking the omni-list I found that there's some comments 
>>>>>> about this same problem but nothing that could help my in getting 
>>>>>> my server up and running. It keeps failing to start woapps as 
>>>>>> time passes until it gets a point where JavaMonitor can't 
>>>>>> communicate to port 1085 and even though some of my  woapps are 
>>>>>> running others are not and can't get them to start.
>>>>>>
>>>>>> I used the ServerAdmin app to change some Apache settings, like 
>>>>>> "Maximun simultaneous connections to 150 (instead of 500 as it 
>>>>>> was)", the "Maximum persistent connections to 7", "connection 
>>>>>> timeout to 300 seconds", "mininum spare servers to 3" and 
>>>>>> "maximum spare servers to 7", but didn't help a bit, I get the 
>>>>>> same behaviour from my server. I also reviewed some "conf" files 
>>>>>> even though they are named ".obsolete" and there I can see a 
>>>>>> KeepAlive variable set to Off.
>>>>>>
>>>>>> I use plain WO applications and never open or close sockets 
>>>>>> (barely heard of them), the fact is that I never used them before 
>>>>>> and all of a sudden I have to deal with them.
>>>>>>
>>>>>> I've tried also to change the opened files limit with "ulimit" 
>>>>>> but it seems is not a command by itself ("command not found").
>>>>>>
>>>>>> Is there any body there that has and solved this kind of 
>>>>>> problem?... I'm really dissapointed that the panther upgrade did 
>>>>>> this to my server, never before had to do anything about socket 
>>>>>> configuration.
>>>>>>
>>>>>>
>>>>>> -Carlos
>>>>>>
>>>>>> _______________________________________________
>>>>>> WebObjects-admin mailing list
>>>>>> [email protected]
>>>>>> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>>>>>>
>>>>> pH : +1-408-9747284
>>>>>
>>> pH : +1-408-9747284
>>>
> pH : +1-408-9747284