Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Too many open files" error #100

Closed
wuyilei opened this issue Jan 14, 2016 · 7 comments
Closed

"Too many open files" error #100

wuyilei opened this issue Jan 14, 2016 · 7 comments

Comments

@wuyilei
Copy link

wuyilei commented Jan 14, 2016

when running nextflow on a grid engine cluster, always got a "too many open files" error during the middle of the running. detailed log as follows.

$ cat .command.log
finding positions of the duplicate reads in the file...
sambamba-markdup: Cannot open or create file './sambamba-pid6283-ztgh/sorted.50.bam' : Too many open files

is it possible related to nextflow?

@pditommaso
Copy link
Member

This is not directly related to nextflow. That error is reported by the sambamba-markdup tool. If you are using nextflow to launch many instances of that tool it could happen that you reached the maximum amount of files that can be opened in your system.

The easiest solution is to increase that limit with ulimit. See, for example, here http://askubuntu.com/questions/162229/how-do-i-increase-the-open-files-limit-for-a-non-root-user

@pditommaso
Copy link
Member

I'm closing the issue. Feel free to comment if you need more explanations.

@wuyilei
Copy link
Author

wuyilei commented Jan 14, 2016

unfortunately, our ulimit is set to unlimited

@pditommaso
Copy link
Member

That is weird. Are you sure you are checking that in the cluster computing
node?

@wuyilei
Copy link
Author

wuyilei commented Jan 15, 2016

i found the following link may be helpful to solve it.

biod/sambamba#177

@wuyilei
Copy link
Author

wuyilei commented Jan 15, 2016

yes, we check ulimit on every node of the cluster

@pditommaso
Copy link
Member

Yes, this confirms that it's a problem with sambamba (I mean the biod/sambamba#177 issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants