Server Help [Solved] Dedicated server on Debian won't start

When the server is starting, it'll get to 'Loaded CodexDatabase in 0.01... seconds', then it'll just say 'Killed'

Is there a way around this or at the very least a way to print more useful logs?

I'm running this on Debian 8. This is a completely fresh install of Starbound via SteamCmd. And here's the rest of the startup log:

Code:

[Info] Root: Preparing Root...
[Info] Root: Done preparing Root.
[Info] Root: Scanning for asset sources in directory '../assets/'
[Info] Root: no runtime config file, creating new default runtime config
[Info] Root: Loaded Configuration in 0.00172121 seconds
[Info] Root: Writing runtime configuration to '../storage/starbound_server.config'
[Info] Root: Scanning for asset sources in directory '../mods/'
[Warn] Root: Unrecognized file in asset directory 'mods_go_here', skipping
[Info] Root: Detected asset source named 'base' at '../assets/packed.pak'
[Info] Root: Detected unnamed asset source at '../assets/user'
[Info] Loading assets from: '../assets/packed.pak'
[Info] Loading assets from: '../assets/user'
[Info] Assets digest is 563ff626b877e7d080472517395bc6c4eda613eaf6ac1576e95136a4ca9b3d64
[Info] Root: Loaded Assets in 1.85121 seconds
[Info] Root: Loaded NameGenerator in 1.93937 seconds
[Info] Root: Loaded PlantDatabase in 0.275368 seconds
[Info] Root: Loaded ObjectDatabase in 0.568344 seconds
[Info] Root: Loaded MonsterDatabase in 0.298352 seconds
[Info] Root: Loaded NpcDatabase in 0.0812875 seconds
[Info] Root: Loaded StagehandDatabase in 0.0115594 seconds
[Info] Root: Loaded VehicleDatabase in 0.00338586 seconds
[Info] Root: Loaded PlayerFactory in 0.00513282 seconds
[Info] Root: Loaded ProjectileDatabase in 0.656083 seconds
[Info] Root: Loaded VersioningDatabase in 0.0547145 seconds
[Info] Root: Loaded EntityFactory in 0.109533 seconds
[Info] Root: Loaded ParticleDatabase in 0.092641 seconds
[Info] Root: Loaded ImageMetadataDatabase in 1.16974e-06 seconds
[Info] Root: Loaded MaterialDatabase in 0.836172 seconds
[Info] Root: Loaded TerrainDatabase in 0.164485 seconds
[Info] Root: Loaded BiomeDatabase in 0.551292 seconds
[Info] Root: Loaded LiquidsDatabase in 0.000674501 seconds
[Info] Root: Loaded StatusEffectDatabase in 0.05838 seconds
[Info] Root: Loaded DamageDatabase in 0.627505 seconds
[Info] Root: Loaded EffectSourceDatabase in 0.0108041 seconds
[Info] Root: Loaded FunctionDatabase in 0.00421906 seconds
[Info] Root: Loaded TreasureDatabase in 0.0525868 seconds
[Info] Root: Loaded DungeonDefinitions in 0.450743 seconds
[Info] Root: Loaded TilesetDatabase in 0.000307864 seconds
[Info] Root: Loaded StatisticsDatabase in 0.00424527 seconds
[Info] Root: Loaded EmoteProcessor in 0.000642126 seconds
[Info] Root: Loaded SpeciesDatabase in 0.0149741 seconds
[Info] Root: Loaded QuestTemplateDatabase in 0.0279142 seconds
[Info] Root: Loaded AiDatabase in 0.00223782 seconds
[Info] Root: Loaded TechDatabase in 0.00116828 seconds
[Info] Root: Loaded CodexDatabase in 0.0102967 seconds
Killed

 

I spoke with some people on a Starbound Discord server and someone asked me to update and install some dependencies

Code:

sudo dpkg --add-architecture i386; sudo apt update; sudo apt install mailutils postfix curl wget file bzip2 gzip unzip bsdmainutils python util-linux ca-certificates binutils bc tmux lib32gcc1 libstdc++6 libstdc++6:i386

After this, the server got farther, and looked to completely start, with the following log (only including what's after the above log)

Code:

[Info] Root: Loaded CodexDatabase in 0.246774 seconds
[Info] Root: Loaded BehaviorDatabase in 0.706423 seconds
[Info] Root: Loaded DanceDatabase in 0.00683591 seconds
[Info] Root: Loaded SpawnTypeDatabase in 0.00870852 seconds
[Info] Root: Loaded RadioMessageDatabase in 0.00542649 seconds
[Info] Root: Loaded ItemDatabase in 5.81065 seconds
[Info] Root: Loaded CollectionDatabase in 2.36882 seconds
[Info] Server Version 1.3.3 (linux x86_64) Source ID: c21069b204d626bfe673a047a2100d2fcd0766d4 Protocol: 743
[Info] UniverseServer: Creating universe storage directory
[Info] UniverseServer: Acquiring universe lock file
[Info] UniverseServer: Loading settings
[Info] UniverseServer: Starting UniverseServer with UUID: b0ee502ce20344416d24c2f02be771aa
[Info] UniverseServer: listening for incoming TCP connections on 0000:0000:0000:0000:0000:0000:0000:0000:21025
Killed

And after this, even without changing anything else, the server will kill itself after printing the "RadioMessageDatabase" step. If I attempt to start it several times after that, it'll eventually revert back to killing itself after CodexDatabase, which makes me think there is a timeout safeguard to prevent the server from hanging. I've only managed to get it to say it was listening to TCP once, and haven't managed to do it again.

 

Restarting the Linux machine on top of the app updates seems to have resolved this problem