Re: MySQL server has gone away

[Reindl Harald]

Am 03.04.2017 um 21:22 schrieb Mahmood N:

well, who did set it that low?


ِDon't know. Maybe the previous admin hadn't used mysql for sending emails!!


on a proper server you have a local smtpd like postfix listening on 
127.0.0.1 and hence you can send thousands of messages within seconds 
from a web-application and your local relay queues messages and try to 
deliver them by default up to 5 days


when you use a remote smtpd directly froma php application your are 
doing all wrong - what when the smtpd is not reachable or got restarted 
in the middle of sending?


how to act on a 4xx temporary error?

anything which takes more then 30 seconds needs to be fixed proper and 
then the timeout would not have been a probkem at all



On Monday, April 3, 2017 11:37 PM, Reindl Harald
 wrote:

Am 03.04.2017 um 20:41 schrieb Mahmood N:

Good news!

I changed wait_timeout=30 to wait_timeout=600 and now the error
disappears... I don't know if long_query_time=1 has effect.


well, who did set it that low?

https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_wait_timeout

http://orbisius.com/howto/web-development/change-mysqls-wait_timeout-interactive_timeout-variables/



On Monday, April 3, 2017 10:32 PM, Mahmood N > wrote:

I tested with both 5 and 1 and see the log files are empty.

I am really confused about that error and it is taking more than 2 weeks
about that!


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

Re: MySQL server has gone away

[Mahmood N]

>well, who did set it that low?
ِDon't know. Maybe the previous admin hadn't used mysql for sending emails!!
Anyway, thanks.
 Regards,
Mahmood 

On Monday, April 3, 2017 11:37 PM, Reindl Harald  
wrote:
 

 

Am 03.04.2017 um 20:41 schrieb Mahmood N:
> Good news!
>
> I changed wait_timeout=30 to wait_timeout=600 and now the error
> disappears... I don't know if long_query_time=1 has effect.

well, who did set it that low?

https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_wait_timeout

http://orbisius.com/howto/web-development/change-mysqls-wait_timeout-interactive_timeout-variables/

> On Monday, April 3, 2017 10:32 PM, Mahmood N  wrote:
> I tested with both 5 and 1 and see the log files are empty.
>
> I am really confused about that error and it is taking more than 2 weeks
> about that!

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



   

Re: MySQL server has gone away

[Reindl Harald]

Am 03.04.2017 um 20:41 schrieb Mahmood N:

Good news!

I changed wait_timeout=30 to wait_timeout=600 and now the error
disappears... I don't know if long_query_time=1 has effect.


well, who did set it that low?

https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_wait_timeout

http://orbisius.com/howto/web-development/change-mysqls-wait_timeout-interactive_timeout-variables/


On Monday, April 3, 2017 10:32 PM, Mahmood N  wrote:
I tested with both 5 and 1 and see the log files are empty.

I am really confused about that error and it is taking more than 2 weeks
about that!


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

Re: MySQL server has gone away

[Mahmood N]

Good news!
I changed wait_timeout=30 to wait_timeout=600 and now the error disappears... I 
don't know if long_query_time=1 has effect. Regards,
Mahmood 

On Monday, April 3, 2017 10:32 PM, Mahmood N  wrote:
 

 Dear reindl,
I tested with both 5 and 1 and see the log files are empty.
I am really confused about that error and it is taking more than 2 weeks about 
that!
 Regards,
Mahmood 


   

   

Re: MySQL server has gone away

[Mahmood N]

Dear reindl,
I tested with both 5 and 1 and see the log files are empty.
I am really confused about that error and it is taking more than 2 weeks about 
that!
 Regards,
Mahmood 


   

Re: MySQL server has gone away

[Reindl Harald]

Am 03.04.2017 um 19:45 schrieb Mahmood N:

So I set long_query_time=5 and restarted the service. Test the email
page again. Still the logs are empty


WTF - you had it set to 5 seconds 2 hours ago
i am out here...

Am 03.04.2017 um 18:11 schrieb Mahmood N:
> The my.conf file contains
>
> log_error=/var/log/mysql/error.log
> slow_query_log=1
> slow_query_log_file=/var/log/mysql/error_slow.log
> max_connections=200
> max_user_connections=30
> wait_timeout=30
> interactive_timeout=50
> long_query_time=5
> character-set-client-handshake = FALSE
> thread_concurrency = 8
> query_cache_size = 16M
> thread_cache_size = 8
> max_allowed_packet = 8M

"long_query_time=5" is low when you talk about 5 seconds as i remember 
in previuos posts - given that a reasonable server should be able to 
handle hunredts to thousands of requests per second anything above 1 
second is a alert sign


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

Re: MySQL server has gone away

[Mahmood N]

So I set long_query_time=5 and restarted the service. Test the email page 
again. Still the logs are empty.
 Regards,
Mahmood 


   

Re: MySQL server has gone away

[Mahmood N]

>since when is phpinfo() - the *real* active configuration be it changed 
>by some config snippet, vhost-configuration or even ini_set() - the same 
>than a random file in /etc?
Sorry I totally didn't understand that sentence... Regards,
Mahmood 


   

Re: MySQL server has gone away

[Reindl Harald]

Am 03.04.2017 um 19:26 schrieb Mahmood N:

given that a reasonable server should be able to
handle hunredts to thousands of requests per second anything above 1
second is a alert sign


Excuse me, do you mean higher values are better? I didn't understand. I
said in my posts that when I submit the email test, the refresh time for
that page is about 5 minutes.


if you think a moment you realize that lower values are better when 5 
seconds don't log any query and you have obvious slow queries



look also in phpinfo() for mysqlnd and mysql params containing "timeout"
and/or "max"


in /etc/php/7.0/apache2/php.ini I see

;mysqlnd.net_read_timeout = 31536000

Note that is comment


since when is phpinfo() - the *real* active configuration be it changed 
by some config snippet, vhost-configuration or even ini_set() - the same 
than a random file in /etc?


http://php.net/manual/en/function.phpinfo.php

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

Re: MySQL server has gone away

[Mahmood N]

>given that a reasonable server should be able to 
>handle hunredts to thousands of requests per second anything above 1 
>second is a alert sign
Excuse me, do you mean higher values are better? I didn't understand. I said in 
my posts that when I submit the email test, the refresh time for that page is 
about 5 minutes. 

>look also in phpinfo() for mysqlnd and mysql params containing "timeout" 
>and/or "max"
in /etc/php/7.0/apache2/php.ini I see
;mysqlnd.net_read_timeout = 31536000

Note that is comment.

 Regards,
Mahmood 


   

Re: MySQL server has gone away

[Reindl Harald]

Am 03.04.2017 um 18:11 schrieb Mahmood N:

The my.conf file contains

log_error=/var/log/mysql/error.log
slow_query_log=1
slow_query_log_file=/var/log/mysql/error_slow.log
max_connections=200
max_user_connections=30
wait_timeout=30
interactive_timeout=50
long_query_time=5
character-set-client-handshake = FALSE
thread_concurrency = 8
query_cache_size = 16M
thread_cache_size = 8
max_allowed_packet = 8M


"long_query_time=5" is low when you talk about 5 seconds as i remember 
in previuos posts - given that a reasonable server should be able to 
handle hunredts to thousands of requests per second anything above 1 
second is a alert sign



I restarted the mysql server (/etc/init.d/mysql restart on ubuntu) and
tested the email page one again. I again see that error message on the
browser, however, the log files are empty.


look also in phpinfo() for mysqlnd and mysql params containing "timeout" 
and/or "max"


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

Re: MySQL server has gone away

[Mahmood N]

The my.conf file contains
log_error=/var/log/mysql/error.log
slow_query_log=1
slow_query_log_file=/var/log/mysql/error_slow.log
max_connections=200
max_user_connections=30
wait_timeout=30
interactive_timeout=50
long_query_time=5
character-set-client-handshake = FALSE
thread_concurrency = 8
query_cache_size = 16M
thread_cache_size = 8
max_allowed_packet = 8M


I restarted the mysql server (/etc/init.d/mysql restart on ubuntu) and tested 
the email page one again. I again see that error message on the browser, 
however, the log files are empty.
 Regards,
Mahmood 


   

Re: MySQL server has gone away

[Reindl Harald]

Am 03.04.2017 um 17:52 schrieb Mahmood N:

Dear all,
Currently max_allowed_packet is set to 8M. That test email is simply a test 
email containing some basic information in the message body to assure that the 
email system works.
Thing that can help me is to put mysql in the debug mode in one terminal and at 
the same time, submit a test email from the browser. Then I can see what is 
going there in sql. This process is similar to sshd debug mode where I can turn 
on the ssh service in the debug mode and see what is what. Is there is any 
other option for debugging, please let me know.


The MySQL Error Log may  contain details explaining why mysqld was unable to 
stay running

If you are referring to /var/log/musql/error.log then I have to say it is empty!


Perhaps you could connect your mysql client, load the screen, then run show 
full processlist every second or so to see what queries are going on.

As I said, I know few things about mysql. Please let me know the steps to do 
that


https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html

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

Re: MySQL server has gone away

[Mahmood N]

Dear all,
Currently max_allowed_packet is set to 8M. That test email is simply a test 
email containing some basic information in the message body to assure that the 
email system works.
Thing that can help me is to put mysql in the debug mode in one terminal and at 
the same time, submit a test email from the browser. Then I can see what is 
going there in sql. This process is similar to sshd debug mode where I can turn 
on the ssh service in the debug mode and see what is what. Is there is any 
other option for debugging, please let me know.



>The MySQL Error Log may  contain details explaining why mysqld was unable to 
>stay running
If you are referring to /var/log/musql/error.log then I have to say it is empty!



>Perhaps you could connect your mysql client, load the screen, then run show 
>full processlist every second or so to see what queries are going on.
As I said, I know few things about mysql. Please let me know the steps to do 
that
 Regards,
Mahmood 
  Show original message 

   

Re: MySQL server has gone away

[shawn l.green]

On 4/3/2017 8:15 AM, Mahmood N wrote:

When I click on the submit button in Moodle and it is waiting for refresh, I 
execute the mysql command but the output is not meaningful

mahmood@ce:/var/www/html/courses$ mysql -u moodle -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 30912
Server version: 5.5.54-0ubuntu0.14.04.1 (Ubuntu)

Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show full processlist
 ->
 ->



Meanwhile using Webmin, I execute the same command for that user and see
  Output from SQL command show full processlist ..
| Id | User | Host | db | Command | Time | State | Info |
| 30912 | moodle | localhost |
  | Sleep | 42 |



I am not expert with MySQL, however as the Moodle admin I am trying to fix the 
problems.
Regards,
Mahmood



You need to consider a few possibilities,

a) Moodle didn't want to wait long enough for the query to complete (a 
Moodle Timeout) so it said "the server is not responding..."


b) Moodle sent MySQL a command that was "too large".  To protect itself 
from abuse, all MySQL instances have a configurable limit about how 
"large" a command can be. If the command is larger than this limit, the 
server rejects it and closes the connection.  (this could explain why 
the query you just attempted from Moodle is not visible in the list of 
executing commands)


c) Something is unstable in your MySQL instance. The MySQL Error Log may 
contain details explaining why mysqld was unable to stay running.  The 
angel process mysqld_safe would try to restart the server automatically 
which could explain why Moodle was only unresponsive for a short while.


Additional resources:
https://dev.mysql.com/doc/refman/5.6/en/problems.html   (in particular, 
review B.5.2)


--
Shawn Green
MySQL Senior Principal Technical Support Engineer
Oracle USA, Inc. - Integrated Cloud Applications & Platform Services
Office: Blountville, TN

Become certified in MySQL! Visit https://www.mysql.com/certification/ 
for details.


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

Re: MySQL server has gone away

[Mahmood N]

When I click on the submit button in Moodle and it is waiting for refresh, I 
execute the mysql command but the output is not meaningful

mahmood@ce:/var/www/html/courses$ mysql -u moodle -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 30912
Server version: 5.5.54-0ubuntu0.14.04.1 (Ubuntu)

Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show full processlist
    ->
    ->



Meanwhile using Webmin, I execute the same command for that user and see
 Output from SQL command show full processlist ..
| Id | User | Host | db | Command | Time | State | Info |
| 30912 | moodle | localhost | 
 | Sleep | 42 |



I am not expert with MySQL, however as the Moodle admin I am trying to fix the 
problems.
Regards,
Mahmood



   

Re: MySQL server has gone away

[Johnny Withers]

I'd suspect the underlying query is poorly designed for the amount of data
you have stored. If you have access to the mysql server you could connect
to it using any mysql client and run 'show full processlist' to see the
query as that page is trying to load. The query is probably in the 'sending
data' state and gets killed at the limit of one of the timeout variables.
This causes the application to throw that error you have.

Copy that query out, prefix it with explain and see if there are any tables
in the query where an index could be added to optimize the database for the
query.



On Mon, Apr 3, 2017 at 6:09 AM, Ken D'Ambrosio <k...@jots.org> wrote:

> Basically, it says that MySQL is not responding to queries. So it likely
> has died, or perhaps is mis-configured.
>
> On April 3, 2017 7:07:25 AM EDT, Mahmood N <nt_mahm...@yahoo.com> wrote:
> >Hi,I am using Moodle which itself uses SQL for the database. Problem is
> >that, when I run the email plugin and execute the command, the refresh
> >time of the page becomes high (in the order of 3-5 minutes) and at the
> >end, I see this message
> >Debug info: MySQL server has gone away
> >SELECT id, sid, state, userid, lastip, timecreated, timemodified FROM
> >mdl_sessions WHERE sid = ?
> >[array (
> > 0 => 'jqfbgd5b0q6e2l81bb5gb87mn3',
> >)]
> >Error code: dmlreadexceptionStack trace:
> >  - line 479 of /lib/dml/moodle_database.php: dml_read_exception thrown
> >- line 1175 of /lib/dml/mysqli_native_moodle_database.php: call to
> >moodle_database->query_end()
> >- line 1551 of /lib/dml/moodle_database.php: call to
> >mysqli_native_moodle_database->get_records_sql()
> >- line 1523 of /lib/dml/moodle_database.php: call to
> >moodle_database->get_record_sql()
> >- line 1502 of /lib/dml/moodle_database.php: call to
> >moodle_database->get_record_select()
> >- line 286 of /lib/classes/session/manager.php: call to
> >moodle_database->get_record()
> >- line 82 of /lib/classes/session/manager.php: call to
> >core\session\manager::initialise_user_session()
> >   - line 785 of /lib/setup.php: call to core\session\manager::start()
> >   - line 27 of /config.php: call to require_once()
> >   - line 30 of /index.php: call to require_once()
> >
> >
> >Although it looks like a bug in Moodle, but the guys said it is a MySQL
> >issue. I am confused about that. If you have any idea please let me
> >know. What does this error say exactly?
> >
> > Regards,
> >Mahmood
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.




-- 
-
Johnny Withers
601.209.4985
joh...@pixelated.net

Re: MySQL server has gone away

[Mahmood N]

Thanks for the quick reply. So, how can I get further information? 

Thing is that, after 5 minutes, when I refresh the page every thing is normal.
 Regards,
Mahmood 

On Monday, April 3, 2017 3:39 PM, Ken D'Ambrosio <k...@jots.org> wrote:
 

 Basically, it says that MySQL is not responding to queries. So it likely has 
died, or perhaps is mis-configured.

On April 3, 2017 7:07:25 AM EDT, Mahmood N <nt_mahm...@yahoo.com> wrote:
Hi,I am using Moodle which itself uses SQL for the database. Problem is that, 
when I run the email plugin and execute the command, the refresh time of the 
page becomes high (in the order of 3-5 minutes) and at the end, I see this 
message
Debug info: MySQL server has gone away
SELECT id, sid, state, userid, lastip, timecreated, timemodified FROM 
mdl_sessions WHERE sid = ?
[array (
 0 => 'jqfbgd5b0q6e2l81bb5gb87mn3',
)]
Error code: dmlreadexceptionStack trace:
   - line 479 of /lib/dml/moodle_database.php: dml_read_exception thrown
   - line 1175 of /lib/dml/mysqli_native_moodle_database.php: call to 
moodle_database->query_end()
   - line 1551 of /lib/dml/moodle_database.php: call to 
mysqli_native_moodle_database->get_records_sql()
   - line 1523 of /lib/dml/moodle_database.php: call to 
moodle_database->get_record_sql()
   - line 1502 of /lib/dml/moodle_database.php: call to 
moodle_database->get_record_select()
   - line 286 of /lib/classes/session/manager.php: call to 
moodle_database->get_record()
   - line 82 of /lib/classes/session/manager.php: call to 
