StopIteration Exceptions for Gevent worker

[dsoprea]

I'm getting this, every time.

This is a test project that elicits the same result (it's a simple, unexceptional project using gevent). Traditionally, I don't use gevent workers. However, I did on a recent project, though I didn't see any errors until last night (which I can't explain).

Nginx:

    upstream gevent_gunicorn_test {
        server unix:/tmp/gevent.gunicorn.sock fail_timeout=0;
    }

    server {
            server_name gevent.local;
            keepalive_timeout 5;

            location /favicon.ico {
                return 404;
            }

            location / {
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Host $http_host;
                proxy_redirect off;

                proxy_pass http://gevent_gunicorn_test;
            }
    }

Config:

bind = 'unix:/tmp/gevent.gunicorn.sock'
worker_class = 'gevent'

Code:

import web

class HandleMe(object):
    def GET(self):
        return 'xyz'

URLS = (
    '/', HandleMe,
)

app = web.application(
            URLS, 
            globals())

wsgi = app.wsgifunc()

Command-line:

$ gunicorn -c gunicorn_conf.py main:wsgi

Request:

$ curl http://gevent.local

Output:

2014-06-14 15:01:50 [42624] [INFO] Starting gunicorn 19.0.0
2014-06-14 15:01:50 [42624] [DEBUG] Arbiter booted
2014-06-14 15:01:50 [42624] [INFO] Listening at: unix:/tmp/gevent.gunicorn.sock (42624)
2014-06-14 15:01:50 [42624] [INFO] Using worker: gevent
2014-06-14 15:01:50 [42629] [INFO] Booting worker with pid: 42629
2014-06-14 15:02:16 [42629] [DEBUG] GET /
2014-06-14 15:02:16 [42629] [ERROR] Error handling request
Traceback (most recent call last):
  File "/Users/dustin/development/python/guni_gevent_test/lib/python2.7/site-packages/gunicorn/workers/async.py", line 116, in handle_request
    raise StopIteration()
StopIteration
2014-06-14 15:02:16 [42629] [DEBUG] Closing connection. 

Versions:

gevent==1.0.1
greenlet==0.4.2
gunicorn==19.0.0
web.py==0.37
wsgiref==0.1.2

I get a result back, but it's always followed-up by this exception.

[benoitc]

what is the return when you're using the --config-check setting?

[benoitc]

also the StopIteration here is normal since the request return an error. However the log should be more useful...

[dsoprea]

The request shouldn't return an error. I don't understand... I'm getting the intended string back, and it's a 200:

$ curl -v http://gevent.local
* Adding handle: conn: 0x7ffeb980d000
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7ffeb980d000) send_pipe: 1, recv_pipe: 0
* About to connect() to gevent.local port 80 (#0)
*   Trying 127.0.0.1...
* Connected to gevent.local (127.0.0.1) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.30.0
> Host: gevent.local
> Accept: */*
> 
< HTTP/1.1 200 OK
* Server nginx/1.4.7 is not blacklisted
< Server: nginx/1.4.7
< Date: Sat, 14 Jun 2014 19:25:03 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< 
* Connection #0 to host gevent.local left intact

...Why is the log indicating an error, and why am I getting back exactly what's expected if it is an error?

The "--config-check" option doesn't appear valid. It's not in the configuration documentation, and I get an error when passing as an option:

$ gunicorn --config-check -c gunicorn_conf.py main:wsgi
usage: gunicorn [OPTIONS] [APP_MODULE]
gunicorn: error: unrecognized arguments: --config-check

How am I supposed to use it?

[benoitc]

Sorry the option was --check-config like the doc said. Te fix above should fix your issue.

[dsoprea]

Everything looks fine with the config. I haven't yet tested the other PR, so the version I'm testing with hasn't changed.

$ PYTHONPATH=rpipe gunicorn --check-config -c rpipe/resources/data/gunicorn_conf_server_dev.py rpipe.app.wsgi_server:wsgi
$ echo $?
0

I'm assuming that your commit fixed it.

[benoitc]

@dsoprea can you test though? the more eyes we are the best it is :)

[dsoprea]

I just hadn't had the opportunity yet.

Later, I went back to the application that experienced it to begin with,
updated the virtualenv to point to Gunicorn master, and still saw the
StopIteration messages.

On Sun, Jun 15, 2014 at 10:59 PM, Benoit Chesneau [email protected]
wrote:

@dsoprea https://github.com/dsoprea can you test though? the more eyes
we are the best it is :)

—
Reply to this email directly or view it on GitHub
#790 (comment).

[benoitc]

I don't follow, do you mean that after fetching the last master and installing it you see the same message?

[dsoprea]

Yes.
On Jun 16, 2014 4:11 AM, "Benoit Chesneau" [email protected] wrote:

I don't follow, do you mean that after fetching the last master and
installing it you see the same message?

—
Reply to this email directly or view it on GitHub
#790 (comment).

[benoitc]

mm don't reproduce it... will recheck asap.

[flupke]

I had the same issue and the current master fixes it.

[fletom]

Having the same issue. Any idea when this fix will make it into a release on PyPI?

[benoitc]

On Mon, Jul 14, 2014 at 10:47 PM, Fletcher Tomalty <[email protected]

wrote:

Having the same issue. Any idea when this fix will make it into a release
on PyPI?

sometimes this week.

[fletom]

@benoitc Great, thanks!

[dsoprea]

Ditto. Thanks, Benoit.
On Jul 14, 2014 5:04 PM, "Fletcher Tomalty" [email protected]
wrote:

@benoitc https://github.com/benoitc Great, thanks!

—
Reply to this email directly or view it on GitHub
#790 (comment).