On 5/5/06, Sander Smeenk <[EMAIL PROTECTED]> wrote:
Quoting Kishore Jalleda ([EMAIL PROTECTED]):

> >Can anyone shed any light on this issue?

> This might shed more light into your problem
> http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

I've read that :)

But still, the query returns the same data, if I run it alone, or in the
complete stats script. Please tell me (how i can find out) why the
script bails out when i run alot of other queries in front of it, and
why it works when i run just that query?

Actually none of the 'reasons' listed at the url you gave me, really
apply to my situation.

Except maybe the "You can also get these errors if you send a query to
the server that is incorrect or too large." topic. But still, explain to
me, why DOES it work when i run just that query, and why DOESN'T it work
when alot of other queries were in front of it...

What is happening is that when you start you perl script which
contains a lot of queries, you are first establishing a connection to
MySQL, and then you are running some queries, and somewhere in between
you are losing connection to the server , now when it comes to Line
695, it tries executing a query again, but the connection has gone and
the query has failed, and possibly thescript has exited.Now this means
you don't have automatic reconnection enabled in your script, if you
do then your script will try to connect to MySQL again and then get a
new connection ID and issue that query again. So I would suggest here
that you make your Perl script auotmatic reconnect aware.

After this what you really have to diagonize is why you are losing
connection to MySQL initially (i.e. at line 98)..Since this is
occuring only  intermittently I am guessing if your max_connections
limit was reached at the time the connection was lost, what are your
"wait_timeout" and "max_connections" settings, and are the initial
queries very large...

Kishore Jalleda

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to