Console [Severe] error on launch
Opened this issue ยท 10 comments
Hi there,
I am currently looking for a plugin that monitors a user's play time and was hoping to find something with MySQL connectivity, this plugin seems ideal however I am having trouble getting it to actually launch.I have re-downloaded the jar file several times so it should not be corrupt and I have edited the config file a number of times to ensure there are no issues.
Looking through the console logs I get the following error.
10:07:33 AM PlayTime: Enabling Playtime v1.4.0
10:07:33 AM PlayTime: Enabling Metrics...
10:07:33 AM PlayTime: Enabling executable manager...
10:07:33 AM PlayTime: Update checks disabled!
10:07:33 AM PlayTime: Enabling Data Manager...
10:07:33 AM PlayTime: Connecting to MySQL database...
10:07:33 AM PlayTime: Successfully connected to database!
10:07:33 AM CONSOLE: [SEVERE] Error occurred while enabling Playtime v1.4.0 (Is it up to date?)
I thought the problem would be with the database as there is no table being created, however the console suggests the database connects perfectly fine. My configuration file is also as follows
general:
debug-level: 3
update-check: true
language:
use-github: true
locale: en_US
check:
death-time: true
online-time: true
afk:
enabled: true
interval: 60
timeout: 900
events:
enabled: true
interval: 10
data:
manager: mysql
managers:
mysql:
host: localhost
port: '3306'
database: minecraft
username: (my username)
password: (my password)
apologies about the formatting, I am not used to github markup.
Are there any known bugs with any other plugins? Any issues you can think of which are causing this error? I would prefer to use this plugin above others but for the moment I just cannot get it to launch.
Thanks for your time,
Joe
You have to have set up a valid mysql database that you can connect to before you use playtime with MySQL storage. The default settings for playtime are not set to any real database, as those are settings you need to provide.
If you already have a MySQL database, are you able to manually create a table within the database?
I do have a valid MySQL database and use it for other plugins, PreciousStones etc. The database, host, port username and password are all correct and exist.
I could create the table manually but I would need all the information regarding the attributes and name of the database for it to work surely?
Is there anything else after this line?:
10:07:33 AM CONSOLE: [SEVERE] Error occurred while enabling Playtime v1.4.0 (Is it up to date?)
Yes there are other lines. I didn't notice this one before but it looks like it is related to the language file.
18:35:23 PlayTime: Enabling Playtime v1.4.0
18:35:23 PlayTime: Enabling Metrics...
18:35:23 PlayTime: Enabling executable manager...
18:35:23 PlayTime: Update checks disabled!
18:35:23 PlayTime: Enabling Data Manager...
18:35:23 PlayTime: Connecting to MySQL database...
18:35:23 PlayTime: Successfully connected to database!
18:35:23 CONSOLE: [SEVERE] Error occurred while enabling Playtime v1.4.0 (Is it up to date?)
18:35:23 CONSOLE: language files are missing the path. Language: en_US Path: data.mysql.cr
Everything following this is just other plugins loading. Nothing else references Playtime
Go to /plugins/Playtime and delete the "lang" folder. It will generate new lang files. Not entirely sure why it didnt' update your lang file, but I'll look into it.
I've deleted the language files as you suggested, but when new ones are generated I am still given the same error.
I'm no genius when it comes to java but it looks like "data.mysql.create-table" should just point to the line in the en_us.yml file. "create-table: Creating table 'playTime' in database '{0}'"
So the line its looking for exists, it just can't find it. I've tried adding permissions to read write and execute to the language files just in case thats the issue but it hasn't done anything to solve the issue.
mind uploading a copy of your current lang file to http://pastie.org/ and linking it here?
http://pastie.org/private/rgeknk16w2uef7ym8mtkw
That should work hopefully :)
Ah yes I see now, this was an error I had already fixed in 1.4.1
You can find the updated version on bukkitdev below, it took a while to become approved (about 10 days).
Small edit:
Looks like even 1.4.1 didn't fix this (it fixed a similar issue). As of right now, the latest development build of Playtime has the bug fix and is relatively stable.