Page MenuHomeSchine - Phabricator
Create Task
Maniphest T2365

Starmade | (Multiplayer) Too many blueprints prevents players from joining/loading sectors
Open, NormalPublic
Actions

Description

We have a problem over at Brierie multiplayer StarMade server regarding blueprints.

It seems that when we reach a certain critical mass of catalog blueprints, players are no longer able to join the game. Specifically, they can join the game, but they are unable to spawn into their sectors (they become stuck at "waiting to spawn").

Clearing all the catalog blueprints fixes the issue, but this results in further problems - partially filled blueprint items for example, will no longer spawn due to the catalog blueprint being removed.

At the moment we have to clear out the blueprints approximately every week or so, as the problem will completely prevent some (but not all) players from spawning into the game.

I have copies of the serverlog (but not starmadelog, unfortunately - those roll over every few hours) if that would be any help.

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
Multiplayer
Reproducible
Not on purpose
Last tested (version)
0.199.535
Category
none/unspecified
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
uncertain
Steps to reproduce

Allow the blueprint catalog to grow unchecked on a populated multiplayer server and the problem will eventually arise.

Serverconfig (server.cfg)
 <replace this block with the file content, 
but do not remove the first and last line. 
Before using the paste function, mark the area from the 
opening angle bracket to the closing angle bracket>
Clientconfig (settings.cfg)
 <replace this block with the file content, 
but do not remove the first and last line. 
Before using the paste function, mark the area from the 
opening angle bracket to the closing angle bracket>

Event Timeline

Kielm created this task.Apr 26 2017, 6:45 PM
lancake moved this task from New / Unconfirmed to Feedback on the Issue Navigation board.Apr 27 2017, 11:23 PM
lancake added a subscriber: lancake.
lancake claimed this task.

-Feedback-

Could you upload those serverlogs you have? Drag and drop them in the comment section to upload to phabricator

lancake shifted this object from the S1 Public space to the S3 Starmade space.Apr 27 2017, 11:24 PM
lancake changed the visibility from "Custom Policy" to "Public (No Login Required)".
lancake changed the edit policy from "Task Author" to "Starmade (Project)".
lancake changed the task status from Open to Feedback.
Restricted Application added a project: Waiting on Author. · View Herald TranscriptApr 27 2017, 11:24 PM
Kielm added a comment.Apr 29 2017, 2:34 PM

Please see attached.

serverlog.1.log.txt2 MBDownload

serverlog.3.log.txt1 MBDownload

serverlog.4.log.txt2 MBDownload

serverlog.2.log.txt4 KBDownload

Restricted Application edited projects, added Customer responded; removed Waiting on Author. · View Herald TranscriptApr 29 2017, 2:34 PM
Restricted Application changed the task status from Feedback to Open. · View Herald Transcript
Kielm added a comment.May 1 2017, 9:30 PM

We have some additional information for you.

The problem occurred again today, a user by the name of Peashooter26 was the first to experience the problem (stuck at "waiting to spawn"). There were almost 300 blueprints in the catalog at the time.

We reset the catalog, but took a set of logs leading up to the problem. Hopefully, tracking the user who experienced the problem through the logs may prove useful. Please see attached.

logstarmade.1.log.txt4 MBDownload

logstarmade.5.log.txt4 MBDownload

logstarmade.6.log.txt4 MBDownload

logstarmade.2.log.txt4 MBDownload

logstarmade.4.log.txt4 MBDownload

serverlog.2.log.txt519 KBDownload

logstarmade.3.log.txt1 MBDownload

logstarmade.0.log.txt691 KBDownload

serverlog.1.log.txt132 KBDownload

serverlog.0.log.txt33 KBDownload

Kielm added a comment.May 7 2017, 3:21 AM

We're taking some preemptive action tomorrow to clear out the blueprints on the server as we're starting to get instability indicative of the type caused by this bug.

Here are some more logs taken from a crash just now. I can't be certain that this bug is the cause, but I believe it is. Hopefully the logs will prove useful.

logstarmade.1.log.txt1 MBDownload

logstarmade.0.log.txt2 MBDownload

serverlog.1.log.txt115 KBDownload

serverlog.0.log.txt16 KBDownload