core\session\manager::initialise_user_session()
   - line 785 of /lib/setup.php: call to core\session\manager::start()
   - line 27 of /config.php: call to require_once()
   - line 30 of /index.php: call to require_once()


Although it looks like a bug in Moodle, but the guys said it is a MySQL issue. 
I am confused about that. If you have any idea please let me know. What does 
this error say exactly?

 Regards,
Mahmood

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

   

Re: MySQL server has gone away

[Ken D'Ambrosio]

Basically, it says that MySQL is not responding to queries. So it likely has 
died, or perhaps is mis-configured.

On April 3, 2017 7:07:25 AM EDT, Mahmood N <nt_mahm...@yahoo.com> wrote:
>Hi,I am using Moodle which itself uses SQL for the database. Problem is
>that, when I run the email plugin and execute the command, the refresh
>time of the page becomes high (in the order of 3-5 minutes) and at the
>end, I see this message
>Debug info: MySQL server has gone away
>SELECT id, sid, state, userid, lastip, timecreated, timemodified FROM
>mdl_sessions WHERE sid = ?
>[array (
> 0 => 'jqfbgd5b0q6e2l81bb5gb87mn3',
>)]
>Error code: dmlreadexceptionStack trace:
>  - line 479 of /lib/dml/moodle_database.php: dml_read_exception thrown
>- line 1175 of /lib/dml/mysqli_native_moodle_database.php: call to
>moodle_database->query_end()
>- line 1551 of /lib/dml/moodle_database.php: call to
>mysqli_native_moodle_database->get_records_sql()
>- line 1523 of /lib/dml/moodle_database.php: call to
>moodle_database->get_record_sql()
>- line 1502 of /lib/dml/moodle_database.php: call to
>moodle_database->get_record_select()
>- line 286 of /lib/classes/session/manager.php: call to
>moodle_database->get_record()
>- line 82 of /lib/classes/session/manager.php: call to
>core\session\manager::initialise_user_session()
>   - line 785 of /lib/setup.php: call to core\session\manager::start()
>   - line 27 of /config.php: call to require_once()
>   - line 30 of /index.php: call to require_once()
>
>
>Although it looks like a bug in Moodle, but the guys said it is a MySQL
>issue. I am confused about that. If you have any idea please let me
>know. What does this error say exactly?
>
> Regards,
>Mahmood

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

MySQL server has gone away

[Mahmood N]

Hi,I am using Moodle which itself uses SQL for the database. Problem is that, 
when I run the email plugin and execute the command, the refresh time of the 
page becomes high (in the order of 3-5 minutes) and at the end, I see this 
message
Debug info: MySQL server has gone away
SELECT id, sid, state, userid, lastip, timecreated, timemodified FROM 
mdl_sessions WHERE sid = ?
[array (
 0 => 'jqfbgd5b0q6e2l81bb5gb87mn3',
)]
Error code: dmlreadexceptionStack trace:
   - line 479 of /lib/dml/moodle_database.php: dml_read_exception thrown
   - line 1175 of /lib/dml/mysqli_native_moodle_database.php: call to 
moodle_database->query_end()
   - line 1551 of /lib/dml/moodle_database.php: call to 
mysqli_native_moodle_database->get_records_sql()
   - line 1523 of /lib/dml/moodle_database.php: call to 
moodle_database->get_record_sql()
   - line 1502 of /lib/dml/moodle_database.php: call to 
moodle_database->get_record_select()
   - line 286 of /lib/classes/session/manager.php: call to 
moodle_database->get_record()
   - line 82 of /lib/classes/session/manager.php: call to 
core\session\manager::initialise_user_session()
   - line 785 of /lib/setup.php: call to core\session\manager::start()
   - line 27 of /config.php: call to require_once()
   - line 30 of /index.php: call to require_once()


Although it looks like a bug in Moodle, but the guys said it is a MySQL issue. 
I am confused about that. If you have any idea please let me know. What does 
this error say exactly?

 Regards,
Mahmood

Re: MySQL server has gone away

[ars k]

Hi Aveek,
I would like to suggest some points here:
You could try increasing the max allowed packets to 128MB. Though you think
16MB is enough, increasing it is not going to affect the server. It is
dynamic value, so you could revert back the changes if you feel so.
Also make sure log_warnings=2 which will give more error messages in error
log.

This is the basic step for this error, if it is not working then we should
check for other options then.

Regards,
Vinodh.k



On Fri, May 27, 2011 at 11:05 AM, Claudio Nanni claudio.na...@gmail.comwrote:

 'MySQL server has gone away'
 Can be a network problem,
 Just to increase complexity :)
  On May 26, 2011 11:03 PM, Prabhat Kumar aim.prab...@gmail.com wrote:
  I had experience with such type of error, It was due lack of resources
  available to MySql, max connections exceeds on the server.
  you can write a simple script which will grab and store output of 'show
  processlist' every min. and later you cna investigate the issue.
 
 
  On Wed, May 25, 2011 at 3:34 AM, Aveek Misra ave...@yahoo-inc.com
 wrote:
 
  Nothing in the error log or the slow query log that suggests that the
 query
  size is too large or us taking too much time to execute.
 
  Thanks
  Aveek
 
  On May 25, 2011, at 3:53 PM, Rik Wasmus wrote:
 
   failed to execute  SELECT * FROM cluster_info WHERE cluster =
  ?:
   MySQL server has gone away
  
   The error MySQL server has gone away is the error from the db
 handle.
  Can
   anyone give me any pointers on why that happens? I looked up the
   documentation in MySQL docs and the most common reason seems to be
 that
  it
   happens if the query size is very large or if there is a timeout.
 None
  of
   them seems to be a probable cause. The max_allowed_packet on the
  server
   is 16 MB and as can be seen in the query above, the query is very
 small
   and nowhere near the size limit. We also have a timeout setting
   (wait_timeout) of 10 minutes and the above query for us cannot
 possibly
   take that amount of time. In any case, given the same query, it
 executes
   correctly 99% of time (so to speak). It fails intermittently with the
   above error. What possibly could be the reason? I also looked at the
 max
   connections on the server at that time (around ~80) and it is much
 less
   than the limit we have (limit is 1000). How can I extract more
  information
   when this happens? This error message sucks since it does not tell me
  what
   exactly happened. The server version is 5.1.45.
  
   Can you access the error log of the server? That can probably shed
 more
  light
   on the issue...
   --
   Rik Wasmus
  
   --
   MySQL General Mailing List
   For list archives: http://lists.mysql.com/mysql
   To unsubscribe:
  http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com
  
 
 
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:
  http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com
 
 
 
 
  --
  Best Regards,
 
  Prabhat Kumar
  MySQL DBA
 
  My Blog: http://adminlinux.blogspot.com
  My LinkedIn: http://www.linkedin.com/in/profileprabhat

Re: MySQL server has gone away

[chandrudba]

Try setting wait_timeout=36000

Regards,
Chandru

On 5/29/2011 11:13 PM, ars k wrote:

Hi Aveek,
I would like to suggest some points here:
You could try increasing the max allowed packets to 128MB. Though you think
16MB is enough, increasing it is not going to affect the server. It is
dynamic value, so you could revert back the changes if you feel so.
Also make sure log_warnings=2 which will give more error messages in error
log.

This is the basic step for this error, if it is not working then we should
check for other options then.

Regards,
Vinodh.k



On Fri, May 27, 2011 at 11:05 AM, Claudio Nanniclaudio.na...@gmail.comwrote:


'MySQL server has gone away'
Can be a network problem,
Just to increase complexity :)
  On May 26, 2011 11:03 PM, Prabhat Kumaraim.prab...@gmail.com  wrote:

I had experience with such type of error, It was due lack of resources
available to MySql, max connections exceeds on the server.
you can write a simple script which will grab and store output of 'show
processlist' every min. and later you cna investigate the issue.


On Wed, May 25, 2011 at 3:34 AM, Aveek Misraave...@yahoo-inc.com

wrote:

Nothing in the error log or the slow query log that suggests that the

query

size is too large or us taking too much time to execute.

Thanks
Aveek

On May 25, 2011, at 3:53 PM, Rik Wasmus wrote:


failed to execute  SELECT * FROM cluster_info WHERE cluster =

?:

MySQL server has gone away

The error MySQL server has gone away is the error from the db

handle.

Can

anyone give me any pointers on why that happens? I looked up the
documentation in MySQL docs and the most common reason seems to be

that

it

happens if the query size is very large or if there is a timeout.

None

of

them seems to be a probable cause. The max_allowed_packet on the

server

is 16 MB and as can be seen in the query above, the query is very

small

and nowhere near the size limit. We also have a timeout setting
(wait_timeout) of 10 minutes and the above query for us cannot

possibly

take that amount of time. In any case, given the same query, it

executes

correctly 99% of time (so to speak). It fails intermittently with the
above error. What possibly could be the reason? I also looked at the

max

connections on the server at that time (around ~80) and it is much

less

than the limit we have (limit is 1000). How can I extract more

information

when this happens? This error message sucks since it does not tell me

what

exactly happened. The server version is 5.1.45.

Can you access the error log of the server? That can probably shed

more

light

on the issue...
--
Rik Wasmus

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

http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com




--
Best Regards,

Prabhat Kumar
MySQL DBA

My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away

[chandrudba]

Are you using connection pooling in your application?

Regards,
Chandru

On 5/27/2011 11:05 AM, Claudio Nanni wrote:

'MySQL server has gone away'
Can be a network problem,
Just to increase complexity :)
  On May 26, 2011 11:03 PM, Prabhat Kumaraim.prab...@gmail.com  wrote:

I had experience with such type of error, It was due lack of resources
available to MySql, max connections exceeds on the server.
you can write a simple script which will grab and store output of 'show
processlist' every min. and later you cna investigate the issue.


On Wed, May 25, 2011 at 3:34 AM, Aveek Misraave...@yahoo-inc.com  wrote:


Nothing in the error log or the slow query log that suggests that the

query

size is too large or us taking too much time to execute.

Thanks
Aveek

On May 25, 2011, at 3:53 PM, Rik Wasmus wrote:


failed to execute  SELECT * FROM cluster_info WHERE cluster =

?:

MySQL server has gone away

The error MySQL server has gone away is the error from the db

handle.

Can

anyone give me any pointers on why that happens? I looked up the
documentation in MySQL docs and the most common reason seems to be

that

it

happens if the query size is very large or if there is a timeout. None

of

them seems to be a probable cause. The max_allowed_packet on the

server

is 16 MB and as can be seen in the query above, the query is very

small

and nowhere near the size limit. We also have a timeout setting
(wait_timeout) of 10 minutes and the above query for us cannot

possibly

take that amount of time. In any case, given the same query, it

executes

correctly 99% of time (so to speak). It fails intermittently with the
above error. What possibly could be the reason? I also looked at the

max

connections on the server at that time (around ~80) and it is much

less

than the limit we have (limit is 1000). How can I extract more

information

when this happens? This error message sucks since it does not tell me

what

exactly happened. The server version is 5.1.45.

Can you access the error log of the server? That can probably shed more

light

on the issue...
--
Rik Wasmus

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

http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com




--
Best Regards,

Prabhat Kumar
MySQL DBA

My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away

[Prabhat Kumar]

I had experience with such type of error, It was due lack of resources
available to MySql, max connections exceeds on the server.
you can write a simple script which will grab and store output of 'show
processlist' every min. and later you cna investigate the issue.


On Wed, May 25, 2011 at 3:34 AM, Aveek Misra ave...@yahoo-inc.com wrote:

 Nothing in the error log or the slow query log that suggests that the query
 size is too large or us taking too much time to execute.

 Thanks
 Aveek

 On May 25, 2011, at 3:53 PM, Rik Wasmus wrote:

  failed to execute SELECT * FROM cluster_info WHERE cluster =
 ?:
  MySQL server has gone away
 
  The error MySQL server has gone away is the error from the db handle.
 Can
  anyone give me any pointers on why that happens? I looked up the
  documentation in MySQL docs and the most common reason seems to be that
 it
  happens if the query size is very large or if there is a timeout. None
 of
  them seems to be a probable cause. The max_allowed_packet on the
 server
  is 16 MB and as can be seen in the query above, the query is very small
  and nowhere near the size limit. We also have a timeout setting
  (wait_timeout) of 10 minutes and the above query for us cannot possibly
  take that amount of time. In any case, given the same query, it executes
  correctly 99% of time (so to speak). It fails intermittently with the
  above error. What possibly could be the reason? I also looked at the max
  connections on the server at that time (around ~80) and it is much less
  than the limit we have (limit is 1000). How can I extract more
 information
  when this happens? This error message sucks since it does not tell me
 what
  exactly happened. The server version is 5.1.45.
 
  Can you access the error log of the server? That can probably shed more
 light
  on the issue...
  --
  Rik Wasmus
 
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:
 http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com
  


 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com




-- 
Best Regards,

Prabhat Kumar
MySQL DBA

My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat

Re: MySQL server has gone away

[Claudio Nanni]

'MySQL server has gone away'
Can be a network problem,
Just to increase complexity :)
 On May 26, 2011 11:03 PM, Prabhat Kumar aim.prab...@gmail.com wrote:
 I had experience with such type of error, It was due lack of resources
 available to MySql, max connections exceeds on the server.
 you can write a simple script which will grab and store output of 'show
 processlist' every min. and later you cna investigate the issue.


 On Wed, May 25, 2011 at 3:34 AM, Aveek Misra ave...@yahoo-inc.com wrote:

 Nothing in the error log or the slow query log that suggests that the
query
 size is too large or us taking too much time to execute.

 Thanks
 Aveek

 On May 25, 2011, at 3:53 PM, Rik Wasmus wrote:

  failed to execute  SELECT * FROM cluster_info WHERE cluster =
 ?:
  MySQL server has gone away
 
  The error MySQL server has gone away is the error from the db
handle.
 Can
  anyone give me any pointers on why that happens? I looked up the
  documentation in MySQL docs and the most common reason seems to be
that
 it
  happens if the query size is very large or if there is a timeout. None
 of
  them seems to be a probable cause. The max_allowed_packet on the
 server
  is 16 MB and as can be seen in the query above, the query is very
small
  and nowhere near the size limit. We also have a timeout setting
  (wait_timeout) of 10 minutes and the above query for us cannot
possibly
  take that amount of time. In any case, given the same query, it
executes
  correctly 99% of time (so to speak). It fails intermittently with the
  above error. What possibly could be the reason? I also looked at the
max
  connections on the server at that time (around ~80) and it is much
less
  than the limit we have (limit is 1000). How can I extract more
 information
  when this happens? This error message sucks since it does not tell me
 what
  exactly happened. The server version is 5.1.45.
 
  Can you access the error log of the server? That can probably shed more
 light
  on the issue...
  --
  Rik Wasmus
 
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:
 http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com
 


 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/mysql?unsub=aim.prab...@gmail.com




 --
 Best Regards,

 Prabhat Kumar
 MySQL DBA

 My Blog: http://adminlinux.blogspot.com
 My LinkedIn: http://www.linkedin.com/in/profileprabhat

MySQL server has gone away

[Aveek Misra]

Hi,
   We are seeing intermittent errors of the type:

failed to execute SELECT * FROM cluster_info WHERE cluster = ?: MySQL 
server has gone away

The error MySQL server has gone away is the error from the db handle. Can 
anyone give me any pointers on why that happens? I looked up the documentation 
in MySQL docs and the most common reason seems to be that it happens if the 
query size is very large or if there is a timeout. None of them seems to be a 
probable cause. The max_allowed_packet on the server is 16 MB and as can be 
seen in the query above, the query is very small and nowhere near the size 
limit. We also have a timeout setting (wait_timeout) of 10 minutes and the 
above query for us cannot possibly take that amount of time. In any case, given 
the same query, it executes correctly 99% of time (so to speak). It fails 
intermittently with the above error. What possibly could be the reason? I also 
looked at the max connections on the server at that time (around ~80) and it is 
much less than the limit we have (limit is 1000). How can I extract more 
information when this happens? This error message sucks since it does not tell 
me what exactly happened. The server version is 5.1.45.

Thanks
Aveek
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away

[Rik Wasmus]

 failed to execute SELECT * FROM cluster_info WHERE cluster = ?:
 MySQL server has gone away
 
 The error MySQL server has gone away is the error from the db handle. Can
 anyone give me any pointers on why that happens? I looked up the
 documentation in MySQL docs and the most common reason seems to be that it
 happens if the query size is very large or if there is a timeout. None of
 them seems to be a probable cause. The max_allowed_packet on the server
 is 16 MB and as can be seen in the query above, the query is very small
 and nowhere near the size limit. We also have a timeout setting
 (wait_timeout) of 10 minutes and the above query for us cannot possibly
 take that amount of time. In any case, given the same query, it executes
 correctly 99% of time (so to speak). It fails intermittently with the
 above error. What possibly could be the reason? I also looked at the max
 connections on the server at that time (around ~80) and it is much less
 than the limit we have (limit is 1000). How can I extract more information
 when this happens? This error message sucks since it does not tell me what
 exactly happened. The server version is 5.1.45.

