Re: MySQL server has gone away
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 Haraldwrote: 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
>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 Haraldwrote: 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
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 Nwrote: 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
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 Nwrote: 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
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
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
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
>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
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
>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
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
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
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
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
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
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
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'Ambrosiowrote: > 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 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
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'Ambrosiowrote: 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 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
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 Nwrote: >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
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
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
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
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
'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
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
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
. 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
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
: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
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
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
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...
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
Re: MySQL server has gone away...
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...
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...
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...
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...
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: mysql server has gone away
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]
Re: MySQL server has gone away. Suddenly.
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.
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.
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]
Re: MySQL server has gone away. Suddenly.
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.
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.
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.
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: MySQL server has gone away ??
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]
RE: MySQL server has gone away
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
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 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?
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]