[Deploying Sakai] Switching from 2.6 to 2.7: Too many open files

[Jean-Francois Leveque]

Thank you all,

Solved this on my side while you were answering (thanks to google and 
mail archives). I've added the following lines to /etc/security/limits.conf:
sakai soft nofile 2048
sakai hard nofile 2048

I didn't go as far as Robert, but doubled from 1024 to 2048 on my test 
server which is halfway right now:

$ /usr/sbin/lsof -p 9396 | wc -l
1537

Cheers,

J-F

Matthew Jones a écrit :
> Yea, we had to do that recently as we are running 2.6 + contrib tools. 
> If you run an "lsof -p <process>" on the running Sakai process you'd see 
> that it has to keep all those jars open. We were probably really close 
> to the default 1024 limit for most OSes with this last release, 2.7 
> certainly pushed that over. Am at ~1697 locally with the extra tools 
> included.
> 
> tomcat at gemini:/home/jonespm$ lsof -p 30488 | wc
>    1697   15143  248412
> 
> Ref: http://collab.sakaiproject.org/pipermail/sakai-dev/2010-April/006887.html
> 
> -Matthew
> 
> On Fri, Sep 3, 2010 at 5:03 AM, Jean-Francois Leveque 
> <jean-francois.leveque at upmc.fr <mailto:jean-francois.leveque at upmc.fr>> 
> wrote:
> 
>     Hi all,
> 
>     Did any of you have to change system configuration on open files when
>     switching from 2.6 to 2.7?
> 
>     Cheers,
> 
>     Jean-Francois