Django session cleanup gets killed

Question

I tried to cleanup my expired django sessions using ./manage.py cleanup and after hitting enter it seems to be doing something for a few seconds and then all it returns is 'killed'. I also tried running the mysql shell and navigate to that table and do 'select * from django_sessions;' and I get kicked from the shell and back to bash with the same message: 'killed'. What is wrong here? How can I debug that?

manage.py cleanup locks the database for killing the old sessions. Sometimes it does not release the database locks gracefully. Try unlocking the tables — karthikr, Sep 06 '12 at 15:41

score 1 · Accepted Answer · edited May 23 '17 at 12:20

1

It seems like something kills long running commands. This is usual sitation on shared hosting. If you are not the owner/administrator of this server, the answer should be given by the actual owner/administrator.

Maybe these answers will help you: Who "Killed" my process and why?

edited May 23 '17 at 12:20

Community

1
1

answered Sep 06 '12 at 22:07

raacer

5,302
3
27
46

thanks, indeed:kernel: Out of memory: Kill process 6652 (python) score 568 or sacrifice child – Bastian Sep 07 '12 at 08:38
Now I need to understand why the cleanup command is eating up all the resources. – Bastian Sep 07 '12 at 08:44

Django session cleanup gets killed

1 Answers1