TOG - The Older Gamers

Phlexor · 1st March 2013, 02:46 PM

Quote:

Disconnected by Server
Internal server error

Okay, don't know what is causing these errors but I mainly get them when using a link book from my mine in the Caverns to go to my home in Spawn City.

Now I'm also getting them when I use an Advanced Chainsaw on Root Strands in the Twilight Forest. Every single time.

I don't know if its the recent changes or the Advanced Chainsaw itself (never used it on Root Strands before, used the regular Chainsaw though), but something needs to be worked out and bug reports submitted to the relevant projects if that's not too much bother?

But only if it doesn't cause long down time of the server. If it will, then I'll learn to live with it!

Irimar · 1st March 2013, 02:59 PM

Quote:

Originally Posted by Phlexor

Now I'm also getting them when I use an Advanced Chainsaw on Root Strands in the Twilight Forest. Every single time.

That's been happening to me since we were on the beta pack. Hadn't tried it since the move to Mindcrack, but I guess it's still a problem.

Next time you get that error, instead of closing Minecraft, press the "Paste my log to pastebin.com" button on the FTB Launcher console and get the URL of the page that comes up. I can't promise that anyone will have an answer, but that gives us the FTB Launcher's log to look at.

Phlexor · 1st March 2013, 03:11 PM

I've done some Googling (probably should have done that first) and it seems to happen to others as well. One place also suggests that if you do it often enough it will corrupt the world as well. So a warning not to try it unless you are running from a backup of the server to test things out.

Also there was nothing in the FTB Launcher log (around the time of the error) and nothing in the client. Unless I'm looking in the wrong place.

DarkDuck · 1st March 2013, 04:10 PM

feel free to submit the bug reports yourself, you do have the crash report on your system. As the server did not crash we will not have a crash report so there is nothing we can do on the admin side until a crash happens to us.

sorry Phlexor, this appears to be all yours to report on for now.

Bru1zer · 1st March 2013, 04:47 PM

I also get this 9/10 times I linkbook out of the wasteland

DaedalusAlpha · 1st March 2013, 08:37 PM

I get it if I stand one block above an RedPower redstone circuit and try to access it (right click) with some sort of placeable block in my hand. The client thinks it should place the block above the circuit, the server thinks the block should not be placed at all so i get thrown out with the internal server error.

Phlexor · 2nd March 2013, 03:29 AM

Quote:

Originally Posted by DarkDuck

feel free to submit the bug reports yourself, you do have the crash report on your system. As the server did not crash we will not have a crash report so there is nothing we can do on the admin side until a crash happens to us.

sorry Phlexor, this appears to be all yours to report on for now.

Does internal server error mean the server or the client, because there is nothing on this end in the console log and no crash report. As far as the client is concerned, i just got booted for the stated reason.

I mean with the link books, they worked fine before the down time and tweaking and nothing has changed on this end so I fail to see how that's a client problem. So I wouldn't even know where to begin with tracking down where the problem is occurring I guess.

DaedalusAlpha · 2nd March 2013, 04:00 AM

I'm simply thinking it's a conflict between what the client thinks and what the server thinks. None of them are wrong per say, but their views of the world can not be combined so the client is kicked.

Cheith · 2nd March 2013, 04:42 AM

Quote:

Originally Posted by Phlexor

Does internal server error mean the server or the client, because there is nothing on this end in the console log and no crash report. As far as the client is concerned, i just got booted for the stated reason.

I mean with the link books, they worked fine before the down time and tweaking and nothing has changed on this end so I fail to see how that's a client problem. So I wouldn't even know where to begin with tracking down where the problem is occurring I guess.

Basically the server is telling the client to get lost as the client has done something the server does not like. Good practice says that an internal server error also means the server will log something, but there is no guarantee of that in this kind of an application.

Cheith.