Solved LWC and MySQL

Hello,
I have been messing with things for awhile and cannot figure out how to get LWC to connect to a MySQL database. Towny, PlotMe, and CoreProtect can, but for some reason LWC is just not giving me any kindness.

Code:

database:
    adapter: mysql
    path: plugins/LWC/lwc.db
    host: localhost
    database: lwc
    username: 'root'
    password: '-withheld-'
    prefix: lwc_
    ping_interval: 300

 

Is it printing some kind of error (a stack track)? If so, could you post it for us?

 

TheEntropy
I found my problem... I was telling it to connect to a database named lwc (which didn't exist) when I wanted it to connect to one named bukkit.

Although, it does have a Stack trace error if you want to help me with that. I'll just give you all the LWC part of the startup:

Code:

[22:46:45 INFO]: [LWC] Enabling LWC v4.4.0 (b881) (July 11, 2013)
[22:46:45 INFO]: [LWC] Connecting to MySQL
[22:46:46 INFO]: [LWC] Dropping old indexes (One time, may take a while!)
[22:46:46 INFO]: [LWC] Creating new indexes (One time, may take a while!)
[22:46:47 INFO]: [LWC] Creating index on internal
[22:46:48 INFO]: ######################################################
[22:46:48 INFO]: ######################################################
[22:46:48 INFO]: SQLite to MySQL conversion required
>OpenJDK 64-Bit Server VM warning: You have loaded library /home/mike/Bukkit/plugins/LWC/lib/native/Linux/amd64/libsqlitejdbc.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
[22:46:49 WARN]: java.lang.UnsatisfiedLinkError: /home/mike/Bukkit/plugins/LWC/lib/native/Linux/amd64/libsqlitejdbc.so: /home/mike/Bukkit/plugins/LWC/lib/native/Linux/amd64/libsqlitejdbc.so: file too short
[22:46:49 INFO]: Successfully converted.
[22:46:49 INFO]: Renaming "plugins/LWC/lwc.db" to "plugins/LWC/lwc.db.old"
[22:46:49 INFO]: SQLite to MySQL conversion is now complete!

 

Mayor_Mike
I checked around a bit and couldn't find a solid answer. From what most people have said: the error can be ignored and doesn't interfere with the plugin's performance.

 

TheEntropy
Well thanks for the help. I do ignore it and the performance is still solid good.

Thanks again for your assistance.