Jump to content
  • 0

Server stopping at random


snowyfleury

Question

Hi there, using format this time:

Launcher/pack Version: server 2.1.1

Operating System: CentOS 6

Version of Java: Java SE Runtime Environment (build 1.7.0_03-b04)

Java HotSpot 64-Bit Server VM (build 22.1-b02, mixed mode)

Description of Problem: Tekkit shuts itself down at random. Often I will receive the [iNFO] stopping server..., but sometimes it simply shuts off without saying anything in the logs.

A few times I got some oddities about not being able to verify users with the minecraft website before crashing, so it's running offline mode right now, without any change in behavior. Those error messages are gone though.

Error Messages: none in server, in client: "Internal exception: java.net.SocketException: Connection reset"

Link to pastebin of log: http://pastebin.com/AvkhLxHe

Link to comment
Share on other sites

21 answers to this question

Recommended Posts

  • 0

That's a full cycle of booting, playing for a few minutes and crashing, but sure let me figure out how to copy out the whole thing. Will edit this post in a bit. Note that it won't be the same exact part of the log because it's crashed a good 5 times since that log.

Link to comment
Share on other sites

  • 0

I'm on Technic Launcher 0.5.4.9 selecting Tekkit from the drop down. Is that not vanilla?

edit: Also, we aren't waiting for it to boot. Me and my friend (He's offline now and thus not in that log) were just reconnecting as soon as we could because the crash happens every 5 minutes or so it feels like. How long should we be waiting?

Link to comment
Share on other sites

  • 0

So I don't know if this is relevant but i'm posting it because it's horribly annoying:

When this crash occurs, anything not in a proper inventory is lost. So any items being dragged with my mouse vanish into nothing, and anything in crafting tables vanishes. It makes crafting valuable items most frightening.

Link to comment
Share on other sites

  • 0

wait for it to stop spamming the console with info. usually this is marked by a line stating how long it took to boot up.

the reason I ask about the vanilla client is that in that log, a person is connecting with a much sorter string of mods than what a tekkit client would have.

Link to comment
Share on other sites

  • 0

The only 2 people connecting are 12345678ew(me) and my friend inferno96.

I've uninstalled worldedit and commandbook if thats of any relevance, I had no use for them and was trying to reduce the possible causes of the issue. Would that have made the list of mods shorter when a person connects?

edit: Also i don't believe I ever get a line stating how long it took to boot. My last line is typically something about equivalent exchange RP2. Will get an exact quote on next boot cycle.

edit2:

09:40:08 [iNFO] RP2 Core successfully loaded in EE.

09:40:08 [iNFO] RP2 World successfully loaded in EE.

Link to comment
Share on other sites

  • 0

removing server mods won't change the mods clients have. those last two lines do sound about right for being finished booting as well.

it just seems like it's having a fit with people joining. normally the list of mods displays twice, but in your log it's 3 times and it ends in a $ way before it should each time.

I guess try a clean reinstall of the server. back up your world if you like, of course. though try it with a whole new one first to see if it explodes

Link to comment
Share on other sites

  • 0

This log looks the same as my test server logs, which run fine and don't crash. Line 206 of the log has the time it took to start "2012-04-08 04:31:55 [iNFO] Done (0.913s)! For help, type "help" or "?"". There are some EE, RP2 and Railcraft messages that appear after this, but that happens on my working server.

Link to comment
Share on other sites

  • 0

It's a semi-managed vps, so tomorrow i'll reinstall the OS and go from there I think, but for now, I just go this odd log when booting:

11:10:06 [sEVERE]    at net.minecraft.server.ChunkProviderServer.loadChunk(ChunkProviderServer.java:135)

11:10:06 [sEVERE]    at net.minecraft.server.ChunkProviderServer.getChunkAt(ChunkProviderServer.java:78)

11:10:06 [sEVERE]    at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:332)

11:10:06 [sEVERE]    at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:178)

11:10:06 [sEVERE]    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:411)

11:10:06 [sEVERE]    at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)

11:10:06 [iNFO] Preparing start region for level 1 (Seed: 7785765189754620511)

11:10:06 [iNFO] Preparing start region for level 2 (Seed: 7785765189754620511)

11:10:06 [iNFO] [ChopTree] Loading ChopTree v1.2.

11:10:06 [iNFO] [ChopTree] Permissions not detected, defaulting to ops.

11:10:06 [iNFO] ChopTree 1.2 enabled!

11:10:06 [iNFO] Server permissions file permissions.yml is empty, ignoring it

11:10:06 [iNFO] Done (0.958s)! For help, type "help" or "?"

11:10:06 [iNFO] RP2 Core successfully loaded in EE.

11:10:06 [iNFO] RP2 World successfully loaded in EE.





Lots of [sEVERE]...







edit: Alright that session with the weird boot shown above just crashed, weird crash too:




11:19:40 [iNFO] Read timed out

11:19:40 [sEVERE] java.net.SocketException: Socket closed

11:19:40 [sEVERE]    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)

Link to comment
Share on other sites

  • 0

It takes an extra 15 minutes to reinstall the OS, and I have all sorts of questionable things in my java installation. Like I said it's a virtual server, so it's not actually reinstalling the OS, it's throwing that server away and instantly receiving a clean new one with the same ip.

Link to comment
Share on other sites

  • 0

Full reinstall done, it behaves the same. This is with pure default settings. All i did was zip my world, ftp it off the vps, reinstall centOS 6 64 bit, reinstall oracle java 7 64 bit via rpm, redownload tekkit, unzip world in tekkit folder, and run it.

Still crashes funny. I'll now be deleting my technic launcher and redownloading that, in hopes that something about it is off.

edit: Brand new launcher doesn't help. New map didn't help either.

edit2: I've copied my log to the apache directory, so it can be viewed here: http://50.115.168.111/server.log

I will try to update that copy every time it crashes.

edit: Is there any way to run the tekkit server in debug mode or something to get more information when it crashes?

Link to comment
Share on other sites

  • 0

Yes the server is absolutely *deciding* to stop, not crashing. That's the exact same thing you would see in the log if I typed stop, except it's missing [CONSOLE] stopping the server... before the [iNFO] stopping the server...

So it's stopping itself, presumably because it's running into a problem.

Link to comment
Share on other sites

  • 0

I think I remember having a problem like this years ago on a vanilla server, and it was solved by increasing some sort of delay. The delay controlled how long the server would wait to finish an action before deciding something had gone wrong IIRC. Is there anything similar in Tekkit?

edit: Well anyway, taking another shot with a different distro in hopes that solves it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...