[MC-98027] Keeping Entity is spammed in the console for all entities and the server becomes extremly laggy, crashing soon after loading into game

Linked issues

duplicates 1

MC-95649 [CONSOLE] keeping entity with UUID spam Resolved

Comments 33

user-f2760 2016-02-25T19:26:29Z

please attach the log and the crash report
also please make a propper description with steps how to reproduce

Gorlov Maxim 2016-03-01T15:14:35Z

Minecraft 1.9 (release)

java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

Server, for example:

...
    [18:03:17] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID fde210a8-2454-4a05-acd5-bef84b3ac4ae
    [18:03:17] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:03:17] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:03:17] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:03:17] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:03:17] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a8dfbae5-44bd-4383-9aaf-b924dc99e685
    [18:03:17] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:03:28] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:03:28] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:03:28] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:03:28] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID d86566d7-c33a-45f3-bd6f-cbb2a2021455
    ...
    [18:05:27] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID fde210a8-2454-4a05-acd5-bef84b3ac4ae
    [18:05:27] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:05:27] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:05:27] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:05:27] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a2a3a912-8fab-405a-8069-8d71530b4503
    [18:05:27] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a8dfbae5-44bd-4383-9aaf-b924dc99e685
    [18:05:27] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:05:37] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:05:37] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:05:37] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 339c2a92-54f1-44eb-83f6-cdbb7dd5c30c
    [18:05:37] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID d86566d7-c33a-45f3-bd6f-cbb2a2021455
    ...

You need crash report of server?

I think this issue reproduce on pre-1.9 worlds

Gorlov Maxim 2016-03-01T21:38:08Z

I have carefully read title...
My server does not crash. And spam to console for not every entity in the game.

Rezzing (Adriana) 2016-03-03T08:00:27Z

I've the same entity spam in my server logs, if I try to continue my 1.8.9 world on 1.9. No crashes but lag spikes and I'm afraid this could damage my game files. Can someone explain, please? Any workarounds?

Gorlov Maxim 2016-03-03T08:37:51Z

@Rezzing I think, we must "recreate" this entityes. Kill/spawn for example.

23 more comments

Rezzing (Adriana) 2016-03-04T05:07:52Z

@Gorlov, ugh, this is basically affecting my entire 350MB region (which is completely vanilla btw.) There must be a better way but repopulating this by hand. That would take forever.

Fábio Cabrita 2016-03-09T20:59:41Z

I had this problem after i made an upgrade on my server from 1.8.9 to 1.9. I am receiving tons of warnings about entitys with certain uuids, and i cannot remove them through command lines (/kill <mob uuid>, /kill @e[type=<mob name>] and /kill @e[!Player]), it seems that the same uuid is not removable from the list, and i have a lot of mobs in this situation. It says that i have killed the mob but after some time it happers again. This result in CPU usage of almost 100%, and after a while, it crashs, and the server restarts.

18:12:25 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:12:49 CONSOLE: [INFO] Killed Horse

18:13:18 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:13:45 CONSOLE: [INFO] Killed Horse

18:13:56 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:14:13 CONSOLE: [INFO] Killed Horse

18:14:42 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:15:24 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

Damien 2016-03-09T21:40:15Z

I'm not getting any crashes, but the daily logs are now 10X the size they were before 1.9 was released. This is impacting how much space each server takes up.

Selected entities keep reporting this message to the console, mostly persistent ones such as villagers and golems, whenever players move around and load chunks.

I can see a huge cascade whenever a player takes a rail past a village for instance.

shufboyardee 2016-03-10T06:03:09Z

I can confirm in 1.9.1-pre1, it doesn't add any NEW spam messages, but when loading worlds from before this, entities STILL spam this message.

Rezzing (Adriana) 2016-03-10T06:26:19Z

@Sealbudsman, 1.9.1-pre1 makes no difference. So please, to not discourage the devs to fix this ASAP: This remains a major issue for worlds generated prior to 1.9.

lolor63 2016-03-10T14:41:49Z

I have the same problem on my server, no crashes but the map is very laggy, it's not my host.
The map was used perfectly with 1.8

I've try repeat /kill @e[type=!Player]
but it do nothing

I've also try the 1.9.1 pre1, but it make no change
[Edit] 1.9.1 pre2 no more change...

shufboyardee 2016-03-10T16:47:03Z

@Rezzing, you are right, I changed my message to affirm that there is still spam in old worlds.

