MySQL broken.

[rmwebs]

Try this:

Fresh copy of the Rasp Pi 'wheezy' build from the official downloads page.

sudo apt-get install mysql-server

It fails. It does install MySQL 5.5, however spits out a bunch of errors when it's finishing the installation, and then refuses to start MySQL at all.

This is on a fresh installation, with an 8GB SD card (so PLENTY of room) on a 512mb Pi (Also tested on a 256mb Pi).

The output of the installation:

Code: Select all

pi@raspberrypi ~ $ sudo apt-get install mysql-server
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  heirloom-mailx libaio1 libdbd-mysql-perl libdbi-perl libhtml-template-perl libmysqlclient16 libnet-daemon-perl libplrpc-perl
  mysql-client-5.5 mysql-common mysql-server-5.5 mysql-server-core-5.5
Suggested packages:
  exim4 mail-transport-agent libipc-sharedcache-perl libterm-readkey-perl tinyca
Recommended packages:
  mailx
The following NEW packages will be installed:
  heirloom-mailx libaio1 libdbd-mysql-perl libdbi-perl libhtml-template-perl libmysqlclient16 libnet-daemon-perl libplrpc-perl
  mysql-client-5.5 mysql-common mysql-server mysql-server-5.5 mysql-server-core-5.5
0 upgraded, 13 newly installed, 0 to remove and 40 not upgraded.
Need to get 9,560 kB of archives.
After this operation, 91.0 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libaio1 armhf 0.3.109-3 [8,944 B]
Get:2 http://mirrordirector.raspbian.org/raspbian/ wheezy/main mysql-common all 5.5.24+dfsg-9 [76.3 kB]
Get:3 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libnet-daemon-perl all 0.48-1 [46.2 kB]
Get:4 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libplrpc-perl all 0.2020-2 [36.0 kB]
Get:5 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libdbi-perl armhf 1.622-1 [895 kB]
Get:6 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libmysqlclient16 armhf 5.1.62-1 [1,828 kB]
Get:7 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libdbd-mysql-perl armhf 4.021-1 [123 kB]
Get:8 http://mirrordirector.raspbian.org/raspbian/ wheezy/main mysql-client-5.5 armhf 5.5.24+dfsg-9 [1,413 kB]
Get:9 http://mirrordirector.raspbian.org/raspbian/ wheezy/main mysql-server-core-5.5 armhf 5.5.24+dfsg-9 [3,021 kB]
Get:10 http://mirrordirector.raspbian.org/raspbian/ wheezy/main mysql-server-5.5 armhf 5.5.24+dfsg-9 [1,714 kB]
Get:11 http://mirrordirector.raspbian.org/raspbian/ wheezy/main heirloom-mailx armhf 12.5-2 [253 kB]                                    
Get:12 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libhtml-template-perl all 2.91-1 [72.0 kB]                              
Get:13 http://mirrordirector.raspbian.org/raspbian/ wheezy/main mysql-server all 5.5.24+dfsg-9 [74.5 kB]                                
Fetched 9,560 kB in 7s (1,329 kB/s)                                                                                                     
Preconfiguring packages ...
Selecting previously unselected package libaio1:armhf.
(Reading database ... 58375 files and directories currently installed.)
Unpacking libaio1:armhf (from .../libaio1_0.3.109-3_armhf.deb) ...
Selecting previously unselected package mysql-common.
Unpacking mysql-common (from .../mysql-common_5.5.24+dfsg-9_all.deb) ...
Selecting previously unselected package libnet-daemon-perl.
Unpacking libnet-daemon-perl (from .../libnet-daemon-perl_0.48-1_all.deb) ...
Selecting previously unselected package libplrpc-perl.
Unpacking libplrpc-perl (from .../libplrpc-perl_0.2020-2_all.deb) ...
Selecting previously unselected package libdbi-perl.
Unpacking libdbi-perl (from .../libdbi-perl_1.622-1_armhf.deb) ...
Selecting previously unselected package libmysqlclient16.
Unpacking libmysqlclient16 (from .../libmysqlclient16_5.1.62-1_armhf.deb) ...
Selecting previously unselected package libdbd-mysql-perl.
Unpacking libdbd-mysql-perl (from .../libdbd-mysql-perl_4.021-1_armhf.deb) ...
Selecting previously unselected package mysql-client-5.5.
Unpacking mysql-client-5.5 (from .../mysql-client-5.5_5.5.24+dfsg-9_armhf.deb) ...
Selecting previously unselected package mysql-server-core-5.5.
Unpacking mysql-server-core-5.5 (from .../mysql-server-core-5.5_5.5.24+dfsg-9_armhf.deb) ...
Processing triggers for man-db ...
Setting up mysql-common (5.5.24+dfsg-9) ...
Selecting previously unselected package mysql-server-5.5.
(Reading database ... 58756 files and directories currently installed.)
Unpacking mysql-server-5.5 (from .../mysql-server-5.5_5.5.24+dfsg-9_armhf.deb) ...
Selecting previously unselected package heirloom-mailx.
Unpacking heirloom-mailx (from .../heirloom-mailx_12.5-2_armhf.deb) ...
Selecting previously unselected package libhtml-template-perl.
Unpacking libhtml-template-perl (from .../libhtml-template-perl_2.91-1_all.deb) ...
Selecting previously unselected package mysql-server.
Unpacking mysql-server (from .../mysql-server_5.5.24+dfsg-9_all.deb) ...
Processing triggers for man-db ...
Processing triggers for menu ...
Setting up libaio1:armhf (0.3.109-3) ...
Setting up libnet-daemon-perl (0.48-1) ...
Setting up libplrpc-perl (0.2020-2) ...
Setting up libdbi-perl (1.622-1) ...
Setting up libmysqlclient16 (5.1.62-1) ...
Setting up libdbd-mysql-perl (4.021-1) ...
Setting up mysql-client-5.5 (5.5.24+dfsg-9) ...
Setting up mysql-server-core-5.5 (5.5.24+dfsg-9) ...
Setting up mysql-server-5.5 (5.5.24+dfsg-9) ...
[ ok ] Stopping MySQL database server: mysqld.
121111 19:52:16 [Note] Plugin 'FEDERATED' is disabled.
121111 19:52:16 InnoDB: The InnoDB memory heap is disabled
121111 19:52:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121111 19:52:16 InnoDB: Compressed tables use zlib 1.2.7
121111 19:52:16 InnoDB: Using Linux native AIO
121111 19:52:16 InnoDB: Initializing buffer pool, size = 128.0M
121111 19:52:16 InnoDB: Completed initialization of buffer pool
121111 19:52:16 InnoDB: highest supported file format is Barracuda.
121111 19:52:17  InnoDB: Waiting for the background threads to start
121111 19:52:18 InnoDB: 1.1.8 started; log sequence number 1595675
121111 19:52:18  InnoDB: Starting shutdown...
121111 19:52:19  InnoDB: Shutdown completed; log sequence number 1595675
[FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.5 (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up heirloom-mailx (12.5-2) ...
update-alternatives: using /usr/bin/heirloom-mailx to provide /usr/bin/mailx (mailx) in auto mode
Setting up libhtml-template-perl (2.91-1) ...
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.5; however:
  Package mysql-server-5.5 is not configured yet.

dpkg: error processing mysql-server (--configure):
 dependency problems - leaving unconfigured
Processing triggers for menu ...
Errors were encountered while processing:
 mysql-server-5.5
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

It's then impossible to run any apt-get commands without MySQL trying to install and failing.

Things I've tried:
- A fresh install (FOUR TIMES)
- A fresh install with a re-downloaded copy of the OS (TWICE)
- Different SD cards (tried a 4GB Sandisk Class 6, a 8GB Sandisk Class 6 and a 16GB PNY MicroSD Class 10
- Rebooting (numerous times)
- apt-get clean
- Modifying the my.cnf to lower the INNODB memory usage

Now, if you do:
sudo /etc/init.d/mysqld restart

It sits for about 15-20 seconds trying to start mysql, then fails with no error provided.

If you do it without sudo, like so:
/etc/init.d/mysqld restart

It says this:

Code: Select all

[FAIL] /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ... failed!

And just to confirm - that the disk is nowhere near full:

Code: Select all

pi@raspberrypi /var/lib $ df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          7.3G  1.5G  5.6G  21% /
/dev/root       7.3G  1.5G  5.6G  21% /
devtmpfs        243M     0  243M   0% /dev
tmpfs            49M  196K   49M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            98M     0   98M   0% /run/shm
/dev/mmcblk0p1   56M   17M   40M  30% /boot

Also tried expanding the rootfs (via the raspi-config gui).

I'm stumped. MySQL just does not work on the Pi at all right now.

Any ideas as to what the hell's happening here?

[simonpb1]

have you tried this as root?
sudo su

[rmwebs]

Yup - no luck with superuser

[lmcc]

I just tried it and it worked for me.

Did your try a

Code: Select all

sudo apt-get update

and

Code: Select all

sudo apt-get upgrade

first?

Now I have MySQL installed and a I'm a Postgres guy...

-L

[rmwebs]

yup, tried that too - still no luck.

Were you able to install it on the latest build (the late-Oct 2012 one) or was it an earlier one? One from earlier in the year was working fine, but the latest one doesn't work at all.

[bgirardot]

I just downloaded the raspbian image 2012-10-28-wheezy-raspbian.zip via bittorrent.

Wrote it to a new SanDisk Ultra 8G SDHC card
expanded the root partition
set the locale
configured my edimax wifi dongle

sudo su
apt-get update
apt-get upgrade
apt-get install mysql-server

and it went just fine.
Mysql is up and running and I can connect to it no problem.

One thing I noticed different between your install log and mine, was mine only had 2 non upgraded packages (which it always has) and yours has 40(?!)

[Narf03]

I have MySQL problem too, but its SD card dependent, last time i uses a Kingston class 4, I manage to install MySQL, but the service sometimes unable to start, now im only using class10(Kingston, PenDrive[brand]) and i no longer having problem with it. Please try some "fast" SD card(some cheapo china made SD card labeled class10 but they work like class4, so test your SD card first).

[rmwebs]

Ok,

Tried this again today on a SD card I pinched from a camera. It is a PNY 4GB class 4 (seemingly, the same type I already tried yesterday) and it worked on that one :/

Something really strange happening there - I know the Pi was selective about SD cards, however branded Sandisk Class 6 ones surely should be ok? It's not like they were nockoffs either - they came from Amazon (and were sold by Amazon - not a marketplace seller).

[bgirardot]

People claim there are counterfeit cards that appear to be exactly real branded cards but are not, sold by reputable retailers who did/do not know the cards they are selling are counterfeit. I have no idea if it is true, but it is possible I suppose.

For kicks I downloaded CrystalDiskMark and am going to test some SD cards just to get a sense of what the different relative speeds of them are. I am sure it is much less than perfect as the "card" speeds are influenced by the USB bus and SD card reader, but I'll see.

[kdiits]

I solved similar use case:
raspi-config -> memory_split: 256 -> 64

Summary:
sudo apt-get remove mysql-server mysql-server-5.5
raspi-config: memory_split: 64
sudo apt-get install mysql-server

[spoon420]

I have been struggling with this problem since I bought my PI for months. I lost rack of how many times I have reinstalled, tried different sd cards, tried updates, tried different versions. Tried changing the password. EVERYTHING GOES FINE UNTILL I TRY INSTALL OR UPDATE MYSQL 5.5 then after that i can't install or update anything!!!! and now my PI will not even finish loading it gets half way then stops DEAD, which means I have to reinstall AGAIN!!! I feel like i'm stuck in a infinate loop that I can't even fix because what i'm doing is right ...[censored] MYSQL is just plain broken! So broke I can't use my pi for anything but media. I need MYSQL etc that's what i'm trying to learn!!! I have treid everything on this forum and everything on every other forum I could find and nothing works!!!!!!!! IN fact the pi told me to run sudo dpkg --configure -a to fix the problem, then it says bash sudo bash dpkg command not found!!!!!!WTH IS GOING ON!!! I am going insane trying the same things over again expecting different results someone help. I even tried changing the memory and changing overclocking!!!! it makes no difference. what I do.

[bgirardot]

I have been struggling with this problem since I bought my PI for months. I lost rack of how many times I have reinstalled, tried different sd cards, tried updates, tried different versions. Tried changing the password. EVERYTHING GOES FINE UNTILL I TRY INSTALL OR UPDATE MYSQL 5.5 then after that i can't install or update anything!!!! and now my PI will not even finish loading it gets half way then stops DEAD, which means I have to reinstall AGAIN!!! I feel like i'm stuck in a infinate loop that I can't even fix because what i'm doing is right ...[censored] MYSQL is just plain broken! So broke I can't use my pi for anything but media. I need MYSQL etc that's what i'm trying to learn!!! I have treid everything on this forum and everything on every other forum I could find and nothing works!!!!!!!! IN fact the pi told me to run sudo dpkg --configure -a to fix the problem, then it says bash sudo bash dpkg command not found!!!!!!WTH IS GOING ON!!! I am going insane trying the same things over again expecting different results someone help. I even tried changing the memory and changing overclocking!!!! it makes no difference. what I do.

What distro are you using?

I suggest you try exactly these steps and no others:

Download and install raspbian from the foundation's download page
On first run expand the root file system via the rasp-config interface
reboot
sudo apt-get update && sudo apt-get upgrade
sudo apt-get install mysql-server

and see what happens.
It has worked literally at least a dozen times for me, I do clean installs all the time testing, exploring and trying to help out on the forums.

[rmwebs]

I have been struggling with this problem since I bought my PI for months. I lost rack of how many times I have reinstalled, tried different sd cards, tried updates, tried different versions. Tried changing the password. EVERYTHING GOES FINE UNTILL I TRY INSTALL OR UPDATE MYSQL 5.5 then after that i can't install or update anything!!!! and now my PI will not even finish loading it gets half way then stops DEAD, which means I have to reinstall AGAIN!!! I feel like i'm stuck in a infinate loop that I can't even fix because what i'm doing is right ...[censored] MYSQL is just plain broken! So broke I can't use my pi for anything but media. I need MYSQL etc that's what i'm trying to learn!!! I have treid everything on this forum and everything on every other forum I could find and nothing works!!!!!!!! IN fact the pi told me to run sudo dpkg --configure -a to fix the problem, then it says bash sudo bash dpkg command not found!!!!!!WTH IS GOING ON!!! I am going insane trying the same things over again expecting different results someone help. I even tried changing the memory and changing overclocking!!!! it makes no difference. what I do.

What distro are you using?

I suggest you try exactly these steps and no others:

Download and install raspbian from the foundation's download page
On first run expand the root file system via the rasp-config interface
reboot
sudo apt-get update && sudo apt-get upgrade
sudo apt-get install mysql-server

and see what happens.
It has worked literally at least a dozen times for me, I do clean installs all the time testing, exploring and trying to help out on the forums.

For what it's worth, I've tried the above steps on the following SD cards, with zero success.

- Sandisk 8GB Class 6
- Sandisk 4GB Class 4
- MyMemory 16GB Class 6
- Lexar 8GB Class 6
- Transcend 4GB Class 6
- Kingston 8GB Class 4
- Verbatim 4GB Class 4
- Unbranded (7dayshop) 16GB Class 4
- Sandisk 32GB Class 10
- PNY 4GB Class 4

It's nothing to do with the SD cards, that much is for sure. At some point something has gone wrong. Clearly there is a bug somewhere as people who previously had working MySQL installations were reporting the same problem after upgrading Raspbian.

As it stands my Pi is sitting here idle as I cant use MySQL on it. I'd like to think I know what I'm doing here. Iv'e been working on unix based systems for over 10 years now, and have managed many servers.

[owen_a]

It tells you what to do in the error. Just simply run this as root;

Code: Select all

dpkg --configure

Or it might be;

Code: Select all

dpkg --configure -a

One of those will continue to configure the packages. If something where to fail, for example, you was installing something then the power got cut to the Pi for whatever reason, then you simply run that command, and it will resume where it left off.

Hope it helps!

[bgirardot]

...As it stands my Pi is sitting here idle as I cant use MySQL on it. I'd like to think I know what I'm doing here. Iv'e been working on unix based systems for over 10 years now, and have managed many servers.

You said yours was working back on Nov 12th. did it stop working?

[rmwebs]

...As it stands my Pi is sitting here idle as I cant use MySQL on it. I'd like to think I know what I'm doing here. Iv'e been working on unix based systems for over 10 years now, and have managed many servers.

You said yours was working back on Nov 12th. did it stop working?

Where did I say that?

I did get it working temporarily. It stopped working again after a reboot and was giving me the "/var/lib/mysql is too full" error again - the same happened when I tried a couple of brand new cards as well.

[bgirardot]

Ok,

Tried this again today on a SD card I pinched from a camera. It is a PNY 4GB class 4 (seemingly, the same type I already tried yesterday) and it worked on that one :/

Something really strange happening there - I know the Pi was selective about SD cards, however branded Sandisk Class 6 ones surely should be ok? It's not like they were nockoffs either - they came from Amazon (and were sold by Amazon - not a marketplace seller).

8th post down, no follow up with a full partition error.

What does df -h output?

[fabhatti]

Having exactly the same issues with mysql installation on Raspbian “wheezy”. Tried everything .. reboot, innodb memory limit, sudo apt-get update && sudo apt-get upgrade etc. but mysql wont start.

@bgirardot: Did you ever get it to run on your raspberry pi?

Thanks

[fabhatti]

Ok in my case I got the mysql running by commenting out the 'bind-address = xxx' line under
/etc/mysql/my.cnf

Following is a link to the thread which helped me with my mysql installation issues.
http://forums.mysql.com/read.php?10,561 ... msg-561282

Hope it helps someone else as well.

[rmwebs]

Just a quick follow up on this. It's most certainly an issue with dodgy SD cards, or at least some sort of incompatibility with certain types.

I've managed to get this working now with a Samsung Essentials Class 19, 32GB SDHC card. Picked it up during the xmas sales from MyMemory. It's not the fastest card around (24 MB/s read) but seems to be better than the others I had tried.

I've not seen Samsung ones around before but thought I'd give it a shot.

The exact process I followed to get MySQL up and running correctly (fresh Wheezy 2012-12-16 Raspbian image) is as follows:

Code: Select all

sudo apt-get update
sudo spt-get upgrade
sudo apt-get install mysql-server mysql-client

The upgrade part took a lot longer than I expected (a good 10-15 minutes on a 120 meg connection). The final command for installing mysql took about 5 minutes.

Unlike before, MySQL started up first time without any problems. Seems to be working perfectly fine now.

So...there ya go!


(Sidenote: It really does make me wonder just how many fake SD cards are out there! Someone must be making a killing selling these duff cards!)

[devdells]

After following much of the advice on this thread (except memory partition) I realized perhaps the model of RasPi had something to do with it. On my 256mb unit I had to follow this other advice and set a lower default for InnoDb in the my.cnf file. Then, and only then, could I resolve this and finish configuring MySql 5.5
... the other post...
http://www.raspberrypi.org/phpBB3/viewt ... 49#p191449

[xo1416]

hi all

use USB Image Tool to write the img?

try to update it from 1.59 to 1.61

maybe, u will have a surprising

Code: Select all

 [ ok ] Starting MySQL database server: mysqld . ..

I dont know the reason but if u wanna to give up ...try it!!

[cyrano]

I did get it working temporarily. It stopped working again after a reboot and was giving me the "/var/lib/mysql is too full" error again - the same happened when I tried a couple of brand new cards as well.

Have you seen this advice:

http://serverfault.com/questions/256729 ... s-too-full

Quote:

Many distributions have their /var directory in the original root partition which is not made big enouch by default to hold real-life data. They usually create separate partition for /usr with thons of space, so your easiest solution would be to stop mysql, copy /var/lib/mysql to /usr/lib/mysql (or /usr/local/lib/mysql no real differenc), delete the original and make a symbolic link in the old place with:

Code: Select all

ln -s /usr/lib/mysql /var/lib/mysql

Of course check that the destination directories have the right permissions.

Sounds like you could be hitting the same frontier. It would also mean SD cards are not the cause of your problems.