http://blog.gmane.org/gmane.comp.python.wsgi.uwsgi.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3685 <pre>Hello, check if __sun__ and __APPLE__ are actually defined and not what they are defined to. thanks, riccardo _______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Riccardo Magliocchetti 2012-05-24T18:12:58 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3684 <pre>Hello, check if __sun__ and __APPLE__ are actually defined and not what they are defined to. thanks, riccardo </pre> Riccardo Magliocchetti 2012-05-24T18:12:12 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3682 <pre>With rev 2228 [1] carbon stats for workers can be skipped, it works fine but using this option also disables total rss size, vsz size and avg response time metrics that are calculated by iterating per worker stats. I've made a quick patch, please take a look at it. [1] - http://projects.unbit.it/uwsgi/changeset/ebde5e6b88cdc590e3b9c53cc2a65709117d8acb Łukasz Mierzwa_______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Łukasz Mierzwa 2012-05-24T13:00:36 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3673 <pre>Howdy, I am just learning how to use uwsgi and have a sample django application running under Nginx. I am running from an Upstart script on Ubuntu. My Upstart script I lifted from the web from Jeremy Bowers: description "uWSGI server for Project Foo" start on runlevel [2345] stop on runlevel [!2345] respawn exec /usr/sbin/uwsgi --socket /opt/run/foo.sock\ --chmod-socket --module wsgi_app\ --pythonpath /opt/django-projects/foo/uwsgi\ -p 1 Notice "-p 1" I believe this should give me one process, which in fact it does. I know this from the output of "ps -A |grep uwsgi" But if I add the flag --daemonize /opt/log/uwsgi/uwsgi.log And then run "ps -A|grep uwsgi" I have ten processes running. I assume this a feature, not a bug. So how do I control the number of processes running in daemonize mode? Thanks, Danny _______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Shevitz, Daniel W 2012-05-23T21:48:47 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3664 <pre>Someone going to europython 2012 on July ? </pre> Roberto De Ioris 2012-05-23T18:27:24 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3662 <pre>HI: The site error log information, I ask why? May 23 16:55:39 www tool.com: no mem for new parser May 23 16:55:43 www tool.com: SDS: Out Of Memory (SDS_ABORT_ON_OOM defined) </pre> 林刚 2012-05-23T09:19:07 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3656 <pre>Hello, the logs may say read() when recvmsg() was called instead. Not a big deal but still. :) cheers, riccardo _______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Riccardo Magliocchetti 2012-05-22T17:51:51 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3654 <pre>Hello. I just run into issue with uwsgi 1.2.3 When i do start_response() with status code "302 Found" and header [('Connection', 'close'), ('Content-Type', 'text/html'), ('Location', 'http://ru.wikipedia.org/wiki/IPad')] and then uwsgi.disconnect() after that nginx says 502 and spits out to error log: 2012/05/22 16:38:12 [error] 54019#0: *132735 upstream prematurely closed connection while reading response header from upstream, client: 81.19.90.149, server: localhost, request: "GET /cl?rex=0317D303E1FD2880&amp;block=serp&amp;st=1337690100&amp;id=title_2&amp;rnd=0.9527389095164835&amp;_URL=http%3A//ru.wikipedia.org/wiki/IPad&amp;yid=1337690100161757-1049739571324732019445193-4-009-XML&amp;ruid=0000001D4F7D452C7D2C470D00000201 HTTP/1.1", upstream: "uwsgi://unix:/var/run/uwsgi_hypernova.sock:", host: "....ru", referrer: "http://....ru/serp?query=ipad" Same application works ok with uwsgi 1.1.2. Sysinfo: FreeBSD 8.1-20100727-SNAP Python 2.7.2 nginx/1.1.16 </pre> Evgeny Turnaev 2012-05-22T12:49:05 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3647 <pre>I've left cron running every minute for whole week and it seems that it managed to eat all of some resources leaving all of my apps dying all the time: pthread_create(): Resource temporarily unavailable [protocol.c line 1981] DAMN ! worker 1 (pid: 2) died :( trying respawn ... Respawned uWSGI worker 1 (new pid: 3) pthread_create(): Resource temporarily unavailable [protocol.c line 1981] DAMN ! worker 1 (pid: 3) died :( trying respawn ... Respawned uWSGI worker 1 (new pid: 4) pthread_create(): Resource temporarily unavailable [protocol.c line 1981] DAMN ! worker 1 (pid: 4) died :( trying respawn ... Respawned uWSGI worker 1 (new pid: 5) pthread_create(): Resource temporarily unavailable [protocol.c line 1981] [...] I also noticed those messages: fork(): Resource temporarily unavailable [master_utils.c line 507] waitpid(): No child processes [master.c line 786] something horrible happened... ...brutally killing workers... pthread_create(): Resource temporarily unavailable [master.c line 411] falling back to non-threaded logger... OVERLOAD !!! unable to offload static file serving I see that I have ~8k zombie processes: www-data 1228 0.0 0.0 0 0 ? Zs 16:09 0:00 [sh] &lt;defunct&gt; And those look like cron command leftovers. I've changed cron command to "date" (I case it was my cron script issue) but after a while I see those zombie processes again. Any hints on how to debug it? Łukasz Mierzwa _______________________________________________ uWSGI mailing list uWSGI&lt; at &gt;lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Łukasz Mierzwa 2012-05-21T14:36:10 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3644 <pre> http://projects.unbit.it/uwsgi/wiki/CustomOptions Feel free to add your ideas/implementations (with credits if you want) to the wiki page </pre> Roberto De Ioris 2012-05-19T09:36:46 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3638 <pre>hello i have this configuration [program:lab] command=/usr/local/bin/uwsgi --socket /home/ubuntu/xxx/lab/lab.sock --pythonpath /home/ubuntu/xxx/lab --master --processes 2 --module juego.deploy_wsgi --socket-timeout 18000 --listen 64 --post-buffering 16384 --disable-logging --max-requests 100 directory=/home/ubuntu/DJANGO/lab user=ubuntu master = 1 autostart=true autorestart=true stdout_logfile=/home/ubuntu/xxx/lab/lab.log redirect_stderr=true stopsignal=QUIT but i have many 502 every time helpme i dont not understand _______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> soporte-9PeQ6qt8bjlpjwWnsQnGQEEOCMrvLtNR< at >public.gmane.org 2012-05-18T19:13:10 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3637 <pre>environments: ubuntu 12.04 server LTS python 2.7 uwsgi 1.2.3 web.py use --limit-as 128 start uwsgi: $ uwsgi -x /etc/uwsgi/apps-enabled/app.xml --limit-as 128 [uWSGI] parsing config file /etc/uwsgi/apps-enabled/shuofr.xml *** Starting uWSGI 1.2.3 (64bit) on [Fri May 18 07:03:00 2012] *** compiled with version: 4.6.3 on 18 May 2012 06:51:07 ... ... ... spawned uWSGI master process (pid: 29231) spawned uWSGI worker 1 (pid: 29232, cores: 1) spawned uWSGI worker 2 (pid: 29233, cores: 1) spawned uWSGI worker 3 (pid: 29234, cores: 1) libgcc_s.so.1 must be installed for pthread_cancel to work &lt;-- got error on here. DAMN ! worker 1 (pid: 29232) died, killed by signal 6 :( trying respawn ... Respawned uWSGI worker 1 (new pid: 29237) ^CSIGINT/SIGQUIT received...killing workers... goodbye to uWSGI. i was installed libgcc_s.so.1. $ ldd /usr/local/bin/uwsgi linux-vdso.so.1 =&gt; (0x00007fff018ab000) libpthread.so.0 =&gt; /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f982c8f5000) libm.so.6 =&gt; /lib/x86_64-linux-gnu/libm.so.6 (0x00007f982c5fb000) libdl.so.2 =&gt; /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f982c3f6000) libxml2.so.2 =&gt; /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007f982c09b000) libpython2.7.so.1.0 =&gt; /usr/lib/libpython2.7.so.1.0 (0x00007f982bb9e000) libc.so.6 =&gt; /lib/x86_64-linux-gnu/libc.so.6 (0x00007f982b7e0000) /lib64/ld-linux-x86-64.so.2 (0x00007f982cb1a000) libz.so.1 =&gt; /usr/local/lib/libz.so.1 (0x00007f982b5c7000) libssl.so.1.0.0 =&gt; /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f982b36b000) libcrypto.so.1.0.0 =&gt; /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f982afa2000) libutil.so.1 =&gt; /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f982ad9f000) libgcc_s.so.1 =&gt; /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f982ab89000) &lt;--- installed libgcc_s.so.1 how about it? </pre> 树上 2012-05-18T07:50:26 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3628 <pre>With this [1] commit we are one step closer to get rid of nginx and use only uWSGI for HTTP(S) stack. If You need ideas for 1.4 roadmap I propose to add tcp router [2] (so that requests are forwarded as plain packets) and SSL support for workers (with SSL sessions stored in memcached/redis). So that SSL would be handled by backend servers and we can scale it up if needed, doing HTTPS on the load balancer is fast and simple solution to deploy, but You can't scale that easily. If You do that on the backend side it basically becomes free, with fastrouter it's very easy to add new node when needed. [1] http://projects.unbit.it/uwsgi/changeset/b809f3abed28fce816428a0ed8cb9d73bba752c7 [2] or let haproxy do it since it's fast, solid and mature, but fastrouter is just to much fun since You don't need to touch any configuration, would it be hard to make fastrouter talk to haproxy and configure backends for it? I think someone already talked about this idea on this mailing list </pre> Łukasz Mierzwa 2012-05-16T17:51:20 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3626 <pre>Is there a way to pass interpreter flags like -3 or -B to the interpreter(s) launched by uWSGI? pyargv seems to pass application vars, not interpreter flags. Thanks! Craig Younkins _______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Craig Younkins 2012-05-16T00:22:55 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3624 <pre>Hi all, We've been bitten in the past by dev/alpha uWSGI versions going into PyPI, and have since pinned a specific version where applicable. However, last week, v1.0.4 disappeared [1], and 404s with "Environment not found". During the rapid-fire 1.2.1, 1.2.2, 1.2.3 release cycle, 1.2.2 has also been made unavailable. Would it be possible to avoid this? It can be quite disruptive, especially because PyPI still lists these versions as being available. [2] (Yes, our cardinal sin of external dependancies in the deploy-cycle is being resolved.) Thanks. -Seamus [1] Expected at http://projects.unbit.it/downloads/uwsgi-1.0.4.tar.gz, now at http://projects.unbit.it/downloads/old/uwsgi-1.0.4.tar.gz _______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Seamus Lawson 2012-05-14T17:12:09 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3621 <pre> Hi everyone, a new maintainance release for uWSGI 1.2 is available. Changelog [20120514] - improved fileno() detection in PSGI responses - implemented psgix.logger facility - nodes are now unsubscribed on suspend (and resubscribed on resume) - improved uwsgi.sendfile() and wsgi.file_wrapper (the second one had a bug in 1.2.2 too) - exceptions are correctly reported in PSGI while a stacktrace is in place - the uwsgi signal framework can now be used in plain async mode - fixed a rack.input read() potential bug - improved async mode on non-linux systems Users of 1.2 tree are encouraged to upgrade. You can download it from http://projects.unbit.it/downloads/uwsgi-1.2.3.tar.gz or use the istaller with the wanted profile and destination path curl http://uwsgi.it/install | bash -s default /usr/bin/uwsgi curl http://uwsgi.it/install | bash -s psgi /usr/bin/uwsgi curl http://uwsgi.it/install | bash -s rack /usr/bin/uwsgi curl http://uwsgi.it/install | bash -s gevent /usr/bin/uwsgi ...and so on... </pre> Roberto De Ioris 2012-05-14T06:12:57 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3620 <pre>Hi Roberto, It would seem that if New Relic becomes unavailable for whatever reason, all UWSGI processes will hang and fail. Please see the following logs. Any suggestions?? Cheers Cal ---- ERROR:newrelic.core.application:Data harvest failed. Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/newrelic-1.1.0. 192-py2.6.egg/newrelic/core/application.py", line 212, in harvest connection, stats.metric_data()) File "/usr/local/lib/python2.6/dist-packages/newrelic-1.1.0. 192-py2.6.egg/newrelic/core/remote.py", line 122, in send_metric_data res = self.invoke_remote(conn,"metric_data",True,self._agent_ run_id,self._agent_run_id,self._metric_data_time,now,metric_data) File "/usr/local/lib/python2.6/dist-packages/newrelic-1.1.0. 192-py2.6.egg/newrelic/core/remote.py", line 156, in invoke_remote return self._remote.invoke_remote(connection, method, compress, agent_run_id, *args) File "/usr/local/lib/python2.6/dist-packages/newrelic-1.1.0. 192-py2.6.egg/newrelic/core/remote.py", line 270, in invoke_remote raise Exception("%s failed: status code %i" % (method, response.status)) Exception: metric_data failed: status code 415 Sun May 13 19:13:15 2012 - writev(): Broken pipe [proto/uwsgi.c line 120] during GET /photos/3366 (71.198.10.132) Sun May 13 19:13:15 2012 - write(): Broken pipe [proto/uwsgi.c line 138] during GET /photos/3366 (71.198.10.132) Sun May 13 19:13:28 2012 - ...The work of process 13599 is done. Seeya! Sun May 13 19:13:29 2012 - writev(): Broken pipe [proto/uwsgi.c line 120] during GET /videos/3379 (108.6.234.190) Sun May 13 19:13:29 2012 - write(): Broken pipe [proto/uwsgi.c line 138] during GET /videos/3379 (108.6.234.190) Sun May 13 19:13:29 2012 - Respawned uWSGI worker 1 (new pid: 9003) INFO:newrelic.core.remote:New Relic Data Collector ( collector-7.newrelic.com:80 &lt;http://collector-7.newrelic.com/&gt;) Sun May 13 19:13:53 2012 - writev(): Broken pipe [proto/uwsgi.c line 120] during GET /videos/4644 (173.70.178.205) Sun May 13 19:14:10 2012 - writev(): Broken pipe [proto/uwsgi.c line 120] during GET /videos/3578 (108.6.234.190) Sun May 13 19:14:10 2012 - write(): Broken pipe [proto/uwsgi.c line 138] during GET /videos/3578 (108.6.234.190) Sun May 13 19:16:58 2012 - ...The work of process 19706 is done. Seeya! Sun May 13 19:16:59 2012 - Respawned uWSGI worker 4 (new pid: 31356) _______________________________________________ uWSGI mailing list uWSGI-FfzAktRlpg7/cILp9QSAqw&lt; at &gt;public.gmane.org http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi </pre> Cal Leeming [Simplicity Media Ltd] 2012-05-13T19:08:12 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3615 <pre>HI: There are a lot of logs, can not be canceled or integration? A log in syslog is divided into many lines, the possibility of a log in syslog into a convenient log viewer May 12 10:54:44 www com: spawned uWSGI worker 5 (pid: 4877, cores: 1) May 12 10:54:44 www com: set cpu affinity for worker 5 to May 12 10:54:44 www com: 4 May 12 10:54:44 www com: spawned uWSGI worker 6 (pid: 4883, cores: 1) May 12 10:54:44 www com: set cpu affinity for worker 6 to May 12 10:54:44 www com: 5 May 12 10:54:44 www com: May 12 10:54:44 www com: spawned uWSGI worker 7 (pid: 4888, cores: 1) May 12 10:54:44 www com: set cpu affinity for worker 7 to May 12 10:54:44 www com: 6 May 12 10:54:44 www com: spawned uWSGI worker 8 (pid: 4889, cores: 1) May 12 10:54:44 www com: set cpu affinity for worker 8 to May 12 10:54:44 www com: 7 May 12 10:54:44 www com: May 12 10:54:44 www com: spawned uWSGI worker 9 (pid: 4891, cores: 1) May 12 10:54:44 www com: set cpu affinity for worker 9 to May 12 10:54:44 www com: 0 </pre> 林刚 2012-05-12T04:00:17 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3614 <pre> Sorry, i need to release an emergency update, as uWSGI 1.2.1 can corrupt http headers on some specific conditions. The new release contains the fix for --exec-as-user-atexit too Upgrade as soon as possible ! http://projects.unbit.it/downloads/uwsgi-1.2.2.tar.gz </pre> Roberto De Ioris 2012-05-11T19:09:44 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3613 <pre>Hi, I have installed the following: easy_install greenlet UWSGI_PROFILE=gevent pip install http://projects.unbit.it/downloads/uwsgi-lts.tar.gz http://gevent.googlecode.com/files/gevent-1.0b2.tar.gz My stack in bottle and nginx. I got my app the work on my local machine but on ec2 Ubuntu..when i run the below command I get the following error. Looking for way to resolve. ubuntu&lt; at &gt;ip-10-130-155-206:/tmp/gevent-1.0b2$ sudo uwsgi --loop gevent -- http :3031 --wsgi-file /home/ubuntu/workspace/rtbopsConfig/rtbServers/ rtbAsyncServers/bottleServer.py --async 10 *** Starting uWSGI 1.2.1 (64bit) on [Fri May 11 16:44:25 2012] *** compiled with version: 4.6.1 on 11 May 2012 15:33:44 detected number of CPU cores: 1 current working directory: /tmp/gevent-1.0b2 detected binary path: /usr/local/bin/uwsgi uWSGI running as root, you can use --uid/--gid/--chroot options *** WARNING: you are running uWSGI as root !!! (use the --uid flag) *** *** WARNING: you are running uWSGI without its master process manager *** your memory page size is 4096 bytes detected max file descriptor number: 100000 async fd table size: 100000 allocated 10320 bytes (10 KB) for 10 cores per worker. lock engine: pthread robust mutexes uWSGI http bound on :3031 fd 4 spawned uWSGI http 1 (pid: 16586) uwsgi socket 0 bound to TCP address 127.0.0.1:60404 (port auto- assigned) fd 3 Python version: 2.7.2+ (default, Oct 4 2011, 20:41:12) [GCC 4.6.1] *** Python threads support is disabled. You can enable it with -- enable-threads *** Python main interpreter initialized at 0x16143a0 your server socket listen backlog is limited to 100 connections *** Operational MODE: async *** WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x16143a0 pid: 16585 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI worker 1 (and the only) (pid: 16585, cores: 10) unavailable loop engine !!! </pre> David Montgomery 2012-05-11T17:12:05 http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/3612 <pre>Hello, http://projects.unbit.it/uwsgi/wiki/CachingFramework Has anyone use "expires" in uwsgi caching? Does it work for you? I don't know if I'm doing something wrong, because it does not work for me. I used "# of seconds to expire" in that func call. Then decided to check source and truly do not see that it's being used in cache.c file on reading stage. </pre> Alex Sergeyev 2012-05-11T14:09:28 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.wsgi.uwsgi.general