Issue information

Issue ID
#5439
Status
Fixed
Severity
None
Started
Hercules Elf Bot
Mar 13, 2012 18:49
Last Post
Hercules Elf Bot
Apr 19, 2012 18:54
Confirmation
Yes (1)
No (0)

Hercules Elf Bot - Mar 13, 2012 18:49

Originally posted by [b]MarkZD[/b]
After 15682 update, when I log into the server my console shows me this message:
"[Error]: Server received crash signal! Attempting to save all online characters!
[Error]: chrif_save: Failed to set up player 2000000:150000 for proper quitting!"


So my map never loads and my char stucks.

Compiled on Ubuntu 64bit enabled.
_______________________________________________________________________________

I reverted it to 15681, and it's working.

This post has been edited by MarkZD on Mar 13, 2012 19:00

Hercules Elf Bot - Mar 13, 2012 19:10

Originally posted by [b]Gepard[/b]
Please provide a backtrace or a more detailed description how to reproduce the crash. Just logging in does not cause any issues for me.

Hercules Elf Bot - Mar 13, 2012 19:28

Originally posted by [b]MarkZD[/b]
I just updated from 15681 and recompiled:
svn update
./configure --enable-64bit
make clean
make sql

Logged in, the error was there.

Hercules Elf Bot - Mar 13, 2012 19:36

Originally posted by [b]Gepard[/b]
Does it crash with another accounts and/or new characters as well?

Hercules Elf Bot - Mar 13, 2012 19:38

Originally posted by [b]MarkZD[/b]
I'll test and try getting and backtrace.

I can't find out a map-server_sql.core to use with gdb, how should I proceed?

I tried with a new account and it still stacks and gives the same error.

This post has been edited by MarkZD on Mar 13, 2012 19:58

Hercules Elf Bot - Mar 13, 2012 20:01

Originally posted by [b]MarkZD[/b]
I can't find out a map-server_sql.core to use with gdb, how should I proceed?

I tried with a new account and it still stacks and gives the same error.

Hercules Elf Bot - Mar 13, 2012 20:25

Originally posted by [b]MarkZD[/b]
I just wrote the core file's name without it and I tried stackdump in tools patch, it says no error and no stack.

Hercules Elf Bot - Mar 13, 2012 21:25

Originally posted by [b]MarkZD[/b]
I don't have any edited file except conf to connect to mysql and char and map ip, but just to make sure I installed it all again, from a new complete svn download and just changed the above specified files and the error still persists.

I'm using 2011-11-16 client, the same specified in mmo.h by default with compatible lub files and reinforcing it's working fine in 15681.

----------------------------------------------------------------------------------------------

If a developer is available to, I can provide him a ssh/sql access so he can check it.

This post has been edited by MarkZD on Mar 13, 2012 21:30

Hercules Elf Bot - Mar 13, 2012 22:30

Originally posted by [b]Gepard[/b]
Here's topic on how to enable coredumps: http://rathena.org/board/topic/53447-how-to-enable-crashcore-dumps-in-your-server-linux/page__view__findpost__p__54065

Hercules Elf Bot - Mar 14, 2012 1:42

Originally posted by [b]MarkZD[/b]
Here's the core dump by gdb's bt full command:

http://pastebin.com/raw.php?i=XqsqsZ1n

Hercules Elf Bot - Mar 14, 2012 10:41

Originally posted by [b]Gepard[/b]
Please replace lines 1519-1522 of map.c with
[CODE]
if (!nick_db->remove(nick_db, db_i2key(charid), &data) || (p = db_data2ptr(&data)) == NULL)
return;[/CODE]
recompile and test.

This post has been edited by Gepard on Mar 14, 2012 10:43

Hercules Elf Bot - Mar 14, 2012 11:32

Originally posted by [b]MarkZD[/b]
It worked!
Thanks.

I noticed that the chars who tried to login during this problem have got hp 0, so when they relog in, they're like zombies with 0 life who can walk by there, as if they're gm with monster ignore activated, because they can't be hit.

I know it's very easy to fix and could be done via scripts but I think it's a little bug too.

Just by using @alive on the char he gets normal.

This post has been edited by MarkZD on Mar 14, 2012 11:56

Hercules Elf Bot - Mar 14, 2012 12:01

Originally posted by [b]Gepard[/b]
Fixed in [rev=15687].

Sorry, the side effects of the bug can't be fixed. You need to fix it manually, or restore SQL database dump from backup created before the update to bugged revision.