Re: Dirtsand Early 2018
Posted: Thu May 17, 2018 6:17 am
Holy cow that's a lot of work.
Good job on this detective work.
Good job on this detective work.
Code: Select all
$sudo fdisk /dev/sda
Code: Select all
std::unordered_map<ST::string, SDL::State, ST::hash_i, ST::equal_i> s_globalStates;
Code: Select all
std::unordered_map<ST::string, SDL::State, ST::hash, ST::equal_i> s_globalStates;
I presume rather than retro fit this change I was presuming we would be best to do it before we run "cmake .." in the dirtsand directory.Tsar Hoikas wrote:You will need to edit the source code for the file AuthServ/AuthDaemon.cpp.
On line 33, you will find this code:Replace it with this code:Code: Select all
std::unordered_map<ST::string, SDL::State, ST::hash_i, ST::equal_i> s_globalStates;
Be sure to save and recompile the server by running sudo make install from the build directory. Note that this change will introduce some subtle bugs into DirtSand with regard to SDL states, but these are currently found on the Gehn Shard, so you will not likely notice anything amiss.Code: Select all
std::unordered_map<ST::string, SDL::State, ST::hash, ST::equal_i> s_globalStates;
This is wrong. What Hoikas has given you is a bugfix to help you along that hasn't been merged into the main code yet. It's not something that belongs in the build instructions, because it will be properly fixed soon. There have been a few delays in getting the fix in, which is what you've run into. It will be in the main code in some form Soon™. His instructions are given for the specific purpose and context of patching your existing install and getting it working without the need to once again wipe everything from scratch. If you choose to do that, then in that case you will want to patch the code before running cmake -DCMAKE_INSTALL_PREFIX=/opt/dirtsand .. to build the server.J'Kla wrote: I presume rather than retro fit this change I was presuming we would be best to do it before we run "cmake .." in the dirtsand directory.
Please tell me if this is wrong. Just out of curiosity is this something that could be changed in the github or is it specific to Shards where this becomes an issue?
No, this is a bugfix that hasn't been merged yet.J'Kla wrote:The question still applies is this only a change to imppliment if issues arise?
I didn't suggest Ubuntu Desktop. I presumed that you would be using it, so I tested it first. I have since, as noted, tested both server and desktop 64-bit editions as provided by Canonical. I also run dirtsand on my own private testing environment which is 32-bit Ubuntu 16.04 LTS. None of this is relevant to the problems you are encountering.J'Kla wrote: On of which was could it have been that it was caused by using 64 bit install of Ubuntu I know that Deledrius suggested Ubuntu Desktop but its overhead on the poor grade server that I have is an issue the desktop just brings too much baggage but the Desktop is available as 32 bit install.
I went back and looked Deledrius said he had tried and installed successfully using Ubuntu server in an earlier post and since Ubuntu 18.04 is only availabe as 64bit I have to assume that is an OK option
You don't need apache2 or php7.2 for dirtsand. The status.php you mention is specific to Mystler's implementation for Destiny that you seem to have copied from his dirtsand.ini.J'Kla wrote:Code: Select all
$ sudo apt-get install build-essential git cmake libpq-dev libssl-dev libreadline-dev zlib1g-dev postgresql postgresql-contrib apache2 php7.2
Mystler would probably appreciate you not using his server status page for your own server.J'Kla wrote:Code: Select all
Server.Gate.Host "mystler.eu" Server.Auth.Host "mystler.eu" Server.DispName "DestinyURU" Server.Status "https://destiny.mystler.eu/status.php" Server.Signup "https://destiny.mystler.eu"
The ^C appears in the console because you have sent the interrupt control character to the console. In fact, if you're using PuTTY, by default it automatically copies highlighted text to the clipboard, and you pressing Ctrl-C is not only NOT performing the copy, but potentially terminating a running process if you have one. I would recommend against assuming that Windows-specific key combinations work the same way in a Linux text console. Don't ignore feedback that the terminal provides and presume it means nothing (this goes double for error messages - they are not gibberish!).J'Kla wrote:You should now be able to highlight this block of code and use [Ctrl][c] to capture this to the clipboard you may get ^c at the prompt but if you are using putty in a windows session you should be able to paste your results into a text editor.
Code: Select all
[Auth] {d9bd6adb-d625-428b-941f-2f9f7b6894cf} signed in as Victor (10104)
[SDL] Requested invalid decriptor version 42 for Personal
[SDL] Received an update for 'AgeSDLHook' using an invalid descriptor!
[SDL] Requested invalid decriptor version 42 for Personal
Segfault at bin/dirtsand(+0x120cf0) [0x5631c0349cf0]
from bin/dirtsand(+0x120e26) [0x5631c0349e26]
from /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fe28d27cf20]
from bin/dirtsand(_ZNSt6vectorIN3SDL8VariableESaIS1_EEixEm+0x10) [0x5631c0364f0e]
from bin/dirtsand(_ZN3SDL5State5mergeERKS0_+0x8b) [0x5631c0363ceb]
from bin/dirtsand(_Z19dm_local_sdl_updateP16GameHost_PrivateP15Game_SdlMessage+0x69) [0x5631c0337048]
from bin/dirtsand(_Z11dm_gameHostP16GameHost_Private+0xbd) [0x5631c0337346]
from bin/dirtsand(_ZSt13__invoke_implIvPFvP16GameHost_PrivateEJS1_EET_St14__invoke_otherOT0_DpOT1_+0x34) [0x5631c033d543]
from bin/dirtsand(_ZSt8__invokeIPFvP16GameHost_PrivateEJS1_EENSt15__invoke_resultIT_JDpT0_EE4typeEOS5_DpOS6_+0x4e) [0x5631c033b0d4]
from bin/dirtsand(_ZNSt6thread8_InvokerISt5tupleIJPFvP16GameHost_PrivateES3_EEE9_M_invokeIJLm0ELm1EEEEDTcl8__invokespcl10_S_declvalIXT_EEEEESt12_Index_tupleIJXspT_EEE+0x43) [0x5631c0346133]
from bin/dirtsand(_ZNSt6thread8_InvokerISt5tupleIJPFvP16GameHost_PrivateES3_EEEclEv+0x2c) [0x5631c03460d4]
from bin/dirtsand(_ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJPFvP16GameHost_PrivateES4_EEEEE6_M_runEv+0x1c) [0x5631c03460a4]
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xbe733) [0x7fe28db24733]
from /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7fe28d6366db]
from /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fe28d35f88f]
Segmentation fault (core dumped)