MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) ( 2002 )

richie60

MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) ( 2002 )


MySQL Server Error:
Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) ( 2002 )

出错日记

谁能帮我看看哪里错误和解决方法啊...
谢谢了

每次出错都是重启才可以...
救命啊....

1. 
   
2. 070622 17:16:52 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ns25500-bin' to avoid this problem.
   
3. 070622 17:16:52 [Note] /usr/sbin/mysqld: ready for connections.
   
4. Version: '5.0.21-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  Gentoo Linux mysql-5.0.21
   
5. mysqld got signal 11;
   
6. This could be because you hit a bug. It is also possible that this binary
   
7. or one of the libraries it was linked against is corrupt, improperly built,
   
8. or misconfigured. This error can also be caused by malfunctioning hardware.
   
9. We will try our best to scrape up some info that will hopefully help diagnose
   
10. the problem, but since we have already crashed, something is definitely wrong
    
11. and this may fail.
    
12. 
    
13. key_buffer_size=16777216
    
14. read_buffer_size=258048
    
15. max_used_connections=16
    
16. max_connections=100
    
17. threads_connected=1
    
18. It is possible that mysqld could use up to
    
19. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
    
20. bytes of memory
    
21. Hope that's ok; if not, decrease some variables in the equation.
    
22. 
    
23. thd=0x42709820
    
24. Attempting backtrace. You can use the following information to find out
    
25. where mysqld died. If you see no messages after this, something went
    
26. terribly wrong...
    
27. Cannot determine thread, fp=0x42272468, backtrace may not be correct.
    
28. Stack range sanity check OK, backtrace follows:
    
29. 0x817b070
    
30. 0x40182e87
    
31. 0x8210ea8
    
32. 0x82178c5
    
33. 0x8217ec4
    
34. 0x8217b61
    
35. 0x821c8b5
    
36. 0x81cf8b0
    
37. 0x81d706f
    
38. 0x81dcf51
    
39. 0x81dd5f9
    
40. 0x819213f
    
41. 0x81983b0
    
42. 0x8198b43
    
43. 0x8199904
    
44. 0x819a364
    
45. 0x4017cd51
    
46. 0x403c3e2a
    
47. New value of fp=(nil) failed sanity check, terminating stack trace!
    
48. Please read [url]http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html[/url] and follow instructions on how to resolve the stack trace. Resolved
    
49. stack trace is much more helpful in diagnosing the problem, so please do
    
50. resolve it
    
51. Trying to get some variables.
    
52. Some pointers may be invalid and cause the dump to abort...
    
53. thd->query at 0x872a4b8 = SELECT DISTINCT t.tid FROM pw_posts t WHERE t.fid NOT IN (-999,3,63) AND ifcheck=1 AND t.authorid IN(1181) ORDER BY tid DESC LIMIT 500
    
54. thd->thread_id=25150
    
55. The manual page at [url]http://www.mysql.com/doc/en/Crashing.html[/url] contains
    
56. information that should help you find out what is causing the crash.
    
57. 070625 13:20:12 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ns25500-bin' to avoid this problem.
    
58. 070625 13:20:12 [Note] /usr/sbin/mysqld: ready for connections.
    
59. Version: '5.0.21-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  Gentoo Linux mysql-5.0.21
    
60. mysqld got signal 11;
    
61. This could be because you hit a bug. It is also possible that this binary
    
62. or one of the libraries it was linked against is corrupt, improperly built,
    
63. or misconfigured. This error can also be caused by malfunctioning hardware.
    
64. We will try our best to scrape up some info that will hopefully help diagnose
    
65. the problem, but since we have already crashed, something is definitely wrong
    
66. and this may fail.
    
67. 
    
68. key_buffer_size=16777216
    
69. read_buffer_size=258048
    
70. max_used_connections=10
    
71. max_connections=100
    
72. threads_connected=1
    
73. It is possible that mysqld could use up to
    
74. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
    
75. bytes of memory
    
76. Hope that's ok; if not, decrease some variables in the equation.
    
77. 
    
78. thd=0x42300480
    
79. Attempting backtrace. You can use the following information to find out
    
80. where mysqld died. If you see no messages after this, something went
    
81. terribly wrong...
    
82. Cannot determine thread, fp=0x42272468, backtrace may not be correct.
    
83. Stack range sanity check OK, backtrace follows:
    
84. 0x817b070
    
85. 0x40182e87
    
86. 0x8210ea8
    
87. 0x82178c5
    
88. 0x8217ec4
    
89. 0x8217b61
    
90. 0x821c8b5
    
91. 0x81cf8b0
    
92. 0x81d706f
    
