View Single Post
Old 25th October 2013, 23:26   #45
milosz
Senior Member
 
Join Date: Apr 2006
Location: chicago
Posts: 123
It's odd, I set ulimit -n 1024000 the day before I started the new DNAS in production, it should have been OK. When I checked it after I got the errors, using ulimit -a, it showed a value of 1024. So I set ulimit -n 1024000 and then ulimit -a showed 1024000.

I just checked it now and ulimit -a shows open files as set to 1024. Something changed the value since last night.

I did ulimit -n 4096 just now, and ulimit -a showed the new value "took" - I'll check it again later see if it changes.

I wonder what is changing the value? If I can't figure it out, I can always run a cron job every 5 minutes to set ulimit -n to 4096 I guess.
milosz is offline