2012-03-27 295 views
4

我在OSX Lion上运行mysql 5.5.22。我的问题是mysqld_safe启动并停止在起始位置像这样。mysqld_safe命令启动然后停止OSX Lion

我输入以下命令:mysqld_safe的

120327 05:33:57 mysqld_safe Logging to '/usr/local/mysql/data/The-BatMobile.local.err'. 
120327 05:33:57 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 

该mysqld_safe的方案已在代码25分钟这段最后一行被拖延了。任何人有想法?我已经完成的谷歌搜索揭示了一些与狮子有关的问题,但没有在这个特定的问题。

编辑//

读取MySQL错误日志后,我发现mysqldsafe可能已经运行表明这种前行的代码:

120327 05:33:57 mysqld_safe Logging to '/usr/local/mysql/data/The-BatMobile.local.err'. 
120327 05:33:57 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 

是我的假设是正确的?

以下是错误日志:

21 120327 11:21:58 mysqld_safe mysqld from pid file /usr/local/mysql/data/the-  batmobile.pid ended 
22 120327 11:23:06 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 
23 120327 11:23:06 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive 
24 120327 11:23:06 [Note] Plugin 'FEDERATED' is disabled. 
25 120327 11:23:06 InnoDB: The InnoDB memory heap is disabled 
26 120327 11:23:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
27 120327 11:23:06 InnoDB: Compressed tables use zlib 1.2.3 
28 120327 11:23:06 InnoDB: Initializing buffer pool, size = 128.0M 
29 120327 11:23:06 InnoDB: Completed initialization of buffer pool 
30 120327 11:23:06 InnoDB: highest supported file format is Barracuda. 
31 120327 11:23:06 InnoDB: Waiting for the background threads to start 
32 120327 11:23:07 InnoDB: 1.1.8 started; log sequence number 1595675 
33 120327 11:23:07 [Note] Event Scheduler: Loaded 0 events 
34 120327 11:23:07 [Note] /usr/local/mysql/bin/mysqld: ready for connections. 
35 Version: '5.5.22' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) 

回答

4

我想我找到了答案,以我自己的问题!

当执行命令mysqld_safe并且'从/ usr/local/mysql/data启动守护进程dbsmon'后没有其他行弹出,它正在工作!

120327 05:33:57 mysqld_safe Logging to '/usr/local/mysql/data/The-BatMobile.local.err'. 
120327 05:33:57 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 

我做了两个测试,以确认这一点:

测试1:mysqld_safe的关

我杀了mysqld_safe的过程,并试图用 “的mysql -u根-p”,并登录它给了我这个错误。

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2): 

测试2:mysqld_safe的:在

它的工作原理!我用“mysql -u root -p”登录并弹出mysql终端!

+0

我还想知道当我输入'sudo。/ mysqld_safe'时发生了什么。我怀疑它正在运行,但找不到下一步该做什么。谢谢(你的)信息! 'sudo ./mysql -u root'是我所需要的mysql CLI。 – 2015-03-10 15:41:35

2

你的回答是正确的 - 这就是mysqld_safe的样子。很高兴你在太疯狂之前就想通了!

要停止mysql而不必手动杀死它,可以使用sudo mysqladmin shutdown

,而不必一个无用的词窗口挂在启动mysql,你可以使用sudo mysqld_safe &这使mysqld在后台运行,你仍然可以使用的词窗口。但是,如果关闭该窗口,它也会杀死mysqld。

应该能够使mysqld的免疫当窗口运行nohup sudo mysqld_safe &关闭垂死但是,这并不为我工作(它在后台启动,但仍然在关闭窗口死亡)。不知道为什么。