I spent an hour trying to figure out what was going on, no luck. i ended
up restarting nginx and the problem resolved. wondering if anyone has
encountered this and knows the cause.
scenario:
1. in development mode, my pyramid app does `debug.log( "------ New Request
%s" % path )` and then a few more lines listing the params
2. i started not seeing this 'header' on a certain url.
3. inspecting thew view callable (which had a json renderer):
i. no calls to debug.log would work
ii. i could 'return' a response until i made a call to check on a
Celery result
iii. once i called out to Celery, i couldn't return a result, it just
locked up ( and no debug logs )
4. an entire url seemed to have gotten corrupted --
i. requests to this would just hang :
"/api/internal/asset/status?xid=123&asset_role=123"
ii. swapping the request params around would let the request go
through. however, still no debug logging for this specific view callable.
5. all other view callables worked fine.
i. i also use class based views, so the debugging for __init__ under
this one view would not work, but it would work for all other views in the
same class
restarting pyramid did nothing.
restarting nginx worked.
according to logs, pyramid was getting all the requests from nginx. i was
also moving the "return" statements down , line by line, to see where any
issues were happening.
i can't wrap my head around what happened. this made absolutely no sense.
just wondering if anyone else has encountered something like this.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
