If you log in to PhpMyAdmin and go to the "Storage Engines" section, you'll notice that InnoDB is not disabled.

See the MySQL manual for more information (13.2.3. InnoDB Configuration).

# mysql -uroot
> show engines;
 MyISAM     | DEFAULT
 InnoDB     | YES
 ...

# cat /etc/mysql/conf.d/storage_engine.cnf
[mysqld]
default-storage-engine = InnoDB

# /etc/init.d/mysql restart

# mysql -uroot
> show engines;
 MyISAM     | ENABLED
 InnoDB     | DEFAULT
 ...

OK,

There is a setting in MySQL in Webmin to set default engine to InnoDB.   Unfortunately, if you enable it, then use the "save and restart" MYSQL Server, the Server won't start.

Plus I just lost the old version of the setup.  TKBAM here we go again.

creating a storage_engines.cnf file breaks MySQL

adding a line

default-storage-engine = InnoDB

also breaks MySql

In phpmyadmin, InnoDB is not even listed as optional Engine.

Not sure how to proceed.  Trying to install Magento in related folder and it requires InnoDB

any help is appreciated.

I can't add this to my.cnf either manually or with the script.

MySQL will not start up again w/ it in Joomla.

storage_engine MyISAM is not editable in MySQL system variables...

Thoughts here? 

Thank you,

L. Arnold mentions that Adrian set him up with a webmin-mysql install that gott InnDB working on his system. Is there something similar that I can do? I have a TKL LAMP system on to which we are currently installing vTiger. We've just entered in all of our users (around 80) and went to do a maintenance release of vTiger to 2.5.1 that requires we switch to InnoDB as our engine. It's not showing up as available at all in our image and 'enabling' it from within Webmin breaks MySQL just as it did for L. Arnold.

Thanks -- and you guys have a great overall product here!

This is the quote of the instructions that were sent by Adrian to get some access.  I think however that it is the "back end" of MySQL that is important and I would be careful about "uninstalling" MySQL as you might also lose your data:

