CRITICAL BUG: [WARNING] [LogBlock Consumer] Failed to add player X about logblock HOT 32 CLOSED

Could be a broken players table.

REPAIR TABLE lb-players;

If that doesn't help, post the error messages including stack trace from server.log

from logblock.

'The storage engine for the table doesn''t support repair'

from logblock.

So paste the stack trace from server.log here

from logblock.

There is none...

"2011-11-22 04:00:19 [INFO] [LogBlock] Permissions plugin found.
2011-11-22 04:00:19 [INFO] [LogBlock] Scheduled consumer with bukkit scheduler."

(Yes, I looked throughout the log)

from logblock.

kk, try this to rebuild the table:
(it's my guess that the table is corrupted)

CREATE TABLE lb-players2 LIKE lb-players;
INSERT INTO lb-players2 SELECT * FROM lb-players;
RENAME TABLE lb-players TO lb-players-old;
RENAME TABLE lb-players2 TO lb-players;

from logblock.

Ok trying it now.

from logblock.

Did not help at all. The issue persists. If you give me the sql, I can dump the database for you, but you probably don't want the main block tables as they are over 4 gb...

from logblock.

I think I got the reason: The playerName column is treated case sensitive.

Try:
ALTER TABLE lb-players ENGINE = MyISAM

from logblock.

Nope. Still occurring... This could be bad.

from logblock.

Wait, my bad. Engine doesn't affect case sensitivity at all, it's the collation:

ALTER TABLE lb-players CHARACTER SET latin1 COLLATE latin1_swedish_ci;

from logblock.

Nope :(

from logblock.

Hm, one last thing: the index could be full.
Change the data type of player id coumns to medium int
ALTER TABLE lb-players MODIFY COLUMN playerid MEDIUMINT UNSIGNED NOT NULL AUTO_INCREMENT;
ALTER TABLE lb-chat MODIFY COLUMN playerid MEDIUMINT UNSIGNED NOT NULL; (if this table exists)
ALTER TABLE lb-<worldname> MODIFY COLUMN playerid MEDIUMINT UNSIGNED NOT NULL;
ALTER TABLE lb-<worldname>-kills MODIFY COLUMN killer MEDIUMINT UNSIGNED, MODIFY COLUMN victim MEDIUMINT UNSIGNED NOT NULL; (if this table exists)

from logblock.

Seems to have worked! :D

from logblock.

2011-11-23 21:19:19 [SEVERE] [LogBlock Consumer] SQL exception on INSERT INTO lb-MainWorld-nether (date, playerid, replaced, type, data, x, y, z) VALUES (FROM_UNIXTIME(1322101129), 66540, 87, 0, 0, '74', 49, '2');:
com.mysql.jdbc.MysqlDataTruncation: Data truncation: Out of range value for column 'playerid' at row 1
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3591)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3525)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1986)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2140)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2620)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2570)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:779)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:622)
at de.diddiz.LogBlock.Consumer.run(Consumer.java:278)
at de.diddiz.LogBlock.CommandsHandler$CommandSaveQueue.run(CommandsHandler.java:506)
at de.diddiz.LogBlock.CommandsHandler$AbstractCommand.(CommandsHandler.java:364)
at de.diddiz.LogBlock.CommandsHandler$CommandSaveQueue.(CommandsHandler.java:490)
at de.diddiz.LogBlock.CommandsHandler$CommandRollback.run(CommandsHandler.java:568)
at de.diddiz.LogBlock.CommandsHandler$AbstractCommand.(CommandsHandler.java:364)
at de.diddiz.LogBlock.CommandsHandler$CommandRollback.(CommandsHandler.java:550)
at de.diddiz.LogBlock.LBToolListener$1.run(LBToolListener.java:93)
at org.bukkit.craftbukkit.scheduler.CraftWorker.run(CraftWorker.java:34)
at java.lang.Thread.run(Unknown Source)

I need to fix all my tables now :( Shouldn't LB be updated to autoscale the ints?

from logblock.

yeah, it's planned, but I didn't get the time yet.

so it works now, great.

from logblock.

Wait, now I get massive lag from LB, increasing as time passes.

from logblock.

What kind of lag?
Growing queue or server laggs?

from logblock.

Server lag. The TPS goes from 20 solid slowly down to 1 TPS. (The server hardware is insane, so it's not that)

from logblock.

As this doesn't affect the MC server itself, check if the MySQL server is having troubles.
It may be necessary to regenerate the playerid indices then.

from logblock.

How would I tell if it is? Is there a way to time it?

from logblock.

I don't know your server, but if you've got root access use htop (on unix machines)

from logblock.

It's a windows server, but the mysql database is running on raided SSD's and (appears) to be having no issues.

In any event, are there any things I can do to optimize the main world table? Its over 4 gb in size.

from logblock.

Try if
ANALYZE TABLE lb-MainWorld;
OPTIMIZE TABLE lb-MainWorld;

changes something, depending on the engine this will rebuild the indices.

or move older log into a seperate table (it's unhandy, but indices will be updated faster)

Btw, are you sure the lag is caused by LB?
As lb uses a queue, it can't really lag the server, without significantly increasing the queue ...

from logblock.

I can confirm that LB is causing significant lag and the queue is not large. Do you know what could be causing this?

from logblock.

kk, what are you logging?

from logblock.

And does the lag disappear when using LB 1.41 instead?
(you need to reenable the things you want to log in old format)

from logblock.

Yes, the lag does disappear, but nothing is being logged. D: What is the old format?

from logblock.

You need to reenable loggings:

Old format:

logBlockCreations: true
logBlockDestroyings: true
logCakes: false
logKills: false
logDoors: false
logFire: true
logSnowFade: false
logChestAccess: false
logSignTexts: true
logWaterFlow: false
logChat: false
logSnowForm: false
logButtonsAndLevers: false
logLeavesDecay: false
logEndermen: false
logLavaFlow: false
logExplosions: true

New format:

logging:
  TNTEXPLOSION: true
  SNOWFORM: true
  MISCEXPLOSION: true
  LEAVESDECAY: false
  SIGNTEXT: true
  KILL: false
  CAKEEAT: false
  LAVAFLOW: false
  CHAT: false
  BLOCKBREAK: true
  FIRE: true
  SWITCHINTERACT: false
  WATERFLOW: false
  BLOCKPLACE: true
  SNOWFADE: false
  CHESTACCESS: true
  CREEPEREXPLOSION: true
  GHASTFIREBALLEXPLOSION: true
  DOORINTERACT: false
  ENDERMEN: true

from logblock.

Unfortunately, after enabling logging, it lags quite a lot. The TPS slowly decreases until it crashes on a save. ( ~70 players, <30% core utilization on all 8 cores and <50% allocated memory usage)

Here is my config:
http://pastie.org/2924721

World config:
http://pastie.org/2924723

from logblock.

Which version was that now, 1.41 or 1.42+ (including latest dev)?

Maybe it could be water/lava flow and leaves decay, especially latter causes a lot of block changes.

from logblock.

LogBlock v1.41 #63

from logblock.

kk, maybe my new config system has mor impact than expected ...

from logblock.