Databases
StackOverflow2013
Postsdbo
POOSError: [Errno 24] Too many open files with Google App Engine Task Queues in Dev Environment
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOSError: [Errno 24] Too many open files with Google App Engine Task Queues in Dev Environment
    primarykey
    data
    text
    <p>I'm testing a Google App Engine application where I've started using task queues to process a batch job. I have a local job that seem a number of tasks in a task queue which seems to <em>create</em> a number of objects in my file system. To be clear: I'm not creating any files, the app server seems to be doing so. </p> <p>I've noticed when creating large numbers of tasks (2000+) in my development environment that at some point my jobs start failing with the following error:</p> <pre><code>&lt;body bgcolor="#f0f0f8"&gt;&lt;font color="#f0f0f8" size="-5"&gt; --&gt; &lt;body bgcolor="#f0f0f8"&gt;&lt;font color="#f0f0f8" size="-5"&gt; --&gt; --&gt; &lt;/font&gt; &lt;/font&gt; &lt;/font&gt; &lt;/script&gt; &lt;/object&gt; &lt;/blockquote&gt; &lt;/pre&gt; &lt;/table&gt; &lt;/table&gt; &lt;/table&gt; &lt;/table&gt; &lt;/table&gt; &lt;/font&gt; &lt;/font&gt; &lt;/font&gt;&lt;pre&gt;Traceback (most recent call last): File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver.py", line 3211, in _HandleRequest self._Dispatch(dispatcher, self.rfile, outfile, env_dict) File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver.py", line 3135, in _Dispatch 'request.') File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/tempfile.py", line 302, in mkstemp File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/tempfile.py", line 236, in _mkstemp_inner OSError: [Errno 24] Too many open files: '/var/folders/rm/rm1N57BDHNCyQUT2mQRTX++++TI/-Tmp-/request.QKY1gF.tmp' &lt;/pre&gt; </code></pre> <p>I'm on OS X 10.6.5 and I'm guessing it's something to do with my OS - though I can't quite wrap my head around why dev_appserver.py would open up so many file descriptors. Even if it's creating one per task won't the rate limiting prevent this problem from occurring?</p> <p>I assume this is a problem I'll only see in dev, but I wanted to ask if anyone else has seen it.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSimon
    1. USSimon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOSError: [Errno 24] Too many open files with Google App Engine Task Queues in Dev Environment
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POOSError: [Errno 24] Too many open files with Google App Engine Task Queues in Dev Environment
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POOSError: [Errno 24] Too many open files with Google App Engine Task Queues in Dev Environment
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload