Root: Unrecognized file in asset directory 'mods_go_here', skipping
Root: Scanning for asset sources in directory './mods/' Root: Loaded Configuration in 0.00200658 seconds Root: Scanning for asset sources in directory './assets/' Will try rebooting later, a lot of services depend on the server to be up.Įdit: Alright, got some room for a reboot. This is the result of the "latest" log, there is 6 total in the log folder. Loading assets from: './assets/packed.pak'" Loading assets from: './assets/packed.pak' Root: Detected unnamed asset source at './assets/user' Root: Detected asset source named 'base' at './assets/packed.pak' Root: Loaded Configuration in 0.000945799 seconds Root: Scanning for asset sources in directory './mods/' Did you try rebooting? Anyway, let's see what we find in your log. but I don't know if something else could result in flock failing like that. This should also reveal the error code they return with:Ĭlarry: The solution in this case would be to kill the running server. One thing you can do is strace the server and log its stderr to a file, then see if the flock calls are failing. There are a few other possible error conditions (see man 2 flock). it would fail if there is already a server running. Though, I do not know why the server cannot lock onto it. If I understand it right, the Universe Directory is where the game world is kept. Now I can see the error message which causes the server to fail launching. NodCommander: Ah, now we are getting somewhere. starbound_server(_ZN4Star14fatalExceptionERKSt9exceptionb+0x42) starbound_server(_ZN4Star14UniverseServerC2ERKNS_6StringE+0x15cc) starbound_server(_ZN4Star23UniverseServerExceptionC1ENSt7_cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x 52) starbound_server(_ZN4Star13StarExceptionC1EPKcNSt7_cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0圆6) Fatal Exception caught: (UniverseServerException) Could not acquire lock for the universe directory Root: Writing runtime configuration to './storage/starbound_nfig' UniverseServer: Acquiring universe lock file
0 kommentar(er)
