Re: [uWSGI] handling large request payloads on a small number of endpoints

2018-02-14 Thread jonathan vanasco
> On Feb 14, 2018, at 1:08 PM, jonathan vanasco <uwsgi-l...@2xlp.com> wrote: > > also, it might be worth adding to the “ThinkToKnow” docs that if you’re doing > anything with oAuth against twitter or Facebook, you should increase the > buffer size. one (or more) plat

[uWSGI] handling large request payloads on a small number of endpoints

2018-02-14 Thread jonathan vanasco
we have a few HTTP endpoints that have very large request payloads (headers + query string). They’re all oAuth endpoints coming in from 3rd parties, with a bunch of header data and a super long query string. the quick fix was to double buffer-size to 8192 is this the best approach? also,

Re: [uWSGI] import error with paste-logger

2017-05-18 Thread jonathan vanasco
, pastescript and pastedeploy in my virtualenv 2. when trying to recreate your issue, I personally ran into problems with permissions of python packages. On May 18, 2017, at 1:15 AM, Gerhard Schmidt wrote: > Am 17.05.2017 um 18:52 schrieb jonathan vanasco: >> can you share the output of &q

Re: [uWSGI] import error with paste-logger

2017-05-17 Thread jonathan vanasco
can you share the output of "pip freeze"? On May 17, 2017, at 3:20 AM, Gerhard Schmidt wrote: > > Noting the ImportError I started to Google and found that i should > install PasteDeploy and PasteScript. > > After installing both and restarting i get a differen ImportError > ImportError: No

Re: [uWSGI] logging broke after a redeployment

2017-05-16 Thread jonathan vanasco
after a few hours we finally figured it out. a random package had this line in it: logging.getLogger().setLevel(logging.DEBUG) that only took... 5 hours to find after writing a few virtualenvs/services to try and replicate this. ___ uWSGI

[uWSGI] logging broke after a redeployment

2017-05-15 Thread jonathan vanasco
our logging broke after a redeployment and I can't seem to figure out what is going on. The loglevel keeps dropping to DEBUG as if nothing is configured. (it's support to be ERROR or CRITICAL) our stack looks like this: 1. supervisord invokes uwsgi

Re: [uWSGI] supervisord questions

2013-06-05 Thread Jonathan Vanasco
On Jun 4, 2013, at 8:08 PM, Alberto Scotto wrote: Well for your problem of having 15 processes, maybe you just need to have a look at processes option PS: the one I sent before was the conf for uWSGI Emperor+FastRouter managed by supervisor. And here is the the real INI conf with

[uWSGI] recommendation sought for production deployment

2013-05-30 Thread Jonathan Vanasco
Hi. I originally deployed a Pyramid app in production like this: nginx - uwsgi - pryamid uwsgi is for the app started with this `uwsgi --options` command That was great, but my needs changed as I've had to launch new applications on the same server. I'm a bit confused with all the

Re: [uWSGI] recommendation sought for production deployment

2013-05-30 Thread Jonathan Vanasco
to our stack, but hope its useful. ___ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi // Jonathan Vanasco c. 646.729.6436 | 415.501.9815 e. jonat...@2xlp.com w. http://findmeon.com/user/jvanasco linkedin

Re: [uWSGI] recommendation sought for production deployment

2013-05-30 Thread Jonathan Vanasco
On May 30, 2013, at 7:06 PM, Alberto Scotto wrote: But in your case Emperor is not enough: for managing Sentry you have to use supervisor (there isn't a uWSGI plugin for it, as far as I know), as stated in Sentry's docs:

Re: [uWSGI] uwsgi process dies when making call to (python) urllib2.open(any_url)

2012-06-13 Thread Jonathan Vanasco
On Jun 13, 2012, at 9:26 AM, Roberto De Ioris wrote: I think i have answered some hours ago on the pyramid/pylons list. Are you sure you have not enabled some memory constraint ? You have not reported the uWSGI configuration, can you post it ? Oh thank you for posting there. I see that

Re: [uWSGI] uwsgi process dies when making call to (python) urllib2.open(any_url)

2012-06-13 Thread Jonathan Vanasco
On Jun 13, 2012, at 10:10 AM, Roberto De Ioris wrote: Do you redefine/use SIGUSR1 in your app ? The worker is killed by the delivery of SIGUSR1, and this is not triggered by uWSGI Are you sure it's SIGUSR1 , and not Signal 10 ( Bus error | SIGBUS ) ? DAMN ! worker 1 (pid: