Happened again today. Took a look at the blacklist. It doesn't seem to
coincide with the vassals that are having problems...
--
Harry Percival
Developer
[email protected]
PythonAnywhere - a fully browser-based Python development and hosting
environment
<http://www.pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
On 16/01/14 11:16, Roberto De Ioris wrote:
yep. What do you suggest we look for?
if the non-spawning vassals are listed, check if they are throttled or
blacklisted. As the error you reported about kill is generally generated
by bad behaving vassals i suspect you have them blacklisted
--
Harry Percival
Developer
[email protected]
PythonAnywhere - a fully browser-based Python development and hosting
environment
<http://www.pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
On 16/01/14 10:58, Roberto De Ioris wrote:
Hey all,
we're seeing a bunch of errors in the logs saying:
kill: No such process [core/emperor.c line 1682
seems the server is stuck in a loop. A couple of vassals seem unable
to
spin up, suspect it's connected.
Any ideas why that might be?
do you have the emperor stats server active ?
it should help discovering what is happening
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
