Cool, I've been putting off seeing if this was fixed since I last seriously ran into this problem but it's good to know I can possibly try some system-wide fix as well.
On 28 November 2011 11:22, Nathan Rusch <[email protected]> wrote: > Seems like it’s possible. Old link, but a quick search yielded this: > http://artur.hefczyc.net/node/27 > > -Nathan > > > *From:* Michael Garrett <[email protected]> > *Sent:* Monday, November 28, 2011 11:14 AM > *To:* Nuke user discussion <[email protected]> > *Subject:* Re: [Nuke-users] Too many open files > > Can you do this with bash on OS X? > > > > On 28 November 2011 02:15, Wouter Klouwen <[email protected]> wrote: > >> On Linux you can increase the amounts of file descriptors you have open >> through executing the 'ulimit -n <some large number>' in your shell before >> you open Nuke. >> Note that the command only works for the current shell session and may be >> subject to more strict system wide limitations such as those set through >> SELinux. >> If you want this to work every time you log in and bash is your shell, >> you can put the line into both .bash_profile and .bashrc in your home >> directory. >> >> HTH, >> Wouter >> >> >> On 27/11/2011 22:36, John RA Benson wrote: >> >>> Seeing this on Linux, suse 11, Nuke 6.2v1. No frameblends or holds but >>> there are frameoffsets. The write node being output has a total of 15 >>> nodes in the tree, 3 reads, 3 time offsets, 3 transforms 3 reformats, 2 >>> merges and a write. There are about 20 other reads with offsets in the >>> script, but not in the tree being written. If those are being opened >>> too, that's probably not helping, but it's still a fraction of the >>> number of reads in a lot of scripts around here. >>> >>> We see this error a lot with frameblends, but usually the scripts are >>> much bigger and there are a lot more reads. in that case the scripts die >>> on open. Amount of frames wouldn't matter. This just seemed extra >>> strange to die randomly in the middle of a render. >>> >>> Sorta glad its happening to others and not just here, only in that its >>> shared misery. Systems is going to increase my file limit tomorrow, will >>> see if it helps. I feel they shouldn't have to - the limit is there for >>> a reason, rights? Seems like Nathan is probably correct in Nuke being >>> lazy about destroying FileReader instances. >>> >>> cheers >>> jrab >>> >>> We had that with many exr type readers and timeoffsets... Removed >>>> every not necessary reads eliminated the error. But sometimes >>>> scrubbing too much the timeline got the error back. >>>> Gabor >>>> >>>> On Sun, Nov 27, 2011 at 7:35 PM, Michael Garrett >>>> <[email protected] <mailto:[email protected]>**> wrote: >>>> >>>> Do you have a bunch of FrameHolds in the script? That seems to be >>>> a catalyst for this issue popping up. >>>> >>>> >>>> On 27 November 2011 09:17, ari Rubenstein <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> I get this daily, usually when scrubbing in the viewer, or >>>> rendering a flipbook. Or hitting the arrow keys quickly >>>> stepping thru frames. >>>> >>>> Quite painful and common. Seems Nuke gets 'congested' with >>>> some temporal operations, more so then shake did in my >>>> experience. >>>> >>>> Ari >>>> >>>> Sent from my iPhone >>>> >>>> On Nov 27, 2011, at 12:10 PM, John RA Benson >>>> <[email protected] >>>> >>>> <mailto:john.benson.macguff@**gmail.com<[email protected]>>> >>>> wrote: >>>> >>>> > Hey there - >>>> > >>>> > Having some strange rendering issues: Very simple script, 3 >>>> read nodes (exr's), just a over b for each. Except it's 4488 >>>> frames long. After a thousand frames or so, the render fails: >>>> > >>>> > OSError: [Errno 24] Too many open files: >>>> '/path/to/frames.4249.exr' >>>> > >>>> > I'm not sure if this is due to nuke or the wrapper and >>>> environment that launches the render. Seems really weird. >>>> Anyone else hit a "Too many open files" after rendering for >>>> awhile? >>>> > >>>> > thanks >>>> > JRAB >>>> > ______________________________**_________________ >>>> > Nuke-users mailing list >>>> > >>>> [email protected].**co.uk<[email protected]> >>>> >>>> <mailto:Nuke-users@support.**thefoundry.co.uk<[email protected]>>, >>>> >>>> >>>> http://forums.thefoundry.co.**uk/<http://forums.thefoundry.co.uk/> >>>> > >>>> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/** >>>> nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> >>>> ______________________________**_________________ >>>> Nuke-users mailing list >>>> >>>> [email protected].**co.uk<[email protected]> >>>> >>>> <mailto:Nuke-users@support.**thefoundry.co.uk<[email protected]>>, >>>> >>>> >>>> http://forums.thefoundry.co.**uk/<http://forums.thefoundry.co.uk/> >>>> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/** >>>> nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> >>>> >>>> >>>> >>>> ______________________________**_________________ >>>> Nuke-users mailing list >>>> >>>> [email protected].**co.uk<[email protected]> >>>> >>>> <mailto:Nuke-users@support.**thefoundry.co.uk<[email protected]>>, >>>> >>>> >>>> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> >>>> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/** >>>> nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> >>>> >>>> >>>> ______________________________**_________________ >>>> Nuke-users mailing list >>>> [email protected].**co.uk<[email protected]> >>>> <mailto:Nuke-users@support.**thefoundry.co.uk<[email protected]> >>>> >, >>>> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> >>>> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> >>>> >>> >>> >>> ______________________________**_________________ >>> Nuke-users mailing list >>> [email protected].**co.uk<[email protected]>, >>> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> >>> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> >>> >> >> >> -- >> Wouter Klouwen, Software Engineer >> The Foundry, 6th Floor, Comms Building, 48 Leicester Sq, London WC2H LT >> Tel: +442079686828 • Fax: +4420 79308906 <%2B4420%2079308906> • >> thefoundry.co.uk >> The Foundry Visionmongers Ltd • Reg.d in England and Wales No: 4642027 >> >> ______________________________**_________________ >> Nuke-users mailing list >> [email protected].**co.uk<[email protected]>, >> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> >> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-users<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users> >> > > ------------------------------ > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
