Strict Standards: Declaration of action_plugin_blog::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/lib/plugins/blog/action.php on line 13

Strict Standards: Declaration of action_plugin_indexmenu::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/lib/plugins/indexmenu/action.php on line 13

Strict Standards: Declaration of action_plugin_importoldchangelog::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/lib/plugins/importoldchangelog/action.php on line 8

Strict Standards: Declaration of action_plugin_importoldindex::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/lib/plugins/importoldindex/action.php on line 8

Strict Standards: Declaration of action_plugin_include::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/lib/plugins/include/action.php on line 19

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/inc/parserutils.php on line 208

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/inc/parserutils.php on line 211

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/inc/parserutils.php on line 421

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/inc/parserutils.php on line 594

Strict Standards: Declaration of cache_instructions::retrieveCache() should be compatible with cache::retrieveCache($clean = true) in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/inc/cache.php on line 291

Deprecated: Function split() is deprecated in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/inc/auth.php on line 154

Strict Standards: Only variables should be passed by reference in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/doku.php on line 73
クラスタエラーログ [開発チーム]

マネージャ

Jun 24 22:31:13 web1 mysqld_safe[2886]: ended
Jun 24 22:31:13 web1 mysqld_safe[2953]: started
Jun 24 22:31:14 web1 mysqld[2956]: 090624 22:31:14  InnoDB: Started; log sequence number 0 43655
Jun 24 22:31:14 web1 mysqld[2956]: 090624 22:31:14 [Note] /usr/sbin/mysqld: ready for connections.
Jun 24 22:31:14 web1 mysqld[2956]: Version: '5.0.32-Debian_7etch10-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution
Jun 24 22:31:14 web1 /etc/mysql/debian-start[2990]: Upgrading MySQL tables if necessary.
Jun 24 22:31:18 web1 /etc/mysql/debian-start[2998]: Checking for crashed MySQL tables.

ノード 1 (131)

