Can we see some code?  The description of what you're doing sounds
just fine, so that leaves open the possibility of a technical error.

On Apr 28, 7:42 am, Sam Lai <samuel....@gmail.com> wrote:
> Maybe database connections aren't closing properly? Don't know where
> to start looking though.
>
> A few weeks ago, I saw something similar (more Django and postgresql
> processes than usual, not doing anything special), but it hasn't
> happened since. Thinking about it, it happened when I was
> reindexing/updating my Whoosh database.
>
> Maybe check open pipes or sockets for the Django processes? Or any
> other open resources for those processes? I didn't really bother to
> investigate when it happened for me as it hasn't happened since, but
> seeing as it is reproducible for you, those are the things I'd take a
> look at first.
>
> On 28 April 2010 06:04, Kenneth Loafman <kenneth.loaf...@gmail.com> wrote:
>
>
>
> > Ping.  Anyone?
>
> > Kenneth Loafman wrote:
> >> Folks,
>
> >> I have a user command that runs, via cron, twice hourly with multiple
> >> threads and queues.  At the end of the run, I wait for all of the queues
> >> to empty and join all of the threads.  I close Xapian, print some log
> >> info, and delete the pid file so another instance can run.  All of this
> >> is completed (log file entries and pid file deleted), yet about 3 times
> >> a day, Django does not exit, leaving the task in memory, but idle.
>
> >> I've scratched my head over this but am getting nowhere fast.  Other
> >> than eating up memory, it does no harm as long as I go in and clean out
> >> the old tasks, but this is getting old.
>
> >> Has anyone else seen this behavior?  Any idea how to debug it?
>
> >> Environment is:
> >> Ubuntu Karmic
> >> Django 1.1.1-1ubuntu1
> >> Python 2.6
> >> MySQL 5.1
>
> >> ...Thanks,
> >> ...Ken
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Django users" group.
> > To post to this group, send email to django-us...@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > django-users+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/django-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group 
> athttp://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to