Moleena Smeedgard 2016-03-11T12:04:21Z

Confirming this for 1.9. In my case, the problem appeared after I updated the map from 1.8, on my multiplayer server.
Chunks are slow at loading, especially if I tp to a region badly affected by duplicate entities, but I don't know if those problems are related.
Affecting passive mobs cows, pigs, chicken, horses, villager and iron golem. So far.

Rezzing (Adriana) 2016-03-11T14:44:42Z

Just in case, a copy of my latest game files (from vanilla 1.8.9, not loaded into 1.9): https://www.dropbox.com/s/y3iqdvoryvi6fak/Cubystar_World_1_8_9_March2016.zip?dl=0

lolor63 2016-03-11T15:05:59Z

I try to load my map in singleplayer but it's the same error.

Someone tested in a 1.9 snapshot?
I think it's similar with the invisible skeleton in snapshots

The 1.9.1 pre3 is available, someone can test this?

[Edit] 1.9.1 pre3 Tested, same error at first test,
@FVbico I test all pre-release myself
I just would like to know how your map reacts with pre-release.

user-f2760 2016-03-11T15:07:41Z

@unknown why not test it in the prerelease yourself?

user-f2760 2016-03-11T16:32:44Z

@unknown I don't have this issue anymore, not sure if I even had it to begin with, and I'm not going to bother downloading one of the maps provided as I'm also doing other things right now.

lolor63 2016-03-11T17:01:38Z

After more test, the error persists, [but i think part of lags are missings, good things.]
[UPDATE] after a long test, no changes, lags are here yet.

@FVbico sorry i'm french, i don't understand your answer, are you saying you have no errors and no lags on your map?

user-f2760 2016-03-11T17:04:15Z

I don't have the issue = I don't have the errors at all

lolor63 2016-03-11T17:09:14Z

Ok nice, with an converted 1.8 map? only with 1.9.1 pre-3?

user-f2760 2016-03-11T17:21:29Z

and I'm not going to bother downloading one of the maps provided as I'm also doing other things right now.

I have no maps from 1.8 in my save files anymore, I do have a map from 1.7 which has been running every snapshot till 1.9.1-pre3, so that one hasn't got(no longer has) the issue

lolor63 2016-03-11T17:30:40Z

so it's surely the snapshot who fix that error, i will test that, thanks for info

user-f2760 2016-03-11T17:38:21Z

@unknown again, I've been playing on every snapshot since 1.7, I changed A LOT during those times, including entities, so it might be that I (unknowingly) managed to fix the issue by accident

lolor63 2016-03-11T17:57:28Z

Yes i understand now,
i will test what snapshot can fix this, since 1.8.9, if it's possible of course, i will tell you if it work.

Damien 2016-03-11T23:49:41Z

"I don't have the issue = I don't have the errors at all"

I might be missing something. Why would you bother commenting that? I don't know that its a universal problem, so I don't think everyone will have it?

It looks like a problem with old maps being brought in - mobs that are persistent for some reason (villagers, or zombies holding things, or named, etc) are spamming the logs. Not everyone sees a slow down.

user-f2760 2016-03-11T23:53:43Z

@unknown I replied this this comment:

@FVbico sorry i'm french, i don't understand your answer, are you saying you have no errors and no lags on your map?

and I know what the problem is in this ticket, I know it has to do with old maps, I'm just telling him that I don't have the issue at all, not even once saw it

user-f2760 2016-03-16T15:27:53Z

actually this is a duplicate of MC-95649

lolor63 2016-03-16T15:38:06Z

Why you close this post, its better explain in this post than the other,?
And there are more people here

user-f2760 2016-03-16T15:39:43Z

because that one was reported earlier

its better explain in this post than the other

and this one has no description

user-f2760 2016-03-16T20:24:12Z

go ahead, just don't make it a discussion forum 😉

Sledge Fox 2016-07-24T13:48:33Z

I have the same problem and I'm no longer able to play the game on my server. Please help!!!

Here the full description of the problem:
http://www.minecraftforum.net/forums/support/server-support/2715194-keeping-entity-that-already-exists-server-version

Ok, I made the mistake to update this buggy game from 1.8.9 to 1.10.2 (Server and Client) and the server gives me error messages like:

[18:37:23] [Server thread/WARN]: Keeping entity Pig that already exists with UUID c7c7fc74-bdca-4d43-a135-69bb3d257d0f
[18:37:23] [Server thread/WARN]: Keeping entity Cow that already exists with UUID c0a0ac0d-3491-44bc-a4c1-71c633cb8fb5
[18:37:23] [Server thread/WARN]: Keeping entity Cow that already exists with UUID 1752c06a-b982-43ac-a323-fb0cd6b0379d
[18:37:23] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 908d49b9-a0f7-4709-aeac-b0a6c0528089
[18:37:23] [Server thread/WARN]: Keeping entity Cow that already exists with UUID 1e4c5bb0-ab4e-499e-bfd4-6a6ed5c8c37f
[18:37:23] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID a58cf73c-99c0-4697-aed5-f63d40fd0804
[18:37:23] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID c64c4d5c-274a-4efb-8500-6417a96cd7ec
[18:37:23] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 3a89e16e-d7d9-41cb-be6d-273936cf40a0
[18:37:23] [Server thread/WARN]: Keeping entity Cow that already exists with UUID cbc367f3-9a5f-4352-a575-962189c57fb8
[18:37:23] [Server thread/WARN]: Keeping entity Cow that already exists with UUID 6fd32058-c6a8-4ef7-a6e2-f9d697d264a4
[18:37:23] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 6f224a6f-f54f-4158-8add-d77fc7fc1926

After a while the Server gets more and more laggy and I lose connection to the Server which runs on my own machine. So, who shall I congratulate for this programming achievement?

Is there a remedy for this nonsense? How can I get my paid game to work as intended? Please help!

P.S.: If I try to kill the things with in the console with "/kill 3882a1be-00c0-4a58-b432-5c31f4503b94" for example, the server tells me, the mob is killed. So I killed all problematic entities, restarted the server and behold, all errors came again.

So, please help!

Sledge Fox 2016-07-24T13:54:42Z

Maybe interesting too: If I stop the server, I get:

stop

[15:53:41] [Server thread/INFO]: Stopping the server
[15:53:41] [Server thread/INFO]: Stopping server
[15:53:41] [Server thread/INFO]: Saving players
[15:53:41] [Server thread/INFO]: Saving worlds
[15:53:41] [Server thread/INFO]: Saving chunks for level 'world'/Overworld
[15:53:41] [Server thread/INFO]: Saving chunks for level 'world'/Nether
[15:53:41] [Server thread/INFO]: Saving chunks for level 'world'/The End
[15:53:41] [Server Shutdown Thread/INFO]: Stopping server
2016-07-24 15:53:41,994 ERROR Attempted to append to non-started appender File
2016-07-24 15:53:41,996 ERROR Unable to write to stream logs/latest.log for appender File
2016-07-24 15:53:41,998 ERROR An exception occurred processing Appender File org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to RandomAccessFile logs/latest.log
        at org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.flush(RollingRandomAccessFileManager.java:109)
        at org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.write(RollingRandomAccessFileManager.java:90)
        at org.apache.logging.log4j.core.appender.OutputStreamManager.write(OutputStreamManager.java:129)
        at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:113)
        at org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender.append(RollingRandomAccessFileAppender.java:96)
        at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:99)
        at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:425)
        at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:406)
        at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:367)
        at org.apache.logging.log4j.core.Logger.log(Logger.java:110)
        at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:1011)
        at net.minecraft.server.MinecraftServer.u(SourceFile:381)
        at net.minecraft.server.MinecraftServer$2.run(SourceFile:738)
Caused by: java.io.IOException: Stream Closed
        at java.io.RandomAccessFile.writeBytes(Native Method)
        at java.io.RandomAccessFile.write(Unknown Source)
        at org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.flush(RollingRandomAccessFileManager.java:106)
        ... 12 more

2016-07-24 15:53:42,032 ERROR Attempted to append to non-started appender ServerGuiConsole
Exception in thread "Server Shutdown Thread" org.apache.logging.log4j.core.appender.AppenderLoggingException: Attempted to append to non-started appender ServerGuiConsole
        at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89)
        at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:425)
        at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:406)
        at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:367)
        at org.apache.logging.log4j.core.Logger.log(Logger.java:110)
        at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:1011)
        at net.minecraft.server.MinecraftServer.u(SourceFile:381)
        at net.minecraft.server.MinecraftServer$2.run(SourceFile:738)

marcono1234 2016-08-28T20:52:35Z

@unknown, what you described last is probably MC-38134