Jun 24 22:27:51 db1 mysqld_safe[2965]: ended
Jun 24 22:27:52 db1 mysqld_safe[3010]: started
Jun 24 22:27:53 db1 mysqld[3013]: 090624 22:27:53  InnoDB: Started; log sequence number 0 43655
Jun 24 22:27:53 db1 mysqld[3013]: 090624 22:27:53 [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=db1-relay-bin' to avoid this problem.
Jun 24 22:27:53 db1 mysqld[3013]: 090624 22:27:53 [Note] /usr/sbin/mysqld: ready for connections.
Jun 24 22:27:53 db1 mysqld[3013]: Version: '5.0.32-Debian_7etch10'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution
Jun 24 22:27:53 db1 /etc/mysql/debian-start[3044]: Upgrading MySQL tables if necessary.
Jun 24 22:27:57 db1 /etc/mysql/debian-start[3054]: Checking for crashed MySQL tables.

ノード 2 (132)

Jun 24 22:07:35 m_db2 mysqld_safe[2883]: ended
Jun 24 22:08:28 m_db2 mysqld_safe[2919]: started
Jun 24 22:08:30 m_db2 mysqld[2922]: 090624 22:08:30  InnoDB: Started; log sequence number 0 43655
Jun 24 22:08:32 m_db2 mysqld_safe[2970]: started
Jun 24 22:08:33 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:33 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:33 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:33 m_db2 mysqld[2973]: 090624 22:08:33  InnoDB: Retrying to lock the first data file
Jun 24 22:08:34 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:34 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:34 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:35 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:35 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:35 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:36 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:36 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:36 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:37 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:37 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:37 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:38 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:38 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:38 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:39 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:39 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:39 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:40 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:40 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:40 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:41 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:41 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:41 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:41 m_db2 mysqld[2922]: 090624 22:08: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=m_db2-relay-bin' to avoid this problem.
Jun 24 22:08:42 m_db2 mysqld[2922]: 090624 22:08:42 [Note] /usr/sbin/mysqld: ready for connections.
Jun 24 22:08:42 m_db2 mysqld[2922]: Version: '5.0.32-Debian_7etch10-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution
Jun 24 22:08:42 m_db2 mysqld[2922]: 090624 22:08:42 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000009' at position 4, relay log './m_db2-relay-bin.000003' position: 98
Jun 24 22:08:42 m_db2 mysqld[2922]: 090624 22:08:42 [Note] Slave I/O thread: connected to master 'zero@192.168.0.131:3306',  replication started in log 'mysql-bin.000009' at position 4
Jun 24 22:08:42 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:42 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:42 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:42 m_db2 mysqld[2922]: 090624 22:08:42 [ERROR] Error reading packet from server: Misconfigured master - server id was not set ( server_errno=1236)
Jun 24 22:08:42 m_db2 mysqld[2922]: 090624 22:08:42 [ERROR] Got fatal error 1236: 'Misconfigured master - server id was not set' from master when reading data from binary log
Jun 24 22:08:42 m_db2 mysqld[2922]: 090624 22:08:42 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000009', position 4
Jun 24 22:08:43 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:43 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:43 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:44 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:44 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:44 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:45 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:45 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:45 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:46 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:46 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:46 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:47 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:47 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:47 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:48 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:48 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:48 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:49 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:49 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:49 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:50 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:50 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:50 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:51 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:51 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:51 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:52 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:52 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:52 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:53 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:53 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:53 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:54 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:54 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:54 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:55 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:55 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:55 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:56 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:56 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:56 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:57 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:57 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:57 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:58 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:58 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:58 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:08:59 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:08:59 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:08:59 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:00 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:00 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:00 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:01 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:01 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:01 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:02 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:02 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:02 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:03 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:03 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:03 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:04 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:04 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:04 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:05 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:05 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:05 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:06 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:06 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:06 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:07 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:07 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:07 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:08 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:08 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:08 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:09 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:09 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:09 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:10 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:10 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:10 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:11 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:11 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:11 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:12 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:12 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:12 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:13 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:13 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:13 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:14 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:14 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:14 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:15 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:15 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:15 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:16 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:16 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:16 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:17 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:17 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:17 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:18 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:18 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:18 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:19 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:19 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:19 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:20 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:20 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:20 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:21 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:21 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:21 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:22 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:22 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:22 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:23 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:23 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:23 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:24 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:24 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:24 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:25 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:25 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:25 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:25 m_db2 mysqld[2922]: 090624 22:09:25 [Note] Error reading relay log event: slave SQL thread was killed
Jun 24 22:09:26 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:26 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:26 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:27 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:27 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:27 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:28 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:28 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:28 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:29 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:29 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:29 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:30 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:30 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:30 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:31 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:31 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:31 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:32 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:32 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:32 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:33 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:33 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:33 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:34 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:34 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:34 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:35 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:35 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:35 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:36 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:36 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:36 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:37 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:37 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:37 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:38 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:38 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:38 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:39 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:39 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:39 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:40 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:40 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:40 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:41 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:41 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:41 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:42 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:42 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:42 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:43 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:43 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:43 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:44 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:44 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:44 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:44 m_db2 ntpd[2786]: synchronized to 133.243.238.244, stratum 1
Jun 24 22:09:45 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:45 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:45 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:46 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:46 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:46 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:47 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:47 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:47 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:48 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:48 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:48 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:49 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:49 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:49 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:50 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:50 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:50 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:51 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:51 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:51 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:52 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:52 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:52 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:53 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:53 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:53 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:54 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:54 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:54 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:55 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:55 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:55 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:56 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:56 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:56 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:57 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:57 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:57 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:58 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:58 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:58 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:09:59 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:09:59 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:09:59 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:00 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:00 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:00 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:01 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:01 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:01 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:02 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:02 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:02 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:03 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:03 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:03 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:04 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:04 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:04 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:05 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:05 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:05 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:06 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:06 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:06 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:07 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:07 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:07 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:08 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:08 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:08 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:09 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:09 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:09 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:10 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:10 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:10 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:11 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:11 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:11 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:12 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:12 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:12 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: Unable to lock ./ibdata1, error: 11
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: Check that you do not already have another mysqld process
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: using the same InnoDB data or log files.
Jun 24 22:10:13 m_db2 mysqld[2973]: 090624 22:10:13  InnoDB: Unable to open the first data file
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: Error in opening ./ibdata1
Jun 24 22:10:13 m_db2 mysqld[2973]: 090624 22:10:13  InnoDB: Operating system error number 11 in a file operation.
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: Error number 11 means 'Resource temporarily unavailable'.
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: Some operating system error numbers are described at
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: Could not open or create data files.
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: If you tried to add new data files, and it failed here,
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: you should now edit innodb_data_file_path in my.cnf back
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: to what it was, and remove the new ibdata files InnoDB created
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: in this failed attempt. InnoDB only wrote those files full of
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: zeros, but did not yet use them in any way. But be careful: do not
Jun 24 22:10:13 m_db2 mysqld[2973]: InnoDB: remove old data files which contain your precious data!
Jun 24 22:10:23 m_db2 mysqld[2973]: 090624 22:10:23 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
Jun 24 22:10:23 m_db2 mysqld[2973]: 090624 22:10:23 [ERROR] Do you already have another mysqld server running on port: 3306 ?
Jun 24 22:10:23 m_db2 mysqld[2973]: 090624 22:10:23 [ERROR] Aborting
Jun 24 22:10:23 m_db2 mysqld[2973]:
Jun 24 22:10:24 m_db2 mysqld[2973]: 090624 22:10:24 [Note] /usr/sbin/mysqld: Shutdown 完了
Jun 24 22:10:24 m_db2 mysqld[2973]:
Jun 24 22:10:29 m_db2 mysqld[2973]: Error in my_thread_global_end(): 1 threads didn't exit
Jun 24 22:10:29 m_db2 mysqld_safe[2993]: ended
Jun 24 22:17:02 m_db2 /USR/SBIN/CRON[3023]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 24 22:17:22 m_db2 mysqld[2922]: 090624 22:17:22 [Note] /usr/sbin/mysqld: Normal shutdown
Jun 24 22:17:22 m_db2 mysqld[2922]:
Jun 24 22:17:22 m_db2 mysqld[2922]: 090624 22:17:22  InnoDB: Starting shutdown...
Jun 24 22:17:23 m_db2 mysqld_safe[3145]: started
Jun 24 22:17:26 m_db2 mysqld[2922]: 090624 22:17:26  InnoDB: Shutdown completed; log sequence number 0 43655
Jun 24 22:17:26 m_db2 mysqld[3148]: 090624 22:17:26  InnoDB: Started; log sequence number 0 43655
Jun 24 22:17:26 m_db2 mysqld[2922]: 090624 22:17:26 [Note] /usr/sbin/mysqld: Shutdown 完了
Jun 24 22:17:26 m_db2 mysqld[2922]:
Jun 24 22:17:27 m_db2 mysqld_safe[3172]: ended
Jun 24 22:17:36 m_db2 mysqld[3148]: 090624 22:17:36 [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=m_db2-relay-bin' to avoid this problem.
Jun 24 22:17:37 m_db2 mysqld[3148]: 090624 22:17:37 [Note] /usr/sbin/mysqld: ready for connections.
Jun 24 22:17:37 m_db2 mysqld[3148]: Version: '5.0.32-Debian_7etch10-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution
Jun 24 22:17:37 m_db2 mysqld[3148]: 090624 22:17:37 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000009' at position 4, relay log './m_db2-relay-bin.000001' position: 4
Jun 24 22:17:37 m_db2 mysqld[3148]: 090624 22:17:37 [Note] Slave I/O thread: connected to master 'zero@192.168.0.131:3306',  replication started in log 'mysql-bin.000009' at position 4
Jun 24 22:17:37 m_db2 mysqld[3148]: 090624 22:17:37 [ERROR] Error reading packet from server: Misconfigured master - server id was not set ( server_errno=1236)
Jun 24 22:17:37 m_db2 mysqld[3148]: 090624 22:17:37 [ERROR] Got fatal error 1236: 'Misconfigured master - server id was not set' from master when reading data from binary log
Jun 24 22:17:37 m_db2 mysqld[3148]: 090624 22:17:37 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000009', position 4
Jun 24 22:17:37 m_db2 /etc/mysql/debian-start[3273]: Upgrading MySQL tables if necessary.
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 46: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 69: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 78: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 106: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 116: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 168: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 171: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 172: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 173: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 174: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 178: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 182: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 207: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 212: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 226: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 230: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 244: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 246: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 259: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 262: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 265: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 271: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 274: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 277: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 294: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 297: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 300: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 306: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 309: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 312: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 315: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 318: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 340: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 362: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 366: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 374: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 428: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 516: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 560: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3276]: ERROR 1050 (42S01) at line 562: Table '#sql-c4b_6' は既にあります
Jun 24 22:17:38 m_db2 /etc/mysql/debian-start[3281]: Checking for crashed MySQL tables.
Jun 24 22:19:24 m_db2 ntpd[2786]: no servers reachable
Jun 24 22:20:45 m_db2 ntpd[2786]: synchronized to 133.243.238.244, stratum 1
Jun 24 22:23:13 m_db2 mysqld[3148]: 090624 22:23:13 [Note] Error reading relay log event: slave SQL thread was killed
Jun 24 22:24:28 m_db2 mysqld[3148]: 090624 22:24:28 [Note] /usr/sbin/mysqld: Normal shutdown
Jun 24 22:24:28 m_db2 mysqld[3148]:
Jun 24 22:24:28 m_db2 mysqld[3148]: 090624 22:24:28  InnoDB: Starting shutdown...
Jun 24 22:24:31 m_db2 mysqld[3148]: 090624 22:24:31  InnoDB: Shutdown completed; log sequence number 0 43655
Jun 24 22:24:32 m_db2 mysqld[3148]: 090624 22:24:32 [Note] /usr/sbin/mysqld: Shutdown 完了
Jun 24 22:24:32 m_db2 mysqld[3148]:
Jun 24 22:24:32 m_db2 mysqld_safe[3312]: ended
Jun 24 22:24:33 m_db2 mysqld_safe[3381]: started
Jun 24 22:24:33 m_db2 mysqld[3384]: 090624 22:24:33  InnoDB: Started; log sequence number 0 43655
Jun 24 22:24:44 m_db2 mysqld[3384]: 090624 22:24:44 [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=m_db2-relay-bin' to avoid this problem.
Jun 24 22:24:44 m_db2 mysqld[3384]: 090624 22:24:44 [Note] /usr/sbin/mysqld: ready for connections.
Jun 24 22:24:44 m_db2 mysqld[3384]: Version: '5.0.32-Debian_7etch10-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution
Jun 24 22:24:44 m_db2 mysqld[3384]: 090624 22:24:44 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000010' at position 457, relay log './m_db2-relay-bin.000001' position: 4
Jun 24 22:24:44 m_db2 mysqld[3384]: 090624 22:24:44 [Note] Slave I/O thread: connected to master 'zero@192.168.0.131:3306',  replication started in log 'mysql-bin.000010' at position 457
Jun 24 22:24:44 m_db2 mysqld[3384]: 090624 22:24:44 [ERROR] Error reading packet from server: Misconfigured master - server id was not set ( server_errno=1236)
Jun 24 22:24:44 m_db2 mysqld[3384]: 090624 22:24:44 [ERROR] Got fatal error 1236: 'Misconfigured master - server id was not set' from master when reading data from binary log
Jun 24 22:24:44 m_db2 mysqld[3384]: 090624 22:24:44 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000010', position 457
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3507]: Upgrading MySQL tables if necessary.
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 46: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 69: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 78: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 106: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 116: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 168: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 171: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 172: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 173: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 174: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 178: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 182: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 207: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 212: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 226: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 230: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 244: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 246: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 259: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 262: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 265: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 271: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 274: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 277: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 294: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 297: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 300: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 306: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 309: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 312: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 315: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 318: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 340: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 362: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 366: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 374: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 428: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 516: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 560: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3513]: ERROR 1050 (42S01) at line 562: Table '#sql-d37_6' は既にあります
Jun 24 22:24:45 m_db2 /etc/mysql/debian-start[3515]: Checking for crashed MySQL tables.
Jun 24 22:24:55 m_db2 mysqld[3384]: 090624 22:24:55 [Note] Error reading relay log event: slave SQL thread was killed

