Content: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Background: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Pattern: Blank Waves Notes Sharp Wood Rockface Leather Honey Vertical Triangles
Welcome to TerraFirmaCraft Forums

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

  • Announcements

    • Dries007

      ATTENTION Forum Database Breach   03/04/2019

      There has been a breach of our database. Please make sure you change your password (use a password manager, like Lastpass).
      If you used this password anywhere else, change that too! The passwords themselves are stored hashed, but may old accounts still had old, insecure (by today's standards) hashes from back when they where created. This means they can be "cracked" more easily. Other leaked information includes: email, IP, account name.
      I'm trying my best to find out more and keep everyone up to date. Discord (http://invite.gg/TerraFirmaCraft) is the best option for up to date news and questions. I'm sorry for this, but the damage has been done. All I can do is try to make sure it doesn't happen again.
    • Claycorp

      This forum is now READ ONLY!   01/20/2020

      As of this post and forever into the future this forum has been put into READ ONLY MODE. There will be no new posts! A replacement is coming SoonTM . If you wish to stay up-to-date on whats going on or post your content. Please use the Discord or Sub-Reddit until the new forums are running.

      Any questions or comments can be directed to Claycorp on either platform.
Sign in to follow this  
Followers 0
InsaneJ

[Can't Fix] Server Exception ticking world

22 posts in this topic

TFC Version #: 0.79.18.673 Forge Version #: 7.10.85.1291 SSP/SMP (SinglePlayer/MultiPlayer): MultiPlayer Description: The server crashes when a player goes to a certain area that has what we think may be falling blocks in it.

java.lang.NoClassDefFoundError: net/minecraft/world/World$2	at net.minecraft.world.World.func_147460_e(World.java:714)	at net.minecraft.world.World.func_147459_d(World.java:648)	at net.minecraft.world.World.func_147444_c(World.java:613)	at net.minecraft.world.World.markAndNotifyBlock(World.java:488)	at net.minecraft.world.World.func_147465_d(World.java:466)	at net.minecraft.world.World.func_147468_f(World.java:573)	at com.bioxx.tfc.Blocks.Terrain.BlockCollapsible.tryToFall(BlockCollapsible.java:278)	at com.bioxx.tfc.Blocks.Terrain.BlockDirt.func_149674_a(BlockDirt.java:188)	at net.minecraft.world.WorldServer.func_147456_g(WorldServer.java:391)	at net.minecraft.world.WorldServer.func_72835_b(WorldServer.java:183)	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:625)	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:334)	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547)	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:427)	at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)

When opening the affected area in MCEdit and doing an analysis of the blocks in the region there are several dozen falling block entities there. Removing all the entities in that area and going there again does not solve the crash. After another server start (with the entities removed) and going to the affected area again the falling block entities return (according to another MCEdit region analysis) and the crash happens again.

 Have you deleted your config files or are using default configs and are still able to reproduce this bug? (Yes/No): Yes Do you have any mods other than Forge and TFC installed? (Yes/No): NoIf yes, which mods?  If you have Optifine or Cauldron installed, can you still reproduce the bug after uninstalling them? (Yes/No): Both server and client were only running Forge + TFC Pastebin.com link of the Crash Report:

Crash-report: http://paste2.org/Oe3Z3me4

fml-server-latest.log: http://paste2.org/91e9W7dL

1

Share this post


Link to post
Share on other sites

I'm going to need a bit more information. A world$2 crash is generally caused by too many block updates happening all at once. There's multiple reasons why this crash could happen. The player could have simply caused a very large collapse, or they could have been using an exploit in the previous version to hold falling blocks up which has since been fixed so they all fell down, or something else entirely. Could you load a copy of the world with 79.17 to see if it still happens? Could you use MCEdit to get more information about the falling blocks? Are they underground, what blocks are they trying to fall onto, etc?

0

Share this post


Link to post
Share on other sites

We've had this problem since 79.17 and waited for 79.18 in the hopes that the infinite sound bug was somehow related and it's fix would solve this problem as well. Running it with 0.79.17.645 again didn't solve the crash.

fml-server-latest.log: http://paste2.org/WtmOzCda

crash-report: http://paste2.org/9Z9Ojgvk

 

I'm fairly certain it has nothing to do with any player-made structures since this problem also happens in places no player has ever build anything. When I analyze region -1, -12 (from the 79.17 crash-report in this post) in MCEdit I see the following:

(0:0),Air,0(0:0),Air,17356060(7:0),Bedrock,545357(11:1),Lava,2536(165:1),Slime Block,4075(165:2),Slime Block,891(165:4),Slime Block,1385(165:5),Slime Block,2393(165:6),Slime Block,2200(165:7),Slime Block,2095(165:10),Slime Block,1195(165:11),Slime Block,2042(165:12),Slime Block,4884(165:13),Slime Block,1931(165:14),Slime Block,18497(165:15),Slime Block,5205(166:0),Barrier,3489(166:1),Barrier,594(166:4),Barrier,867(166:8),Barrier,2707(166:13),Barrier,1801(166:15),Barrier,26(167:0),Trapdoor,5598(168:1),Future Block!,8275748(169:1),Future Block!,127845(176:2),Future Block!,3429908(177:2),Future Block!,6976961(177:4),Future Block!,1430584(188:5),Future Block!,40(190:5),Future Block!,260740(192:0),Future Block!,24568(192:5),Future Block!,86708(202:5),Future Block!,62333(204:0),Future Block!,12(204:1),Future Block!,64(204:2),Future Block!,5218(205:0),Future Block!,2067(216:3),Future Block!,67(216:4),Future Block!,99(216:11),Future Block!,91(218:3),Future Block!,594(218:4),Future Block!,601(218:11),Future Block!,759(231:3),Future Block!,1(233:0),Future Block!,1(239:0),Future Block!,2133(239:8),Future Block!,2178(427:0),Future Block!,901045(428:0),Future Block!,31(429:0),Future Block!,15884(435:5),Future Block!,1710(472:0),Future Block!,39(473:0),Future Block!,45(476:0),Future Block!,2(482:0),Future Block!,380(482:1),Future Block!,7(482:6),Future Block!,1(482:11),Future Block!,1(488:5),Future Block!,337131,,,<Entities>,116Bat,Bat,15creeperTFC,creeperTFC,7endermanTFC,endermanTFC,3pigTFC,pigTFC,3skeletonTFC,skeletonTFC,21spiderTFC,spiderTFC,5squidTFC,squidTFC,30zombieTFC,zombieTFC,32,,,<TileEntities>,65693IronBloom,IronBloom,1Sea Weed,Sea Weed,1710TerraEarlyBloomery,TerraEarlyBloomery,1TileEntityCrop,TileEntityCrop,39ore,ore,61875worldItem,worldItem,2067

 

Oddly enough this region file doesn't seem to have any falling blocks stored in it. The region files I investigated earlier did. Here is one of region -1,-12 which contains the spawn area for that world:

(0:0),Air,0(0:0),Air,29311642(0:1),Air,1(0:2),Air,1(0:4),Air,160(0:5),Air,1(0:11),Air,27(1:0),Stone,69610(7:0),Bedrock,864073(11:1),Lava,2536(22:0),Lapis Lazuli Block,796(64:5),Wooden Door,1(64:8),Wooden Door,1(65:2),Ladder,15(65:3),Ladder,6(68:2),Wall Sign,4(89:0),Glowstone,623(132:0),Tripwire,2(165:1),Slime Block,12999(165:2),Slime Block,248(165:4),Slime Block,1974(165:5),Slime Block,8080(165:6),Slime Block,4470(165:7),Slime Block,1943(165:10),Slime Block,593(165:11),Slime Block,2854(165:12),Slime Block,6416(165:13),Slime Block,4426(165:14),Slime Block,23093(165:15),Slime Block,3180(166:0),Barrier,1529(166:1),Barrier,3693(166:4),Barrier,5(166:5),Barrier,873(166:8),Barrier,3086(166:13),Barrier,1928(166:15),Barrier,1796(167:0),Trapdoor,3640(168:1),Future Block!,13859241(168:2),Future Block!,756686(169:1),Future Block!,127847(176:2),Future Block!,4375727(177:2),Future Block!,12719927(177:4),Future Block!,1431619(177:5),Future Block!,140(180:2),Future Block!,127(180:10),Future Block!,289(181:4),Future Block!,4(183:2),Future Block!,38(184:2),Future Block!,220(186:1),Future Block!,23(187:1),Future Block!,18(187:2),Future Block!,3(189:5),Future Block!,7929(190:0),Future Block!,460(190:5),Future Block!,259164(190:13),Future Block!,11(192:0),Future Block!,86758(192:2),Future Block!,37073(192:5),Future Block!,113845(202:0),Future Block!,23(202:1),Future Block!,10(202:5),Future Block!,61643(202:13),Future Block!,46(202:14),Future Block!,2(204:0),Future Block!,9(204:1),Future Block!,66(204:2),Future Block!,4513(205:0),Future Block!,1187(209:5),Future Block!,29(211:4),Future Block!,9(212:4),Future Block!,3(216:3),Future Block!,448(216:4),Future Block!,1628(216:11),Future Block!,1045(218:3),Future Block!,3429(218:4),Future Block!,17444(218:11),Future Block!,9286(222:0),Future Block!,1(222:4),Future Block!,78(223:0),Future Block!,12(224:0),Future Block!,5(225:1),Future Block!,1(228:0),Future Block!,1(239:0),Future Block!,3603(239:8),Future Block!,3615(241:4),Future Block!,20(243:4),Future Block!,10(243:12),Future Block!,10(247:0),Future Block!,1(411:5),Future Block!,616(415:5),Future Block!,48(427:0),Future Block!,2498860(427:8),Future Block!,21(428:0),Future Block!,185(429:0),Future Block!,16168(429:1),Future Block!,24(429:2),Future Block!,5(429:3),Future Block!,1(429:8),Future Block!,16(429:9),Future Block!,33(429:10),Future Block!,2(435:2),Future Block!,93(435:5),Future Block!,1930(442:1),Future Block!,1(442:8),Future Block!,1(456:0),Future Block!,2(456:7),Future Block!,1(460:0),Future Block!,3(461:0),Future Block!,1(472:0),Future Block!,19(476:0),Future Block!,11(478:9),Future Block!,1(478:10),Future Block!,1(478:11),Future Block!,1(479:4),Future Block!,4(479:5),Future Block!,2(482:0),Future Block!,299(487:2),Future Block!,9509(487:5),Future Block!,359355,,,<Entities>,55fallingBlock,fallingBlock,55,,,<TileEntities>,90116Barrel,Barrel,3Bellows,Bellows,1LightEmitter,LightEmitter,3Pottery,Pottery,3Sea Weed,Sea Weed,2023Sign,Sign,4TerraFirepit,TerraFirepit,5TerraForge,TerraForge,1TileEntityCrop,TileEntityCrop,19TileEntityFarmland,TileEntityFarmland,29ToolRack,ToolRack,1chest,chest,6leatherRack,leatherRack,5ore,ore,86826worldItem,worldItem,1187

 

As you can see there are 55 stored falling block entities in that region file. Those blocks seem to be located underground. This is what they look like:

Posted Image

The top rows (red) are the falling blocks. The row directly below that is air and the row below that is vanilla Minecraft stone which was placed there in an attempt to prevent the crashes. Before the vanilla stone the area was made up of 190:5 which crashed in the same manner.

 

 

 

1

Share this post


Link to post
Share on other sites

It's literally just a crash because too many block updates are happening at the same time for the game to handle. It's the exact same crash that some servers have when large sequoia trees are chopped down and all the leaf blocks update.

 

Every time that a falling block lands, a block update happens. If you have a whole bunch of falling blocks landing on the ground at the same time, you get a lot of block updates.

 

The reason that you're seeing this even in areas that no players have built in is because when a chunk is loaded, some of the dirt, sand and gravel blocks will get a random update, and attempt to fall. If they successfully fall, then all of their floating neighbors are going to fall too. This is most commonly seen with entire mountainsides shifting around when generating new terrain. It's no different than finding a massive area of floating sand and vanilla, and then breaking one of the blocks to cause the rest to fall. The only change is that instead of a player breaking a block, it's triggered by just a random tick from the chunk loading.

 

