after updating today the server i host wont start anymore.
logs:
[00:00:00]: PersistRootStorage is now /home/dst/.klei//dst/world1/overworld/
[00:00:00]: Starting Up
[00:00:00]: Version: 493438
[00:00:00]: Current time: Thu Jan 27 20:12:28 2022
[00:00:00]: System Name: Linux
[00:00:00]: Host Name: Luna
[00:00:00]: Release(Kernel) Version: 5.13.0-27-generic
[00:00:00]: Kernel Build Timestamp: #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022
[00:00:00]: Machine Arch: x86_64
[00:00:00]: Don't Starve Together: 493438 LINUX
[00:00:00]: Build Date: 7644
[00:00:00]: Mode: 32-bit
[00:00:00]: Parsing command line
[00:00:00]: Command Line Arguments: -conf_dir dst -cluster world1 -shard overworld
[00:00:00]: Initializing distribution platform
[00:00:00]: ....Done
[00:00:00]: THREAD - started 'GAClient' (4131633984)
[00:00:00]: Error, failed to change working directory to ../data
[00:00:00]: CurlRequestManager::ClientThread::Main()
[00:00:00]: Mounting file system databundles/klump.zip skipped.
[00:00:00]: Mounting file system databundles/shaders.zip skipped.
[00:00:00]: Mounting file system databundles/fonts.zip skipped.
[00:00:00]: Mounting file system databundles/anim_dynamic.zip skipped.
[00:00:00]: Mounting file system databundles/bigportraits.zip skipped.
[00:00:00]: Mounting file system databundles/images.zip skipped.
[00:00:00]: Mounting file system databundles/scripts.zip skipped.
[00:00:00]: [Steam] SteamGameServer_Init(11000, 12346)
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 3 milliseconds to initialize
RecordSteamInterfaceCreation (PID 63584): SteamGameServer014 /
RecordSteamInterfaceCreation (PID 63584): SteamUtils010 /
Setting breakpad minidump AppID = 322330
[00:00:01]: [Steam] SteamGameServer_Init success
RecordSteamInterfaceCreation (PID 63584): SteamGameServer014 /
RecordSteamInterfaceCreation (PID 63584): STEAMUGC_INTERFACE_VERSION016 /
Missing interface adapter for STEAMUGC_INTERFACE_VERSION016
Segmentation fault (core dumped)
for me starting up the server, each and every time.
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
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