m_db2:/var/log# cat /etc/mysql/my.cnf

m_db2:/var/log# cat /etc/mysql/my.cnf
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

#default-character-set=utf8

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/japanese
skip-external-locking

default-storage-engine = NDBCLUSTER
default-character-set=utf8
skip-character-set-client-handshake
set-variable = wait_timeout=1800
set-variable = interactive_timeout=1800

ndbcluster
ndb-connectstring=web1
master-host=db1
master-user=zero
read_only
innodb_support_xa = on
#debug yo ejiri add
log = /tmp/mysql.query.log


#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address           = 127.0.0.1
#
# * Fine Tuning
#
key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 128K
thread_cache_size       = 8
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log            = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log_slow_queries       = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
#server-id              = 1
log_bin                 = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days        = 10
max_binlog_size         = 100M
#binlog_do_db           = include_database_name
#binlog_ignore_db       = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the NDB Data Nodes (ndbd processes)
# not from the NDB Management Nodes (ndb_mgmd processes).
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1

[MYSQL_CLUSTER]
ndb-connectstring=web1

#
# * IMPORTANT: Additional settings that can override those from this file!
#
!includedir /etc/mysql/conf.d/

db1:/var/log# cat /etc/mysql/my.cnf

db1:/var/log# cat /etc/mysql/my.cnf
#
## The MySQL database server configuration file.
##
## You can copy this to one of:
## - "/etc/mysql/my.cnf" to set global options,
## - "~/.my.cnf" to set user-specific options.
##
## One can use all long options that the program supports.
## Run program with --help to get a list of available options and with
## --print-defaults to see which it would actually understand and use.
##
## For explanations see
## http://dev.mysql.com/doc/mysql/en/server-system-variables.html
#
## This will be passed to all mysql clients
## It has been reported that passwords should be enclosed with ticks/quotes
## escpecially if they contain "#" chars...
## Remember to edit /etc/mysql/debian.cnf when changing the socket location.
#[client]
#port            = 3306
#socket          = /var/run/mysqld/mysqld.sock
#
##default-character-set=utf8
#
## Here is entries for some specific programs
## The following values assume you have at least 32M ram
#
## This was formally known as [safe_mysqld]. Both versions are currently parsed.
#[mysqld_safe]
#socket          = /var/run/mysqld/mysqld.sock
#nice            = 0
#
#[mysqld]
##
## * Basic Settings
##
#user            = mysql
#pid-file        = /var/run/mysqld/mysqld.pid
#socket          = /var/run/mysqld/mysqld.sock
#port            = 3306
#basedir         = /usr
#datadir         = /var/lib/mysql
#tmpdir          = /tmp
#language        = /usr/share/mysql/japanese
#skip-external-locking
#
#default-storage-engine = NDBCLUSTER
#default-character-set=utf8
#skip-character-set-client-handshake
#set-variable = wait_timeout=1800
#set-variable = interactive_timeout=1800
#
#ndbcluster
#ndb-connectstring=web1
#master-host=db1
#master-user=zero
#read_only
#innodb_support_xa = on
##debug yo ejiri add
#log = /tmp/mysql.query.log
#
#
##
## Instead of skip-networking the default is now to listen only on
## localhost which is more compatible and is not less secure.
##bind-address           = 127.0.0.1
##
## * Fine Tuning
##
#key_buffer              = 16M
#max_allowed_packet      = 16M
#thread_stack            = 128K
#thread_cache_size       = 8
##max_connections        = 100
##table_cache            = 64
##thread_concurrency     = 10
##
## * Query Cache Configuration
##
#query_cache_limit       = 1M
#query_cache_size        = 16M
##
## * Logging and Replication
##
## Both location gets rotated by the cronjob.
## Be aware that this log type is a performance killer.
##log            = /var/log/mysql/mysql.log
##
## Error logging goes to syslog. This is a Debian improvement :)
##
## Here you can see queries with especially long duration
##log_slow_queries       = /var/log/mysql/mysql-slow.log
##long_query_time = 2
##log-queries-not-using-indexes
##
## The following can be used as easy to replay backup logs or for replication.
##server-id              = 1
#log_bin                 = /var/log/mysql/mysql-bin.log
## WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
#expire_logs_days        = 10
#max_binlog_size         = 100M
##binlog_do_db           = include_database_name
##binlog_ignore_db       = include_database_name
##
## * BerkeleyDB
##
## Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
#skip-bdb
##
## * InnoDB
##
## InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
## Read the manual for more InnoDB related options. There are many!
## You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
##skip-innodb
##
## * Security Features
##
## Read the manual, too, if you want chroot!
## chroot = /var/lib/mysql/
##
## For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
##
## ssl-ca=/etc/mysql/cacert.pem
## ssl-cert=/etc/mysql/server-cert.pem
## ssl-key=/etc/mysql/server-key.pem
#
#
#
#[mysqldump]
#quick
#quote-names
#max_allowed_packet      = 16M
#
#[mysql]
##no-auto-rehash # faster start of mysql but no tab completition
#
#[isamchk]
#key_buffer              = 16M
#
##
## * NDB Cluster
##
## See /usr/share/doc/mysql-server-*/README.Debian for more information.
##
## The following configuration is read by the NDB Data Nodes (ndbd processes)
## not from the NDB Management Nodes (ndb_mgmd processes).
##
## [MYSQL_CLUSTER]
## ndb-connectstring=127.0.0.1
#
#[MYSQL_CLUSTER]
#ndb-connectstring=web1
#
##
## * IMPORTANT: Additional settings that can override those from this file!
##
#!includedir /etc/mysql/conf.d/

