Dedicated Server crashing after a few minutes of gameplay [Linux][1.6.9]

[nimmo]

Game version: 1.6.9
Game mode: Dedicated Server
Bug Location: N/A
Steps to Reproduce: Start Server
Reproduction Rate: Approximately 10 minutes of server running
Screenshot: N/A
Bug Description: The multiplayer server seems to crash every few minutes. Whilst running it runs fine, but suddenly crashes
Mods used: None
Logs:
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-01_21-34.log
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-01_21-34.log
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-01_21-43.log
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-01_21-53.log
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-01_22-02.log
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-01_22-09.log
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-01_22-32.log

Server Config:
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/SettingsServer.xml
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/ModsConfig.xml

Any assistance would be greatly appreciated.
Any assistance would be greatly appreciated.

[kyokei]

From what I can see it's not able to generate the Galaxy correctly.

Is this a totally new world or have people played in it already?
If it's new then I would suggest deleting the save and letting the game remake the world.

If it's an existing world then I would upload the save and share it here so that AI_Enabled can take a look.

[nimmo]

It was a completely new world, I'll try creating a fresh one and seeing what that gives. Thanks.

[ai_enabled]

Hello!

Thanks for reporting.
The crash happens because of Thread.Abort call. More server crash logs will help us investigate the issue.
By the way, are you running the server with Bundle-executable, or you simply run it as "mono VoidExpanse.ServerMono.exe"? If you don't use Bundle-executable, could you try running the game with it please?

Regards!

[nimmo]

Thanks for getting me some more things to work with.

I'd been running the server with "./VoidExpanse.serverMono.exe --dedicated" as the wiki page I was reading suggested.

I'll start running it as bundled and upload any additional crashlogs that are generated.

[kyokei]

btw it doesn't hurt installing mono also by doing the apt-get install mono-complete if you are on a debian based OS

[nimmo]

Installed Mono-complete now and ensured I'm running using the bundled launcher.

Here's the latest crash log:
https://dl.dropboxusercontent.com/u/3204079/VoidExpanse%20Crashlogs/Server_VoidExpanse_2016-04-03_17-43.log

It managed 50 minutes this time which was a good bit better than last time.

[ai_enabled]

Thank you for reporting.
This is a new issue introduced at v1.6.9. We will fix it ASAP.

[nimmo]

If you have seen something new in that latest log then I'm glad I helped, but I think that it is really all linked to the hard drives in the server being close to failure.

Last night both disks that form the raid array completely failed and had to be replaced.

The game locking up for a few seconds and then crashing was happening elsewhere too it turns out and both disks have now been replaced. I will be out of town from now until Friday, so won't be able to reinstall and then test the server again until the weekend but am fairly sure it'll all be fine now that the drives have been replaced.

Thanks again for your assistance in trying to get to the bottom of this and my apologies for taking your time where it turned out to be unrelated.

[ai_enabled]

nimmo, thanks for your detailed explanation! So this is a hardware-only issue.
I've noticed in the logs that the game aborted its main thread. This is usually happens by timeout only when the main thread stuck for some reason on processing.
It seems in your case it may be stuck on IO-operation method, accessing the faulty disk drive.

But the log doesn't reveal why it happens - that's what we're going to fix now. Then we could easily identify the source code line on which the game is stuck. This will be useful if somebody report similar issue (and for our future games also!).

Regards!