Re: connector mxj can't init db on linux

Hello Andreas,

On Wed, 2006-05-03 at 11:32 +0200, Andreas Schlicker wrote:
> > 
> > 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.
[snip]
> 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:
[snip]
> 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.
> 

Right, we need a datadir in order for mysqld to be able to run, but if
we use the datadir that was created we have the same problem? Hrm. 

This is beginning to point to it being outside of the Connector/MXJ
wrapper and something more related to the server. However it might have
something to do with the datadir files provided by the Connector/MXJ
wrapper.

Okay let's try this: inside the connector-jar file is a "datadir.jar"

  jar xvf ~/path/connector-mxj.jar 4-1-13/data_dir.jar
  mkdir data
  cd data
  jar xvf ../4-1-13/data_dir.jar

this will unpack a "fresh" datadir for us to work with.

> On the laptop, the second procedure works perfectly.

Right, we seem to have narrowed it down to some problem with the files
in the datadir. That's a good sign.

Also, a co-worker of mine asked to get the results of "dpkg -l" from a
working system and from a non working system, to see if maybe there is a
subtle difference. This also may help us try to model the environment.

>  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.

We could certainly try the 5.0 development release, but since you think
it may not have made a difference, let's hold off on that for a moment.
It also may be that it would work fine with a fresh data dir. But that's
a just a wild guess, I'd like to see if we can establish whether it's a
a Connector/MXJ wrapper specific issue or not, first.

Cheers and Good Luck!
 -- Eric


> 
> Regards,
> Andreas
> 

-- 
Eric Herman, Software Developer
MySQL AB, www.mysql.com
Mobile: +1 206 913 8942

Are you MySQL certified?  www.mysql.com/certification


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