• 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!

Crash/Cpu 100%

Lares

Member
Joined
Feb 8, 2010
Messages
315
Reaction score
7
Helo I have problem with my server. Any player make "crash" on my ots
my server:
Code:
Debian "Lenny" 
TFS 0.3.6pl1

I dont have any errors in console but my cpu = 100% and ots dont work

when i used gdb i have:

Code:
(gdb) bt
#0  0x00007f0ce84e9cd8 in epoll_wait () from /lib/libc.so.6
warning: (Internal error: pc 0x5b1802 in read in psymtab, but not in symtab.)

#1  0x00000000005b1803 in boost::asio::detail::epoll_reactor<false>::run (this=w                 arning: (Internal error: pc 0x5b13d0 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x5b1802 in read in psymtab, but not in symtab.)


0x8ae540, block=<value optimized out>)
    at /usr/include/boost/asio/detail/epoll_reactor.hpp:470
warning: (Internal error: pc 0x5b3f7e in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x5b3f7e in read in psymtab, but not in symtab.)

#2  0x00000000005b3f7f in boost::asio::detail::task_io_service<boost::asio::deta                 il::epoll_reactor<false> >::run (this=warning: (Internal error: pc 0x5b3cd6 in r                 ead in psymtab, but not in symtab.)

warning: (Internal error: pc 0x5b3f7e in read in psymtab, but not in symtab.)

0x8ae370, ec=<value optimized out>)
    at /usr/include/boost/asio/detail/task_io_service.hpp:260
#3  0x00000000005acf98 in ServiceManager::run (this=0x7fff4eab33e0)
    at /usr/include/boost/asio/impl/io_service.ipp:68
#4  0x0000000000555a29 in main (argc=<value optimized out>,
    argv=<value optimized out>) at otserv.cpp:356
(gdb)

Maybe someone know where is problem ?
 
BUMP
I am having this exacly problem, with 0.3.6pl1 TFS on debian 6, 7.5, ubuntu 12, 14, 15. But on windows it works :(
Do you discovered what is causing this segmentation fault ? @Lares
 
Back
Top