There is also in the Magento Patch thread on the Forum.  Install MySQL is mentioned as part of the patch.  Someone should research how to "step up" MySQL.  IE, the Magento Patch is going over the TKL Lucid 11rc Core build.  MySQL being loaded must somehow be different than what is going into the 11rc builds that have MYSQL preloaded.  (I will explore on my Joomla 11rc build that also won't take InnoDB.

__

note the && should be treated as a separate line in SSH :12320 setup.  I have bad experience running some systems just from the command line in WebMin though I prefer to stay in WebMin.

Also, by having this access I was able to change my MySQL passwords for security sake.

-------

You can install the webmin modules

I am going to try this, but possible word of caution.  It may be that certain settings need to be loaded in your cfg files -- at the very least, make a copy of my.cnf (location referenced above somewhere - I think -> here

/etc/mysql/

 The default install has quite a bit of annotation in it.  My experience earlier this week was that Webmin (in Joomla 11rc) was reformatting the file pretty extensively and importantly taking out the annotations which you can learn from.

By being able to get the original text back into that file I could get MySQL to start after a "break" trying to set InnoDB.

Test next on my "empty" Joomla box.  lets see if it works tommorrow AM.  its late.

Thanks for the advice and support everyone.

So, with enough poking around today I found this:

http://forums.innodb.com/read.php?3,1241,1243

Here's a succinct quote:

There is a innodb_plugin shipped with Ubuntu 10.04. The problem is it's 1.05 and they have no plans of ever updating it...In fact according to what they said they will never ship a newer version of mysql than 5.1.41 for the 10.04 LTS Which means it will be years before we can use innodb_plugin in a supported manner on Ubuntu LTS.

Ouch. Except that if you click through the actual conversation, it seems that you can compile a recent version of MySQL for yourself that would contain all the latest-n-greatest stuff. If you don't, you need to use an old version of the plugin and deal with any instabilties that may create.

I'm not nearly brave (nor competent) enough to try compiling MySQL and then recreate all the necessary configs to get it running in TKL like it is now (Stable, secure, etc.). Now if there were a script... :-)

Technically Jed meister's line is a script:

apt-get update && apt-get install webmin-mysql mysql-server

Unfortunately TKL joomla 11rc is not taking the mysql-server part (though there is a server built in).

I spent a lot of time  (you are welcome to read the lower part of this, but my conclusion is tht this must have something to do with the debian.cnf file (directly above my.cnf) as calling InnoDB as the default, no matter what, kills this version, and any thing apt-get will call, in MySQL. 

This line is in System Variables of the two systems. 

ignore_builtin_innodb OFF

The only variable I believe there is left is that Adrian's Magento Build was built from Core rather than perhaps a LAMP build as I expect Joomla was built (because it has a PostFix server also attached).

I will peer a bit into the Magento Patch to see if there isn't some other call that was made when installing MySQL.  There is probably an extra line somewhere in the "sources" setup which would tie into why the mysql-server command is not taking.  (I can't find the sources just this minute)

back in a bit.

L. Arnold

I looked a bit at the Magento thread and there is a call out in Adrian's Magento thread with the same call (later on the line there is also a call to "php5-mysql".

I just did a call to "php5-mysql" and got the response in my SSH box:

• "the following packages were automatically installed and are no longer required.
• webmin-mount
• use 'apt-get autoremove' to remove them."

Seems webmin-mount is an important piece here...So...  I log into web-min, go to mysql server, change the default again to InnoDB,  press save.  Server Stops..   won't restart.

Back to File manager, rename my.cnf to my.cnf.bak3....  rename my.cnf.bak2 to my.cnf

Back to MySQL Database Server (in WebMin) and the Server is all by itself running again.

Not sure what to do.  I still get the following error when trying to get a Magento install running on this "testbed"  (not Adrians).

• • Database server does not support the InnoDB storage engine.
  • Database connection error.

Under Engines (seen in phpmyadmin which I can see on this system but not on Adrians Magento Build)  I see the following available:

Perhaps we have the BLACKHOLE build going, but tbo, I am not sure even what the default engine is here.  Probably "Federated" as it shows up with a slightly different color in my actual list (don't take this as absolute).  my.cnf says (NADA) about default engine.

It does say this (and seems to have info commented out, so I am going to Uncomment the first line below and see what happens ...)  Just Did but nothing:  # and * both appear to be comment codes, and I don't think simply saying InnoDB will do anything.

# * InnoDB

#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!

So, now on to the Adrian's Magento build of my.cnf  (need to shut this one down as they share the same IP and Host config.... I believe I toggled the default in this one to read  (again all comments gone which is the sign of a WebMin Edit and save command)

expire_logs_days    = 10
max_binlog_size         = 100M
default-storage-engine = InnoDB

So, Manually add the default-storage-engine=InnoDB  and MySQL is not running again.  Can Manually Remove it (bypassing Webmin) and it is running again..  but for Grins I am going to restart the box..

index.php on the box:

• Database Error: Unable to connect to the database:Could not connect to MySQL

comment the line back out (# default-storage-engine=InnoDB) and everything is working again.

I'll bet the issue is in debian.cnf  which seems to have all to do with the Debian mysql.sock scripts which I don't know anything about to comment...

Lets get this fixed somehow.

L. Arnold

#!/bin/bash -ex
install()
{
    DEBIAN_FRONTEND=noninteractive apt-get -y \
        -o DPkg::Options::=--force-confdef \
        -o DPkg::Options::=--force-confold \
        install $@
}

cleanup_apt()
{
    rm -r /var/cache/apt/*
    mkdir /var/cache/apt/archives

________

install mysql-server works later in the patch script.

http://ubuntuforums.org/showthread.php?t=534530

(still don't see the actual "line of code" needed to remove and properly reinstall... but it is looking like MySQL would need to be uninstalled, then reinstalled using some of the code in the patch and referenced usage in the link...

    DEBIAN_FRONTEND=noninteractive apt-get -y \
        -o DPkg::Options::=--force-confdef \
        -o DPkg::Options::=--force-confold \
        install $@

The realilty is that Ubuntu Lucid needs to make InnoDB work for many reasons it seems.  Other work to do for now.  I do still want Joomla and Magento to coexist but will probably apply Joomla to the Magento box if I can now.

It seemed that the process was solvable so I kept looking at what I could find.    I do think it will be a big problem though if InnoDB is not supported in the next build.  Magento, for instance, requires it and it seems to be broadly used in other systems.

There are builds, for instance from JumpBox that have everything packaged (at a price).

I don't believe that Magento changed anything in the MySQL build as Magento would not take after a normal install on the Joomla Box.  On the Magento Patch Box it did take (yes after working on it for a while - but some of those problems were from my not understanding the "directions".  Others from the directions having caveats that needed to be worked through.

Anyway, this is all a "RC" subject.  Not even pertaining, that I can see, to current builds.

all the best,

L. Arnold

This thread seemed to finish off  with some rather negative conclusions.

Here is what I found:

1) InnoDB failed to start after install of the TKL LAMP 11RC.

2) The innoDB config in /etc/mysql/my.cnf is basically blank so is of little help.  This initially lead me to wonder if I needed to add in some reasonable defaults to "fix" the problem.  Apparently the defaults are stored elsewhere.

3) If the innoDB engine fails to start the default settings do not show up in webmin, but do appear when the engine starts successfully.

4) I found deleting the /var/lib/mysql/ib_logfile0 and /var/lib/mysql/logfile1 as suggested by the devs above then a mysql restart and I was good to go.  Note that THEN I was able use the Webmin MySQL Server Config to change the default storage engine without issue.  Reversing that order might not be as successful as the default engine would fail. 

5) There are several issues published elsewhere regarding apparmor, plugins etc that proved to be great distractions but were not ultimately helpful.

For me the only issue has been finding the cause of the initial corruption with the innoDB logs during the install.  I have had no further log problems.  Has anyone reported log problems over time?

BTW, just to be explicit.... none of the above is a criticism of TKL but I wanted to change the direction of this thread so others do not give up on InnoDB prematurely.  I suspect the problem is related to an install error and InnoDB's particular nature.

Great product!  Switched from CentOS because of TKL.

Thanks,

Richard

Richard, 

Thanks for your succinct and upbeat update.  I was reading about the log files in another thread as well.  Fully agree about the great product.  I am expecting the final version releases that are being worked on now will have this worked out. Great to know we can, so simply, work it out now as well.  May have to try a TKL Magento Patch on top of LAMP again.  It is nice having PHPMySQL be autoconfigured - though I note lots of good info here on configuring MySQL as well.