• 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 Compiling 0.4

Status
Not open for further replies.
AchTung

AchTung

Member
Joined
Nov 12, 2009
Messages
1,352
Reaction score
7
Location
Germany
Hehe, since I'm a Ubuntu User, I face many problems which I try to solve all via google searching. But now I got a problem which I can't solve with google. That's why I want to ask you guys now.

Problem
My problem right now is that I compiled the latest 0.4 dev. Afterwards I tried to run it. But I got this error:

Code: 
theforgottenserver: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:38: boost::condition_variable::~condition_variable(): Assertion `!pthread_cond_destroy(&cond)' failed.
Aborted

I suppose it's something wrong with permissions etc but I'm not sure how to solve it. I also went into this directory and found out that I ain't got the folder "run". So how can I solve it? I would really appreciate many solutions.
 
Last edited:
Sort by date Sort by votes
Hehe thanks for the help. Could you explain me why people shouldn't use it as Root? Also which security tools do yo advice to protect a Ubuntu System.
And is this message in the terminal normal?:

Code: 
[15:26:13.177] >> Checking software version... running sub version, please mind it's unstable and only for testing purposes!
[15:26:13.177] > Current version information - version: 0.4_DEV, patch: 0, build: 0, timestamp: 0.
[15:26:13.177] > Latest version information - version: 0.3.6, patch: 0, build: 3293, timestamp: 1260652199.

Since I though 0.4 is more stable then the latest version and even more stable then 0.2 as I heard.

Rep for ya anyway^
 
Upvote 0 Downvote
You can search up my iptables script. It's the old version used by a few servers, doesn't really block more then magebomb and SYN attacks, but it gives you a somewhat ok protection.

Also, never ever run the server as root. Mysql etc needs to be initalized by root, but TFS doesn't need it. You can also run the server in a screen shell and with "while true; do ./forgottenserver; done" to have a restarter on it, and still be able to look at the errors (instead of nohup method). And the biggest security risk of all must be everyone you give access too, quite few really need full access to the server. Scripters, mappers and so just need access to scripts (data folder), and you can make a simply web wrapper to start the server again if it fails totaly, to make it easier for GMs to come to a rescue.

Just my 2 cents.
 
Upvote 0 Downvote
I never found your IP table script on otland.net. Actualy I can't find them :( But thanks for the detailed reply. But what about the quote of my second post? It's said that 0.4 is more unstable the 0.36?
 
Upvote 0 Downvote
Maybe im wrong (50%), but how can a unfinished distro be more stable than well, a stable distro?... I guess that 0.4 will be more stable than 0.3 distros, if not, I would say the TFS developer wasted their time in 0.4, but I doubt that it is more stable than 0.3 for now... anyway, why do you care about which one is more stable or so?, both are indredibly stable, with 0.3.5 it was 100% stable for me ;s
 
Upvote 0 Downvote
Might be but stability is an important factor in Open Tibia bussiness I suppose since people will complain, if the server suddenly crash in a battle or something like that. People would cry blabla etc My 0.3.5 can get uptimes of maximum 70h I think since it's windows and sux :(
 
Upvote 0 Downvote
70h?, well, make global save... at 2:00am, people will get used to it (just like they do in tibia rl), and it will close always at the same hour, so you will avoid unexpected crashes in important moments like battles as you said ;s, would be good that your server stays 100% of the time online, but this is a decent solution for now maybe? ;s
 
Upvote 0 Downvote
My Server ain't crashing so often thats why I won't use the global save. I thought about it but said na, if the server suddenly crash due to a crash bug, then people will cry for sure since of no server saves. And I want high uptime since I'm working on a low stages project.
 
Upvote 0 Downvote
Sorry for the double post, but currently I got this error:

Code: 
theforgottenserver: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:38: boost::condition_variable::~condition_variable(): Assertion `!pthread_cond_destroy(&cond)' failed.
Aborted

What's wrong with it? Is it a compiling bug? And how can I use command via terminals for saving etc? Since there ain't any tutorial for it lol.
 
Upvote 0 Downvote
0.4 is the most stable, but there might be some bugs around. But before it'll be released, it should be 99.99% stable.
 
Upvote 0 Downvote
AchTung said:
I never found your IP table script on otland.net. Actualy I can't find them :( But thanks for the detailed reply. But what about the quote of my second post? It's said that 0.4 is more unstable the 0.36?
Click to expand...

the rev from 0.4 its more stable then 0.3.6 lawl
 
Upvote 0 Downvote
AchTung said:
Sorry for the double post, but currently I got this error:

Code: 
theforgottenserver: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:38: boost::condition_variable::~condition_variable(): Assertion `!pthread_cond_destroy(&cond)' failed.
Aborted

What's wrong with it? Is it a compiling bug? And how can I use command via terminals for saving etc? Since there ain't any tutorial for it lol.
Click to expand...

bump
 
Upvote 0 Downvote
Something like this?

Code: 
Loaded symbols for /lib/tls/i686/cmov/libresolv.so.2
0x00df9422 in __kernel_vsyscall ()
(gdb) continue
Continuing.
[New Thread 0xb62f5b70 (LWP 2912)]

Program received signal SIGABRT, Aborted.
0x00df9422 in __kernel_vsyscall ()
(gdb) Continue
Continuing.
[Thread 0xb6af6b70 (LWP 2886) exited]
[Thread 0xb62f5b70 (LWP 2912) exited]

It appears in my terminal. Afterwards i tried to save it as a .txt file but then only this happens:

Code: 
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) exit
Undefined command: "exit".  Try "help".
(gdb) Hangup detected on fd 0
Error detected on fd 0
error detected on stdin

I'm using the gdb correctly? oO
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top