Title: server stops communicating with clients, but is otherwise fine.
Version: 3.1.2
OS: xp professional 2002 service pack 3
Java Version: java version "1.7.0_09" Java SE Runtime Environment (build 1.7.0_09-b05) Java HotSpot Client VM (build 23.5-b02, mixed mode, sharing)
Description of Problem:
after adding redstone wire to an area with the //set 136:256 command, the redstone wire does not appear. any placing of blocks in the location of the non-existent wires fails, and causing a block update at occupied locations causes the server to stop responding to client requests.
the server console responds flawlessly. it ops and deops like a dream and correctly writes to the files.
stopping the server appears to proceed normally
since the server seems to think it is in perfect order, it does not fail and close.
the failure of communication has been happening for weeks (three times over about 1.5 months (finally tracked the failure down (yay))).
the server does not respond to client requests at all. including clients running on the server machine.
a web browser (chrome) functions on server machine, so address is operational and correct. however, a client on the server machine, using it's own address, or a loopback address, is unable to raise a response from the tekkit classic server.
restarting the server allows normal connections and spawns, until the area with the failed terrain has a block update. at that point, the server ceases to communicate again. it also reports the last players logged in at the time of the failure as still logged in.
blocks updated before the communication failure no longer cause the server to fail when updated again.
Error Messages:
none, but server says this over and over as it stops responding.
"
at eloraam.core.TileMultipart.deleteBlock(TileMultipart.java:70)
at eloraam.core.TileCovered.onBlockNeighborChange(TileCovered.java:38)
at eloraam.core.BlockMultipart.doPhysics(BlockMultipart.java:29)
at net.minecraft.server.World.k(World.java:528)
at net.minecraft.server.World.applyPhysics(World.java:503)
at net.minecraft.server.World.update(World.java:469)
at net.minecraft.server.World.setTypeId(World.java:444)
at eloraam.core.BlockMultipart.removeMultipartWithNotify(BlockMultipart.
Question
loqk
Title: server stops communicating with clients, but is otherwise fine.
Version: 3.1.2
OS: xp professional 2002 service pack 3
Java Version: java version "1.7.0_09" Java SE Runtime Environment (build 1.7.0_09-b05) Java HotSpot Client VM (build 23.5-b02, mixed mode, sharing)
Description of Problem:
after adding redstone wire to an area with the //set 136:256 command, the redstone wire does not appear. any placing of blocks in the location of the non-existent wires fails, and causing a block update at occupied locations causes the server to stop responding to client requests.
the server console responds flawlessly. it ops and deops like a dream and correctly writes to the files.
stopping the server appears to proceed normally
since the server seems to think it is in perfect order, it does not fail and close.
the failure of communication has been happening for weeks (three times over about 1.5 months (finally tracked the failure down (yay))).
the server does not respond to client requests at all. including clients running on the server machine.
a web browser (chrome) functions on server machine, so address is operational and correct. however, a client on the server machine, using it's own address, or a loopback address, is unable to raise a response from the tekkit classic server.
restarting the server allows normal connections and spawns, until the area with the failed terrain has a block update. at that point, the server ceases to communicate again. it also reports the last players logged in at the time of the failure as still logged in.
blocks updated before the communication failure no longer cause the server to fail when updated again.
Error Messages:
none, but server says this over and over as it stops responding.
"
at eloraam.core.TileMultipart.deleteBlock(TileMultipart.java:70)
at eloraam.core.TileCovered.onBlockNeighborChange(TileCovered.java:38)
at eloraam.core.BlockMultipart.doPhysics(BlockMultipart.java:29)
at net.minecraft.server.World.k(World.java:528)
at net.minecraft.server.World.applyPhysics(World.java:503)
at net.minecraft.server.World.update(World.java:469)
at net.minecraft.server.World.setTypeId(World.java:444)
at eloraam.core.BlockMultipart.removeMultipartWithNotify(BlockMultipart.
java:256)
"
Error Log:
1 answer to this question
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now