TWLan Forum

Hi there, taking a hard look at Lekensteyn's event handler (event.sh) I came up with this:

1. #screen -S event
2. ./event.sh (events handler started and works fine)
3. CTRL+A+D to detach (and I detached)

After a couple of hours, after #screen -R event (reading event screen) I see "Segmentation fault" and ./event.sh stopped executing.

So I run #dmesg | grep event.sh and I receive:

Can someone bring some light on this one ?

P.S. - I am using Debian 6.0 2.6.32-5-amd64 on a 2GB RAM VPS at hetzner.de

Already read that, unfortunately, changing permissions didn't help.

Some say it's caused by the RAM memory, though, Edi ran the game and the events handler on a 76GB RAM server with the same distro, same configuring steps, using dotdeb packages and it still returned segfault.

Now, we are testing the handler on Ubuntu 11.10 Oneiric Ocelot (x86_64 - amd64) and, it worked perfectly for two hours and counting. We'll watch it closely and report the segfault problem at libc2 extension installed by php5-dev package used usually to "phpize" (IFS) to dotdeb.org .

Edi's blog entry about this: http://blog.dwar.ro/2011/12/os-change-debian-to-ubuntu/
Ingame printscreen: http://img259.imageshack.us/img259/5903/capturecws.png

If it's considered advertising, just delete de links, though, it's not related to twlan engine or any like that.

Cheers, Sinner.

After simplifying all that we could on the events handler, no significantly results came up.
Ubuntu 11.10 failed too, debian distro failed too, time to try with RedHat distro.

So, we changed again the distro to centos 6 on another kernel. Aparrently, CentOS has no problem in starting and mantaining the handler started for continuous use. I'll keep you posted if anything happens. Though, CentOS executes the game files in 6ms (average) with eAccelerator extension.

Quote:Edi ran the game and the events handler on a 76GB RAM server with the same distro

OnlineServer?

--offtopic--
@steffengy, is a new game that we've been coding from scratch for a while now, though, it has the same idea as tribal wars. So yes, I don't see why hosting it online would be a problem.

-- ontopic --
Bad news, the shell script still crashed on CentOS. We just had to get rid of the "pid file tracking part", the mysql status check and the $running trap 1 2 3 15, assuming that incrementing numbers on and on for such a long time results a segmentation fault.

So a simple infinite loop with no incrementation solved the segmentation fault problem. for ( ; ; ) do command done;