Just like there is no fix for all the block updates caused by chopping down a large sequoia tree, there is no fix for all the block updates caused by an extremely large cave-in, or collapse of dirt and gravel blocks. Imagine that a cave has generated in such a way that its entire ceiling is composed of dirt and gravel blocks. If any of those blocks updates, then the entire cave is going to collapse on itself because the dirt and gravel ceiling isn't supposed to be floating.

 

Also, placing the vanilla stone underneath the entities just makes the problem worse, because now all the blocks are falling onto the same flat terrain, and will likely land all at the same time, creating a bunch of block updates all at once. If instead the falling blocks just fall naturally onto uneven ground, they will be landing and therefore causing block updates at a slightly more spread out pace.

 

Edit: If you want to "fix" this issue, you'll need kill all of the falling block entities, and inform your players that they need to be careful when out exploring and that they should be exercising extreme caution so they don't ever intentionally cause a large cave-in, or just collapse of dirt/gravel/sand blocks.

Edited by Kittychanley
0

Share this post


Link to post
Share on other sites

The problem occurs when a single player joins the sever. That person doesn't even have to do anything, just join. Therefore it can't really be avoided by being careful when out exploring I'm afraid.

 

If the problem lies in too many block updates due to falling blocks. Wouldn't a possible solution be to limit the amount of simultaneously falling blocks? Perhaps something like: blocks needs to fall, check how many are already falling, any block that goes over the limit (config option?) gets put in a queue, check queue every 10 ticks or so?

 

If what you say is correct it should only affect the behavior of really large cave-ins. The smaller ones that aren't a problem should then happen as they do now.

1

Share this post


Link to post
Share on other sites

Right, when that player joins they load the chunks that all the falling blocks are in. So now the chunks are loaded and falling, then they land on the ground causing a block updates. Lots of block updates happen immediately after the player joins because the falling blocks have been loaded, and the game crashes. You'd get the exact same result if a different player who is already online on the server walked over to where that single "bad" player would appear if he logged in.

 

Adding a system to limit the max number of falling blocks at once is not something that can feasibly be implemented in standard TFC. It would require a rewrite of how we currently handle falling blocks, so it would not be implemented until TFC2 if at all.

0

Share this post


Link to post
Share on other sites

Do you have any indication of how many falling blocks are too many? Because from what I can tell so far it's never more than a few dozen at a time. In the MCEdit example posted above it's 55 falling blocks for a single region file.

 

On vanilla Minecraft (running on Spigot) I've seen literally hundreds of thousands of falling sand blocks fall down without much more than a bit of lag for a few seconds while they updated. On our TFC server we've seen it process and log over a million block updates an hour due to snow without problems.

 

You're one of the TFC devs and if you say the problem is caused by too many block updates then who am I to argue with that? It's just that I'm not seeing it right now. When there are too many block updates happening on a server it will cause the server to lag, time out or even freeze but it doesn't crash. I've never seen a server crash because of the load being too high. Going out of memory, sure that will crash a server. Having a ton of entities spawned in will cause you to disconnect. Having several thousands of block updates per second will cause low TPS. But server crashes are most always a result of a bug of some kind.

 

Please reconsider the diagnosis of this problem.

1

Share this post


Link to post
Share on other sites

Well the likely thing that will work is to sacrifice the region to save the rest of the server. The effected region could just be deleted and allowed to regenerate. Alternatively the chunks effected could just be emptied to bedrock with MCEdit and then regenerated. I know that WorldEdit //regen does work in TFC, it just won't regenerate any ores, so the regenerated chunks are completely lacking in ores.

0

Share this post


Link to post
Share on other sites

After fixing a handful of affected areas we've given up hope that this will solve the issue for us. The problem seems to happen all over the map at different locations.

1

Share this post


Link to post
Share on other sites

Well I loaded up that seed to have a look to see if I could replicate what happened. So the player that triggered this issue was mining a very large shallow graphite vein that was on the edge of a precarious ravine. They did not take the new falling blocks destroying ores mechanic and triggered a cave in which due to the way the blocks fell and how the vein generated resulted in a perfect storm of blocks falling on the ores destroying, falling more and more. This is what triggered the loop of notifyBlockOfNeighborChange which is crashing your server. I'm not sure if this is a rare occurrence or not with the new mechanic, but it is exceedingly hard to test. It would require backing up a specific map and figuring out the exact blocks to mine/support in the right order to trigger the event.

