Reputation
1,207
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
5 6
Newest
 Yearling
Impact
~58k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
2d
awarded  Yearling
Jul
25
answered Is it possible to get uwsgi to restart on 500 errors
Mar
25
comment uWSGI reload not picking up new code changes
some note: emperor = true in the vassal file will spawn another emperor (i do not think this is what you want), tcp sockets have no permissions (so chmod/chown socket is useless), daemonization is not needed in vassals (it will be ignored) uid and gid are ignored too as the emperor already dropped privileges
Dec
15
comment uWSGI emperor spawning two processes for one application
It is the master. It is implicit when running under the Emperor as it maintains the communication/monitoring with it
Dec
11
comment uwsgi + nginx + flask: upstream prematurely closed after file is downloaded
Your uWSGI log stops before the worker is loaded (unless you did not pasted it). Are you sure you are not calling app.run() in your entry point ?
Dec
10
comment uwsgi + nginx + flask: upstream prematurely closed after file is downloaded
report uWSGI startup logs and request logs when doing the request
Nov
14
answered uWSGI writes log as root
Oct
29
answered uWSGI cannot load virtualenv
Oct
17
comment uWSGI appears to be losing requests
well, it limits the address space of the process, it may work on 32bit systems where the address space cannot raise over 2/4GB, but on 64bit systems it is very easy to use/abuse it for mmapping files or other advanced things
Oct
17
comment uWSGI appears to be losing requests
if you refer to the "seeya" entries, they are expected as you configured max-requests, but they happen after the request has been served (infact you see uWSGI logging it successfully). A part from this one, having limit-as (expecially on 64bit system) is a truly bad idea. Btw, check nginx logs, they will show for sure if some request failed.
Oct
17
comment uWSGI appears to be losing requests
Is there any reason why you think it is losing requests ?
Oct
4
comment Different Python versions under the same uwsgi Emperor?
you can follow this paragraph: uwsgi-docs.readthedocs.org/en/latest/…
Sep
12
awarded  Nice Answer
Sep
2
awarded  Yearling
Aug
26
comment uWSGI raises segfaults when defining several mount points in preforking+threaded mode
Use The Emperor, and yes you will end mounting one app per vassal. Each app will be bound to a different socket, so you need to configure nginx to route requests to each of them.
Aug
26
answered uWSGI raises segfaults when defining several mount points in preforking+threaded mode
Jul
30
answered i'm having to restart the uwsgi process
Jul
30
answered Socket error with uWSGI
Jun
20
awarded  Critic
Jun
20
answered centos + apache + uWSGI any option?