Page 1 of 1

Got signal 11 - caught?

Posted: Sat Oct 04, 2008 10:58 am
by John Adams
I finally caught what I think is one of the disconnect/client crashy bugs that have been plaguing me lately. The dreaded Got Signal 11 during world entry. According to where the code breaks, it is here:

Code: Select all

EQ2Stream.h Line 261
inline uint32 GetrIP() { return remote_ip; }
Not sure if this means anything more to you, or is just a simple factor of internet latency or my dynamic IP setup.

Posted: Tue Oct 07, 2008 4:07 pm
by LethalEncounter
Do you have to have anything printed to the screen right before the Signal 11?

Posted: Tue Oct 07, 2008 4:27 pm
by John Adams
I'll have to check that the next time. Usually if there is something unusual, I mention it too - so I am guessing there was nothing unusual before the Got signal 11.

Re: Got signal 11 - caught?

Posted: Mon Jun 22, 2009 7:02 am
by John Adams
Regarding this old bugger...

LE, is there any way to force World to terminate, rather than spew "Got signal 11" repeatedly? For me, I am piping console output to a text file so we have evidence when/if something goes wrong. But when this Got signal 11 occurs, it is at a very high rate of speed, repeating endlessly, and the drive fills up on my linux box (20GB last night). I'd like to avoid having to set up "auto-log-choppers" because that kinda defeats the purpose of trapping console to the log, meh?

I guess what I am saying is, billions of lines of Got signal 11 really isn't telling anyone anything, and can we get it to stop doing that and just pop it once and simply terminate eq2world.

Thanks

Re: Got signal 11 - caught?

Posted: Mon Jun 22, 2009 2:59 pm
by LethalEncounter
This is on linux, right? Does it still occur if you run it in gdb?

Re: Got signal 11 - caught?

Posted: Mon Jun 22, 2009 3:53 pm
by John Adams
No, in gdb it exits for me to do a bt.

Re: Got signal 11 - caught?

Posted: Mon Jun 22, 2009 4:12 pm
by LethalEncounter
kk, yah that is the same as running in debug mode. I'll look into it and see if I can force a close on a signal 11.

Re: Got signal 11 - caught?

Posted: Fri Jun 26, 2009 4:01 pm
by John Adams
Hah it happened again today :(

Code: Select all

[john@mmo-eq2dev logs]$ ls -lt
total 22534196
-rw-rw-r-- 1 john eq2emu 23052472320 2009-06-26 05:11 world
[john@mmo-eq2dev logs]$
Big-ass log!

Re: Got signal 11 - caught?

Posted: Fri Jun 26, 2009 8:21 pm
by LethalEncounter
I changed the way that the zones were being processed to make them FAR more efficient and more reliable. I'm running all 419 zones static right now and my CPU is between 2-7%.

http://eq2emulator.net/ScreenShots/2009 ... static.JPG

Of course it is using almost 1GB of RAM, but we can improve memory usage later. That and I'm using a lot of data that hasn't been cleaned up yet. Could you try to crash it? Hopefully I can get any bugs worked out before I check it in.

Re: Got signal 11 - caught?

Posted: Fri Jun 26, 2009 9:05 pm
by John Adams
Wow, that is very exciting. I will try and hop on now real quick.


Edit: Done. :)

Re: Got signal 11 - caught?

Posted: Sat Jun 27, 2009 4:28 am
by LethalEncounter
Heh, yah I need to fix a memory leak somehow. It said it ran out of memory when you were on, even though it was only a tad over 1 GB. :/

Re: Got signal 11 - caught?

Posted: Tue Jun 30, 2009 7:26 pm
by Scatman
Just got signal 11 on a /reload spawns. It depoped the zone, but before it said it was repoping world crashed.

Re: Got signal 11 - caught?

Posted: Wed Jul 01, 2009 7:08 am
by John Adams
Scat, if you are on Dev, run gdb eq2world and then "r" to run the world, see if you can catch the crash. If so, type "bt" and get the back trace, post it here.

I know you know this, but I am reiterating for anyone else on Linux that wants to help root out bugs ;)

Re: Got signal 11 - caught?

Posted: Wed Jul 01, 2009 7:41 am
by Scatman
Gahh I always forget to do that. Next time ;)

Re: Got signal 11 - caught?

Posted: Mon Aug 10, 2009 9:20 am
by John Adams
Btw, Got signal 11 has been replaced by Got signal 4.

Soon we'll be to 0, and the problem will be solved. yay.