forums › forums › Monyog › Using Monyog › Errcode:2006 Errmsg:mysql Server Has Gone Away
- This topic is empty.
-
AuthorPosts
-
-
December 20, 2009 at 10:14 pm #30206
Brad
MemberIn doing a little more diggin, I cannot even locate a file named “ymysql.cpp” on the server (find / -name ymysql.cpp) nor can I locate a directory named “webyog”.
-
December 21, 2009 at 4:41 am #30207
Sayan Chaliha
MemberHey Brad,
“MySQL server has gone away” is generated by the MySQL client library (libmysql) that we use in MONyog. There are several reasons as to why this error occurs. I'd refer you to this blog post (note that it is in two parts), but in brief:
— This error occurs when MySQL does not respond to MONyog's (or any client's, for that matter) query after a successful connection;
— The most common cause in this case is that MySQL's 'wait_timeout' variable is set lower than MONyog's data collection interval. Use the following query to determine your server's 'wait_timeout':
Code:SHOW GLOBAL VARIABLES LIKE 'wait_timeout';— An immediate resolution to your problem would be to increase the 'wait_timeout' of your server:
Code:SET GLOBAL wait_timeout=28800;28800 implies 8 Hrs, which is the default in most MySQL distributions.
— Note that this error doesn't affect MONyog's functionality nor that of MySQL's.
Also, it is improbable that you'd find 'lib/webyog/src/ymysql.cpp' or any other MONyog source file. The error log records the exact line number of the source file that generated the error so that our debugging team knows exactly which part of the source code registered the error.
-
December 21, 2009 at 3:48 pm #30208
Brad
MemberWell, adjusting the wait_timeout parameter in my.cnf seems to have remedied the scenario. Thanks for you assistance.
I would never leave the value set to 8 hours, however, adjusting it to exceed the Data Collection interval abated the error.
Thanks again.
-
-
AuthorPosts
- You must be logged in to reply to this topic.