Dreamhost, Django and MySQL server connection

Does anyone else who uses Dreamhost has problems with MySQL
connection
going away?

The project I suggested hosting there is not even
inproduction yet, but
we get MySQL server errors    a lot (a few times a day).
Sometimes it's
just Django error 500, but other times I get a Python
traceback screen.

Is it just plain unlucky me and an unreliable MySQL server
on Dreamhost
or I should have used something more robust than the setup
described in
http://wi
ki.dreamhost.com/index.php/Django?

TIA,
Edgars

We've got our django project hosted over at Site5 and we
have a similar
MySQL problem: A (2006, MySQL server has gone away) error,
whenever the
site hasn't been accessed in a while. It seems to be
related to your
mysql interactive timeout setting. There's a bit of a
general
discussion about this problem here on the Site5 forums:
http://
forums.site5.com/showthread.php?t=7281

I'm not sure who's 'fault' it is, Django's for not
checking if it can
still make queries within the 'interactive session's
timelimit', or
MySQL's for closing the connection after it's interactive
timeout,
maybe you can stop it from closing an interative session at
all? If you
figure out how please let me know...

At the moment we've just asked Site5 to set out interactive
timeout a
bit higher, it means that if no one hits the site in ~5mins
the next
person to will get a 'MySQL server has gone away' error...
which they
will have to refresh but then they can browse normally...
unless they
idle for 5mins.

It would be great to get this fixed tho...

- foot

foot wrote:
> We've got our django project hosted over at Site5 and
we have a similar
> MySQL problem: A (2006, MySQL server has gone away)
error, whenever the
[snip]
> It would be great to get this fixed tho...

It was fixed 5 months ago but didn't make it to trunk.
Please try 
http://code.
djangoproject.com/ticket/463 (the new patch by nash) and
see 
if it helps you.

Thanks,

Eugene

Edgars Jekabsons wrote:
> Does anyone else who uses Dreamhost has problems with
MySQL connection
> going away?

I use Dreamhost without any problems, because I use MySQL
patch (ticket 
#463 --- http://code.
djangoproject.com/ticket/463). Please use the last 
version by nesh --- it was updated to use fair RW lock. I
have no idea 
why it didn't make to trunk yet --- I never heard complains
about the patch.

Thanks,

Eugene

Jamison Roberts wrote:
> I have nothing but problems with Dreamhost + Django. 
More specifically 
> Dreamhost + Python.  I hate that company and will be
switching as soon 
> as my year is up.

What "more specifically" was your problem with
Python?

> Can I threadjack and ask for a host recommendation?

http://code.djangoproject.com/wiki/DjangoFriendlyWebHos
ts

Thanks,

Eugene

On Mon, 13 Feb 2006 11:12:27 -0800
"Edgars Jekabsons" <edgars.jekabsonsgmail.com> wrote:

> 
> Does anyone else who uses Dreamhost has problems with
MySQL connection
> going away?
> 
> The project I suggested hosting there is not even
inproduction yet,
> but we get MySQL server errors    a lot (a few times a
day).
> Sometimes it's just Django error 500, but other times
I get a Python
> traceback screen.
> 
> Is it just plain unlucky me and an unreliable MySQL
server on
> Dreamhost or I should have used something more robust
than the setup
> described in http://wi
ki.dreamhost.com/index.php/Django?
> 
> TIA,
> Edgars
> 

I seemed to have a problem with a test environment I setup. 
But my
"main production" environment is doing better. 
I don't think it would
hurt anything to replicate your current database on a new DB
which
you setup in the Dreamhost panel.

I wrote a little ping script which requests a URL in my app
which
triggers a simple database lookup.  I run the script on a
cron job every
5 minutes on a server on my LAN at home.  Over the past 8
days, it's
only reported back 4 errors. After I got the sense to store
the
resulting error pages, it looks like one is a 500 error
(which feels
like a database problem) and one is a a URL lookup failure. 
The latter
is a little weird.  I'll try to beef up the error trapping
and
reporting when I get a chance.  

One of the reasons I did this, though, was on Dreamhost my
app is
running under fastcgi.  Since it's a low-traffic site, the
response
time for a new request after no requests have happened in a
while is
miserable.  So, this script keeps the site alive and
hopefully provides
users with a little better experience and provides
information for when
the site was having problems.  Anyway, that's not exactly
what you were
asking, but I hope it's helpful nonetheless.

- jmj