List:General Discussion« Previous MessageNext Message »
From:jitendra ranjan Date:August 19 2010 3:07pm
Subject:Re: MySQL Server has gone away
View as plain text  
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.000001' (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.000001' (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 19:07:46 [Warning] option 'thread_cache_size': unsigned value 33554432 adjusted to
16384
100813 19:07:46 InnoDB: Started; log sequence number 0 44054
100813 19:07:47 [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.
100813 19:07:47 [ERROR] Failed to open the relay log
'/var/run/mysqld/mysqld-relay-bin.000001' (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.000001' (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.prabhat@stripped> wrote:


From: Prabhat Kumar <aim.prabhat@stripped>
Subject: Re: MySQL Server has gone away
To: "Krishna Chandra Prajapati" <prajapatikc@stripped>
Cc: "jitendra ranjan" <jitendra_ranjan@stripped>, mysql@stripped
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 <
prajapatikc@stripped> 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_ranjan@stripped>wrote:
>
> > 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



Thread
MySQL Server has gone awayjitendra ranjan18 Aug
  • Re: MySQL Server has gone awayKrishna Chandra Prajapati19 Aug
    • Re: MySQL Server has gone awayPrabhat Kumar19 Aug
      • Re: MySQL Server has gone awayjitendra ranjan19 Aug
        • Re: MySQL Server has gone awayAnanda Kumar20 Aug
          • Re: MySQL Server has gone awayjitendra ranjan20 Aug
        • Re: MySQL Server has gone awayMySQL)20 Aug