• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Linux Running 2 TFS instances on same the same machine

Guxi

Developer
Joined
Mar 17, 2012
Messages
128
Reaction score
12
Location
Croatia
I already have one TFS instance running which binds on default ports; 7171,7172.

I am able to start the second TFS instance on other ports(such as: 7571, 7572), however when a player attempts to connect to the server it just throws:
theforgottenserver: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:81: boost::condition_variable::~condition_variable(): Assertion `!ret' failed.
Aborted


Click here to see detailed debug (GDB backtrace)
0x0000785e307e3067 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x0000785e307e3067 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x0000785e307e4448 in __GI_abort () at abort.c:89
#2 0x0000785e307dc266 in __assert_fail_base (fmt=0x785e30914f18 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion@entry=0x5db305 "!ret",
file=file@entry=0x5db3c0 "/usr/include/boost/thread/pthread/condition_variable_fwd.hpp",
line=line@entry=81,
function=function@entry=0x5db680 <boost::condition_variable::~condition_variable()::__PRETTY_FUNCTION__> "boost::condition_variable::~condition_variable()") at assert.c:92
#3 0x0000785e307dc312 in __GI___assert_fail (assertion=0x5db305 "!ret",
file=0x5db3c0 "/usr/include/boost/thread/pthread/condition_variable_fwd.hpp", line=81,
function=0x5db680 <boost::condition_variable::~condition_variable()::__PRETTY_FUNCTION__> "boost::condition_variable::~condition_variable()") at assert.c:101
#4 0x000000000042134f in ~condition_variable (this=0x874f28 <Scheduler::getInstance()::scheduler+104>,
__in_chrg=<optimized out>) at /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:81
#5 Scheduler::~Scheduler (this=0x874ec0 <Scheduler::getInstance()::scheduler>, __in_chrg=<optimized out>)
at scheduler.h:63
#6 0x0000785e307e5b29 in __run_exit_handlers (status=0, listp=0x785e30b535a8 <__exit_funcs>,
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#7 0x0000785e307e5b75 in __GI_exit (status=<optimized out>) at exit.c:104
#8 0x0000785e307cfb4c in __libc_start_main (main=0x54c06e <main(int, char**)>, argc=1, argv=0x7a742854f898,
init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7a742854f888)
at libc-start.c:321
#9 0x0000000000414a59 in _start ()


Does this have to anything with the first TFS instance?
 
Solution
@Guxi this sounds like a boost bug, you can try defining NDEBUG macro, doing that assert() does nothing and you server will not crash at least, no guarantee that will it works tho.
@Guxi this sounds like a boost bug, you can try defining NDEBUG macro, doing that assert() does nothing and you server will not crash at least, no guarantee that will it works tho.
 
Solution
@Guxi this sounds like a boost bug, you can try defining NDEBUG macro, doing that assert() does nothing and you server will not crash at least, no guarantee that will it works tho.

I've just compiled with NDEBUG flag and it didn't solve the problem. Same as before, TFS process just dies when I attempt to connect (no assert warning this time because of the NDEBUG)
Thanks for the idea though!
 
Back
Top