Jump to content

Segmentation fault - dedicated server 455818, macOS 10.14, trying to update mods


myxal
  • Fixed

$SUBJECT

My update command:

( cd "${_DSROOT}/bin" || cd "${_DSROOT}/dontstarve_dedicated_server_nullrenderer.app/Contents/MacOS" || cd "${_DSROOT}/Contents/MacOS" ; ./dontstarve_dedicated_server_nullrenderer -only_update_server_mods )

Tried clearing ~/Documents/Klei/DoNotStarveTogether (renamed the folder), no change. Build 455818 OSX





User Feedback


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.

I see that SteamGameServer_init failed, this is a requirement for downloading mods now, so please ensure that you have supplied valid ports.

  • Thanks 3

Share this comment


Link to comment
Share on other sites

Wow, working through the weekend? Thanks!

That got me a bit further (opened port 27015 TCP/UDP, 27031-27036 UDP and 27036 TCP), but still can't update mods:

[00:00:02]: DelDirectory [../mods/workshop-346962876] 0: ok.
[00:00:02]: cWorkshopMod::UnzipMod ../mods/workshop-346962876
src/tier1/fileio.cpp (4914) : Assertion Failed: s_bExit
src/tier1/fileio.cpp (4914) : Assertion Failed: s_bExit
src/tier1/fileio.cpp (4916) : Assertion Failed: m_vecRegisteredWriters.Count() == 0
src/tier1/fileio.cpp (4916) : Assertion Failed: m_vecRegisteredWriters.Count() == 0
Bad thread localsrc/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
src/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
Bad thread localBad thread localsrc/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
src/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
Bad thread localBad thread localsrc/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
src/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited

Log: server_log-update_server_logs.txt

And when trying to launch a cluster:

libc++abi.dylib: terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >

Crashlog attached. 

Server log: server_log-cluster_start.txt

dontstarve_dedicated_server_nullrenderer_2021-03-13-221758_roberta.crash

Edited by myxal

Share this comment


Link to comment
Share on other sites

21 minutes ago, myxal said:

Wow, working through the weekend? Thanks!

That got me a bit further (opened port 27015 TCP/UDP, 27031-27036 UDP and 27036 TCP), but still can't update mods:


[00:00:02]: DelDirectory [../mods/workshop-346962876] 0: ok.
[00:00:02]: cWorkshopMod::UnzipMod ../mods/workshop-346962876
src/tier1/fileio.cpp (4914) : Assertion Failed: s_bExit
src/tier1/fileio.cpp (4914) : Assertion Failed: s_bExit
src/tier1/fileio.cpp (4916) : Assertion Failed: m_vecRegisteredWriters.Count() == 0
src/tier1/fileio.cpp (4916) : Assertion Failed: m_vecRegisteredWriters.Count() == 0
Bad thread localsrc/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
src/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
Bad thread localBad thread localsrc/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
src/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
Bad thread localBad thread localsrc/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited
src/tier1/fileio.cpp (4976) : Assertion Failed: CFileWriterThread already exited

Log: server_log-update_server_logs.txt

And when trying to launch a cluster:


libc++abi.dylib: terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >

Crashlog attached. 

Server log: server_log-cluster_start.txt

dontstarve_dedicated_server_nullrenderer_2021-03-13-221758_roberta.crash 91.08 kB · 1 download

The first crash is actually just a weird steam bug, mods should have updated just fine, you can ignore the Assertion Failed warnings.
The second crash I will investigate on monday.

  • Thanks 2

Share this comment


Link to comment
Share on other sites

Just did some experiments on my Mac..
If the path of a lua file is longer than 256 byte, then it will cause such exception..

  • Like 1
  • Thanks 1

Share this comment


Link to comment
Share on other sites

26 minutes ago, Hubert Zhang said:

Just did some experiments on my Mac..
If the path of a lua file is longer than 256 byte, then it will cause such exception..

that is very helpful, thanks!

  • Thanks 1

Share this comment


Link to comment
Share on other sites

We had this similar problem before with our linux dedicated server but now we can't load mod files at all.

 

 

Share this comment


Link to comment
Share on other sites



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 account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...