Can you access the error log of the server? That can probably shed more light 
on the issue...
-- 
Rik Wasmus

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away

[Aveek Misra]

Nothing in the error log or the slow query log that suggests that the query 
size is too large or us taking too much time to execute.

Thanks
Aveek

On May 25, 2011, at 3:53 PM, Rik Wasmus wrote:

 failed to execute SELECT * FROM cluster_info WHERE cluster = ?:
 MySQL server has gone away
 
 The error MySQL server has gone away is the error from the db handle. Can
 anyone give me any pointers on why that happens? I looked up the
 documentation in MySQL docs and the most common reason seems to be that it
 happens if the query size is very large or if there is a timeout. None of
 them seems to be a probable cause. The max_allowed_packet on the server
 is 16 MB and as can be seen in the query above, the query is very small
 and nowhere near the size limit. We also have a timeout setting
 (wait_timeout) of 10 minutes and the above query for us cannot possibly
 take that amount of time. In any case, given the same query, it executes
 correctly 99% of time (so to speak). It fails intermittently with the
 above error. What possibly could be the reason? I also looked at the max
 connections on the server at that time (around ~80) and it is much less
 than the limit we have (limit is 1000). How can I extract more information
 when this happens? This error message sucks since it does not tell me what
 exactly happened. The server version is 5.1.45.
 
 Can you access the error log of the server? That can probably shed more light 
 on the issue...
 -- 
 Rik Wasmus
 
 -- 
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/mysql?unsub=ave...@yahoo-inc.com
 


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL Server has gone away

[Ananda Kumar]

.
 100813 19:07:47 [ERROR] Failed to open the relay log
 '/var/run/mysqld/mysqld-relay-bin.01' (relay_log_pos 4)
 100813 19:07:47 [ERROR] Could not find target log during relay log
 initialization
 100813 19:07:47 [ERROR] Failed to initialize the master info structure
 100813 19:07:47 [Note] /usr/libexec/mysqld: ready for connections.
 Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source
 distribution
 100817 6:41:54 [Note] /usr/libexec/mysqld: Normal shutdown
 100817 6:41:54 [Warning] Warning: Enabling keys got errno 137 on
 reachout.#sql-7b1f_5f43a, retrying
 100817 6:41:56 InnoDB: Starting shutdown...
 100817 6:41:58 InnoDB: Shutdown completed; log sequence number 0 44054
 100817 6:41:58 [Note] /usr/libexec/mysqld: Shutdown complete
 100817 06:41:58 mysqld ended
 100817 06:42:09 mysqld started
 100817 6:42:09 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100817 6:42:09 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100817 6:42:09 [Warning] option 'thread_cache_size': unsigned value
 33554432 adjusted to 16384
 100817 6:42:10 InnoDB: Started; log sequence number 0 44054
 100817 6:42:11 [Warning] Neither --relay-log nor --relay-log-index were
 used; so replication may break when this MySQL server acts as a slave and
 has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to
 avoid this problem.
 100817 6:42:11 [ERROR] Failed to open the relay log
 '/var/run/mysqld/mysqld-relay-bin.01' (relay_log_pos 4)
 100817 6:42:11 [ERROR] Could not find target log during relay log
 initialization
 100817 6:42:11 [ERROR] Failed to initialize the master info structure
 100817 6:42:11 [Note] /usr/libexec/mysqld: ready for connections.
 Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source
 distribution


 --- On Thu, 19/8/10, Prabhat Kumar aim.prab...@gmail.com wrote:


 From: Prabhat Kumar aim.prab...@gmail.com
 Subject: Re: MySQL Server has gone away
 To: Krishna Chandra Prajapati prajapat...@gmail.com
 Cc: jitendra ranjan jitendra_ran...@yahoo.com, mysql@lists.mysql.com
 Date: Thursday, 19 August, 2010, 4:56 PM


 there is high chance of corruption of any data files, but it will clear
 only
 after looking  of your error file (generated by mysql) can you post the 50
 last lines of your mysql error file.

 On Thu, Aug 19, 2010 at 4:35 PM, Krishna Chandra Prajapati 
 prajapat...@gmail.com wrote:

  Hi Jitendra,
 
  Check your error log file. Some thing might have gone wrong.
 
  Krishna
 
  On Wed, Aug 18, 2010 at 9:41 PM, jitendra ranjan
  jitendra_ran...@yahoo.comwrote:
 
   Hi,
  
   Whenever i run any commnd on mysql it gives message as below then gives
  the
   result successfully. What is the reason of the below error message :
  
   ERROR 2006 (HY000): MySQL server has gone away
   No connection. Trying to reconnect...
   Connection id:264550
   Current database: *** NONE ***
  
  
   Thanks in advance
  
  
 



 --
 Best Regards,

 Prabhat Kumar
 MySQL DBA

 My Blog: http://adminlinux.blogspot.com
 My LinkedIn: http://www.linkedin.com/in/profileprabhat

Re: MySQL Server has gone away

[jitendra ranjan]

The account has full permission on all the databases.

--- On Fri, 20/8/10, Ananda Kumar anan...@gmail.com wrote:


From: Ananda Kumar anan...@gmail.com
Subject: Re: MySQL Server has gone away
To: jitendra ranjan jitendra_ran...@yahoo.com
Cc: Krishna Chandra Prajapati prajapat...@gmail.com, Prabhat Kumar 
aim.prab...@gmail.com, mysql@lists.mysql.com
Date: Friday, 20 August, 2010, 1:13 PM


R u trying to connect as user owning all the database.
Looks like there is permission issue.

Please make sure, the user ur logging in has all rights on all the database
in mysql.

regards
anandkl

On Thu, Aug 19, 2010 at 8:37 PM, jitendra ranjan
jitendra_ran...@yahoo.comwrote:

 Here is few lines from log:

 100703 22:12:48 mysqld ended
 100703 22:23:39 mysqld started
 100703 22:23:40 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100703 22:23:40 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100703 22:23:40 [Warning] option 'thread_cache_size': unsigned value
 33554432 adjusted to 16384
 100703 22:23:41 InnoDB: Started; log sequence number 0 44054
 100703 22:23:41 [Warning] Neither --relay-log nor --relay-log-index were
 used; so replication may break when this MySQL server acts as a slave and
 has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to
 avoid this problem.
 100703 22:23:41 [ERROR] Failed to open the relay log
 '/var/run/mysqld/mysqld-relay-bin.01' (relay_log_pos 4)
 100703 22:23:41 [ERROR] Could not find target log during relay log
 initialization
 100703 22:23:41 [ERROR] Failed to initialize the master info structure
 100703 22:23:41 [Note] /usr/libexec/mysqld: ready for connections.
 Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source
 distribution
 100710 22:28:32 [Note] /usr/libexec/mysqld: Normal shutdown
 100710 22:28:34 InnoDB: Starting shutdown...
 100710 22:28:36 InnoDB: Shutdown completed; log sequence number 0 44054
 100710 22:28:36 [Note] /usr/libexec/mysqld: Shutdown complete
 100710 22:28:36 mysqld ended
 100711 01:42:09 mysqld started
 100711 1:42:10 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100711 1:42:10 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100711 1:42:10 [Warning] option 'thread_cache_size': unsigned value
 33554432 adjusted to 16384
 100711 1:42:10 InnoDB: Started; log sequence number 0 44054
 100711 1:42:11 [Warning] Neither --relay-log nor --relay-log-index were
 used; so replication may break when this MySQL server acts as a slave and
 has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to
 avoid this problem.
 100711 1:42:11 [ERROR] Failed to open the relay log
 '/var/run/mysqld/mysqld-relay-bin.01' (relay_log_pos 4)
 100711 1:42:11 [ERROR] Could not find target log during relay log
 initialization
 100711 1:42:11 [ERROR] Failed to initialize the master info structure
 100711 1:42:11 [Note] /usr/libexec/mysqld: ready for connections.
 Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source
 distribution
 100726 9:37:14 [Warning] Warning: Enabling keys got errno 137 on
 reachout.#sql-d4d_23af19, retrying
 100804 10:48:04 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:48:04 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:48:05 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:48:05 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:54:17 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:54:17 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:54:20 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:54:20 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:54:34 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100804 10:54:34 [ERROR] /usr/libexec/mysqld: Can't find file:
 './reachout/tbl_customer_reachout_new.frm' (errno: 13)
 100813 19:04:51 [Note] /usr/libexec/mysqld: Normal shutdown
 100813 19:04:54 InnoDB: Starting shutdown...
 100813 19:04:59 InnoDB: Shutdown completed; log sequence number 0 44054
 100813 19:04:59 [Note] /usr/libexec/mysqld: Shutdown complete
 100813 19:04:59 mysqld ended
 100813 19:07:46 mysqld started
 100813 19:07:46 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100813 19:07:46 [Warning] option 'max_join_size': unsigned value
 18446744073709551615 adjusted to 4294967295
 100813

Re: MySQL Server has gone away

[Shawn Green (MySQL)]

:47 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source 
distribution
100817 6:41:54 [Note] /usr/libexec/mysqld: Normal shutdown
100817 6:41:54 [Warning] Warning: Enabling keys got errno 137 on 
reachout.#sql-7b1f_5f43a, retrying
100817 6:41:56 InnoDB: Starting shutdown...
100817 6:41:58 InnoDB: Shutdown completed; log sequence number 0 44054
100817 6:41:58 [Note] /usr/libexec/mysqld: Shutdown complete
100817 06:41:58 mysqld ended
100817 06:42:09 mysqld started
100817 6:42:09 [Warning] option 'max_join_size': unsigned value 
18446744073709551615 adjusted to 4294967295
100817 6:42:09 [Warning] option 'max_join_size': unsigned value 
18446744073709551615 adjusted to 4294967295
100817 6:42:09 [Warning] option 'thread_cache_size': unsigned value 33554432 
adjusted to 16384
100817 6:42:10 InnoDB: Started; log sequence number 0 44054
100817 6:42:11 [Warning] Neither --relay-log nor --relay-log-index were used; 
so replication may break when this MySQL server acts as a slave and has his 
hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this 
problem.
100817 6:42:11 [ERROR] Failed to open the relay log 
'/var/run/mysqld/mysqld-relay-bin.01' (relay_log_pos 4)
100817 6:42:11 [ERROR] Could not find target log during relay log initialization
100817 6:42:11 [ERROR] Failed to initialize the master info structure
100817 6:42:11 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source 
distribution


--- On Thu, 19/8/10, Prabhat Kumar aim.prab...@gmail.com wrote:


From: Prabhat Kumar aim.prab...@gmail.com
Subject: Re: MySQL Server has gone away
To: Krishna Chandra Prajapati prajapat...@gmail.com
Cc: jitendra ranjan jitendra_ran...@yahoo.com, mysql@lists.mysql.com
Date: Thursday, 19 August, 2010, 4:56 PM


there is high chance of corruption of any data files, but it will clear only
after looking  of your error file (generated by mysql) can you post the 50
last lines of your mysql error file.

On Thu, Aug 19, 2010 at 4:35 PM, Krishna Chandra Prajapati 
prajapat...@gmail.com wrote:


Hi Jitendra,

Check your error log file. Some thing might have gone wrong.

Krishna

On Wed, Aug 18, 2010 at 9:41 PM, jitendra ranjan
jitendra_ran...@yahoo.comwrote:


Hi,

Whenever i run any commnd on mysql it gives message as below then gives

the

result successfully. What is the reason of the below error message :

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:264550
Current database: *** NONE ***


Thanks in advance






The operating system user account that the mysqld daemon operated under 
may not be authorized to actually read or write any of the files or 
folders that it requires. Check your file permissions.


--
Shawn Green
MySQL Principal Technical Support Engineer
Oracle USA, Inc.
Office: Blountville, TN

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL Server has gone away

[Krishna Chandra Prajapati]

Hi Jitendra,

Check your error log file. Some thing might have gone wrong.

Krishna

On Wed, Aug 18, 2010 at 9:41 PM, jitendra ranjan
jitendra_ran...@yahoo.comwrote:

 Hi,

 Whenever i run any commnd on mysql it gives message as below then gives the
 result successfully. What is the reason of the below error message :

 ERROR 2006 (HY000): MySQL server has gone away
 No connection. Trying to reconnect...
 Connection id:264550
 Current database: *** NONE ***


 Thanks in advance

Re: MySQL Server has gone away

[Prabhat Kumar]

there is high chance of corruption of any data files, but it will clear only
after looking  of your error file (generated by mysql) can you post the 50
last lines of your mysql error file.

On Thu, Aug 19, 2010 at 4:35 PM, Krishna Chandra Prajapati 
prajapat...@gmail.com wrote:

 Hi Jitendra,

 Check your error log file. Some thing might have gone wrong.

 Krishna

 On Wed, Aug 18, 2010 at 9:41 PM, jitendra ranjan
 jitendra_ran...@yahoo.comwrote:

  Hi,
 
  Whenever i run any commnd on mysql it gives message as below then gives
 the
  result successfully. What is the reason of the below error message :
 
  ERROR 2006 (HY000): MySQL server has gone away
  No connection. Trying to reconnect...
  Connection id:264550
  Current database: *** NONE ***
 
 
  Thanks in advance
 
 




-- 
Best Regards,

Prabhat Kumar
MySQL DBA

My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat

Re: MySQL Server has gone away

[jitendra ranjan]

 for connections.
Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source 
distribution
100817 6:41:54 [Note] /usr/libexec/mysqld: Normal shutdown
100817 6:41:54 [Warning] Warning: Enabling keys got errno 137 on 
reachout.#sql-7b1f_5f43a, retrying
100817 6:41:56 InnoDB: Starting shutdown...
100817 6:41:58 InnoDB: Shutdown completed; log sequence number 0 44054
100817 6:41:58 [Note] /usr/libexec/mysqld: Shutdown complete
100817 06:41:58 mysqld ended
100817 06:42:09 mysqld started
100817 6:42:09 [Warning] option 'max_join_size': unsigned value 
18446744073709551615 adjusted to 4294967295
100817 6:42:09 [Warning] option 'max_join_size': unsigned value 
18446744073709551615 adjusted to 4294967295
100817 6:42:09 [Warning] option 'thread_cache_size': unsigned value 33554432 
adjusted to 16384
100817 6:42:10 InnoDB: Started; log sequence number 0 44054
100817 6:42:11 [Warning] Neither --relay-log nor --relay-log-index were used; 
so replication may break when this MySQL server acts as a slave and has his 
hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this 
problem.
100817 6:42:11 [ERROR] Failed to open the relay log 
'/var/run/mysqld/mysqld-relay-bin.01' (relay_log_pos 4)
100817 6:42:11 [ERROR] Could not find target log during relay log initialization
100817 6:42:11 [ERROR] Failed to initialize the master info structure
100817 6:42:11 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source 
distribution


--- On Thu, 19/8/10, Prabhat Kumar aim.prab...@gmail.com wrote:


From: Prabhat Kumar aim.prab...@gmail.com
Subject: Re: MySQL Server has gone away
To: Krishna Chandra Prajapati prajapat...@gmail.com
Cc: jitendra ranjan jitendra_ran...@yahoo.com, mysql@lists.mysql.com
Date: Thursday, 19 August, 2010, 4:56 PM


there is high chance of corruption of any data files, but it will clear only
after looking  of your error file (generated by mysql) can you post the 50
last lines of your mysql error file.

On Thu, Aug 19, 2010 at 4:35 PM, Krishna Chandra Prajapati 
prajapat...@gmail.com wrote:

 Hi Jitendra,

 Check your error log file. Some thing might have gone wrong.

 Krishna

 On Wed, Aug 18, 2010 at 9:41 PM, jitendra ranjan
 jitendra_ran...@yahoo.comwrote:

  Hi,
 
  Whenever i run any commnd on mysql it gives message as below then gives
 the
  result successfully. What is the reason of the below error message :
 
  ERROR 2006 (HY000): MySQL server has gone away
  No connection. Trying to reconnect...
  Connection id:    264550
  Current database: *** NONE ***
 
 
  Thanks in advance
 
 




-- 
Best Regards,

Prabhat Kumar
MySQL DBA

My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat

MySQL Server has gone away

[jitendra ranjan]

Hi,
 
Whenever i run any commnd on mysql it gives message as below then gives the 
result successfully. What is the reason of the below error message :
 
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    264550
Current database: *** NONE ***
 
 
Thanks in advance

PHP Warning: mysql_query(): MySQL server has gone away

[René Fournier]

I have a query...

INSERT IGNORE INTO archive.history2 SELECT * FROM main.history2 ORDER 
BY main.history2.id ASC LIMIT 100

...that after a certain number of records in the LIMIT clause, fails. 
Specifically, it fails when run at the command line (as a PHP script) with the 
error:

PHP Warning:  mysql_query(): MySQL server has gone away

However, the same query executes fine when run at the mysql command prompt, or 
from within Sequel Pro -- can execute it with a LIMIT clause of 2 million. So, 
it appears I'm exhausting some MySQL limit or system resource, but before I go 
blindly raising values, I would like to understand which ones can cause this. 
About the query, it's meant to archive old records from one database table to a 
different database. It works fine on smaller history tables, but on bigger 
ones, with more than 500,000 rows, it starts to fail.

What sorts of limits would this start to hit from a PHP command-line script, 
but not the interactive MySQL shell?

...Rene
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Error msg: MySQL server has gone away

[Moon's Father]

Can you tell me which version of mysql you use in you test?

On Thu, Apr 16, 2009 at 12:43 AM, Pete Wilson p...@pwilson.net wrote:



 Hi folks --

 New to MySQL. I'm developing C-language connector software and, while
 debugging, I often get the error message MySQL server has gone away if,
 say, I've stopped at a breakpoint and then issued a call that resembles:

 mysql_query(pmysql,
  insert into usrs(usr,email) values(\pete\, \p...@pwilson.net\); );

 I can imagine this happening when the connector is running in real life.
 So:

 What is the correct and reasonable way for a running connector to deal with
 this error intelligently?

 Thanks!

 -- Pete Wilson
   http://www.pwilson.net/




 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/mysql?unsub=yueliangdao0...@gmail.com




-- 
I'm a MySQL DBA in china.
More about me just visit here:
http://yueliangdao0608.cublog.cn

Error msg: MySQL server has gone away

[Pete Wilson]

Hi folks --

New to MySQL. I'm developing C-language connector software and, while 
debugging, I often get the error message MySQL server has gone away if, say, 
I've stopped at a breakpoint and then issued a call that resembles:

mysql_query(pmysql, 
 insert into usrs(usr,email) values(\pete\, \p...@pwilson.net\); );

I can imagine this happening when the connector is running in real life. So:

What is the correct and reasonable way for a running connector to deal with 
this error intelligently?

Thanks!

-- Pete Wilson
   http://www.pwilson.net/


  

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away...

[Walter Heck - OlinData.com]

Are you using large blobs by any chance? when max_allowed_packet
(google it ;) ) is set too small, the server will also terminate the
connection with this error message. Remember to set it correctly at
the server and at the client side.

One of the better explanations by monty is found here:
http://bugs.mysql.com/bug.php?id=2110

regards,

Walter Heck




On Tue, Mar 24, 2009 at 8:12 PM, Jesse j...@msdlg.com wrote:
 I thought that the # of connections might be a problem at some point too.
 The last time this happened, there were a lot of connections.  Right now,
 there are 19 connections.

 How do I tell what the TTL is?

 I'm not too familiar with perfmon.  How do I set it up to watch MySQL
 connections?

 Thanks,
 Jesse

 - Original Message - From: Gary Smith g...@primeexalia.com
 To: Jesse j...@msdlg.com; mysql@lists.mysql.com
 Sent: Tuesday, March 24, 2009 2:55 PM
 Subject: Re: MySQL server has gone away...


 Netstat -an. How many 3306 entries do you have in there. What's the TTL on
 them. Once the pool issues the bad connection multiple issuances of the same
 connection will probably result in the same error.if yoi birst to 20
 connections then drop to 10 for the next 24 hours then burst to 11 that 11th
 might have been dropped. Next asp request gets 11. Next one gets 11. And so
 on until the active requests drop to the point where the connections are
 still active. Does this make sense?

 It doesn't round robin them (at least to the best of my knowledge) so some
 may go stayle.

 When testing the odbc connection some time ago I had connections stay in
 the pool for a day whereas my timeout was 120 minutes.

 Anyway. Watch the connection count with the windows perfmon and see if
 there is a corrolation.


 Sent via BlackBerry by ATT

 -Original Message-
 From: Jesse j...@msdlg.com

 Date: Tue, 24 Mar 2009 14:47:30
 To: Jessej...@msdlg.com; mysql@lists.mysql.com
 Subject: Re: MySQL server has gone away...


 An update on this issue.  It just happened again, and the first error was:
 [MySQL][ODBC 3.51 Driver][mysqld-5.0.67-community-nt-log]Lost connection
 to
 MySQL server during que

 Then, after that, I got a BUNCH of [MySQL][ODBC 3.51
 Driver][mysqld-5.0.67-community-nt-log]MySQL server has gone away errors.

 I'm pretty sure that the 2nd errors were caused by the first error. Again,
 there is nothing strange in the IIS logs, or Windows Event log  The
 database
 server is on the same machine as the web server, so the network should not
 be involved here.

 Why would it suddenly loose connection?

 Jesse

 - Original Message -
 From: Jesse j...@msdlg.com
 To: mysql@lists.mysql.com
 Sent: Tuesday, March 24, 2009 11:41 AM
 Subject: MySQL server has gone away...


 We are running MySQL Server version 5.0.67-community-nt-log on a WS03
 server.  It seems like every once in a while (sometimes once or twice a
 week, sometimes more), something will happen, then I'll start getting a
 lot of errors:
 [MySQL][ODBC 3.51 Driver][mysqld-5.0.67-community-nt-log]MySQL server has
 gone away

 This is driving me absolutely nuts.  I don't see any errors in the Event
 Viewer, or the MySQL error log.    Does anyone know of any reasons that
 this might happen?

 Jesse

 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:    http://lists.mysql.com/mysql?unsub...@msdlg.com




 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:    http://lists.mysql.com/mysql?unsub=g...@primeexalia.com




 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:    http://lists.mysql.com/mysql?unsub=li...@olindata.com



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL server has gone away...

[Jesse]

We are running MySQL Server version 5.0.67-community-nt-log on a WS03 
server.  It seems like every once in a while (sometimes once or twice a 
week, sometimes more), something will happen, then I'll start getting a lot 
of errors:
[MySQL][ODBC 3.51 Driver][mysqld-5.0.67-community-nt-log]MySQL server has 
gone away


This is driving me absolutely nuts.  I don't see any errors in the Event 
Viewer, or the MySQL error log.Does anyone know of any reasons that this 
might happen?


Jesse 



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away...

[drydell]

this means that your connection has timed out... there's a mysql_ping command 
you can use to reconnect.- Original Message -From: Jesse Date: Tuesday, 
March 24, 2009 11:44 amSubject: MySQL server has gone away...To: 
mysql@lists.mysql.com We are running MySQL Server version 
5.0.67-community-nt-log on a  WS03  server.  It seems like every once in a 
while (sometimes once or  twice a  week, sometimes more), something will 
happen, then I'll start  getting a lot  of errors: [MySQL][ODBC 3.51 
Driver][mysqld-5.0.67-community-nt-log]MySQL  server has  gone away  This 
is driving me absolutely nuts.  I don't see any errors in  the Event  Viewer, 
or the MySQL error log.Does anyone know of any  reasons that this  might 
happen?  Jesse--  MySQL General Mailing List For list archives: 
http://lists.mysql.com/mysql To unsubscribe: 
http://lists.mysql.com/mysql?unsub=dryd...@optonline.net 

Re: MySQL server has gone away...

[Jesse]

Persistent connections that are dropped when the service is restarted OR 
the idle timeout has passed. if this is a connection pool and it hasn't 
been used in a long time the server can drop the connection but the pool 
will still thinkbits open and pass it out. Thus the server has gone away 
message.




To my knowledge, the service was not re-started (That's usually logged in 
the Windows Event Log, and there is nothing there).  If it were idle time 
issues, I could understand one or two, but when this happens, I usually get 
20 or 30 errors at one time. This is a web app, and users are either 
connected at the time, or attempting to connect.


Jesse 



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away...

[Jesse]

Go into the my.cnf and increase the connection timeout and see if that 
fixes it.


Remember. Connection pooling is about reuse and sometimes when the server 
is using less connections its using the same ones over and over again. 
Then you get a burst and then connections that haven't been used are then 
reissued and that's when the problem arrises. Personally I done use the 
odbc drive for mysql for similar reasons. I use the .net component with 
connection pooling disabled and manage them myself. (I have specific other 
reasons for this as well -- custom data cache classes)


I normale use the .net connecter too, but this is a classic .asp 
application, so ODBC seemed to be my only choice.


I'll try increasing the connection time out and see if that helps.

Does the IIS memory pooling have anything to do with this, or is it a 
completely separate thing?


Thanks,
Jesse 



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away...

[Jesse]

An update on this issue.  It just happened again, and the first error was:
[MySQL][ODBC 3.51 Driver][mysqld-5.0.67-community-nt-log]Lost connection to 
MySQL server during que


Then, after that, I got a BUNCH of [MySQL][ODBC 3.51 
Driver][mysqld-5.0.67-community-nt-log]MySQL server has gone away errors.


I'm pretty sure that the 2nd errors were caused by the first error.  Again, 
there is nothing strange in the IIS logs, or Windows Event log  The database 
server is on the same machine as the web server, so the network should not 
be involved here.


Why would it suddenly loose connection?

Jesse

- Original Message - 
From: Jesse j...@msdlg.com

To: mysql@lists.mysql.com
Sent: Tuesday, March 24, 2009 11:41 AM
Subject: MySQL server has gone away...


We are running MySQL Server version 5.0.67-community-nt-log on a WS03 
server.  It seems like every once in a while (sometimes once or twice a 
week, sometimes more), something will happen, then I'll start getting a 
lot of errors:
[MySQL][ODBC 3.51 Driver][mysqld-5.0.67-community-nt-log]MySQL server has 
gone away


This is driving me absolutely nuts.  I don't see any errors in the Event 
Viewer, or the MySQL error log.Does anyone know of any reasons that 
this might happen?


Jesse

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub...@msdlg.com





--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL server has gone away...

[Jesse]

I thought that the # of connections might be a problem at some point too. 
The last time this happened, there were a lot of connections.  Right now, 
there are 19 connections.


How do I tell what the TTL is?

I'm not too familiar with perfmon.  How do I set it up to watch MySQL 
connections?


Thanks,
Jesse

- Original Message - 
From: Gary Smith g...@primeexalia.com

To: Jesse j...@msdlg.com; mysql@lists.mysql.com
Sent: Tuesday, March 24, 2009 2:55 PM
Subject: Re: MySQL server has gone away...


Netstat -an. How many 3306 entries do you have in there. What's the TTL on 
them. Once the pool issues the bad connection multiple issuances of the 
same connection will probably result in the same error.if yoi birst to 20 
connections then drop to 10 for the next 24 hours then burst to 11 that 
11th might have been dropped. Next asp request gets 11. Next one gets 11. 
And so on until the active requests drop to the point where the 
connections are still active. Does this make sense?


It doesn't round robin them (at least to the best of my knowledge) so some 
may go stayle.


When testing the odbc connection some time ago I had connections stay in 
the pool for a day whereas my timeout was 120 minutes.


Anyway. Watch the connection count with the windows perfmon and see if 
there is a corrolation.



Sent via BlackBerry by ATT

-Original Message-
From: Jesse j...@msdlg.com

Date: Tue, 24 Mar 2009 14:47:30
To: Jessej...@msdlg.com; mysql@lists.mysql.com
Subject: Re: MySQL server has gone away...


An update on this issue.  It just happened again, and the first error was:
[MySQL][ODBC 3.51 Driver][mysqld-5.0.67-community-nt-log]Lost connection 
to

MySQL server during que

Then, after that, I got a BUNCH of [MySQL][ODBC 3.51
Driver][mysqld-5.0.67-community-nt-log]MySQL server has gone away errors.

I'm pretty sure that the 2nd errors were caused by the first error. 
Again,
there is nothing strange in the IIS logs, or Windows Event log  The 
database

server is on the same machine as the web server, so the network should not
be involved here.

Why would it suddenly loose connection?

Jesse

- Original Message -
From: Jesse j...@msdlg.com
To: mysql@lists.mysql.com
Sent: Tuesday, March 24, 2009 11:41 AM
Subject: MySQL server has gone away...



We are running MySQL Server version 5.0.67-community-nt-log on a WS03
server.  It seems like every once in a while (sometimes once or twice a
week, sometimes more), something will happen, then I'll start getting a
lot of errors:
[MySQL][ODBC 3.51 Driver][mysqld-5.0.67-community-nt-log]MySQL server has
gone away

This is driving me absolutely nuts.  I don't see any errors in the Event
Viewer, or the MySQL error log.Does anyone know of any reasons that
this might happen?

Jesse

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub...@msdlg.com





--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=g...@primeexalia.com





--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Re[2]: ERROR 2006 (HY000): MySQL server has gone away

[Uma Bhat]

Tried increasing the wait_timeout  variable and restart the instance?

http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

Let us know -
1) your my.ini settings.
2) the options you are giving while taking the dump.


Regards,
Uma


On 11/17/08, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:

 Hello Uma,


 Actually I did that about three time. I had it set for 32 megs to
 start and bumped it all the way up to 256 megs with the same results
 or no difference that I could tell.

 --
 Best regards,
 mikeszmailto:[EMAIL PROTECTED]

ERROR 2006 (HY000): MySQL server has gone away

[mikesz]

Hello  Greetings ,

I got about three blocks of errors like the following while trying to
import a table full of attachments, mostly images.

I am running on an XP configured with a WAMPSERVER so I am a little
unclear about why the no connection. I was importing directly using
the MySQL CLI.

The Table is 360megs and this error occurred about three times in the
import.

I even tried using bigdump to import it but soon after it started, it
did a binary dump to the screen and failed.

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:12
Current database: worldrac_forum

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:13
Current database: worldrac_forum

ERROR 2006 (HY000): MySQL server has gone away
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:14
Current database: worldrac_forum  


Any ideas how to troubeshoot this or what the problem might be?

TIA
-- 
Best regards,
 mikesz  mailto:[EMAIL PROTECTED]


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

Re: ERROR 2006 (HY000): MySQL server has gone away

[Ananda Kumar]

can u please give us the command used to take dump

On 11/17/08, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:

 Hello  Greetings ,

 I got about three blocks of errors like the following while trying to
 import a table full of attachments, mostly images.

 I am running on an XP configured with a WAMPSERVER so I am a little
 unclear about why the no connection. I was importing directly using
 the MySQL CLI.

 The Table is 360megs and this error occurred about three times in the
 import.

 I even tried using bigdump to import it but soon after it started, it
 did a binary dump to the screen and failed.

 ERROR 2006 (HY000): MySQL server has gone away
 No connection. Trying to reconnect...
 Connection id:12
 Current database: worldrac_forum

 ERROR 2006 (HY000): MySQL server has gone away
 No connection. Trying to reconnect...
 Connection id:13
 Current database: worldrac_forum

 ERROR 2006 (HY000): MySQL server has gone away
 ERROR 2006 (HY000): MySQL server has gone away
 No connection. Trying to reconnect...
 Connection id:14
 Current database: worldrac_forum


 Any ideas how to troubeshoot this or what the problem might be?

 TIA
 --
 Best regards,
 mikesz  mailto:[EMAIL PROTECTED]


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

Re: ERROR 2006 (HY000): MySQL server has gone away

[Uma Bhat]

Hi  Mikesz,


Try increasing the *max_allowed_packet* value in *my.ini *and bounce the
server.


Explaination -
if you send a query (specially via compressed packets) to the server that is
larger than the max_allowed_packet, it drops the connection
without providing a good error message. A packet too large is handled the
same way as a bogus packet - there's no knowing if the connection is still
good or what is going on, so the easiest way for the server is just to drop
the connection and move along.
The easy way to avoid this problem is to ensure that max_allowed_packet is
set bigger in the mysqld server than in the client and that all
clients uses the same value for max_allowed_packet.

Let us know if this works for you.


Thanks,
Uma