93. 0x81dcf51
    
94. 0x81dd5f9
    
95. 0x819213f
    
96. 0x81983b0
    
97. 0x8198b43
    
98. 0x8199904
    
99. 0x819a364
    
100. 0x4017cd51
     
101. 0x403c3e2a
     
102. New value of fp=(nil) failed sanity check, terminating stack trace!
     
103. Please read [url]http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html[/url] and follow instructions on how to resolve the stack trace. Resolved
     
104. stack trace is much more helpful in diagnosing the problem, so please do
     
105. resolve it
     
106. Trying to get some variables.
     
107. Some pointers may be invalid and cause the dump to abort...
     
108. thd->query at 0x8772958 = SELECT DISTINCT t.tid FROM pw_posts t WHERE t.fid NOT IN (-999,3,63,82) AND ifcheck=1 AND ((t.subject LIKE '%少男少女%' OR t.content LIKE '%少男少女%') ) ORDER BY tid DESC LIMIT 500
     
109. thd->thread_id=6936
     
110. The manual page at [url]http://www.mysql.com/doc/en/Crashing.html[/url] contains
     
111. information that should help you find out what is causing the crash.
     
112. 070625 22:10:35 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ns25500-bin' to avoid this problem.
     
113. 070625 22:10:35 [Note] /usr/sbin/mysqld: ready for connections.
     
114. Version: '5.0.21-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  Gentoo Linux mysql-5.0.21
     
115. mysqld got signal 11;
     
116. This could be because you hit a bug. It is also possible that this binary
     
117. or one of the libraries it was linked against is corrupt, improperly built,
     
118. or misconfigured. This error can also be caused by malfunctioning hardware.
     
119. We will try our best to scrape up some info that will hopefully help diagnose
     
120. the problem, but since we have already crashed, something is definitely wrong
     
121. and this may fail.
     
122. 
     
123. key_buffer_size=16777216
     
124. read_buffer_size=258048
     
125. max_used_connections=10
     
126. max_connections=100
     
127. threads_connected=1
     
128. It is possible that mysqld could use up to
     
129. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
     
130. bytes of memory
     
131. Hope that's ok; if not, decrease some variables in the equation.
     
132. 
     
133. thd=0x42414720
     
134. Attempting backtrace. You can use the following information to find out
     
135. where mysqld died. If you see no messages after this, something went
     
136. terribly wrong...
     
137. Cannot determine thread, fp=0x42272468, backtrace may not be correct.
     
138. Stack range sanity check OK, backtrace follows:
     
139. 0x817b070
     
140. 0x40182e87
     
141. 0x8210ea8
     
142. 0x82178c5
     
143. 0x8217ec4
     
144. 0x8217b61
     
145. 0x821c8b5
     
146. 0x81cf8b0
     
147. 0x81d706f
     
148. 0x81dcf51
     
149. 0x81dd5f9
     
150. 0x819213f
     
151. 0x81983b0
     
152. 0x8198b43
     
153. 0x8199904
     
154. 0x819a364
     
155. 0x4017cd51
     
156. 0x403c3e2a
     
157. New value of fp=(nil) failed sanity check, terminating stack trace!
     
158. Please read [url]http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html[/url] and follow instructions on how to resolve the stack trace. Resolved
     
159. stack trace is much more helpful in diagnosing the problem, so please do
     
160. resolve it
     
161. Trying to get some variables.
     
162. Some pointers may be invalid and cause the dump to abort...
     
163. thd->query at 0x8774350 = SELECT DISTINCT t.tid FROM pw_posts t WHERE t.fid NOT IN (-999,3,63,82) AND ifcheck=1 AND ( (t.subject LIKE '%花样少男少女%' OR t.content LIKE '%花样少男少女%') ) ORDER BY tid DESC LIMIT 500
     
164. thd->thread_id=428
     
165. The manual page at [url]http://www.mysql.com/doc/en/Crashing.html[/url] contains
     
166. information that should help you find out what is causing the crash.
     
167. 070625 22:47:09 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=ns25500-bin' to avoid this problem.
     
168. 070625 22:47:09 [Note] /usr/sbin/mysqld: ready for connections.
     
169. Version: '5.0.21-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  Gentoo Linux mysql-5.0.21
     

复制代码

chenchenlinux

应该是你的mysqld服务没有打开，可以使用以下两种方法：
1、service mysqld start
2、/etc/init.d/mysqld start

richie60

谢谢楼上得回答..
我知道　是这个没有运转了　这样开启..
我发出错日记上来　是想问一下　怎么解决出错得地方..
因为每次出错　都要去重启数据　狠麻烦..