after .157 came out the server shoots that error and would not let me mine anything till I restarted the game, fine whatever. however after this last series of updates the problems happens every few minutes now, I found out the hard way when its doing it it refuses to save anything, so yea ive lost about 12 hours of work. Almost tempted to uninstall and never look back.
Bug on Server serialization error
- Thread starter gashnal
- Start date
- Joined
- Aug 30, 2013
- Messages
- 28
- Reaction score
- 1
Did You mean:
#####################################################
[2014-06-26 10:19:41] org.apache.commons.lang3.SerializationException: Planet(728)[s724]Planet (r201)[10000000hp]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1403772229223; entity-instance LAST WRITTEN 0; UID: ENTITY_PLANET_41_20_35_6_1402335158958
[2014-06-26 10:19:41] at org.schema.game.common.controller.io.SegmentDataIO.a(SourceFile:830)
[2014-06-26 10:19:41] at qa.handle(SourceFile:1182)
[2014-06-26 10:19:41] at pM.a(SourceFile:311)
[2014-06-26 10:19:41] at org.schema.game.common.controller.SegmentBuffer.a(
#####################################################
I ve the Same Problem, tonns of this message, since 0.157 or 0.158 looks like the server are not able to save the Entities
#####################################################
[2014-06-26 10:19:41] org.apache.commons.lang3.SerializationException: Planet(728)[s724]Planet (r201)[10000000hp]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1403772229223; entity-instance LAST WRITTEN 0; UID: ENTITY_PLANET_41_20_35_6_1402335158958
[2014-06-26 10:19:41] at org.schema.game.common.controller.io.SegmentDataIO.a(SourceFile:830)
[2014-06-26 10:19:41] at qa.handle(SourceFile:1182)
[2014-06-26 10:19:41] at pM.a(SourceFile:311)
[2014-06-26 10:19:41] at org.schema.game.common.controller.SegmentBuffer.a(
#####################################################
I ve the Same Problem, tonns of this message, since 0.157 or 0.158 looks like the server are not able to save the Entities
- Joined
- Aug 30, 2013
- Messages
- 28
- Reaction score
- 1
Problem Still exists with 0.1582:
[2014-06-26 12:20:00] [SEND][SERVERMESSAGE] [SERVERMSG (type 3): Serious Exception On Server
Serialization failed: Please send in
report from server] to RegisteredClient: xxGhostxx (3) [Captain_Reynolds]connected: true
[2014-06-26 12:20:00] org.apache.commons.lang3.SerializationException: SpaceStation[ENTITY_SPACESTATION_1403781264716(837)]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1403781334075; entity-instance LAST WRITTEN 0; UID: ENTITY_SPACESTATION_1403781264716
[2014-06-26 12:20:00] at org.schema.game.common.controller.io.SegmentDataIO.a(SourceFile:830)
[2014-06-26 12:20:00] at qa.handle(SourceFile:1182)
[2014-06-26 12:20:00] at pM.a(SourceFile:311)
[2014-06-26 12:20:00] at org.schema.game.common.controller.SegmentBuffer.a(SourceFile:733)
[2014-06-26 12:20:00] at org.schema.game.common.controller.SegmentBufferManager.a(SourceFile:725)
[2014-06-26 12:20:00] at pY.writeAllBufferedSegmentsToDatabase(SourceFile:1177)
[2014-06-26 12:20:00] at uM.a(SourceFile:102)
[2014-06-26 12:20:00] at uO.run(SourceFile:1865)
[2014-06-26 12:20:00] at org.schema.schine.network.server.ServerEntityWriterThread.run(SourceFile:47)
[2014-06-26 12:20:00] [SEND][SERVERMESSAGE] [SERVERMSG (type 3): Serious Exception On Server
Serialization failed: Please send in
report from server] to RegisteredClient: xxGhostxx (3) [Captain_Reynolds]connected: true
[2014-06-26 12:20:00] org.apache.commons.lang3.SerializationException: SpaceStation[ENTITY_SPACESTATION_1403781264716(837)]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1403781334075; entity-instance LAST WRITTEN 0; UID: ENTITY_SPACESTATION_1403781264716
[2014-06-26 12:20:00] at org.schema.game.common.controller.io.SegmentDataIO.a(SourceFile:830)
[2014-06-26 12:20:00] at qa.handle(SourceFile:1182)
[2014-06-26 12:20:00] at pM.a(SourceFile:311)
[2014-06-26 12:20:00] at org.schema.game.common.controller.SegmentBuffer.a(SourceFile:733)
[2014-06-26 12:20:00] at org.schema.game.common.controller.SegmentBufferManager.a(SourceFile:725)
[2014-06-26 12:20:00] at pY.writeAllBufferedSegmentsToDatabase(SourceFile:1177)
[2014-06-26 12:20:00] at uM.a(SourceFile:102)
[2014-06-26 12:20:00] at uO.run(SourceFile:1865)
[2014-06-26 12:20:00] at org.schema.schine.network.server.ServerEntityWriterThread.run(SourceFile:47)
- Joined
- Aug 19, 2013
- Messages
- 407
- Reaction score
- 243
This is bad.... if the server cannot save entities... game breaking don't ya think?
It's happening on Trace. Is there a way to easily send server logs in game?
It's happening on Trace. Is there a way to easily send server logs in game?
I am in total rage mode over this ( who really enjoys pissing away 12 hours of there valuable free time )
I didn't realize it wasn't saving I just thought something was lagging with physical objects like it usually complains about no big deal.
force save from the concole, update restart... where is all the work I just finished on Deep Space Nine.... FFFFUUUUUUUUUUUUUUUUU!!!!
I didn't realize it wasn't saving I just thought something was lagging with physical objects like it usually complains about no big deal.
force save from the concole, update restart... where is all the work I just finished on Deep Space Nine.... FFFFUUUUUUUUUUUUUUUUU!!!!
I've had this error a few times on my local server that I run for myself and a brother. Started noticing it last night, just left the server running and I didn't notice any issues with gameplay.
Unsure if related, but when I start the dedicated server, One of the ships that are docked to my station doesn't get a box on the core(So you can select it and board, or walk to it and hit R to get in). Had to break the docking module and the the ship appears to be a ship again. After placing docking module and re-docking, works as normal till next server restart. Has only occured for the past, 3-4 days maybe.
Unsure if related, but when I start the dedicated server, One of the ships that are docked to my station doesn't get a box on the core(So you can select it and board, or walk to it and hit R to get in). Had to break the docking module and the the ship appears to be a ship again. After placing docking module and re-docking, works as normal till next server restart. Has only occured for the past, 3-4 days maybe.
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
Still occurring on v0.1584 (even though the bug tracker #564 says a fix was implemented in 0.1584). When I search the logs from our server I see over 100 different entities associated with a Serialization Exception error (One being my station) since update to v0.1584. Seems to be no option but to restart the server when something is loaded that is associated with the error. After the error has occurred once, then on every save event, it also bring up the error at the same time.
I did get about 6 hours with no error, but during this time I was the only one connected to the server and I was in build mode in a docked ship trying very hard to get enough thrusters into it so it would get to at least 1/2 the 200km/h server limit (151m long ship and 15,000 weight, but this is another problem).
I did get about 6 hours with no error, but during this time I was the only one connected to the server and I was in build mode in a docked ship trying very hard to get enough thrusters into it so it would get to at least 1/2 the 200km/h server limit (151m long ship and 15,000 weight, but this is another problem).
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
Sadly I'd like to report that this error is still occurring, however, much less frequently in v0.1591. Mostly I see the errors associated with asteroids or default stations while players are flying around space like this:
log.txt.18:[2014-07-05 14:59:12] org.apache.commons.lang3.SerializationException: SpaceStation[ENTITY_SPACESTATION_1404536319624(1815)]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1404536343326; entity-instance LAST WRITTEN 0; UID: ENTITY_SPACESTATION_1404536319624
But occasionally it is on a player's ship while they are building it, like this:
log.txt.13:[2014-07-05 22:59:09] org.apache.commons.lang3.SerializationException: Ship[Ayretech Salvage Scow](17866); Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1404557104441; entity-instance LAST WRITTEN 0; UID: ENTITY_SHIP_Ayretech Salvage Scow
This ship rolled back to almost nothing when the server was rebooted.
Luckily for me, I have a resource where I can search all the log files at once for key words (serialization) quickly when I see the error pop up ingame to make sure it's not on something player owned, and can then take immediate action to rectify it (reboot server) if I'm online when it happens.
log.txt.18:[2014-07-05 14:59:12] org.apache.commons.lang3.SerializationException: SpaceStation[ENTITY_SPACESTATION_1404536319624(1815)]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1404536343326; entity-instance LAST WRITTEN 0; UID: ENTITY_SPACESTATION_1404536319624
But occasionally it is on a player's ship while they are building it, like this:
log.txt.13:[2014-07-05 22:59:09] org.apache.commons.lang3.SerializationException: Ship[Ayretech Salvage Scow](17866); Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1404557104441; entity-instance LAST WRITTEN 0; UID: ENTITY_SHIP_Ayretech Salvage Scow
This ship rolled back to almost nothing when the server was rebooted.
Luckily for me, I have a resource where I can search all the log files at once for key words (serialization) quickly when I see the error pop up ingame to make sure it's not on something player owned, and can then take immediate action to rectify it (reboot server) if I'm online when it happens.
okay, so it's not just me... but i have a place to look.
run a dedicated server via the .bat (1024mb min, 4096 max)
on the SAME machine, connect to the server as a client (fullscreen works best at disrupting it)
get another person to join (my brother is local via wireless)
set server speed to 750
sector size 7500
and do stuff, soon it'll spit physics exceptions (if plexlifts are used) or do physics cleanups on entities...
shortly after, it'll start "server not responding" (5 secs, 10 secs...)
when this begins, minimise the game, and click the SERVER cmd window... sometimes it'll recover.
if it does, play more, it will not last more then an hour after that.
system specs
first generation i7 cpu
2X 4gb Ram (dual channeled)
nvidia geforce 560 Ti (not boost) (outputs to a old tv at 1280X720 resolution)
3tb western digital green harddrive (multi partitioned) (starmade is installed on a partition)
250gb harddrive (windows 7 is installed on this)
software specs
windows 7 (64 bit)
java (32 bit and 64 bit, updated today, no change)
nvidia drivers 340.52
run a dedicated server via the .bat (1024mb min, 4096 max)
on the SAME machine, connect to the server as a client (fullscreen works best at disrupting it)
get another person to join (my brother is local via wireless)
set server speed to 750
sector size 7500
and do stuff, soon it'll spit physics exceptions (if plexlifts are used) or do physics cleanups on entities...
shortly after, it'll start "server not responding" (5 secs, 10 secs...)
when this begins, minimise the game, and click the SERVER cmd window... sometimes it'll recover.
if it does, play more, it will not last more then an hour after that.
system specs
first generation i7 cpu
2X 4gb Ram (dual channeled)
nvidia geforce 560 Ti (not boost) (outputs to a old tv at 1280X720 resolution)
3tb western digital green harddrive (multi partitioned) (starmade is installed on a partition)
250gb harddrive (windows 7 is installed on this)
software specs
windows 7 (64 bit)
java (32 bit and 64 bit, updated today, no change)
nvidia drivers 340.52
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
Still getting this serialization error in v0.1611. Much more often than with previous versions. From observation it appears to happen most with ships that are moving.
Scenario: Get in your ship (small cargo in my case), fly around a few shops buying and selling parts, randomly, a serialization error will start to appear for the ship you are flying. Then you head for home, dock the ship, quit the game, wait 5 minutes and log back in and your ship is gone. The ship can be found at the location the serialization error occurred. The real entity remains where the error occurred, and you are left flying in a ghost ship that will vanish when it unloads.
Sample error from the logs:
log.txt.0:[2014-08-08 09:27:50] org.apache.commons.lang3.SerializationException: Ship[K10-Cargo](368)sec[2437]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1407452004917; entity-instance LAST WRITTEN 1407451864773; UID: ENTITY_SHIP_K10-Cargo-Shuttle
This ship was spawned as "K10-Cargo-Shuttle" from the catalog and renamed with the faction block to "K10-Cargo". I've been using this ship for months without error until the last update. The error happens to nearly every ship, and every player when they fly for some length of time (eg. 60min shopping trip). Both new ship builds and catalog ship purchases.
Scenario: Get in your ship (small cargo in my case), fly around a few shops buying and selling parts, randomly, a serialization error will start to appear for the ship you are flying. Then you head for home, dock the ship, quit the game, wait 5 minutes and log back in and your ship is gone. The ship can be found at the location the serialization error occurred. The real entity remains where the error occurred, and you are left flying in a ghost ship that will vanish when it unloads.
Sample error from the logs:
log.txt.0:[2014-08-08 09:27:50] org.apache.commons.lang3.SerializationException: Ship[K10-Cargo](368)sec[2437]; Tried to write old version over new (rollbackbug) entity-UID LAST WRITTEN 1407452004917; entity-instance LAST WRITTEN 1407451864773; UID: ENTITY_SHIP_K10-Cargo-Shuttle
This ship was spawned as "K10-Cargo-Shuttle" from the catalog and renamed with the faction block to "K10-Cargo". I've been using this ship for months without error until the last update. The error happens to nearly every ship, and every player when they fly for some length of time (eg. 60min shopping trip). Both new ship builds and catalog ship purchases.