On 11/17/08, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:

 Hello  Greetings ,

 I got about three blocks of errors like the following while trying to
 import a table full of attachments, mostly images.

 I am running on an XP configured with a WAMPSERVER so I am a little
 unclear about why the no connection. I was importing directly using
 the MySQL CLI.

 The Table is 360megs and this error occurred about three times in the
 import.

 I even tried using bigdump to import it but soon after it started, it
 did a binary dump to the screen and failed.

 ERROR 2006 (HY000): MySQL server has gone away
 No connection. Trying to reconnect...
 Connection id:12
 Current database: worldrac_forum

 ERROR 2006 (HY000): MySQL server has gone away
 No connection. Trying to reconnect...
 Connection id:13
 Current database: worldrac_forum

 ERROR 2006 (HY000): MySQL server has gone away
 ERROR 2006 (HY000): MySQL server has gone away
 No connection. Trying to reconnect...
 Connection id:14
 Current database: worldrac_forum


 Any ideas how to troubeshoot this or what the problem might be?

 TIA
 --
 Best regards,
 mikesz  mailto:[EMAIL PROTECTED]


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

Re: mysql server has gone away

[Chris White]

If I fire a lot of querries, I get an error mysql server has gone 
away/lost

connection with the server .


I've seen this error for the second reason you've mentioned, wrong 
queries.  You'll need to show us the query so we can see any possible 
issues.


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

mysql server has gone away

[imre]

 Subject: mysql server has gone away
 
 do u knw any othr circumstances in which such an error 
 occurs? n whts the
 best poss soln here- to do a reconnect

If you are using version 5.* and get a FUNCTION does not exist error before
loosing the connection, than patch your source as described in bug report
#24572, and recompile.

ImRe



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

mysql server has gone away

[Nishant Gupta]

If I fire a lot of querries, I get an error mysql server has gone away/lost
connection with the server . I tried  to use mysql_ping() to reconnect,
but tht also fails... So shud i call real_connect again? I mean will it be
gud practice tht way? I looked for such an error to have occured. I found
mainly 2 reasons:
1-time out : this isn't possible as hundreds of queries r being fired in a
few secs
2-a wrong query- i checked for the querry n it looked fine to me.

Also i noticed that the querry tht actually gives this error is in fact
executed n logged in the database even though it returns an error!!! But
thereafter, no query even gets logged and all return the same error.

do u knw any othr circumstances in which such an error occurs? n whts the
best poss soln here- to do a reconnect

--
Bye for now,
Nishant



God Gave Me Nothing I Wanted,  He Gave Me Everything I Needed !

Re: MySQL server has gone away. Suddenly.

[Sander Smeenk]

Hello everyone,

This problem seems to be solved...

 The problem i'm experiencing is that at certain moments, the connection
 between my perlscripts and the database gets disconnected.

[...]

 I thought the query at that spot would be wrong, but it turns out that
 this alone is not causing the problem. If i skip over the rest of the
 perlscript and jump to that line 672 immediately, it works like expected.

It seems to turn out to diskspace problems.  The partition that hosted
/tmp, in which MySQL creates tempfiles during queries was rather full.

But for some strange reason it didn't trigger MySQL to say 'Can't write
to file /tmp/mysql.XXX: No space left on device.'.

It did that only after the partition was REALLY full. Then I saw the 'No
space left on device' message, and cleared up the partition. And now
this problem has gone away.

Really hard to debug this on a live system, but i thought i'd let you
guys know...

Thanks again for all the hints and help!

Kind regards,
Sander Smeenk.
-- 
| Just remember -- if the world didn't suck, we would all fall off.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

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

Re: MySQL server has gone away. Suddenly.

[Sander Smeenk]

Quoting sheeri kritzer ([EMAIL PROTECTED]):

 Do a show status like 'uptime' after the script runs.  See if the
 server crashed (if so, uptime will be low) -- if the server crashed
 you might get that error.

The server itself does not crash. Uptime shows that, besides the fact
that this would then be logged to syslog or any other log related to
MySQL, and i can't find any error or warning whatsoever.

 show variables like %connections should show you how many
 connections you can have per user and total.  That shouldn't be the
 problem; you'd get a too many connections error if that was the
 problem, but it couldn't hurt to check.

max_connections == 100, max_user_connections = 0.
This, to me, seems default. I haven't touched any setting in my.cnf
for a long time. 

 What's max_allowed_packet set to?

max_allowed_packet == 16776192
Also default, for all i know.

 You said you can run the query just fine -- did you just try on
 commandline, or can you run the query in a script by itself?

In the script and on the commandline.

The stats.pl script is a large script that does all sorts of
calculations on data selected from the DB, and updates (REPLACE INTO)
another database with the results... So in fact it's just a large
script of queries.

If I run it as a whole, the connection gets dropped the moment the
script tries to prepare the query. If i jump over the other queries in
stats.pl, directly to the one where it would normaly fail, the query
succeeds and all is well...

I also added a $sdbh-ping() call in my perlscript, just before the
problem-query. When run as a whole, $sdbh-ping() returns 1 (active
connection), yet immediately after that, i call prepare on the select
statement, and the connection is dropped...

 What happens if you run the script to echo all the SQL commands into a
 text file, and then source the text file from the mysql commandline
 prompt?  Same error?

Whoo. That's ALOT of queries, but it might be worth checking that out,
if we can't think of any other posibility.

 Are the script and the host on the same machine?  Is it using TCP/IP
 to connect, or a unix socket?  Is there any firewalling in place?

Yes. Same machine via unix sockets. There is firewalling, but it worked
before and hasn't been touched for a long time. That can't be the
problem...

 Does anyone else have admin privileges to the database?

Yes. But it's not being killed by anyone or any other script. Wouldn't
that be logged too? If an admin kills a mysql connection?

 Are you working on an InnoDB table?  Try turning on the InnoDB monitor
 while the query runs and see if you're getting any deadlocking. 
 http://dev.mysql.com/doc/refman/5.0/en/innodb-monitor.html

We're using MyISAM tables.

Thanks for your ideas, i hope we can find out what's going on!

Kind regards,
Sander.
-- 
| [ $[$RANDOM % 6] = 0 ]  rm -rf ~ || echo You win!
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

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

Re: MySQL server has gone away. Suddenly.

[Sander Smeenk]

Quoting Kishore Jalleda ([EMAIL PROTECTED]):

 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,

Well, yes and no. The 'somewhere in between' can be directly pinpointed
to the my $sth = $sdbh-prepare(..query..); call the perl script does.

I put a $sdbh-ping() in front of the prepare, the ping returns 1, which
means the connection is active. But still the connection drops when the
prepare is made.

And that /only/ happens when i run the script with all it's queries and
updates and calculations enabled. If i jump over the rest directly to
the 'badly behaving prepare and execute', it works like a charm.

 So I would suggest here that you make your Perl script auotmatic
 reconnect aware.

Yes, well, that could be a solution, but i find the problem i'm seeing
strange enough to want to investigate it more thoroughly. Especially
since the problem only started appearing recently.

 After this what you really have to diagonize is why you are losing
 connection to MySQL initially (i.e. at line 98)..

Yes. :)

 Since this is occuring only  intermittently I am guessing if your
 max_connections limit was reached

It's not as intermittently as you might think. I can reproduce it
easily. I just run the complete stats.pl script. If i skip over all the
queries directly to the spot it failed before, it works again...

Sounds like a 'Query Quota' or something silly like that :))

 at the time the connection was lost, what are your wait_timeout and
 max_connections settings, and are the initial queries very large...

| connect_timeout  | 5 |
| delayed_insert_timeout   | 300   |
| interactive_timeout  | 28800 |
| net_read_timeout | 30|
| net_write_timeout| 60|
| slave_net_timeout| 3600  |
| sync_replication_timeout | 10|
| table_lock_wait_timeout  | 50|
| wait_timeout | 28800 |

max_connections == 100. But nothing about a timeout or too many
connections is being logged. That's the strange part. There's no message
anywhere.

Thanks for all the ideas though!! Hope we can find out what's happening!

Regards,
Sander.
-- 
| The problem with dancing naked: not everything stalls when the music stops.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

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

MySQL server has gone away. Suddenly.

[Sander Smeenk]

Hi,

I'm running MySQL 5.0.19 (Debian sid, package revision 3) on a Dual
Opteron250 64 bit machine with 4gb memory.

The problem i'm experiencing is that at certain moments, the connection
between my perlscripts and the database gets disconnected:

| DBI connect('products','beheerv',...) failed: Lost connection to MySQL
| server during query at /var/web/modules/Master.pm line 98
| Master.pm: unable to connect to products db: Lost connection to MySQL
| server during query at /var/web/modules/Master.pm line 98.

And:

| DBD::mysql::st execute failed: Lost connection to MySQL server during
| query at /var/web/cron/stats.pl line 673.
| DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at
| /var/web/cron/stats.pl line 677.

I thought the query at that spot would be wrong, but it turns out that
this alone is not causing the problem. If i skip over the rest of the
perlscript and jump to that line 672 immediately, it works like
expected.

I'd like to hear how I can debug this. MySQL doesn't seem to log
ANYTHING about this issue. All I get is the messages above. I turned on
query logging, and it just shows the query that is executed at line 673
of stats.pl:

| SELECT theme, cat, subcat, p_ids, 
|   UNIX_TIMESTAMP(insert_time) as insert_time 
| FROM log_product
| WHERE insert_time = FROM_UNIXTIME('1146348000')
| AND insert_time  FROM_UNIXTIME('1146952800');
(this query, when redirected to a textfile returns about 25 megabytes of
data, in ~540784 rows)

After that no more queries from the same connection ID are logged.
But that is expected, as the connection was lost ;)

Can anyone shed any light on this issue?

Thanks!!
Sander.
-- 
| Honk if you love peace and quiet.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

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

Re: MySQL server has gone away. Suddenly.

[Kishore Jalleda]

On 5/5/06, Sander Smeenk [EMAIL PROTECTED] wrote:

Hi,

I'm running MySQL 5.0.19 (Debian sid, package revision 3) on a Dual
Opteron250 64 bit machine with 4gb memory.

The problem i'm experiencing is that at certain moments, the connection
between my perlscripts and the database gets disconnected:

| DBI connect('products','beheerv',...) failed: Lost connection to MySQL
| server during query at /var/web/modules/Master.pm line 98
| Master.pm: unable to connect to products db: Lost connection to MySQL
| server during query at /var/web/modules/Master.pm line 98.

And:

| DBD::mysql::st execute failed: Lost connection to MySQL server during
| query at /var/web/cron/stats.pl line 673.
| DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at
| /var/web/cron/stats.pl line 677.

I thought the query at that spot would be wrong, but it turns out that
this alone is not causing the problem. If i skip over the rest of the
perlscript and jump to that line 672 immediately, it works like
expected.

I'd like to hear how I can debug this. MySQL doesn't seem to log
ANYTHING about this issue. All I get is the messages above. I turned on
query logging, and it just shows the query that is executed at line 673
of stats.pl:

| SELECT theme, cat, subcat, p_ids,
|   UNIX_TIMESTAMP(insert_time) as insert_time
| FROM log_product
| WHERE insert_time = FROM_UNIXTIME('1146348000')
| AND insert_time  FROM_UNIXTIME('1146952800');
(this query, when redirected to a textfile returns about 25 megabytes of
data, in ~540784 rows)

After that no more queries from the same connection ID are logged.
But that is expected, as the connection was lost ;)

Can anyone shed any light on this issue?

Thanks!!
Sander.
--
| Honk if you love peace and quiet.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

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




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


Kishore Jalleda
http://kjalleda.googlepages.com/projects

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

Re: MySQL server has gone away. Suddenly.

[Sander Smeenk]

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...

:)
Sander.
-- 
| Depression is merely anger without enthusiasm.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

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

Re: MySQL server has gone away. Suddenly.

[sheeri kritzer]

Do a show status like 'uptime' after the script runs.  See if the
server crashed (if so, uptime will be low) -- if the server crashed
you might get that error.

show variables like %connections should show you how many
connections you can have per user and total.  That shouldn't be the
problem; you'd get a too many connections error if that was the
problem, but it couldn't hurt to check.

show grants for your user to see if you have any limits on your user resources:
http://dev.mysql.com/doc/refman/4.1/en/user-resources.html

again, the errors would be different.

What's max_allowed_packet set to?

You said you can run the query just fine -- did you just try on
commandline, or can you run the query in a script by itself?

What happens if you run the script to echo all the SQL commands into a
text file, and then source the text file from the mysql commandline
prompt?  Same error?

Are the script and the host on the same machine?  Is it using TCP/IP
to connect, or a unix socket?  Is there any firewalling in place?

Does anyone else have admin privileges to the database?  They might be
manually killing the query, if it hangs up.  (I've had this done to
me, where an admin kept killing long queries without asking folks who
was doing them).

Are you working on an InnoDB table?  Try turning on the InnoDB monitor
while the query runs and see if you're getting any deadlocking. 
http://dev.mysql.com/doc/refman/5.0/en/innodb-monitor.html


-Sheeri


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...

:)
Sander.
--
| Depression is merely anger without enthusiasm.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

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




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

Re: MySQL server has gone away. Suddenly.

[Kishore Jalleda]

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]

Re: DBD::mysql::st execute failed: MySQL server has gone away

[Luke Vanderfluit]

Ravi Prasad LR wrote:


Luke,

 


Yup. Basically if I do a particular query from the command line,
I get the following error:
===
InnoDB: Error: tried to read 16384 bytes at offset 1 3469819904.
InnoDB: Was only able to read -1.
060327  8:25:41  InnoDB: Operating system error number 5 in a file
operation.
InnoDB: Error number 5 means 'I/O error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
060327 08:25:41  mysqld restarted
060327  8:25:42  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060327  8:25:42  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 2096716847.
InnoDB: Doing recovery: scanned up to log sequence number 2 2096716847
InnoDB: Last MySQL binlog file position 0 79, file name
./ticketdb-bin.15
060327  8:25:42  InnoDB: Flushing modified pages from the buffer pool...
060327  8:25:42  InnoDB: Started; log sequence number 2 2096716847
/opt/csw/mysql4/libexec/mysqld: ready for connections.
Version: '4.1.18-log'  socket: '/tmp/mysql.sock'  port: 3306  Source
distribution
   



It looks like your disk is having problems.What does 'dmesg' 
or /var/log/messages  say
 


You're right it was the disk.
Kind regards.
Luke.


Thanks,
Ravi 




 




--
Luke

Re: DBD::mysql::st execute failed: MySQL server has gone away

[sheeri kritzer]

What happens if you try to connect to the database on the commandline?

-Sheeri

On 3/24/06, Luke Vanderfluit [EMAIL PROTECTED] wrote:
 Hi.

 I'm getting the following error running apache2 with modperl, mysql
 4.1.18 and RT 3.4.5
 *error:*DBD::mysql::st execute failed: MySQL server has gone away at
 /usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm
 line 70.
 *context:*
 *...*
 *66:*   if ($self-{lock}) {
 *67:*   local $self-{dbh}-{RaiseError} = 1;
 *68:*
 *69:*   my $sth = $self-{dbh}-prepare_cached(q{SELECT
 RELEASE_LOCK(?)}, {}, 1);
 *70:*   $sth-execute($self-{lockid});
 *71:*
 *72:*   $self-{lock} = 0;
 *73:*   }
 *74:*   }
 *...*

 *code stack:*
 /usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:70
 /usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:81
 /usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:87
 /usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/HTML/Mason/Request.pm:1249


 If anyone can help, I'd appreciate it.
 Kind regards.

 --
 Luke




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

Re: DBD::mysql::st execute failed: MySQL server has gone away

[Luke Vanderfluit]

Hi Sheeri.

sheeri kritzer wrote:


What happens if you try to connect to the database on the commandline?
 


Yup. Basically if I do a particular query from the command line,
I get the following error:
===
InnoDB: Error: tried to read 16384 bytes at offset 1 3469819904.
InnoDB: Was only able to read -1.
060327  8:25:41  InnoDB: Operating system error number 5 in a file 
operation.

InnoDB: Error number 5 means 'I/O error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
060327 08:25:41  mysqld restarted
060327  8:25:42  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060327  8:25:42  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 2096716847.
InnoDB: Doing recovery: scanned up to log sequence number 2 2096716847
InnoDB: Last MySQL binlog file position 0 79, file name 
./ticketdb-bin.15

060327  8:25:42  InnoDB: Flushing modified pages from the buffer pool...
060327  8:25:42  InnoDB: Started; log sequence number 2 2096716847
/opt/csw/mysql4/libexec/mysqld: ready for connections.
Version: '4.1.18-log'  socket: '/tmp/mysql.sock'  port: 3306  Source 
distribution

=

Your help is appreciated.
Thanks.
Kind regards.
Luke



-Sheeri

On 3/24/06, Luke Vanderfluit [EMAIL PROTECTED] wrote:
 


Hi.