Have you tried downgrading to build .15? I'm guessing you have, but if not give that a shot.  Change the config to have ore blocks not destoryed. (The Kitty Edit completed by Bunsan.)

Edit: the location I took from your location in the crash report.

0

Share this post


Link to post
Share on other sites

Thank you (and Kitty and whomever else may have looked at it :)) for taking the time to investigate. Unfortunately the problem isn't in one location, it's happening all over the map at dozens of locations.

 

Players enjoy the dangers of cave ins. Turning that off would disappoint a lot of people. Because of this we have decided to generate a new map for our hardcore server using TFC 79.18.

 

Should we happen to encounter this problem again, would you be interested in follow up reports?

Edited by InsaneJ
1

Share this post


Link to post
Share on other sites

It wasn't the cave ins I said to shut off, but the destroying ore part. Turning it off, even briefly, could break the loop that is crashing the server. Best of luck with new map.

0

Share this post


Link to post
Share on other sites

InsaneJ, were you able to solve this by disabling destroying ore for a bit?

0

Share this post


Link to post
Share on other sites

I've been working a bit behind the scenes with this world as well and did some further testing.

 

I disabled the cavein option in the config with no effect. I then disabled the ore destroy with no effect. I also tested keeping the caveins on and the ore destroy off with no effect. I then backdated the world to .15 and repeated the last steps with no change. The problem persists.

Edited by Jiro_89
0

Share this post


Link to post
Share on other sites

I don't have the time now to do all the tests and upload the logs. 

I understand that without that, there is not much you guys can say.

Today I try to update our server to 0.79.18 and something funny happened, the server would not crash, but the every player upon entering the server would have their client crash.

We have a ton of mods, and it is a Cauldron Server, so it will take a lot of testing to find the cause of the problem. In the end we just reverted to the 0.79.17.

I had no idea the update could cause a problem like that. It was really weird because the server was working fine up untill we upload the new update.

I will do some tests tomorrow and try to post the logs. 

0

Share this post


Link to post
Share on other sites

If you have the cellars mod installed on the server, or any add-on that adds a custom anvil recipe, that's probably the cause. Anvil recipes were tweaked in .18 that breaks compatibility with some addons on servers

0

Share this post


Link to post
Share on other sites

Thanks for the help Kitty. No we do not have the cellars addon, I read on their tread that is having some issues with servers.

This is a list of the mods we have:

BiblioCraft[v1.10.4][MC1.7.10].jarBiblioWoods[TerraFirmaCraftV0.79.17][v1.0].jarCarpenters Blocks v3.3.4.2 .jarCodeChickenCore-1.7.10-1.0.4.35-universal.jarCraftHeraldry 1.1.3.jarCustomNPCs_1.7.10c.jarFarseek-1.0.5.jarfastcraft-1.21.jarHQM-The Journey (4.2.3).jarMineTweaker3-1.7.10-3.0.9B.jarNotEnoughItems-1.7.10-1.0.4.95-universal.jarOptiFine_1.7.10_HD_B6.jarShadersModCore-v2.3.28-mc1.7.10-f.jarshipsMod-v1.7.10-1.0.2.jarStreams-0.1.4.jarTerraFirmaCraftNEIplugin-1.7.10-1.4.0.19.jarWaila-1.5.10_1.7.10.jar[1.7.10]Decorations-1.0.17.jar[1.7.10]LeatherWaterSac-3.5.B79.jar[1.7.10]Merchants-1.0.29.jar[1.7.10]TerraFirmaCraft-0.79.17.645.jar

The hard part is that there is no log on the server, the server does not crash, only the player client does it.
I will try to get a test server with just tfc and no other plugins or mods, if the problem persists I will post the client crash log.
0

Share this post


Link to post
Share on other sites

Merchants mod has the same issue as cellars. That is probably what is causing your problem.

0

Share this post


Link to post
Share on other sites

You just save me from a whole lot of testing. Thank you very much. I will remove Merchants on the test server and see if that solves the problem. If it does we can ask Aleksey for an update to his addon.

0

Share this post


Link to post
Share on other sites

And BiblioWoods TFC also adds anvil recipes.

0

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0