> I found the cause behind why the workers were being killed. A few
> weeks ago I added the following function in the uwsgi_utils.py file
> (see config from original post):
>
> @timer(900)
> def update_directory_visible_cache(num):
> import cPickle as pickle
>
> from django.core.cache import cache
>
> from businesses.models import Business
>
> dir_visible_list = []
> for business in Business.objects.filter(biz_status='ACTIVE'):
> if business.directory_visible:
> dir_visible_list.append(business.pk)
>
> cache.set('dir_visible_list', pickle.dumps(dir_visible_list), 1800)
>
>
> After removing this function, everything has been working perfectly
> over the last 2 days and no workers have been killed (that I can see,
> at least) in the logs. After reviewing the old logs more thoroughly,
> I noticed several lines like this:
>
> registered signal 66
> you can register max 64 timers !!!
>
> registered signal 67
> you can register max 64 timers !!!
>
> registered signal 68
> you can register max 64 timers !!!
>
> etc etc..
This condition should raise a python exception:
ValueError("unable to add timer")
can you check if it is raised ? (you should see the message in the logs
soon after the "you can register max 64 timers !!!" error)
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
