The open files limit is

bobyon · Post by **bobyon** » Thu Oct 03, 2013 12:02 pm

What setting is it that when changed would cause this warning to start appearing in logs.

node_Compute1: The open files limit is 10240; raising to 1048575.

A number of different changes were made recently to our grid servers and those changes resulted in the above message showing up in logs where prior to the changes the warning was not present.

I thought the setting was the ulimit -n but that has been put back to the original setting and we are still getting the warning.

Thanks,
Bob

chulett · Post by **chulett** » Thu Oct 03, 2013 12:38 pm

I'm not sure off the top of my head but if you modify a job to run "ulimit -a" as a Before Job option, then you could look for which show a current value of 10240. That should at least narrow it down if not answer the question.

bobyon · Post by **bobyon** » Thu Oct 03, 2013 12:51 pm

yup. done that.

We've got the ulimit settings back to where they were before all the changes were applied but something still is causing this message to appear in the logs.

I was quite surprised to still see the msgs in the logs after resetting the ulimit values.

abhinavagarwal · Post by **abhinavagarwal** » Fri Oct 04, 2013 9:37 am

Hi Bob...

While you have tried your hands on the ulimit setting already... I would like to add few more things on the same.

The user-id which is running the job, user-id which has been used to create the node directories, user-id which is used to make communication possible between the grid architecture---- I hope every user-id has ulimit set to unlimited.

Hope this help!

bobyon · Post by **bobyon** » Mon Oct 07, 2013 10:47 am

abhinavagarwal wrote:The user-id which is running the job, user-id which has been used to create the node directories, user-id which is used to make communication possible between the grid architecture---- I hope every user-id has ulimit set to unlimited.!

We only changef the ulimit setting on the ids that are used for submitting jobs. How would I determine which other ids are involved?

abhinavagarwal · Post by **abhinavagarwal** » Mon Oct 07, 2013 1:03 pm

hi Bob

Plz check -

user-id which has been used to create the node directories - this may be dsadmin id or root or any users on the box.

user-id which is used to make communication possible between the grid architecture - this may be root or may be dsadmin id.

Cheers.

ray.wurlod · Post by **ray.wurlod** » Mon Oct 07, 2013 1:53 pm

Run a job that has ExecSH as its before-job subroutine and execute the id command. The user that runs the job will appear in the job log.

You can (should) also use web console for Information Server to check the Engine credentials.