From: Claudio Nanni
Date: March 10 2009 8:08am
Subject: Re: mysql behaviour
List-Archive: http://lists.mysql.com/mysql/216653
Message-Id: <53bcf3a60903100108v48c75f23jac4816d5fd940d8a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=000e0cd3404e61cf1c0464bf40a4

--000e0cd3404e61cf1c0464bf40a4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Miguel,
I think it would also be very useful to watch the django error log,
just to be check any clue for the aborted_clients, that is clients which
connections was closed not gracefully.

De nada!

Claudio



2009/3/10 Miguel <mcm@stripped>

>  aparently, it says that the error log is in the syslog file but here I
> didnt find any errors.
>
> I will cofigure an exclusive log file for the slow connections and the
> errors.
>
> Thank you very much for your help.
>
> best regards,
> Miguel
>
>
> On Tue, 2009-03-10 at 00:41 +0100, Claudio Nanni wrote:
>
> I do not know how debian works,
> but in any case it is not even 'thinkable' a MySQL instance without
> being able to read the error log,
> you should at least be able to read MySQL server output (error log)
> before going any further.
>
> Dealing with the status you could reset the status and start monitoring
> the status variables from now on to see the behavior,
> but again, all the possible informations are needed to debug a supposed
> mysql performance issue.
>
> If you can do it, configure the exclusive error log file and restart the
> server.
>
> Cheers
>
> Claudio
>
>
> Miguel wrote:
> > i m not lucky, the server has not an exclusive error log. It is not
> > configure. It says:  Error logging goes to syslog. This is a Debian
> > improvement :)
> >
> > but I can not see anything clear in syslog.
> >
> >
> >
> >
> > On Mon, 2009-03-09 at 23:20 +0100, Claudio Nanni wrote:
> >> uld be
> >> just a Django problem (does not close correctly connections),
>
>
>
>

--000e0cd3404e61cf1c0464bf40a4--