| View previous topic :: View next topic |
| Author |
Message |
spike666
n00b
Joined: 17 Dec 2003
Posts: 70
Location: Brooklyn, NY
|
 Posted: Wed Dec 06, 2006 12:41 am Post subject: mysql crashing when setting up phpmyadmin [SOLVED] |
 |
|
Hey,
So, I've been going through the beginnings of this great Gentoo virtual email howto that I found. When I get up to the part about configuring phpmyadmin, I emerged it without a hitch.
However, when I came to the part about doing the initialization, this happens:
| Code: | fingerbib spike # mysql -u root -p < /usr/share/webapps/phpmyadmin/2.9.1.1/sqlscripts/mysql/2.9.1.1_create.sql
Enter password:
ERROR 2013 (HY000) at line 3: Lost connection to MySQL server during query |
a subsequent attempt shows this:
| Code: | fingerbib spike # mysql -u root -p < /usr/share/webapps/phpmyadmin/2.9.1.1/sqlscripts/mysql/2.9.1.1_create.sql
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) |
After inspecting my mysqld.err log, I see that mysqld is crashing:
| Code: | 061205 19:34:37 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.26-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-5.0.26-r1
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=16777216
read_buffer_size=258048
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation. |
I don't have any issues with my website accessing my databases at all and the machine's got plenty of RAM in it, so I'm sure that's not the problem. I can also access it from the commandline without issues. It only crashes when I try to do the PMA initialization script.
any ideas?
800mhz G4/1.25GB RAM
uname: Linux fingerbib 2.6.10-gentoo-r6 #6 Fri Aug 19 02:30:00 EDT 2005 ppc 7450, altivec supported GNU/Linux
_________________
Spike Grobstein
spike.grobste.in
Last edited by spike666 on Wed Dec 06, 2006 4:30 pm; edited 1 time in total |
|
| Back to top |
|
 |
XenoTerraCide
Veteran
Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA
|
| Posted: Wed Dec 06, 2006 4:30 am Post subject: |
|
|
maybe it's the double quote single qoute path bug. try rebuilding mysql. I ran afoul that bug in amarok. it's in bugzilla but I don't want look it up right now.
basically it's looking for this path.
| Code: |
'/var/run/mysqld/mysqld.sock'
|
like this
| Code: |
"'/var/run/mysqld/mysqld.sock'"
|
so it thinks the ' ' are in the path. the bug was fixed but requires a recompile.
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help. |
|
| Back to top |
|
|
spike666
n00b
Joined: 17 Dec 2003
Posts: 70
Location: Brooklyn, NY
|
| Posted: Wed Dec 06, 2006 4:36 am Post subject: |
|
|
| XenoTerraCide wrote: | | try rebuilding mysql. |
I tried that. I also tried a revdeb-rebuild on mysql (which re-emerged like 3 packages) but to no avail.
once mysql crashes, when I try to start it back up, it says:
| Code: | fingerbib spike # /etc/init.d/mysql restart
* Stopping mysql ...
* Stopping mysqld (0) [ ok ]
* 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) [ ok ] |
so I dunno what else to do. =/
_________________
Spike Grobstein
spike.grobste.in |
|
| Back to top |
|
|
XenoTerraCide
Veteran
Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA
|
| Posted: Wed Dec 06, 2006 4:47 am Post subject: |
|
|
sorry was just a guess... try running it as mysqld with gdb or strace. and see what the show. maybe they will give you some hints 
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help. |
|
| Back to top |
|
|
magic919
Advocate
Joined: 17 Jun 2005
Posts: 2182
Location: Berkshire, UK
|
| Posted: Wed Dec 06, 2006 7:58 am Post subject: |
|
|
| You could try running some of the SQL by hand and see if you can locate the problem bit(s). |
|
| Back to top |
|
|
spike666
n00b
Joined: 17 Dec 2003
Posts: 70
Location: Brooklyn, NY
|
| Posted: Wed Dec 06, 2006 4:33 pm Post subject: |
|
|
ok, I fixed it!
basically, I found that mysqld was bombing out when I ran GRANT SELECT. after googling around a bit, I found a bug posted where a guy was having a similar problem and he attempted to run mysql_fix_privilege_tables which didn't solve it for him.
It did, however, solve it for me.
I assume what happened is that I inadvertently upgraded to mysql 5 and never updated my tables and that's what caused all my problems.
so, thanks guys!
_________________
Spike Grobstein
spike.grobste.in |
|
| Back to top |
|
|
|
Networking & Security
