I've experienced a series of strange crashes lately.
Sigsegv printed some random scripts and PCs every time, and I cant make a sense of it.
Lets see:
Build: POL097-2006-10-29 RC Coregina (gentoo)
Last Script: pkg/spawnnet/spawnnet.ecl PC: 395
Stack Backtrace:
[0x8220dce]
[0x243420]
[0x8119fbb]
[0x8167ea2]
[0x8176d9c]
[0x81ec09c]
[0x81efc66]
[0x81edcf7]
[0x812f9f2]
[0x81304c9]
[0x80f66da]
[0x8225829]
[0x8225b6b]
[0x826e858]
[0x82b714e]
=== CUT ===
395: Func(7,4): GetObjProperty
Build: POL097-2006-10-29 RC Coregina (gentoo)
Last Script: scripts/ai/spellkillpcs.ecl PC: 1528
Stack Backtrace:
[0x8220dce]
[0xf86420]
[0x8066d1e]
[0x806228d]
[0x81ebd32]
[0x81edcf7]
[0x812f9f2]
[0x81304c9]
[0x80f66da]
[0x8225829]
[0x8225b6b]
[0x826e858]
[0x82b714e]
=== CUT ===
npcdesc.cfg:
1528: get member 'idlesound'
Last Script: pkg/skills/alchemy.ecl PC: 3115
Stack Backtrace:
[0x8220dce]
[0x6fa420]
[0x8066d1e]
[0x806228d]
[0x81ebd32]
[0x81edcf7]
[0x812f9f2]
[0x81304c9]
[0x80f66da]
[0x8225829]
[0x8225b6b]
[0x826e858]
[0x82b714e]
=== CUT ===
normal cfg:
3115: get member 'sx'
Build: POL097-2006-10-29 RC Coregina (gentoo)
Last Script: scripts/ai/merchant.ecl PC: 8039
Stack Backtrace:
[0x8220dce]
[0x942420]
[0x8066d1e]
[0x806228d]
[0x81ebd32]
[0x81edcf7]
[0x812f9f2]
[0x81304c9]
[0x80f66da]
[0x8225829]
[0x8225b6b]
[0x826e858]
[0x82b714e]
=== CUT ===
npcdesc.cfg:
8039: get member 'wealth'
Everything seems to crash on core funcs calls, what the heck is going on?
Nothing was wrong for a long time, it worked well, some crashes from time to time. Maybe a Pol-Dev can shed some light on those traces?
One more thing, I've got that warning message:
Error in analyzing libc version string [2.4]. Please contact Core-Team.
Hm.. dunno what is the newest version, have I got an old one?
Pol crashed a couple of times with that assert too:
Assertion Failed: pthread_create( &th, &http_attr, http_conn_thread_stub, reinterpret_cast<void*>(client_socket) ) == 0, pol/polwww.cpp, line 1019
Usually, it worked more than a day and probably received a couple thousands of http requests, but.. should it happen?
Thanks for any help.
Strange Crashes
I know, that those are a common mistakes, but...CWO wrote:Did you upgrade your core lately?
Did you make sure you replace your .em files with the new ones from the core?
Did you recompile your scripts after applying the new .em files?
Sure I've done it, U can see which release I'm using in backtraces logs, next.. If I hadnt compiled all scripts, Pol would throw me an error at the begining with bad version number.
If I hadnt replaced .em files, I surely would have a better crashes, is it not?
Hm.. dunno what to think now, but its possible that I found what caused those strange crashes. It was some hardware glitch. We've changed configuration of ram, we use 4 slots, 2 kings and 2 others.
Configuration was changed from king king other other to king other king other, and then crashes started to appear. My knowledge on diffrent ram cooperation and motherboard handling it is limited, so, I didnt expect it.
Anyway, Pol has probably nothing to do with that.
Hm.. thanks for one response
Configuration was changed from king king other other to king other king other, and then crashes started to appear. My knowledge on diffrent ram cooperation and motherboard handling it is limited, so, I didnt expect it.
Anyway, Pol has probably nothing to do with that.
Hm.. thanks for one response
Assertion Failed: pthread_create( &th, &http_attr, http_conn_thread_stub, reinterpret_cast<void*>(client_socket) ) == 0, pol/polwww.cpp, line 1019
Unfortunatelly, this assert is still poping up.
Dunno, any idea why pol cant create thread for http request?
It happens usually after 1 day uptime or more, http requests interval is set to 15s.
Unfortunatelly, this assert is still poping up.
Dunno, any idea why pol cant create thread for http request?
It happens usually after 1 day uptime or more, http requests interval is set to 15s.