I have occasional crash problems.

[myavuzokumus]

Bug Report

Description

I tried 16 players together. In uncertain times I usually get the error on the server when creating the cave.

Expected behavior

Correction of crash problems.

Screenshots or video

If applicable, add screenshots to help explain your problem.

Server Information:

• Database being used (YAML, JSON, MySQL, MongoDB): YAML
• OS: Linux
• Java Version: Java 8
• BentoBox version: 1.2.1

[BONNe]

Pls, can you provide crash log, bentobox v message and plugin list.

[myavuzokumus]

I have 2 crash report.
https://paste.ee/p/NjGj5
https://paste.ee/p/i0SP1

[tastybento]

@OverBrave Do these crashed happen when players going to the end, (as mentioned on Discord)?

@BONNe If so, then it may be caused by the server not being able to find a place to stick the end exit island and going into an infinite loop. If that's the case, then the 1.3.0 build with the fix I did for end exit island may help (maybe). Or your end generator may need to make the chunks around 0,0 clear from 250 and above.

[BONNe]

Hmm... for me, it just put it in the top and invalidate, but did not crash a server.
But I will try to get rid of it. (as I do not like 250 limitation :()

[myavuzokumus]

I tried bentobox 1.3 snapshot but when the end goes down.

[BONNe]

@OverBrave , you could try to lower world height (f.e. 250 or 240) and regenerate cave block worlds.
You can do it by changing world-depth in caveblock config.

[myavuzokumus]

Same problem its continues

[tastybento]

@OverBrave Can you try this version of Caveblock and see if it helps?
caveblock-0.1.0.jar.zip

@BONNe I just make a version that makes a hole around 0,0 for chunks so the end exit island can be placed. This is to test to see if the crash is caused by an infinite loop search for a spot to place the island.

[myavuzokumus]

Again crashed.
crash-2019-02-06_10.48.38-server.txt

[tastybento]

You will need to stop the server, delete the Cave End World completely and then try it. Did you delete the world before testing?

[myavuzokumus]

Yes.

[tastybento]

Can you share your console log from the last crash?

[myavuzokumus]

latest.log

[tastybento]

That is far more useful. I was barking up the wrong tree. Thanks. Investigating.

[tastybento]

Work around should be to remove the NETHER_BRICK and CHORUS_FRUIT entries from the config.yml and any other materials mentioned in the console log errors.

• MATERIAL:NETHER_BRICK:10:5
• MATERIAL:CHORUS_FRUIT:1:3

It seems the populator is having an issue setting those blocks. It's random because they are chosen at random.

Need to work out why, but it's past midnight, so another day! Or maybe @BONNe can work it out.

[tastybento]

Found the issue. Fixing now.

[robert-beckley]

I know this was closed and i should make my own ticket but im still having the issue and i never had thoese materials in the list. i wil try and get a crashlog now but the way the server crashes it does not make a log.

[tastybento]

@robert-beckley Yes, please do that.