Results 1 to 6 of 6
Hi all, ive just upgraded mysql.
The mysql service now wont start.
ps aux | grep "mysql" reports back nothing.
/etc/init.d/mysql start outputs this:
* Starting mysql ...
* Strange, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 09-01-2010 #1Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
[SOLVED] Gentoo Mysql 5.1.50 - ERROR 2002 / Mysql not starting!
Hi all, ive just upgraded mysql.
The mysql service now wont start.
ps aux | grep "mysql" reports back nothing.
/etc/init.d/mysql start outputs this:
* Starting mysql ...
* Strange, the socket file already exist in "/var/run/mysqld/mysqld.sock"
* it will be removed now and re-created by the MySQL server
* BUT please make your checks.
* Starting mysql (/etc/mysql/my.cnf)
Any ideas?
- 09-01-2010 #2
Where is the error?
- 09-01-2010 #3
- 09-02-2010 #4
I think when you upgraded MySQL, you were still running the older version or the newer version found the old "/var/run/mysqld/mysqld.sock" and then deleted it, no harm done.
I do not respond to private messages asking for Linux help, Please keep it on the forums only.
All new users please read this.** Forum FAQS. ** Adopt an unanswered post.
I'd rather be lost at the lake than found at home.
- 09-02-2010 #5Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
Thanks for the help so far!

Sadly I just cant get mysql to run in anyway. Heres some info from /var/log/mysql/mysqld.err:
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133318 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0xa28f5d8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0xbfeaebdc thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x1e) [0x844875a]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=0
thd->killed=NOT_KILLED
The manual page contains
information that should help you find out what is causing the crash.
100902 10:10: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=mysqld-bin' to avoid this problem.
ERROR: 1049 Unknown database 'mysql'
100902 10:10:09 [ERROR] Aborting
100902 10:10:09 [Note] /usr/sbin/mysqld: Shutdown complete
- 09-06-2010 #6Just Joined!
- Join Date
- Sep 2010
- Posts
- 4
SOLVED!!!
The problem is with the -max-128-idx use flag.
I disabled it. Recompiled and now everything is fine.



