Ubuntu – uWSGI error: the master disconnected: i will kill theself. How it happened

pythonUbuntuuwsgi

error message:

uWSGI worker 5 screams: UAAAAAAH my master disconnected: i will kill myself !!!

I use uWSGI as server to hold my pyramid app on Ubuntu 12.04

Best Answer

There are tons of reasons for the master to die, normally master's death is governed by the user, but if, for some reason, it dies abruptuly, the workers have to follow him. As the worker (being a child) has no way to know what happened, you cannot expect more infos.

A common error is sending KILL to the master to reboot/destroy uWSGI, this will lead to worker being 'orphaned'. Generally master's death should be reported in logs (with a backtrace in case of memory corruption), maybe if you paste them we could find the cause.

Related Solutions

Ubuntu – way to force pid in upstart script

do not daemonize under upstart, it is not needed

Nginx – UWSGI, Django, nginx cookie issue – causes 405 Error

Ok, so it looks like increasing uwsgi buffer size to 16k has stopped the errors. I guess the django messages cookie is too large? I'm not sure which solution is best out of switching to session storage or increasing the buffer, but there you go.

My uwsgi command now looks like this:

uwsgi --master --http-socket :8082 \
      --wsgi-file /var/django/mysite/apache/live.wsgi \
      --touch-reload /var/django/mysite/apache/live.wsgi \
      --buffer-size 16384

According to the django messages docs,

Old messages are dropped if the cookie data size would exceed 4096 bytes.

So I guess it makes sense that the uwsgi buffer needs to be greater than this.

Best Answer

Related Solutions

Ubuntu – way to force pid in upstart script

Nginx – UWSGI, Django, nginx cookie issue – causes 405 Error

Related Topic