Problem creating sandbox with make_sandbox on Ubuntu 8.04

Asked by damien on 2009-08-10

Hi,
I'm trying to create a single sandbox server using mysql-5.1.37. However, the process always fails. When I call make_sandbox and pass the appropriate tar file as a parameter, I first receive the following warnings (I have pasted the full output below but highlighted the warnings here for clarity):

*******BEGIN SNIPPET****************
090810 11:01:45 [Warning] /home/damien/5.1.37/bin/mysqld: unknown option '--loose-skip-innodb'
090810 11:01:45 [Warning] /home/damien/5.1.37/bin/mysqld: unknown option '--loose-skip-ndbcluster'
*******END SNIPPET****************

Some InnoDB related messages are then output, followed by:

*******BEGIN SNIPPET****************
090810 11:01:46 InnoDB: Started; log sequence number 0 0
ERROR: 1193 Unknown system variable 'have_csv'
090810 11:01:46 [ERROR] Aborting
*******END SNIPPET****************

This is then followed by:

*******BEGIN SNIPPET****************
error while creating grant tables
Installing MySQL system tables...

Installation of system tables failed! Examine the logs in
/home/damien/sandboxes/msb_5_1_37/data for more information.
*******END SNIPPET****************

There is no log information dumped to the folder indicated above. Does anyone have any suggestions about what I might be doing wrong? There is an existing installation of mysql-5.0.51 on the machine.

Thanks for your help!

Here is the full output:

unpacking /home/damien/mysql-5.1.37-linux-x86_64-icc-glibc23.tar.gz
Executing low_level_make_sandbox --basedir=/home/damien/5.1.37 \
        --sandbox_directory=msb_5_1_37 \
        --install_version=5.1 \
        --sandbox_port=5137 \
        --no_ver_after_name \
        --force \
        --my_clause=log-error=msandbox.err
    The MySQL Sandbox, version 3.0.04
    (C) 2006,2007,2008,2009 Giuseppe Maxia
installing with the following parameters:
upper_directory = /home/damien/sandboxes
sandbox_directory = msb_5_1_37
sandbox_port = 5137
check_port = 0
no_check_port = 0
datadir_from = script
install_version = 5.1
basedir = /home/damien/5.1.37
my_file =
operating_system_user = damien
db_user = msandbox
db_password = msandbox
my_clause = log-error=msandbox.err
prompt_prefix = mysql
prompt_body = [\h] {\u} (\d) > '
force = 1
no_ver_after_name = 1
verbose = 0
load_grants = 1
no_load_grants = 0
no_show = 0
do you agree? ([Y],n) y
090810 11:08:37 [Warning] /home/damien/5.1.37/bin/mysqld: unknown option '--loose-skip-innodb'

090810 11:08:37 [Warning] /home/damien/5.1.37/bin/mysqld: unknown option '--loose-skip-ndbcluster'

InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
090810 11:08:37 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
090810 11:08:37 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
090810 11:08:37 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
090810 11:08:37 InnoDB: Started; log sequence number 0 0
ERROR: 1193 Unknown system variable 'have_csv'
090810 11:08:37 [ERROR] Aborting

090810 11:08:37 InnoDB: Starting shutdown...
090810 11:08:39 InnoDB: Shutdown completed; log sequence number 0 43655
090810 11:08:39 [Note] /home/damien/5.1.37/bin/mysqld: Shutdown complete

error while creating grant tables
Installing MySQL system tables...

Installation of system tables failed! Examine the logs in
/home/damien/sandboxes/msb_5_1_37/data for more information.

You can try to start the mysqld daemon with:

    shell> /home/damien/5.1.37/bin/mysqld --skip-grant &

and use the command line tool /home/damien/5.1.37/bin/mysql
to connect to the mysql database and look at the grant tables:

    shell> /home/damien/5.1.37/bin/mysql -u root mysql
    mysql> show tables

Try 'mysqld --help' if you have problems with paths. Using --log
gives you a log in /home/damien/sandboxes/msb_5_1_37/data that may be helpful.

The latest information about MySQL is available on the web at
http://www.mysql.com/. Please consult the MySQL manual section
'Problems running mysql_install_db', and the manual section that
describes problems on your OS. Another information source are the
MySQL email archives available at http://lists.mysql.com/.

Please check all of the above before mailing us! And remember, if
you do mail us, you MUST use the /home/damien/5.1.37/scripts/mysqlbug script!

Question information

Language:
English Edit question
Status:
Answered
For:
MySQL Sandbox Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

Damien,
I am trying to understand the problem.

1) Where does the --loose-skip-innodb come from? Is it in some options file? (it should be ignored, but let's check it) Is it in some environment variable? ("set | grep -i 'innodb'" should give you the answer)

2) Does the sandbox work with other MySQL tarballs? (5.0.x, for example)

Thanks

Giuseppe

damien (damien) said : #2

Hi Giuseppe,
Thanks for your prompt reply.
In reply to point 1 - I don't know! I'm using a machine that was
configured by someone else, so I'm still looking into it. Your grep
suggestion did not throw up any results however.
In reply to point 2 - I tried mysql-5.0.83, and it worked! Would there
be some difference between this and the 5.1.x version I was using?

Cheers!
Damien

On 8/10/09, Giuseppe Maxia <email address hidden> wrote:
> Your question #79618 on MySQL Sandbox changed:
> https://answers.edge.launchpad.net/mysql-sandbox/+question/79618
>
> Status: Open => Answered
>
> Giuseppe Maxia proposed the following answer:
> Damien,
> I am trying to understand the problem.
>
> 1) Where does the --loose-skip-innodb come from? Is it in some options
> file? (it should be ignored, but let's check it) Is it in some
> environment variable? ("set | grep -i 'innodb'" should give you the
> answer)
>
> 2) Does the sandbox work with other MySQL tarballs? (5.0.x, for example)
>
> Thanks
>
> Giuseppe
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.edge.launchpad.net/mysql-sandbox/+question/79618/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.edge.launchpad.net/mysql-sandbox/+question/79618
>
> You received this question notification because you are a direct
> subscriber of the question.
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>

Damien,
I still can't find the reason for the message you got.
Installing MySQL 5.1.37 in several servers was successful for me.
What seems to be happening is a mix of 5.0 and 5.1 binaries.

To see if there is a mixup with previous installations, you can do the following:

~/sandboxes/stop_all
export SANDBOX_HOME=$HOME/test_sandboxes
make_sandbox /home/damien/mysql-5.1.37-linux-x86_64-icc-glibc23.tar.gz

Can you help with this problem?

Provide an answer of your own, or ask damien for more information if necessary.

To post a message you must log in.