Hi,
we have a problem with the debug toolbar. It is working fine, when the
application is run via pserve on local development machines. When running
the application using uwsgi, the debug toolbar fails quite often. Or one
could also say, it works "sometimes", which of course makes it hard to
reproduce and debug the problem. Our uwsgi command line is something like
this:
uwsgi --chdir /pack/app --socket ${SOCKET} --chmod-socket=666
/pack/app/ini/${INI}.ini
The ini section in the ini file looks like this:
[uwsgi]
master = True
processes = 2
threads = 2
lazy = True
lazy-apps = True
paste = config:%p
buffer-size = 65535
enable-threads = True
Searching Google I was not able to find anything regarding uwsig +
debugtoolbar. So either nobody is using it or we are the only ones having
problems. ;-) So my first question would be: Is somebody else using the
debug toolbar with a uwsgi hosted application? And of course the second:
Any hint what might be wrong with our settings?
As I said, it is quite hard to reproduce the problem, so I can only provide
quite vague additional details:
- I looks like some headers are messed up, when be passed to the debug
toolbar and that seems to cause problems. But I have no idea where and how
this is happening.
- I think, the problem started quite a while ago, when updating the debug
toolbar to version 2. Looks like it is an isolated application internally,
so the way it works, seems to have changed quite a lot. My guess would be,
that the way uwsgi spawns processes is messing up things. Any hint in that
direction would be very appreciated.
cheers,
Achim
--
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 https://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
