Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server Crash on startup #2903

Closed
Whazaaaaa opened this issue May 5, 2017 · 22 comments
Closed

Server Crash on startup #2903

Whazaaaaa opened this issue May 5, 2017 · 22 comments

Comments

@Whazaaaaa
Copy link

Whazaaaaa commented May 5, 2017

Description

My server crashes on startup with very little crash-logs. I'm hoping someone can help me solve the issue.
Ae2 has been great so far but I didnt expect this random crash.
This crash happens right after the server is fully started.

I cant really reproduce the issue this just happend out of nowhere and im hoping for a quick edit in a file or whatever that can fix this.

Environment

CRASHLOG: https://pastebin.com/LDjwu292
most system info can also be found in here.

  • Minecraft Version: 1.10.2
  • AE2 Version: appliedenergistics2-rv4-alpha-11
  • Forge Version: FTBserver-1.10.2-12.18.3.2254-universal (2254)
  • Sponge Version: spongeforge-1.10.2-2281-5.2.0-BETA-2303
  • Modpack: AllTheMods 2.54b
  • Multiplayer (players go from 5 to 20 at a time) so its quite populated
@mindforger
Copy link
Collaborator

hm ... this corrupted block thing is becoming viral somewhow, this is at least the third issue with a case of an wrong blockaccess @yueh
funny difference this time it is not an access to a non-existent creative energy cell this time it's a slab

@Whazaaaaa
Copy link
Author

Is there a way to find out in what chunk or whatever it was? So I can remove it and fix the problem?

@mindforger
Copy link
Collaborator

from the crash i suppose either somewhere around the controller or any point where ME parts meet with slabs, no coordinates, maybe AE2 can hook into that particular exception and create a bit debug output as the 4th one is almost predefined to happen

@Ommina
Copy link

Ommina commented May 5, 2017

I see no logging of the position.

I presume you have multiple crash reports by now. Do they all (around or at line 71) read the same "BlockStateContainer{block=tconstruct:seared_slab, properties=[half, type]}"?

It's a bit perplexing, as immediately before the error, it checks to ensure the tile is, in fact a Controller.

@Whazaaaaa
Copy link
Author

All crash report are identical

@mindforger
Copy link
Collaborator

well it COULD be that sponge is interfering here, all checks may fail if sponge does some sort of recycling at the very wrong moment (talking about concurrent modifications of some sort)

check your logfile if somebody joined the game all the time right before the crash, you could possibly reduce the terrain by 9 chunks around his login coordinates then
also make a flyover around all known ME structures and try to pin it down this way (you may need to modify you coordinates in the savegame if you are unable to join)

if it is utterly random happening you can try to run a copy of the server without sponge

@Whazaaaaa
Copy link
Author

Thing is the server crashes without any player being online.

@mindforger
Copy link
Collaborator

mindforger commented May 5, 2017

that supports my theorey of sponge interference ... as so called ghost loading of unloaded chunks adjacent to loaded chunks can cause such issues ... it can also be foamfix ... very hard to say

@Whazaaaaa
Copy link
Author

The server sorta timed out and I did see some foamfix log before I restarted the server. but that log is probably long gone since it only saves the last 4. Now trying without sponge tho

@Whazaaaaa
Copy link
Author

Seems that removing sponge has 'solved' the problem. What can I do now? Find the place and remove it?

@Whazaaaaa
Copy link
Author

So I can join the game properly without spongeforge. But I need to find the spot that is causing this. Would I be correct to think that I would need to find a seared stone slab?

@mindforger
Copy link
Collaborator

try to disable "optimizations" in the sponge config, but thanks for clearing this up, sponge seems to recycle chunkdata and causing such a mess probably ... but i am only guessing!

@Whazaaaaa
Copy link
Author

Turned off optimizations without any luck :(
Here is the crash from the log itself
https://pastebin.com/b0Gu0ht0
Its probably the same but who knows

@Whazaaaaa
Copy link
Author

Would it be an idea to either remove ae2 of tinkers construct from the world?

@mindforger
Copy link
Collaborator

would be interesting to know if that solves it permanently
i would guess it will crash again but with another block ... maybe not instantly

@Ommina
Copy link

Ommina commented May 6, 2017

That said, if it is some weirdness through Sponge, there may not be anything actually corrupt in the world.

Are you able & willing to make a world download available (the 'will crash' version). I wouldn't mind spending a bit of time tracking down the actual position of the (allegedly) broken block.

@Whazaaaaa
Copy link
Author

@Ommina https://whazaaaaa.stackstorage.com/s/DiySJUcrcc1XqWL
This is the worldfolder from before I went into the world without sponge. Perhaps you can still find issues ^^

@HadenOverlord
Copy link

I was having the same issue but for me, the issue occurred when I reset my world I got it to work again by downgrading my Ae2 version to alpha-9.

@HadenOverlord
Copy link

nv it still doesn't work it is definitely a sponge issue because the server works fine without sponge

@Idesmi
Copy link

Idesmi commented Jun 4, 2017

I am having the same issue on the same version.

fml-junk-earlystartup.txt
fml-server-latest.txt

@mindforger
Copy link
Collaborator

@Idesmi well it is not good to hear you have the same problem, but the more important, did you try the same steps? or did you just skip the issue and post to it ? :)

@yueh
Copy link
Member

yueh commented Jul 1, 2017

We do not support Sponge officially.

Should you be able to reproduce it without it, please update the issue accordingly and we will reopen it.

@yueh yueh closed this as completed Jul 1, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants