Page 1 of 1

Invalid block data data in database: unsupported NameIdMapping version

PostPosted: Thu Feb 27, 2014 22:50
by CraigyDavi
I keep getting this error which crashes the server and causes it to shutdown, here is the full debug:
Code: Select all
22:11:18: ERROR[EmergeThread0]: Invalid block data in database (0,-1933,0) (SerializationError): unsupported NameIdMapping version
22:11:18: ACTION[ServerThread]: Updated online player file
22:11:25: ERROR[EmergeThread0]: Invalid block data in database (0,-1933,0) (SerializationError): unsupported NameIdMapping version
22:11:27: ERROR[main]: ERROR: An unhandled exception occurred: Invalid data in MapBlock (0,-1933,0)
22:11:27: ERROR[main]: ----
22:11:27: ERROR[main]: "Invalid block data in database"
22:11:28: ERROR[main]: See debug.txt.
22:11:28: ERROR[main]: You can ignore this using [ignore_world_load_errors = true].


I have added ignore_world_load_errors = true into the config but I'd rather fix the problem so that the server window stops getting clogged up with error messages.

Would anyone know the problem? I use 0.4.9-dev.

PostPosted: Thu Feb 27, 2014 22:55
by CraigyDavi
After I added the ignore world errors to the config this shows up every few seconds:
Code: Select all
22:53:39: ERROR[EmergeThread0]: Invalid block data in database (0,-1933,0) (SerializationError): unsupported NameIdMapping version
22:53:39: ERROR[EmergeThread0]: Ignoring block load error. Duck and cover! (ignore_world_load_errors)

PostPosted: Thu Feb 27, 2014 23:30
by PilzAdam
CraigyDavi wrote:which crashes the server and causes it to shutdown

Does it crash or does it shutdown properly? It cant do both at the same time.

I guess it would be best if you just replay a backup of the world.

PostPosted: Fri Feb 28, 2014 15:16
by CraigyDavi
PilzAdam wrote:
CraigyDavi wrote:which crashes the server and causes it to shutdown

Does it crash or does it shutdown properly? It cant do both at the same time.

I guess it would be best if you just replay a backup of the world.


It shutdown. I think it has fixed itself now though as there are no more errors.