Eggdrop Crash

Slaktarn · Post by **Slaktarn** » Sun May 24, 2009 2:29 pm

Hay everyone...

I have a small problem. I run 23bots whit my hub. And when my computer lag out sometimes all bots lose the connection to my hub, But thats not the problem, the problem is when all bots try to connect to the hub again at same time then the hub crash.. And i need to restart it. Are it any way to avoid this problem. Like only accept 1 connection at same time or some connection order or intrval or anything. So it don´t need to crash...

Have try to search in the forum but it seems to not be any slotion in here what i can found

Mvh Slaktarn

Post by **nml375** » Sun May 24, 2009 2:51 pm

To my best knowledge, there shouldn't be any problems handling 20+ incoming connections at once.

Could you post some details as to version and patches of your eggdrops, and any scripts you are running?

Also, you say your hub crashes. Does it generate any coredumps?

Slaktarn · Post by **Slaktarn** » Mon May 25, 2009 12:04 am

nml375 wrote:To my best knowledge, there shouldn't be any problems handling 20+ incoming connections at once.

Could you post some details as to version and patches of your eggdrops, and any scripts you are running?

Also, you say your hub crashes. Does it generate any coredumps?

Sure i got this one

Code: Select all

Exception: STATUS_ACCESS_VIOLATION at eip=6341B3DC
eax=00000000 ebx=00451E08 ecx=0000003D edx=10526F58 esi=00000380 edi=0000003D
ebp=0022B9A0 esp=0022B948 pid 4064, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022B9A0  6341B3DC  (00000023, 00451E08, 0000003D, 0022B9E0)
0022B9D0  0041E825  (FFFFFFDD, 0044D116, 00454A18, 0022B9F8)
0022BA20  00424642  (0022BB78, 0000000B, 0022BB20, 61017BE0)
0022BA30  00424A9B  (0000000B, 00000004, FFFFFFDE, 00000006)
0022BB20  61017BE0  (000004D0, 0000EA60, 000000A4, 0022BB68)
0022BC40  61098048  (FFFFC5F7, 0022BC78, 0000001C, 0041AAD0)
0022BD50  61018CD9  (0022BE34, 0022CE68, 0022BE50, 0022BE10)
0022BD74  7C938752  (0022BE34, 0022CE68, 0022BE50, 0022BE10)
0022BE1C  7C938723  (0021E000, 0022BE50, 0022BE34, 0022BE50)
0022C168  7C93855E  (00000022, 00451E08, 0000000B, 0022C1A8)
0022C198  0041E8DF  (0000001F, 0044C55D, 0000100D, 000007BC)
0022C4B8  0041E159  (0000001E, 10577960, 00000081, 1053AF48)
0022C4D8  00420087  (7F000001, 10577960, 00000001, 00000000)
0022C508  0042069C  (7F000001, 10577960, 00000001, 1054ED08)
0022C528  00D016B8  (7F000001, 00000024, 00000400, 0022C6BE)
0022C6D8  0041BA6F  (00000000, 0022CA90, 00000000, 00444480)
End of stack trace (more stack frames may be present)

Post by **nml375** » Mon May 25, 2009 11:19 am

'k
In the doc/ directory, you'll find a file named "BUG-REPORT". Within it you'll find details on how to do a backtrace on the coredump.

Or is that a windrop?

Slaktarn · Post by **Slaktarn** » Wed May 27, 2009 2:51 pm

nml375 wrote:'k
In the doc/ directory, you'll find a file named "BUG-REPORT". Within it you'll find details on how to do a backtrace on the coredump.

Or is that a windrop?

Its an Eggdrop under Fedora 10 know its just died and dident post any report output

Post by **nml375** » Wed May 27, 2009 5:06 pm

'k

Is there any core.xxxx files within your eggdrop directory?

Slaktarn · Post by **Slaktarn** » Wed May 27, 2009 10:51 pm

nml375 wrote:'k

Is there any core.xxxx files within your eggdrop directory?

Yes it is but its emty

Post by **nml375** » Thu May 28, 2009 9:17 am

Hmm, that is unfortunate..
Could you try and increase the core limit and reproduce the crash?

(run "ulimit -c 10000" just before you start your eggdrop)