on Thu May 15 2008, Jonas Borgström <jonas-AT-edgewall.com> wrote:
> Emmanuel Blot wrote: >> >>> I think these errors are caused by temporary "normal" server >>> overloading. >>> The traffic on teo is ever increasing and the server is at peak hours >>> approaching max capacity. >> >> Ok, thanks for the feedback, I was wondering whether it could have >> been a regression introduced w/ 0.11. > > No I don't think so. And the memory issue we experienced earlier with > 0.11b1 is gone and the usage looks stable: > > http://www.edgewall.org/rrd/mem-day.png (lighttpd is restarted at 6AM) We haven't upgraded our Trac in some time, so we're still using a slightly older 0.11-dev, but recently we have been having regular -- often daily -- episodes where our PostgreSQL connection starts throwing File "/usr/local/lib/python2.5/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 69, in _cursor self.connection = Database.connect(conn_string, **self.options) OperationalError: FATAL: connection limit exceeded for non-superusers Obviously something is leaking DB connections. This does seem a bit familiar. -- Dave Abrahams BoostPro Computing http://www.boostpro.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