I'm getting the following error running apache2 with modperl, mysql
4.1.18 and RT 3.4.5
*error:*DBD::mysql::st execute failed: MySQL server has gone away at
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm
line 70.
*context:*
*...*
*66:*   if ($self-{lock}) {
*67:*   local $self-{dbh}-{RaiseError} = 1;
*68:*
*69:*   my $sth = $self-{dbh}-prepare_cached(q{SELECT
RELEASE_LOCK(?)}, {}, 1);
*70:*   $sth-execute($self-{lockid});
*71:*
*72:*   $self-{lock} = 0;
*73:*   }
*74:*   }
*...*

*code stack:*
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:70
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:81
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:87
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/HTML/Mason/Request.pm:1249


If anyone can help, I'd appreciate it.
Kind regards.

--
Luke



   



 




--
Luke

Re: DBD::mysql::st execute failed: MySQL server has gone away

[Ravi Prasad LR]

Luke,

 Yup. Basically if I do a particular query from the command line,
 I get the following error:
 ===
 InnoDB: Error: tried to read 16384 bytes at offset 1 3469819904.
 InnoDB: Was only able to read -1.
 060327  8:25:41  InnoDB: Operating system error number 5 in a file
 operation.
 InnoDB: Error number 5 means 'I/O error'.
 InnoDB: Some operating system error numbers are described at
 InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
 InnoDB: File operation call: 'read'.
 InnoDB: Cannot continue operation.
 060327 08:25:41  mysqld restarted
 060327  8:25:42  InnoDB: Database was not shut down normally!
 InnoDB: Starting crash recovery.
 InnoDB: Reading tablespace information from the .ibd files...
 InnoDB: Restoring possible half-written data pages from the doublewrite
 InnoDB: buffer...
 060327  8:25:42  InnoDB: Starting log scan based on checkpoint at
 InnoDB: log sequence number 2 2096716847.
 InnoDB: Doing recovery: scanned up to log sequence number 2 2096716847
 InnoDB: Last MySQL binlog file position 0 79, file name
 ./ticketdb-bin.15
 060327  8:25:42  InnoDB: Flushing modified pages from the buffer pool...
 060327  8:25:42  InnoDB: Started; log sequence number 2 2096716847
 /opt/csw/mysql4/libexec/mysqld: ready for connections.
 Version: '4.1.18-log'  socket: '/tmp/mysql.sock'  port: 3306  Source
 distribution

It looks like your disk is having problems.What does 'dmesg' 
or /var/log/messages  say.

Thanks,
Ravi 



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

DBD::mysql::st execute failed: MySQL server has gone away

[Luke Vanderfluit]

Hi.

I'm getting the following error running apache2 with modperl, mysql 
4.1.18 and RT 3.4.5
*error:*  	DBD::mysql::st execute failed: MySQL server has gone away at 
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm 
line 70.

*context:*  
*...*   
*66:*   if ($self-{lock}) {
*67:*   local $self-{dbh}-{RaiseError} = 1;
*68:*   
*69:*  	my $sth = $self-{dbh}-prepare_cached(q{SELECT 
RELEASE_LOCK(?)}, {}, 1);

*70:*   $sth-execute($self-{lockid});
*71:*   
*72:*   $self-{lock} = 0;
*73:*   }
*74:*   }
*...*   

*code stack:*  
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:70

/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:81
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/Apache/Session/Lock/MySQL.pm:87
/usr/local/stow/perl-5.8.7/lib/site_perl/5.8.7/HTML/Mason/Request.pm:1249


If anyone can help, I'd appreciate it.
Kind regards.

--
Luke

Re: MySQL server has gone away ??

[Gleb Paharenko]

Hello.



See:

  http://dev.mysql.com/doc/refman/5.0/en/gone-away.html



 Any reason why this happens? Should I be worried?=20



You have an old MySQL version (4.1.8), upgrade to the latest release.





Jørn Dahl-Stamnes wrote:

 I have been using mysql client for some time when I got this error:

 

 mysql select * from mytable;

 ERROR 2006 (HY000): MySQL server has gone away

 No connection. Trying to reconnect...

 ERROR 1045 (28000): Access denied for user 'username'@'my.ip.addr' (usi=

 ng=20

 password: YES)

 ERROR:

 Can't connect to the server

 

 mysql quit

 Bye

 $ mysql -h sql -u sqluser -p

 Enter password:

 Welcome to the MySQL monitor.  Commands end with ; or \g.

 Your MySQL connection id is 6669 to server version: 4.1.8-standard

 

 

 MySQL is running on a server and I have to go through a firewall to reach i=

 t.

 Any reason why this happens? Should I be worried?=20

 

 =2D-=20

 J=F8rn Dahl-Stamnes

 homepage: http://www.dahl-stamnes.net/dahls/

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




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

MySQL server has gone away ??

[Jørn Dahl-Stamnes]

I have been using mysql client for some time when I got this error:

mysql select * from mytable;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 1045 (28000): Access denied for user 'username'@'my.ip.addr' (using 
password: YES)
ERROR:
Can't connect to the server

mysql quit
Bye
$ mysql -h sql -u sqluser -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 6669 to server version: 4.1.8-standard


MySQL is running on a server and I have to go through a firewall to reach it.
Any reason why this happens? Should I be worried? 

-- 
Jørn Dahl-Stamnes
homepage: http://www.dahl-stamnes.net/dahls/

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

RE: MySQL server has gone away

[Kraer, Joseph]

Thank you for your help, Shawn.  I had to dig a little, but I found the
way to set the global variable to a larger size and was able to complete
my restore.

 

I may yet get the hang of this.  :-)

Joseph Tito Kraer 
Business Systems Analyst 
Taylor, Bean  Whitaker Mortgage Corp 





From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 16, 2005 4:39 PM
To: Kraer, Joseph
Cc: mysql@lists.mysql.com
Subject: Re: MySQL server has gone away

 



Kraer, Joseph [EMAIL PROTECTED] wrote on 11/16/2005 04:17:17 PM:

 First let me say that I'm a newbie and that I've seen a few instances
of
 this error in the list, but I haven't seen my case.
 
 I'm running WAMP5, v. 1.4.4.  I'm trying to restore an Eventum v. 1.4
 backup done with mysqldump in a LAMP machine.  The restoration process
 invariably stops at line 517.  I've split the 4.19GB backup file into
 16MB portions for easy view and looked at the first file portion in
 WordPad.  There's nothing esoteric in the neighborhood of line 517.
 I've tried to do this restoration through the following command line:
 shell mysql -uusername -ppassword eventum  sourcefile.sql.  The
 process also bombs out if I try to use MySQL Administrator.
 
 Any suggestions?
 
 Joseph Tito Kraer
 Business Systems Analyst
 Taylor, Bean  Whitaker Mortgage Corp
 

I saw that error frequently until I discovered what the
max_allowed_packet setting was for. It sounds as though you have an
extended insert command at that location of your file and that the
length of the command exceeds the max_allowed_packet setting. 

SHOW VARIALBES LIKE 'max%'; 

Reset it to meet or exceed the largest INSERT command in your dump
files. 

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine

MySQL server has gone away

[Kraer, Joseph]

First let me say that I'm a newbie and that I've seen a few instances of
this error in the list, but I haven't seen my case.

I'm running WAMP5, v. 1.4.4.  I'm trying to restore an Eventum v. 1.4
backup done with mysqldump in a LAMP machine.  The restoration process
invariably stops at line 517.  I've split the 4.19GB backup file into
16MB portions for easy view and looked at the first file portion in
WordPad.  There's nothing esoteric in the neighborhood of line 517.
I've tried to do this restoration through the following command line:
shell mysql -uusername -ppassword eventum  sourcefile.sql.  The
process also bombs out if I try to use MySQL Administrator.

Any suggestions?

Joseph Tito Kraer
Business Systems Analyst
Taylor, Bean  Whitaker Mortgage Corp
1417 N Magnolia Avenue
Ocala, FL 34470
Ph. 352-671-0678
Fax 352-671-0778
Int. x11678

For change requests, enhancements, or design changes, please email
Business Systems at [EMAIL PROTECTED]

For all support issues, please contact Application Support at
[EMAIL PROTECTED] or call 352-671-0262 (internal ext.
11262).



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

Re: MySQL server has gone away

[SGreen]

Kraer, Joseph [EMAIL PROTECTED] wrote on 11/16/2005 04:17:17 PM:

 First let me say that I'm a newbie and that I've seen a few instances of
 this error in the list, but I haven't seen my case.
 
 I'm running WAMP5, v. 1.4.4.  I'm trying to restore an Eventum v. 1.4
 backup done with mysqldump in a LAMP machine.  The restoration process
 invariably stops at line 517.  I've split the 4.19GB backup file into
 16MB portions for easy view and looked at the first file portion in
 WordPad.  There's nothing esoteric in the neighborhood of line 517.
 I've tried to do this restoration through the following command line:
 shell mysql -uusername -ppassword eventum  sourcefile.sql.  The
 process also bombs out if I try to use MySQL Administrator.
 
 Any suggestions?
 
 Joseph Tito Kraer
 Business Systems Analyst
 Taylor, Bean  Whitaker Mortgage Corp
 1417 N Magnolia Avenue
 Ocala, FL 34470
 Ph. 352-671-0678
 Fax 352-671-0778
 Int. x11678
 
 For change requests, enhancements, or design changes, please email
 Business Systems at [EMAIL PROTECTED]
 
 For all support issues, please contact Application Support at
 [EMAIL PROTECTED] or call 352-671-0262 (internal ext.
 11262).
 

I saw that error frequently until I discovered what the max_allowed_packet 
setting was for. It sounds as though you have an extended insert command 
at that location of your file and that the length of the command exceeds 
the max_allowed_packet setting.

SHOW VARIALBES LIKE 'max%';

Reset it to meet or exceed the largest INSERT command in your dump files.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine

Re: MySQL server has gone away error?

[Gleb Paharenko]

Hello.



Check your MySQL error log. Sever could die during the query.

See:

  http://dev.mysql.com/doc/mysql/en/gone-away.html





Michael [EMAIL PROTECTED] wrote:

 I'm using PHP with MySQL to save files uploaded by users (up to 50MB) to 

 a database. I'm having problems getting MySQL to handle this much data 

 in a single query I guess.

 

 I was getting a *max allowed packet error so I raised that. Now I get a 

 MySQL server has gone away error. Can anyone tell me which setting I 

 probably need to change to make this work? Thanks.

 *

 

 --

 Michael [EMAIL PROTECTED]

 http://kavlon.org

 

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




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

MySQL server has gone away error?

[Michael]

I'm using PHP with MySQL to save files uploaded by users (up to 50MB) to 
a database. I'm having problems getting MySQL to handle this much data 
in a single query I guess.


I was getting a *max allowed packet error so I raised that. Now I get a 
MySQL server has gone away error. Can anyone tell me which setting I 
probably need to change to make this work? Thanks.

*

--
Michael [EMAIL PROTECTED]
http://kavlon.org


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

Re: help please : ERROR 2006: MySQL server has gone away

[Gleb Paharenko]

Hello.



4.0.17 is old enough. You may switch to the debug version and attempt to

find the clues in debug or trace files. Can you reproduce an error on the

latest release (4.1.9 now)? Do you lost connection to the server with

other statements, than 'SHOW DATABASES'? Please answer on this questions:

 -What operating system do you use?

 -Do you use official binaries?





[snip]

We still have the problem...

In the error log, I have nothing about problem. I only have that:

050203 00:34:14  mysqld started

/u01/mysql/libexec/mysqld: ready for connections.

Version: '4.0.17-log'  socket: '/tmp/mysql.sock'  port: 3306

 If I do show variables, I have max_allowed_packet = 16776192

IF I log into mysql with :mysql -uroot --max_allowed_packet=16M  -p



After I do:show databases; and I receive the answer.

After I wait 30 sec and launch the command show databases; again  and now I 
have the

error:



ERROR 2006: MySQL server has gone away

No connection. Trying to reconnect...

Marois, David [EMAIL PROTECTED] wrote:

[snip]

Marois, David [EMAIL PROTECTED] wrote:



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




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

Re: help please : ERROR 2006: MySQL server has gone away

[Gleb Paharenko]

Hello.



Does the problem remain? What is in the error log? Please, send

us information about MySQL and operating system versions. There are

two variables: max_allowed_packet - one has client, another has server.

Run mysql with --max_allowed_packet=16M and mysqld with the same value.

May be you have some ulimits which cause such behaviour? 





[snip]

And 

max_allowed_packet  = 16776192 

David

Hi, 

my interactive_timeout variable is

interactive_timeout 3600

  Thanks !Marois, David [EMAIL PROTECTED] wrote:

[snip]



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




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

help please : ERROR 2006: MySQL server has gone away

[Marois, David]

We still have the problem...
 
In the error log, I have nothing about problem. I only have that:
050203 00:34:14  mysqld started
/u01/mysql/libexec/mysqld: ready for connections.
Version: '4.0.17-log'  socket: '/tmp/mysql.sock'  port: 3306
 
If I do show variables, I have max_allowed_packet = 16776192
 
IF I log into mysql with :mysql -uroot --max_allowed_packet=16M  -p
 
After I do:show databases; and I receive the answer.
After I wait 30 sec and launch the command show databases; again  and now I 
have the error:
 
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
 
 
David 
 

 
Hello.
 
Does the problem remain? What is in the error log? Please, send
us information about MySQL and operating system versions. There are
two variables: max_allowed_packet - one has client, another has server.
Run mysql with --max_allowed_packet=16M and mysqld with the same value.
May be you have some ulimits which cause such behaviour? 

 
-Message d'origine-
De : Marois, David 
Envoyé : 2 février, 2005 09:16
À : 'mysql@lists.mysql.com'
Objet : Re: help please : ERROR 2006: MySQL server has gone away


And 
 
max_allowed_packet  = 16776192 
 
 
David

 
Hi, 
my interactive_timeout variable is
 
interactive_timeout 3600
 
Thanks !
 
David
 
 
Hello.
 
I've asked you about interactive_timeout, not wait_timeout.
 

Mark [EMAIL PROTECTED] wrote:
 -Original Message-
 From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
 
 Sent: woensdag 2 februari 2005 12:46
 To: [EMAIL PROTECTED]
 Subject: Re: help please : ERROR 2006: MySQL server has gone away
 
 Hello.
 
 What's the value of the interactive_timeout system variable? See:
 http://dev.mysql.com/doc/mysql/en/server-system-variables.html
 http://dev.mysql.com/doc/mysql/en/gone-away.html
 
 I believe he already answered that in part:
 
  Also, my variable wait_timeout = 3600.
 
 1 hour, that is, instead of the default 8 (28800).
 
 - Mark
 
 

 
David Marois
 mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
 

Re: help please : ERROR 2006: MySQL server has gone away

[Michael Dykman]

So far, you have only showed us the client-view of the problem..  look
in you data directories on the server machine... there is likely an
error file there which should give you some insight (unless permissions
for that directory are seriously messed up).  IF there is no error file,
determine which user MySQL is running as (default: mysql) and confirm
that user has read/write permissions to that directory and
subdirectories.

There are a few misconfigurations which take MySQL a bit of time to fail
on.. I know I had similar results last summer doing a manual
source-install of MySQL 4.1 which was related to the data-directory
permissions.. Having sorted it out, the server has been extremely stable
under heavy load for several continuous months now.

 - michael dykman


On Thu, 2005-02-03 at 08:38, Marois, David wrote:
 We still have the problem...
  
 In the error log, I have nothing about problem. I only have that:
 050203 00:34:14  mysqld started
 /u01/mysql/libexec/mysqld: ready for connections.
 Version: '4.0.17-log'  socket: '/tmp/mysql.sock'  port: 3306
  
 If I do show variables, I have max_allowed_packet = 16776192
  
 IF I log into mysql with :mysql -uroot --max_allowed_packet=16M  -p
  
 After I do:show databases; and I receive the answer.
 After I wait 30 sec and launch the command show databases; again  and now I 
 have the error:
  
 ERROR 2006: MySQL server has gone away
 No connection. Trying to reconnect...
  
 
 David 
  
 
  
 Hello.
  
 Does the problem remain? What is in the error log? Please, send
 us information about MySQL and operating system versions. There are
 two variables: max_allowed_packet - one has client, another has server.
 Run mysql with --max_allowed_packet=16M and mysqld with the same value.
 May be you have some ulimits which cause such behaviour? 
 
  
 -Message d'origine-
 De : Marois, David 
 Envoy : 2 fvrier, 2005 09:16
  : 'mysql@lists.mysql.com'
 Objet : Re: help please : ERROR 2006: MySQL server has gone away
 
 
 And 
  
 max_allowed_packet  = 16776192 
  
 
 David
 
  
 Hi, 
 my interactive_timeout variable is
  
 interactive_timeout 3600
  
 Thanks !
  
 David
  
 
 Hello.
  
 I've asked you about interactive_timeout, not wait_timeout.
  
 
 Mark [EMAIL PROTECTED] wrote:
  -Original Message-
  From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
  
  Sent: woensdag 2 februari 2005 12:46
  To: [EMAIL PROTECTED]
  Subject: Re: help please : ERROR 2006: MySQL server has gone away
  
  Hello.
  
  What's the value of the interactive_timeout system variable? See:
  http://dev.mysql.com/doc/mysql/en/server-system-variables.html
  http://dev.mysql.com/doc/mysql/en/gone-away.html
  
  I believe he already answered that in part:
  
   Also, my variable wait_timeout = 3600.
  
  1 hour, that is, instead of the default 8 (28800).
  
  - Mark
  
  
 
  
 David Marois
  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
  
