Possible regression, need some assistance debugging

I am working with the amaroK team and have run into a little problem since
upgrading mysql to 5.0.18. We use mysql as one of the choices for the music
collection database, and since upgrading mysql to 5.0.18, I am getting an
error about the server having gone away after amaroK sits idle for awhile
(overnight). This is the error

"[CollectionDB] MYSQL QUERY FAILED: MySQL server has gone away"

This error appears and continues until the application is killed and
restarted. I am not sure if it is a bug or desired behavior, so I thought I
would ask here first before posting a bug.

When I RTFM, I see that there is an explanation about the wait_timeout
parameter here http://dev.mysql.com/doc/refman/5.0/en/gone-away.html I
didn't recall this behavior in 5.0.17 so I downgraded to test and after
attempting the same task, the error does appear for a second in the console,
but eventually the the query is completed successfully. So, 5.0.17 allows a
connection to be re-opened after being idle for the wait_timout period, but
5.0.18 does not.

So the question is, what changed from 5.0.17 to 5.0.18 and is this intentional
or a regression? perhaps there is some test that must be performed in amaroK
so that a new connection can be opened when the wait_timeout period is
exceeded.

The amarok bug in the KDE database is here for further information.
http://bugs.kde.org/show_bug.cgi?id=120198

--
Greg


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=23048 6&dat=121642

Re: Possible regression, need some assistance debugging

Hi!

On Jan 18, Greg Meyer wrote:
> I am working with the amaroK team and have run into a little problem
> since upgrading mysql to 5.0.18. We use mysql as one of the choices
> for the music collection database, and since upgrading mysql to
> 5.0.18, I am getting an error about the server having gone away after
> amaroK sits idle for awhile (overnight). This is the error
>
> "[CollectionDB] MYSQL QUERY FAILED: MySQL server has gone away"
>
> This error appears and continues until the application is killed and
> restarted. I am not sure if it is a bug or desired behavior, so I
> thought I would ask here first before posting a bug.
>
> When I RTFM, I see that there is an explanation about the
> wait_timeout parameter here
> http://dev.mysql.com/doc/refman/5.0/en/gone-away.html I didn't recall
> this behavior in 5.0.17 so I downgraded to test and after attempting
> the same task, the error does appear for a second in the console, but
> eventually the the query is completed successfully. So, 5.0.17 allows
> a connection to be re-opened after being idle for the wait_timout
> period, but 5.0.18 does not.
>
> So the question is, what changed from 5.0.17 to 5.0.18 and is this
> intentional or a regression? perhaps there is some test that must be
> performed in amaroK so that a new connection can be opened when the
> wait_timeout period is exceeded.

A quick look in changeset comments didn't reveal anything that woud
explain that. Please submit a bugreport at bugs.mysql.com (and try to
provide a repeatable test case :).

Regards,
Sergei

--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Kerpen, Germany
<___/ www.mysql.com

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Possible regression, need some assistance debugging

On Thursday 19 January 2006 7:34 am, Sergei Golubchik wrote:
> On Jan 18, Greg Meyer wrote:
> >
> > So the question is, what changed from 5.0.17 to 5.0.18 and is this
> > intentional or a regression? =A0perhaps there is some test that must be
> > performed in amaroK so that a new connection can be opened when the
> > wait_timeout period is exceeded.
>
> A quick look in changeset comments didn't reveal anything that woud
> explain that. Please submit a bugreport at bugs.mysql.com (and try to
> provide a repeatable test case :).

Okay, thanks for the info. I guess the thing to do then is to see if I can=
=20
find some other amarok user that also uses mysql to see if it can be=20
reproduced, or perhaps I can try to reproduce it myself on another machine=
=20
with a different Linux distro.

Extending the wait_timeout to 16 hours seems to have provided a workaround =
for=20
the problem, since when I woke up this morning, database access is working=
=20
fine. =20
=2D-=20
Greg

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org

Re: Possible regression, need some assistance debugging

If you know your application is going to sit for long periods of time
between interactions with the database it should call mysql_ping() prior
to running queries
or be prepared to reconnect and retry in the event of a lost connection.
I don't believe increasing the wait_timout is the correct solution.

Greg Meyer wrote:

>On Thursday 19 January 2006 7:34 am, Sergei Golubchik wrote:
>
>
>>On Jan 18, Greg Meyer wrote:
>>
>>
>>>So the question is, what changed from 5.0.17 to 5.0.18 and is this
>>>intentional or a regression? perhaps there is some test that must be
>>>performed in amaroK so that a new connection can be opened when the
>>>wait_timeout period is exceeded.
>>>
>>>
>>A quick look in changeset comments didn't reveal anything that woud
>>explain that. Please submit a bugreport at bugs.mysql.com (and try to
>>provide a repeatable test case :).
>>
>>
>
>Okay, thanks for the info. I guess the thing to do then is to see if I can
>find some other amarok user that also uses mysql to see if it can be
>reproduced, or perhaps I can try to reproduce it myself on another machine
>with a different Linux distro.
>
>Extending the wait_timeout to 16 hours seems to have provided a workaround for
>the problem, since when I woke up this morning, database access is working
>fine.
>
>


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org