Re: [Condor-users] Trouble getting file descriptor tunings to apply to condor processes when a machine reboots

[Ian Chesal <ichesal@xxxxxxxxxxxxxxxxxx>]

Hi Lans,

Sorry for the delay -- getting this information turned out to take longer than I thought it would.

I appreciate the help. It looks like you're on to something...

On Thursday, May 19, 2011 at 4:09 PM, Lans Carstensen wrote:

So you can hand-check what limits are being set at startup by inspecting:

cat /proc/`/sbin/pidof condor_schedd`/limits

Show that on machine startup the scheduler does *not* have the proper limits applied to it. I see:

Max open files            1024                1024 files

But after the scheduler is restarted they are applied:

Max open files            32768                262144 files 

RHEL5 init scripts use "runuser" for daemons like Condor.
/etc/pam.d/runuser invokes pam_limits.so to regulate limits. So you
probably need to set your per-process limits in /etc/security/limits.conf:

condor soft nofile 65535
condor hard nofile 65535

In /etc/security/limits.conf I set:

*  soft  nofile  32768

*  hard  nofile  262144

Maybe it's the wildcards?

Thanks again for the tips and help on this one.

Regards,

- Ian

 

-- 
Ian Chesal
ichesal@xxxxxxxxxxxxxxxxxx

http://www.cyclecomputing.com/