permissionDefault in the configuration to
'version' in config to
The updater couldn't find out the UUID for the given name. This is probably because in the meantime, the player has changed their name. The player's old record has been given a dummy UUID. Nothing will crash or become corrupt because of this, but if the player rejoins the server, they will be given a new record with their new name. All old actions they have logged will be listed under their old name permanently, while actions logged from now on will use their current name, whatever they change it to.
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'bukkit.lb-world' doesn't exist
The table 'lb-world' doesn't exist in your LogBlock setup. For each table that does exist, run these commands in SQL (may take a while, run them each separately). After doing so set
'version' in config.yml to
'1.57' and your SQL has been 'updated'. Note that if you already have modified your columns to allow for large enough integers, just update the config and don't worry about the table alteration.
ALTER TABLE `<name>` MODIFY `x` MEDIUMINT NOT NULL ALTER TABLE `<name>` MODIFY `y` SMALLINT NOT NULL ALTER TABLE `<name>` MODIFY `z` MEDIUMINT NOT NULL
This means that the amount of blocks in the queue is higher than that of which can be processed and written into the database. The changes aren't lost, even if the server stops! Only a server crash will lead to the loss of the queue. The following are possible causes and solutions for this issue:
Too many players for your setup Depends on whether you are using a remote SQL server, etc. Increase the processed block count: consumer: delayBetweenRuns: 5 timePerRun: 200
Temporarily peak due to forest fires, huge explosion(s) or massively large amounts of liquid flow Don't worry, it'll be processed soon.
The queue just processes really slow This may be due to high cpu load, or something entirely different. You will see the queue building up slowly and taking a considerably lengthy amount of time to process at shutdown. consumer: forceToProcessAtLeast: 25 These values are only demonstrative and need to be fine-tuned depending on your server size and setup.
When this error is shown at a server reload/shutdown and there are no
Queue overloaded messages being spammed, set
consumer.useBukkitScheduler to false to have a Java timer used instead. More info over at the Configuration page.
This shouldn't happen. Please open an issue ticket (click Issues above!) with the following information:
Your server has just reached more than 65000 players logging in to it. The original database table scheme was designed to fit 65535 entries, so you may soon run into the problem where LogBlock will not log new users. To prevent this, you should update your database scheme asap:
USE minecraft; ALTER TABLE `lb-players` CHANGE `playerid` `playerid` INT UNSIGNED NOT NULL AUTO_INCREMENT; ALTER TABLE `lb-chat` CHANGE `playerid` `playerid` INT UNSIGNED NOT NULL; ALTER TABLE `lb-<world>` CHANGE `playerid` `playerid` INT UNSIGNED NOT NULL; ALTER TABLE `lb-<world>-kills` CHANGE `killer` `killer` INT UNSIGNED NOT NULL; ALTER TABLE `lb-<world>-kills` CHANGE `victim` `victim` INT UNSIGNED NOT NULL;
Either change the url in the config to an existing database or create a new one named the same as the one already in the Configuration (to save your time), or, update the name in configuration to the name of the new database.
Please update the database schema.
Make sure worldTables and worldTables have an equal count of entries and do actually contain entries. See Installation for correct setup. Each world needs a table!
Your world has a larger radius than 32,767 blocks. You need to either limit the map to a radius of 32k blocks, or change the data types of the columns x and z from SMALLINT to MEDIUMINT, which allows you a radius of 8,388,607 blocks. If that wouldn't be enough you can also use INT (radius of 2,147,483,647 blocks). This will result in a larger database size.
SQL USE `minecraft`; ALTER TABLE `lb-world` MODIFY x MEDIUMINT NOT NULL; ALTER TABLE `lb-world` MODIFY z MEDIUMINT NOT NULL;
Likely your MySQL server crashed recently, thus, your database is corrupted. In most cases this is fixable by executing the following SQL commands: (replace