zero@prende_db2:~$ cat /etc/mysql/my.cnf

zero@prende_db2:~$ cat /etc/mysql/my.cnf
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

default-character-set=utf8

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/japanese
skip-external-locking

default-storage-engine = NDBCLUSTER
default-character-set=utf8
skip-character-set-client-handshake
set-variable = wait_timeout=1800
set-variable = interactive_timeout=1800


ndbcluster
ndb-connectstring=192.168.0.147


#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address           = 127.0.0.1
#
# * Fine Tuning
#
key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 128K
thread_cache_size       = 8
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log            = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log_slow_queries       = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
#server-id              = 1
log_bin                 = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days        = 10
max_binlog_size         = 100M
#binlog_do_db           = include_database_name
#binlog_ignore_db       = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the NDB Data Nodes (ndbd processes)
# not from the NDB Management Nodes (ndb_mgmd processes).
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1

[MYSQL_CLUSTER]
ndb-connectstring=192.168.0.147


#
# * IMPORTANT: Additional settings that can override those from this file!
#
!includedir /etc/mysql/conf.d/

web1:/etc/mysql# cat ndb_mgmd.cnf

web1:/etc/mysql# cat ndb_mgmd.cnf
# Example Ndbcluster storage engine config file.
#
[ndbd default]
NoOfReplicas= 2
MaxNoOfConcurrentOperations= 10000
DataMemory= 80M
IndexMemory= 24M
TimeBetweenWatchDogCheck= 30000
DataDir= /var/lib/mysql-cluster
MaxNoOfOrderedIndexes= 512
#ServerPort = 63132

[ndb_mgmd default]
DataDir= /var/lib/mysql-cluster

[ndb_mgmd]
Id=1
HostName= web1

[ndbd]
Id= 2
HostName= db1

[ndbd]
Id= 3
HostName= db2

[mysqld]
Id= 4
HostName= db1

[mysqld]
Id= 5
HostName= db2

[mysqld]
#Id= 6

[mysqld]
#Id= 7

# choose an unused port number
# in this configuration 63132, 63133, and 63134
# will be used
[tcp default]
PortNumber= 63132
クラスタエラーログ.txt · 最終更新: 2010/07/27 15:46 (外部編集)
www.chimeric.de Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0

Strict Standards: Only variables should be passed by reference in /var/www/vhosts/w629.ws.domainking.cloud/enjoy-lei.com/dokuwiki/doku.php on line 81