StrongAuth, Inc. Forums

[c094728]

I'm using JBOSS / mysql and I'm trying to follow the docs at http://www.strongkey.org/resources/documentation/installation/howto-create-schema.html to install the strongkey schema.  It tells me that if the table names show as upper case then the /etc/my.cfg file is incorrect but it looks ok and when I look at the customers.sql files, the scripts appear to be creating all of the tables in upper case.  i.e create table GROUPS...  The cli test utility fails  with symkey.groups doesn't exist.  I'm pulling my hair out.   HELP!!!

[arshadnoor]

4 questions to help resolve this:

1) What version number of MySQL are you using? 
2) Are you using Windows or Linux? 
3) In which directory do you have the my.cnf file located? 
4) Can you post a copy of your my.cnf file? 

Thanks.

[c094728]

The answers to those questions are below.  My concern is that the scripts that create the stongkey schema have the table names in upper case.  Is the lower_case_table_names=1 setting suppose to make all upper case tables accessible as lower case?


1) What version number of MySQL are you using? 
mysql-5.0.41-linux-i686.tar.tar

2) Are you using Windows or Linux? 
 Red Hat Enterprise Linux ES release 3 (Taroon Update 4)

3) In which directory do you have the my.cnf file located? 
/etc/

4) Can you post a copy of your my.cnf file? 
[mysqld]
datadir=/usr/local/mysql/data
#####################################
# Change the value for the following
# variable to the name of the user
# who is installing MySQL
#####################################
user=dklxxxxxxxx
lower_case_table_names=1

[mysql.server]
basedir=/usr/local/mysql


log=/usr/local/mysql/log/wcdxxx.log
log-error=/usr/local/mysql/log/wcdxxx.err
innodb_data_home_dir = /usr/local/mysql/ibdata
innodb_log_group_home_dir = /usr/local/mysql/iblogs
innodb_data_file_path = ibdata1:10M:autoextend
innodb_flush_log_at_trx_commit = 1
set-variable = innodb_buffer_pool_size=5M
set-variable = innodb_additional_mem_pool_size=5M
set-variable = innodb_log_file_size=5M
set-variable = innodb_log_buffer_size=5M
lower_case_table_names=1

[mysqld_safe]
err-log=/usr/local/mysql/log/mysqld_safe.log
pid-file=/usr/local/mysql/log/mysqld_safe.pid

[arshadnoor]

The lower_case_table_names parameter forces all tablenames to be in lower-case; this makes it portable across operating systems such as Linux, UNIX, Windows, etc.

Your my.cnf file looks alright; I'm assuming that there are no read-permission problems on that file.  The only difference I can notice is that we haven't tested StrongKey on RHEL3; only RHEL4, FC6, OpenSUSE 10 and Windows 2003.  So, I'm wondering if RHEL3 may be causing this problem.  We have no way of testing it since we don't have a copy of RHEL3.  however, you can verify that this works correctly on any of the other OSs

[c094728]

Your instructions say to start mysql using ./configure  When I look in configure I see it starts mysql with ./bin/mysqld_safe --no-defaults.  I believe --no-defaults tells it to not read the my.cnf file.  I was finally able to get it to work by starting up with ./bin/mysqld_safe --defaults-file=/etc/my.cnf.     mysql then had problems with file ownership because the user in the my.cnf was myself but the mysql database files were owned by mysql.mysql.  I changed the user in my.cnf to mysql and now it starts up.  When I run the cli.jar test I get a bunch of  errorkey: symkey.sks.msg.rverr.0009.  errors.   I suspect I may have a problem with the  jwsdp-2_0 installation as several of the jars listed on the http://www.strongkey.org/resources/documentation/installation/howto-install-skcl.html page were missing from my app server. specifically FastInfoset and the JAXB files.  Was it the jwsdp2.0 installation that was suppose to put these there?

[arshadnoor]

Yes, the JWSDP installs FastInfoset and JAXB.  Check the installation page for the SKCL - http://www.strongkey.org/resources/documentation/installation/howto-install-skcl.html - if any of these jars are missing from the client (or server side), StrongKey will not work.

[snajsoft]

./bin/mysqld_safe --defaults-file=/etc/my.cnf

I tried starting mySQL with the above commands and get the following errors:

nohup: ignoring input and redirecting stderr to stdout
Starting mysqld daemon with databases from /usr/local/mysql5/data
STOPPING server from pid file /usr/local/mysql5/log/mysqld_safe.pid
080923 15:19:43  mysqld ended

Could anyone help me understand whats happening overe here? Is there anything wrong with my.cnf?

[snajsoft]

./bin/mysqld_safe --defaults-file=/etc/my.cnf

I tried starting mySQL with the above commands and get the following errors:

nohup: ignoring input and redirecting stderr to stdout
Starting mysqld daemon with databases from /usr/local/mysql5/data
STOPPING server from pid file /usr/local/mysql5/log/mysqld_safe.pid
080923 15:19:43  mysqld ended

Could anyone help me understand whats happening overe here? Is there anything wrong with my.cnf?

Problem resolved by creating a folder - "log" in /usr/local/mysql5 with appropriate permissions.

[zeff]

thanks guys..i had the same prob..good thing i stumble on this