-- 
 - michael dykman
 - [EMAIL PROTECTED]


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

RE : help please : ERROR 2006: MySQL server has gone away

[Marois, David]

Hi Michael,
Yesterday, I restarted the server and the mysql database.
And In the errorlog, I only have 
050203 00:34:14 mysqld started
/u01/mysql/libexec/mysqld: ready for connections.
Version: '4.0.17-log' socket: '/tmp/mysql.sock' port: 3306

Also, I verified and my mysql user have access to write into my errorlog file 
and in my directories.

David

David Marois
-Message d'origine-
De : Michael Dykman [mailto:[EMAIL PROTECTED] 
Envoyé : 3 février, 2005 10:02
À : Marois, David
Cc : MySQL List
Objet : Re: help please : ERROR 2006: MySQL server has gone away


So far, you have only showed us the client-view of the problem..  look
in you data directories on the server machine... there is likely an
error file there which should give you some insight (unless permissions
for that directory are seriously messed up).  IF there is no error file,
determine which user MySQL is running as (default: mysql) and confirm
that user has read/write permissions to that directory and
subdirectories.

There are a few misconfigurations which take MySQL a bit of time to fail
on.. I know I had similar results last summer doing a manual
source-install of MySQL 4.1 which was related to the data-directory
permissions.. Having sorted it out, the server has been extremely stable
under heavy load for several continuous months now.

 - michael dykman


On Thu, 2005-02-03 at 08:38, Marois, David wrote:
 We still have the problem...
  
 In the error log, I have nothing about problem. I only have that:
 050203 00:34:14  mysqld started
 /u01/mysql/libexec/mysqld: ready for connections.
 Version: '4.0.17-log'  socket: '/tmp/mysql.sock'  port: 3306
  
 If I do show variables, I have max_allowed_packet = 16776192
  
 IF I log into mysql with :mysql -uroot --max_allowed_packet=16M  -p
  
 After I do:show databases; and I receive the answer.
 After I wait 30 sec and launch the command show databases; again  and now I 
 have the error:
  
 ERROR 2006: MySQL server has gone away
 No connection. Trying to reconnect...
  
 
 David 
  
 
  
 Hello.
  
 Does the problem remain? What is in the error log? Please, send
 us information about MySQL and operating system versions. There are
 two variables: max_allowed_packet - one has client, another has server.
 Run mysql with --max_allowed_packet=16M and mysqld with the same value.
 May be you have some ulimits which cause such behaviour? 
 
  
 -Message d'origine-
 De : Marois, David 
 Envoyé : 2 février, 2005 09:16
 À : 'mysql@lists.mysql.com'
 Objet : Re: help please : ERROR 2006: MySQL server has gone away
 
 
 And 
  
 max_allowed_packet  = 16776192 
  
 
 David
 
  
 Hi, 
 my interactive_timeout variable is
  
 interactive_timeout 3600
  
 Thanks !
  
 David
  
 
 Hello.
  
 I've asked you about interactive_timeout, not wait_timeout.
  
 
 Mark [EMAIL PROTECTED] wrote:
  -Original Message-
  From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
  
  Sent: woensdag 2 februari 2005 12:46
  To: [EMAIL PROTECTED]
  Subject: Re: help please : ERROR 2006: MySQL server has gone away
  
  Hello.
  
  What's the value of the interactive_timeout system variable? See:
  http://dev.mysql.com/doc/mysql/en/server-system-variables.html
  http://dev.mysql.com/doc/mysql/en/gone-away.html
  
  I believe he already answered that in part:
  
   Also, my variable wait_timeout = 3600.
  
  1 hour, that is, instead of the default 8 (28800).
  
  - Mark
  
  
 
  
 David Marois
  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
  
-- 
 - michael dykman
 - [EMAIL PROTECTED]





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

Re: help please : ERROR 2006: MySQL server has gone away

[Gleb Paharenko]

Hello.



What's the value of the interactive_timeout system variable? See:

  http://dev.mysql.com/doc/mysql/en/server-system-variables.html

  http://dev.mysql.com/doc/mysql/en/gone-away.html





Marois, David [EMAIL PROTECTED] wrote:

 [-- text/plain, encoding 7bit, charset: iso-8859-1, 19 lines --]

 

 Hi,

 I have this error when I am connected in mysql:

 

 ERROR 2006: MySQL server has gone away. No connection. Trying to reconnect...

 

 I only did this command: show databases;

 and received the error.

 

 I noticed that if I don't send a command since 25 sec, I have the error.

 

 Also, my variable wait_timeout = 3600.

 

 Any ideas ?

 

 

 David Marois

 mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

 

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




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

RE: help please : ERROR 2006: MySQL server has gone away

[Mark]

 -Original Message-
 From: Gleb Paharenko [mailto:[EMAIL PROTECTED] 
 Sent: woensdag 2 februari 2005 12:46
 To: mysql@lists.mysql.com
 Subject: Re: help please : ERROR 2006: MySQL server has gone away
 
 Hello.
 
 What's the value of the interactive_timeout system variable? See:
 http://dev.mysql.com/doc/mysql/en/server-system-variables.html
 http://dev.mysql.com/doc/mysql/en/gone-away.html

I believe he already answered that in part:

  Also, my variable wait_timeout = 3600.

1 hour, that is, instead of the default 8 (28800).

- Mark


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

Re: help please : ERROR 2006: MySQL server has gone away

[Gleb Paharenko]

Hello.



I've asked you about interactive_timeout, not wait_timeout.





Mark [EMAIL PROTECTED] wrote:

 -Original Message-

 From: Gleb Paharenko [mailto:[EMAIL PROTECTED] 

 Sent: woensdag 2 februari 2005 12:46

 To: mysql@lists.mysql.com

 Subject: Re: help please : ERROR 2006: MySQL server has gone away

 

 Hello.

 

 What's the value of the interactive_timeout system variable? See:

 http://dev.mysql.com/doc/mysql/en/server-system-variables.html

 http://dev.mysql.com/doc/mysql/en/gone-away.html

 

 I believe he already answered that in part:

 

  Also, my variable wait_timeout = 3600.

 

 1 hour, that is, instead of the default 8 (28800).

 

 - Mark

 

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




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

Re: help please : ERROR 2006: MySQL server has gone away

[Marois, David]

Hi, 
my interactive_timeout variable is
 
interactive_timeout 3600
 
Thanks !
 
David
 
 
Hello.
 
I've asked you about interactive_timeout, not wait_timeout.
 

Mark [EMAIL PROTECTED] wrote:
 -Original Message-
 From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
 
 Sent: woensdag 2 februari 2005 12:46
 To: [EMAIL PROTECTED]
 Subject: Re: help please : ERROR 2006: MySQL server has gone away
 
 Hello.
 
 What's the value of the interactive_timeout system variable? See:
 http://dev.mysql.com/doc/mysql/en/server-system-variables.html
 http://dev.mysql.com/doc/mysql/en/gone-away.html
 
 I believe he already answered that in part:
 
  Also, my variable wait_timeout = 3600.
 
 1 hour, that is, instead of the default 8 (28800).
 
 - Mark
 
 

 
David Marois
 mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
 

Re: help please : ERROR 2006: MySQL server has gone away

[Marois, David]

And 
 
max_allowed_packet  = 16776192 
 
 
David

 
Hi, 
my interactive_timeout variable is
 
interactive_timeout 3600
 
Thanks !
 
David
 
 
Hello.
 
I've asked you about interactive_timeout, not wait_timeout.
 

Mark [EMAIL PROTECTED] wrote:
 -Original Message-
 From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
 
 Sent: woensdag 2 februari 2005 12:46
 To: [EMAIL PROTECTED]
 Subject: Re: help please : ERROR 2006: MySQL server has gone away
 
 Hello.
 
 What's the value of the interactive_timeout system variable? See:
 http://dev.mysql.com/doc/mysql/en/server-system-variables.html
 http://dev.mysql.com/doc/mysql/en/gone-away.html
 
 I believe he already answered that in part:
 
  Also, my variable wait_timeout = 3600.
 
 1 hour, that is, instead of the default 8 (28800).
 
 - Mark
 
 

 
David Marois
 mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
 

help please : ERROR 2006: MySQL server has gone away

[Marois, David]

Hi,
I have this error when I am connected in mysql:
 
ERROR 2006: MySQL server has gone away. No connection. Trying to reconnect...
 
I only did this command: show databases;
and received the error.
 
I noticed that if I don't send a command since 25 sec, I have the error.
 
Also, my variable wait_timeout = 3600.
 
Any ideas ?
 
 
David Marois
 mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
 

MySQL server has gone away

[goblin]

Hello mysql,

the message MySQL server has gone away appears during
upload to db mediumblob file of size  2M

i tried to set max_allowed_packet=16M in my.cnf
(and it shows me 16M in mysqladmin variables),
but error still appears

any ideas?

used mysql4.1 (mysql3.23.58) on FreeBSD
-- 
Best regards,
 goblin  mailto:[EMAIL PROTECTED]


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

Re: [Error] Mysql server has gone away

[David BORDAS]

hi,

I always have my problem and i didn't find any solution pour the moment.
Please, if somone have an idea ... :(

Thanks
David

Subject: [Error] Mysql server has gone away  3.23.53a
Date: Thu, 19 Dec 2002 17:23:31 +0100

I've some problem with my Mysql servers since the beginning of this week.

I've got plenty of error like this :
Failed to connect to database: Error: Access denied for user:
´[EMAIL PROTECTED]´ to database ´DB1´
MySQL server has gone away
Error Nø1, please contact webmaster ...

In fact, clients are C cgi compiled with libmysql ( in this package
MySQL-devel-3.23.49-1.i386.rpm )
The Cgi is ok and have worked well since several mounths.

Error Nø1 : connection mysql ok, can't execute my query

It seems that mysql disconnect me before i can execute my query.
But query is just after the connection in the code ... :(

Mysql server is always up and didn't gone away any more ...

Server : Linux Redhat
2 * PIII 1 Ghz
1Go ram
Scsi raid 5
mysql-3.23.53a-pc-linux-gnu-i686.tar.gz ( binary )

As you can see, i connect to my server via a 100Mb LAN.
The LAN is ok, all ethernet card are 100Mb Full Duplex without any collision
or packet dropped.
Exemple :

RX packets:259950587 errors:0 dropped:0 overruns:0 frame:0
TX packets:1809122347 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:100
RX bytes:3130833186 (2985.7 Mb)  TX bytes:1637489037 (1561.6 Mb)

Here's the my.cnf :
# The MySQL server
[mysqld]
port= 3306
socket = /tmp/mysql.sock
skip-locking
skip-name-resolve
set-variable= key_buffer=256M
set-variable= back_log=150
set-variable= record_buffer=1M
set-variable= sort_buffer=1M
set-variable= max_allowed_packet=1M
set-variable= thread_stack=128K
set-variable= max_connections=700
set-variable= max_connect_errors=100
set-variable= table_cache=512
set-variable= net_read_timeout=180
set-variable= net_write_timeout=180
set-variable= wait_timeout=3600
set-variable= thread_concurrency=4

I can't see anything in the error log.

Mysqld is still alive and still responding 99% of the time.

Status : Threads: 3  Questions: 3065350  Slow queries: 46  Opens: 91  Flush
tables: 1  Open tables: 66 Queries per second avg: 9.052

Show Status :
Aborted_clients   4401
Aborted_connects374
Bytes_received332129641
Bytes_sent  1691254415
[...]
Created_tmp_disk_tables   0
Created_tmp_tables211
Created_tmp_files 1290
Handler_delete   | 11135  |
Handler_read_first   | 226|
Handler_read_key | 2005755|
Handler_read_next| 1714626349 |
Handler_read_prev| 0  |
Handler_read_rnd | 2613047|
Handler_read_rnd_next| 62634691   |
Handler_update   | 357300 |
Handler_write| 304440 |
Key_blocks_used  | 62869  |
Key_read_requests| 97082717   |
Key_reads| 60114  |
Key_write_requests   | 487582 |
Key_writes   | 392106 |
Max_used_connections | 23 |
Not_flushed_key_blocks   | 0  |
Not_flushed_delayed_rows | 0  |
Open_tables  | 66 |
Open_files   | 102|
Open_streams | 0  |
Opened_tables| 91
Questions| 3065612|
Select_full_join | 0  |
Select_full_range_join   | 0  |
Select_range | 600|
Select_range_check   | 0  |
Select_scan  | 51701  |
Slave_running| OFF|
Slave_open_temp_tables   | 0  |
Slow_launch_threads  | 0  |
Slow_queries | 46 |
Sort_merge_passes| 645|
Sort_range   | 99887  |
Sort_rows| 2613047|
Sort_scan| 20030  |
Table_locks_immediate| 1841001|
Table_locks_waited   | 1977   |
Threads_cached   | 0  |
Threads_created  | 1226346|
Threads_connected| 2  |
Threads_running  | 1  |
Uptime   | 338664

Extract of the mysql.db table :
192.168.10.4 | DB1 | JForvC15 | Y ( select priv ... )


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

[Error] Mysql server has gone away 3.23.53a

[David Bordas]

Hi all,

I've some problem with my Mysql servers since the beginning of this week.

I've got plenty of error like this :
Failed to connect to database: Error: Access denied for user:
´[EMAIL PROTECTED]´ to database ´DB1´
MySQL server has gone away
Error Nø1, please contact webmaster ...

In fact, clients are C cgi compiled with libmysql ( in this package
MySQL-devel-3.23.49-1.i386.rpm )
The Cgi is ok and have worked well since several mounths.

Error Nø1 : connection mysql ok, can't execute my query

It seems that mysql disconnect me before i can execute my query.
But query is just after the connection in the code ... :(

Server : Linux Redhat
2 * PIII 1 Ghz
1Go ram
Scsi raid 5
mysql-3.23.53a-pc-linux-gnu-i686.tar.gz ( binary )

As you can see, i connect to my server via a 100Mb LAN.
The LAN is ok, all ethernet card are 100Mb Full Duplex without any collision
or packet dropped.
Exemple :

RX packets:259950587 errors:0 dropped:0 overruns:0 frame:0
TX packets:1809122347 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:100
RX bytes:3130833186 (2985.7 Mb)  TX bytes:1637489037 (1561.6 Mb)

Here's the my.cnf :
# The MySQL server
[mysqld]
port= 3306
socket = /tmp/mysql.sock
skip-locking
skip-name-resolve
set-variable= key_buffer=256M
set-variable= back_log=150
set-variable= record_buffer=1M
set-variable= sort_buffer=1M
set-variable= max_allowed_packet=1M
set-variable= thread_stack=128K
set-variable= max_connections=700
set-variable= max_connect_errors=100
set-variable= table_cache=512
set-variable= net_read_timeout=180
set-variable= net_write_timeout=180
set-variable= wait_timeout=3600
set-variable= thread_concurrency=4

I can't see anything in the error log.

Mysqld is still alive and still responding 99% of the time.

Status : Threads: 3  Questions: 3065350  Slow queries: 46  Opens: 91  Flush
tables: 1  Open tables: 66 Queries per second avg: 9.052

Show Status :
Aborted_clients   4401
Aborted_connects374
Bytes_received332129641
Bytes_sent  1691254415
[...]
Created_tmp_disk_tables   0
Created_tmp_tables211
Created_tmp_files 1290
Handler_delete   | 11135  |
Handler_read_first   | 226|
Handler_read_key | 2005755|
Handler_read_next| 1714626349 |
Handler_read_prev| 0  |
Handler_read_rnd | 2613047|
Handler_read_rnd_next| 62634691   |
Handler_update   | 357300 |
Handler_write| 304440 |
Key_blocks_used  | 62869  |
Key_read_requests| 97082717   |
Key_reads| 60114  |
Key_write_requests   | 487582 |
Key_writes   | 392106 |
Max_used_connections | 23 |
Not_flushed_key_blocks   | 0  |
Not_flushed_delayed_rows | 0  |
Open_tables  | 66 |
Open_files   | 102|
Open_streams | 0  |
Opened_tables| 91
Questions| 3065612|
Select_full_join | 0  |
Select_full_range_join   | 0  |
Select_range | 600|
Select_range_check   | 0  |
Select_scan  | 51701  |
Slave_running| OFF|
Slave_open_temp_tables   | 0  |
Slow_launch_threads  | 0  |
Slow_queries | 46 |
Sort_merge_passes| 645|
Sort_range   | 99887  |
Sort_rows| 2613047|
Sort_scan| 20030  |
Table_locks_immediate| 1841001|
Table_locks_waited   | 1977   |
Threads_cached   | 0  |
Threads_created  | 1226346|
Threads_connected| 2  |
Threads_running  | 1  |
Uptime   | 338664

Extract of the mysql.db table :
192.168.10.4 | DB1 | JForvC15 | Y ( select priv ... )

Thanks to all.
David


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

ERROR 2006: MySQL server has gone away

[William Blair Wagner]

Hi Gurus,

I'm relatively new to MySQL - been studying it for the past 2 months. So 
far, so good (or Great).

I recently moved from MySQL 3.23.22 to 4.0.2-alpha-debug-log on our 
4.6.1-RELEASE-p10 FreeBSD server. Using the mysql client, I noticed an 
annoying message immediately after every query:

ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id:13

I checked in the error log file and find this repeated, for every 
occurance of this error on my screen:

/usr/local/libexec/mysqld: read looped with error 35, aborting thread

I've checked the variables and settings. All of the timeouts are default.

+--+---+
| Variable_name| Value |
+--+---+
| connect_timeout  | 30|
| delayed_insert_timeout   | 300   |
| flush_time   | 0 |
| innodb_lock_wait_timeout | 50|
| interactive_timeout  | 28800 |
| long_query_time  | 10|
| net_read_timeout | 120   |
| net_write_timeout| 180   |
| slave_net_timeout| 3600  |
| slow_launch_time | 2 |
| timezone | EDT   |
| wait_timeout | 28800 |
+--+---+


If I type queries real fast, immediately after eachother, I don't get 
this error. The error gets logged in the log file exactly 5 seconds 
after a query if I dont' type anything. 5 seconds!!!

I've checked the /etc/my.cnf file and its default. No .my.cnf files to 
worry about.

Any thoughts?


Is this info useful at all:


mysql status;
--
mysql  Ver 12.10 Distrib 4.0.2-alpha, for unknown-freebsdelf4.6 (i386)

Connection id:  10
Current database:   samp_db
Current user:   blairwag@localhost
SSL:Not in use
Current pager:  stdout
Using outfile:  ''
Server version: 4.0.2-alpha-debug-log
Protocol version:   10
Connection: Localhost via UNIX socket
Client characterset:latin1
Server characterset:latin1
UNIX socket:/tmp/mysql.sock
Uptime: 20 min 22 sec

Threads: 1  Questions: 90  Slow queries: 0  Opens: 14  Flush tables: 1 
Open tables: 8  Queries per second avg: 0.074  Memory in use: 46839K 
Max memory used: 46902K

-- 

  William Blair Wagner : Education is not always knowing the answer,
  [EMAIL PROTECTED] : ...but rather knowing where to look for it!



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: ERROR 2006:MySQL server has gone away

[Egor Egorov]

Anil,
Friday, June 28, 2002, 8:57:06 PM, you wrote:

AG I have a table with the following description:
AG mysql describe xoops_groups_modules_link;
AG +-+-+--+-+-+---+
AG | Field   | Type| Null | Key | Default | Extra |
AG +-+-+--+-+-+---+
AG | groupid | int(5)  |  | MUL | 0   |   |
AG | mid | int(5)  |  | | 0   |   |
AG | type| char(1) |  | | |   |
AG +-+-+--+-+-+---+
AG with the folloing contents in it:
AG mysql select * from xoops_groups_modules_link;
AG +-+-+--+
AG | groupid | mid | type |
AG +-+-+--+
AG |   1 |   1 | A|
AG |   1 |   2 | A|
AG |   1 |   1 | R|
AG |   1 |   2 | R|
AG |   2 |   1 | R|
AG |   2 |   2 | R|
AG |   3 |   1 | R|
AG |   3 |   2 | R|
AG +-+-+--+
AG Now, when i run the following query:
AG mysql select * from xoops_groups_modules_link where type='R' and mid=2 and
AG groupid=3 ;
AG ERROR 2006: MySQL server has gone away
AG No connection. Trying to reconnect...
AG Connection id:1
AG Current database: xoops

AG ERROR 2013: Lost connection to MySQL server during query

AG I cant find out why its happening so!!
AG Can someone plz help me.

AG Infact this table is dumped from a dump. If i create a same table by myself
AG and then run the same query it executes fine. Isn't that strange!!

Check your table with CHECK TABLE statement, is there any error in the
output?





-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   ___/   www.mysql.com



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

ERROR 2006: MySQL Server Has Gone Away

[Diego, Emil]

I am having a problem reading a SQL script to recreate a database.  I am
runing mysql 3.23 on Redhat linux 7.2.  The SQL file contains 35 megs worth
of data.  Everytime i try running it to recreate my database from a backup i
get the following error:
ERROR 2006: MySQL server has gone away.

I beleive that it is failing in the same spot.  I have one very large table
that has over 1 meg 
worth of data in a single row.  I beleive that is where the SQL is failing.
Is there anything I can do to modify the configuration to allow large SQL
statements like that to run.



Emil Diego
Web Coordinator
University of Miami School of Business
[EMAIL PROTECTED]
ph: 305.284.5449
fx: 305.284.3404

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: ERROR 2006: MySQL Server Has Gone Away

[James Carrier]

Hello Emil

You need to increase the max packet size that mysql can handle... try 
putting this in your my.cnf file under [mysqld]:

set-variable = max_allowed_packet=5M

and restarting your server (obv. if you're starting mysql from the command 
line use the switch --max_allowed_packet)

james



At 10:35 04/03/2002 -0500, Diego, Emil wrote:
I am having a problem reading a SQL script to recreate a database.  I am
runing mysql 3.23 on Redhat linux 7.2.  The SQL file contains 35 megs worth
of data.  Everytime i try running it to recreate my database from a backup i
get the following error:
ERROR 2006: MySQL server has gone away.

I beleive that it is failing in the same spot.  I have one very large table
that has over 1 meg
worth of data in a single row.  I beleive that is where the SQL is failing.
Is there anything I can do to modify the configuration to allow large SQL
statements like that to run.



Emil Diego
Web Coordinator
University of Miami School of Business
[EMAIL PROTECTED]
ph: 305.284.5449
fx: 305.284.3404

-
Before posting, please check:
http://www.mysql.com/manual.php   (the manual)
http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail 
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

James Carrier

Bullet Online :: Aim Higher [http://www.bulletonline.com]
41b Beavor Lane, London W6 9BL

Tel +44 (0) 20 8834 3442
Fax +44 (0) 20 8741 2790


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

MySQL server has gone away

[Pablo Monti]

Hi, people !
 
I'm having a trouble with a program written in C.
This program try to create a record on a table, and it
receives the 2006 error code, MySQL server has gone
away.
 
I've looked at the MySQL manual, searched the Web but
the solutions posted doesn't worked for me.
 
I've checked the mysqld, and it's up and running.
 
I've runned manually the same INSERT command of the
C program from mysql. It worked and created the record
succesfully.
 
Any help ? Sorry for my poor English :-)
 
Thanks in advance
 
Pablo
 
PD:
 
My MySQL's version is mysql-max-2.23.43 for Linux
(Intel libc6 systems), binary distribution,
downloaded from www.mysql.com I've created my tables
as InnoDB type.
 
The SQL command which fails is:
 
INSERT INTO Merchants ( mer_id, mer_name,
mer_enabled,mer_time_stamp, mer_mti_id, mer_view,
mer_legend1, mer_legend2, mer_legend3, mer_legend4,
mer_legend5,
mer_legend6, mer_legend7, mer_legend8,
mer_ext_int_type, mer_loc_id,
mer_last_update_time_stamp ) VALUES ( '1115',
'Master Card e-commerce prueba', 1, 982006525, '',
'',
'', '', '', '', '', '', '', '', 2, '', 0 )
 
The table descriptions is:
 
CREATE TABLE Merchants (
mer_id CHAR (16) NOT NULL,
mer_name   CHAR (30) NOT NULL,
mer_enabledSMALLINT(1) UNSIGNED
 NOT NULL,
mer_time_stamp INTEGER NOT NULL,
mer_mti_id CHAR (4) NOT NULL,
mer_view   CHAR (1) NOT NULL,
mer_legend1CHAR (80) NOT NULL,
mer_legend2CHAR (80) NOT NULL,
mer_legend3CHAR (80) NOT NULL,
mer_legend4CHAR (80) NOT NULL,
mer_legend5CHAR (80) NOT NULL,
mer_legend6CHAR (80) NOT NULL,
mer_legend7CHAR (80) NOT NULL,
mer_legend8CHAR (80) NOT NULL,
mer_ext_int_type   SMALLINT NOT NULL,
mer_loc_id CHAR (4) NOT NULL,
mer_last_update_time_stamp INTEGER NOT NULL,
PRIMARY KEY ( mer_id )
)
TYPE = InnoDB
 
My /etc/my.cnf configuration file is as follows:

# Example mysql config file for medium systems.
#
# This is for a system with little memory (32M - 64M)
where MySQL plays
# a important part and systems up to 128M very MySQL
is used together with
# other programs (like a web server)
#
# You can copy this file to
# /etc/mf.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
(in this
# installation this directory is /usr/local/mysql/var)
or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the
program supports.
# If you want to know which options a program support,
run the program
# with --help option.

# The following options will be passed to all MySQL
clients
[client]
#password   = your_password
port= 3306
socket  = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3306
socket  = /tmp/mysql.sock
skip-locking
set-variable= key_buffer=16M
set-variable= max_allowed_packet=1M
set-variable= table_cache=64
set-variable= sort_buffer=512K
set-variable= net_buffer_length=8K
set-variable= myisam_sort_buffer_size=8M
log-bin
server-id   = 1

# Point the following paths to different dedicated
disks
#tmpdir = /tmp/ 
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#set-variable   = bdb_cache_size=4M
#set-variable   = bdb_max_lock=1

# Uncomment the following if you are using Innobase
tables
innodb_data_file_path = ibdata1:400M
innodb_data_home_dir = /usr/local/mysql/innodb/
innodb_log_group_home_dir = /usr/local/mysql/innodb/
innodb_log_arch_dir = /usr/local/mysql/innodb/
set-variable = innodb_mirrored_log_groups=1
set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=5M
set-variable = innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
innodb_log_archive=0
set-variable = innodb_buffer_pool_size=16M
set-variable = innodb_additional_mem_pool_size=2M
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50

[mysqldump]
quick
set-variable= max_allowed_packet=16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not
familiar with SQL
#safe-updates

[isamchk]
set-variable= key_buffer=20M
set-variable= sort_buffer=20M
set-variable= read_buffer=2M
set-variable= write_buffer=2M

[myisamchk]
set-variable= key_buffer=20M
set-variable= sort_buffer=20M
set-variable= read_buffer=2M
set-variable= write_buffer=2M

[mysqlhotcopy]
interactive-timeout


Conectate a Internet GRATIS con Yahoo! Conexión: 
http://conexion.yahoo.com.ar

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com

MySQL server has gone away

[mackenziej]

Description:

In testing a script that I want to put in a cron, the mysqld keeps crashing eachtime I 
run the script to test it.  I've tried substituting in raw numbers for the variables 
in the script, but to no avail.  In attempting to troubleshoot, I logged onto the 
monitor and could duplicate the problem with simple entries.
I can provide any information required.  :)

Offending Lines in Script:
$setdate = $pingsdb-query(insert into sla(date) values('$date'));
$input = $pingsdb-query(update sla set avail1='$availability{1}' and 
packet1='$packetloss{1}' and resp1='$response{1}' where date='$date');

Script Output:
DBD::mysql::st execute failed: MySQL server has gone away at 
/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/Mysql.pm line 172.

MYSQL Logs:
/usr/libexec/ld-elf.so.1: 
/usr/local/bin/new_mysql/mysql-3.23.38-unknown-freebsdelf4.3-i386/bin/mysqld: 
Undefined symbol strtoll
010614 20:32:21  mysqld restarted
010614 20:32:21  Warning: setrlimit returned ok, but didn't change limits. Max open 
files is 1640
010614 20:32:21  Warning: Changed limits: max_connections: 500  table_cache: 565
/usr/local/bin/new_mysql/mysql-3.23.38-unknown-freebsdelf4.3-i386/bin/mysqld: ready 
for connections

How-To-Repeat:

Offending Lines in Script:
$setdate = $pingsdb-query(insert into sla(date) values('$date'));
$input = $pingsdb-query(update sla set avail1='$availability{1}' and 
packet1='$packetloss{1}' and resp1='$response{1}');

MYSQL Logs:
/usr/libexec/ld-elf.so.1: 
/usr/local/bin/new_mysql/mysql-3.23.38-unknown-freebsdelf4.3-i386/bin/mysqld: 
Undefined symbol strt
oll
010614 20:32:21  mysqld restarted
010614 20:32:21  Warning: setrlimit returned ok, but didn't change limits. Max open 
files is 1640
010614 20:32:21  Warning: Changed limits: max_connections: 500  table_cache: 565
/usr/local/bin/new_mysql/mysql-3.23.38-unknown-freebsdelf4.3-i386/bin/mysqld: ready 
for connections

mysql describe sla;
+-++--+-+-+---+
| Field   | Type   | Null | Key | Default | Extra |
+-++--+-+-+---+
| date| date   | YES  | | NULL|   |
| avail0  | float(6,2) | YES  | | NULL|   |
| packet0 | float(6,2) | YES  | | NULL|   |
| resp0   | float(6,2) | YES  | | NULL|   |
| avail1  | float(6,2) | YES  | | NULL|   |
| packet1 | float(6,2) | YES  | | NULL|   |
| resp1   | float(6,2) | YES  | | NULL|   |
| avail2  | float(6,2) | YES  | | NULL|   |
| packet2 | float(6,2) | YES  | | NULL|   |
| resp2   | float(6,2) | YES  | | NULL|   |
| avail3  | float(6,2) | YES  | | NULL|   |
| packet3 | float(6,2) | YES  | | NULL|   |
| resp3   | float(6,2) | YES  | | NULL|   |
| avail4  | float(6,2) | YES  | | NULL|   |
| packet4 | float(6,2) | YES  | | NULL|   |
| resp4   | float(6,2) | YES  | | NULL|   |
+-++--+-+-+---+
16 rows in set (0.00 sec)

mysql insert into sla(avail0,packet0,resp0) values('99.9965','100','38.090643');
Query OK, 1 row affected (0.01 sec)

mysql update sla set avail1='99.9965' and packet1='100' and resp1='38.090643';
ERROR 2013: Lost connection to MySQL server during query

Fix:


Submitter-Id:  submitter ID
Originator:James Mackenzie
Organization:
 
MySQL support: none
Synopsis:  MySQLd crashes when perl script attempts to update table
Severity:  critical
Priority:  medium
Category:  mysql
Class: sw-bug
Release:   mysql-3.22.32 (Source distribution)

Environment:

I'm using the standard build of mysql and perl.

System: FreeBSD tactoo.dco.psi.ca 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Wed Jan 24 
16:14:54 EST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/TACTOO  i386


Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc
GCC: Using builtin specs.
gcc version 2.95.2 19991024 (release)
Compilation info: CC='gcc'  CFLAGS=''  CXX='gcc'  CXXFLAGS=''  LDFLAGS=''
Configure command: ./configure  --with-unix-socket-path=/var/tmp/mysql.sock 
--with-low-memory --with-mit-threads=yes
Perl: This is perl, version 5.005_03 built for i386-freebsd

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

MySQL server has gone away error

[Sean Conley]

I posted a couple of days ago abou this error and got no response, so I am
trying again with a bit more detail this time.  I am running mysql
3.23.28-gamma on a pretty much stock RH 6.2 box.  I am accessing the
database using Perl CGI scripts and the DBI API.  I have reset the
max_allowed_packet and wait_timeout values to 10M and 32 hours
respectively as is suggested in the manual, but this has had no
effect.  Here are the specifics from the error logs:

DBD::mysql::st execute failed: MySQL server has gone away at
/cgi-bin/common/utility.pl line 85.

010109 14:37:27  Aborted connection 265218 to db: '' user: ''
host: `localhost' (Got timeout reading communication packets)
010109 14:37:27  /usr/local/libexec/mysqld: Shutdown Complete

010109 14:37:27  mysqld ended\n


Sean Conley


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php