Re: connector mxj can't init db on linux

Hi Eric,

> My proposal is to alter the test programs to just use Connector/J and
> JDBC ... and to move the starting and stopping of the database to the
> command line between applications.
> 
> Now to start the server you'll need to run the same command that
> Connector/MXJ constructs from the arguments which you provide. It will
> look something like this:
> 
> /path/to/basedir/mysqld \
>  --no-defaults \
>  --pid-file=/path/to/basedir/MysqldResource.pid \
>  --socket=/path/to/basedir/mysql.sock \
>  --port=3336 \
>  --datadir=/path/to/basedir/data \
>  --basedir=/path/to/basedir
> 
> You can find out exactly what command line arguments are being used by
> running your test program and viewing the Connector/MXJ output. You
> should see a reconstruction of the command line with each command line
> element encapsulated in square brackets.
> 
> Then, to terminate the database, use "kill <PID>". 
> You can find the PID by looking at the screen output of the mysqld
> command, or by reading the MysqldResource.pid file.
> 
> First, I'd like you to give this a go on your laptop where we expect
> everything to succeed. Once it works there, second, I'd like to have you
> give it a try with one of the machines on which we're experiencing the
> "InnoDB: Unable to lock ./ibdata1, error: 11" problem.

I tried this but I get another problem. If I have an empty data dir and 
start mysqld on the command line on my workstation, I get this output:

InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060503 11:18:13  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060503 11:18:14  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...
060503 11:18:14  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
060503 11:18:14  InnoDB: Started; log sequence number 0 0
060503 11:18:14 [ERROR] Fatal error: Can't open privilege tables: Table 
'mysql.host' doesn't exist

However, if I use the system tables created by running mysqld through 
connector-mxj, I get the same "InnoDB: Unable to lock ./ibdata1, error: 
11" problem after starting mysqld from the command line.

On the laptop, the second procedure works perfectly. I will try to use 
another mysqld executable but this will probably not help. I just 
remembered that I tried the connector/mxj 5.0 development release with 
the same problem.

Regards,
Andreas

-- 
MySQL Java Mailing List
For list archives: http://lists.mysql.com/java
To unsubscribe:    http://lists.mysql.com/[email protected]