SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001914SphereServerexecutable - linux buildpublic13-02-11 22:5718-01-14 18:45
Reportertrinax 
Assigned ToBen 
PrioritynormalSeveritymajorReproducibilityrandom
StatusclosedResolutionunable to reproduce 
PlatformLinuxOSDebianOS Version5.0
Product Version20-09-2009, 0.56b Prerelease 
Target VersionFixed in Version 
Nightly VersionAutomated (specify build number)
Experimental FlagsDiagonalWalkCheck, New_Triggers, WalkCheck, AllowTelnetPacketFilter, NetworkOutThread
Option FlagsCommand_Sysmsgs, FileCommands, NoHouseMuteSpeech
Internal Build Number1414
Summary0001914: Segmentation fault
DescriptionSegmentation Fault with no additional information.

19:53:P'Chadwick' was killed by N'Angel Mummy', N'Orc Lord', N'orc bomber', N'Giant Spider'.
19:53:FATAL:Segmentation fault

About 5000~ fault in 1 min and ends with this:

19:54:FATAL:Segmentation fault
19:54:FATAL:Segmentation fault
19:54:FATAL:Segmentation fault
19:54:CRITICAL:'Main' thread hang, restarting...
19:54:FATAL:Server Unstable: Aborted

What should I do?
Steps To Reproduce
Additional Information
Tagscrash
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
13-02-11 22:57trinaxNew Issue
14-02-11 11:11trinaxNote Added: 0000915
14-02-11 11:12trinaxNote Edited: 0000915bug_revision_view_page.php?bugnote_id=0000915#r116
14-02-11 14:56MirravinNote Added: 0000916
14-02-11 15:00trinaxNote Added: 0000917
14-02-11 15:01trinaxNote Edited: 0000917bug_revision_view_page.php?bugnote_id=0000917#r118
14-02-11 15:06MirravinNote Added: 0000918
14-02-11 15:09trinaxNote Added: 0000919
14-02-11 15:13trinaxNote Edited: 0000919bug_revision_view_page.php?bugnote_id=0000919#r120
14-02-11 15:13trinaxNote Edited: 0000919bug_revision_view_page.php?bugnote_id=0000919#r121
14-02-11 22:34trinaxNote Edited: 0000915bug_revision_view_page.php?bugnote_id=0000915#r122
14-02-11 22:34trinaxNote Edited: 0000915bug_revision_view_page.php?bugnote_id=0000915#r123
14-02-11 23:56trinaxNote Edited: 0000915bug_revision_view_page.php?bugnote_id=0000915#r124
15-02-11 00:04trinaxNote Edited: 0000917bug_revision_view_page.php?bugnote_id=0000917#r125
15-02-11 00:04trinaxNote Edited: 0000917bug_revision_view_page.php?bugnote_id=0000917#r126
15-02-11 12:16trinaxNote Added: 0000923
15-02-11 13:01trinaxTag Attached: crash
16-02-11 00:10trinaxNote Added: 0000927
16-02-11 00:10trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r132
16-02-11 00:21trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r133
16-02-11 00:22trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r134
16-02-11 00:43trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r135
16-02-11 00:43trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r136
16-02-11 00:45trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r137
16-02-11 00:51trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r138
16-02-11 00:52trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r139
16-02-11 00:53trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r140
16-02-11 01:03trinaxNote Edited: 0000927bug_revision_view_page.php?bugnote_id=0000927#r141
16-02-11 10:48trinaxNote Added: 0000928
16-02-11 15:29trinaxNote Added: 0000929
17-02-11 13:46trinaxNote Added: 0000934
17-02-11 14:00MrSugarCubeNote Added: 0000935
17-02-11 14:03trinaxNote Added: 0000936
17-02-11 14:07trinaxNote Edited: 0000936bug_revision_view_page.php?bugnote_id=0000936#r143
17-02-11 20:36trinaxNote Added: 0000937
17-02-11 20:38trinaxNote Edited: 0000937bug_revision_view_page.php?bugnote_id=0000937#r145
17-02-11 20:39trinaxNote Edited: 0000937bug_revision_view_page.php?bugnote_id=0000937#r146
17-02-11 20:39trinaxNote Edited: 0000937bug_revision_view_page.php?bugnote_id=0000937#r147
17-02-11 23:47trinaxNote Edited: 0000937bug_revision_view_page.php?bugnote_id=0000937#r148
19-02-11 15:09MrSugarCubeNote Added: 0000939
19-02-11 23:26MrSugarCubeNote Edited: 0000939bug_revision_view_page.php?bugnote_id=0000939#r152
20-02-11 11:39trinaxNote Added: 0000940
20-02-11 14:14MrSugarCubeNote Added: 0000941
20-02-11 14:38MrSugarCubeNote Edited: 0000941bug_revision_view_page.php?bugnote_id=0000941#r154
20-02-11 17:02trinaxNote Added: 0000942
20-02-11 23:14trinaxNote Edited: 0000942bug_revision_view_page.php?bugnote_id=0000942#r156
22-02-11 13:24trinaxNote Edited: 0000942bug_revision_view_page.php?bugnote_id=0000942#r159
24-02-11 00:16trinaxNote Edited: 0000942bug_revision_view_page.php?bugnote_id=0000942#r160
24-02-11 11:59trinaxNote Added: 0000947
24-02-11 12:25MrSugarCubeNote Added: 0000948
24-02-11 12:26MrSugarCubeNote Edited: 0000948bug_revision_view_page.php?bugnote_id=0000948#r164
24-02-11 14:28MirravinNote Added: 0000949
24-02-11 18:02MirravinNote Edited: 0000949bug_revision_view_page.php?bugnote_id=0000949#r166
25-02-11 00:09trinaxNote Added: 0000950
25-02-11 00:09trinaxNote Edited: 0000950bug_revision_view_page.php?bugnote_id=0000950#r168
12-03-11 12:12trinaxNote Added: 0000956
13-03-11 05:15MrSugarCubeNote Added: 0000960
13-03-11 10:07trinaxNote Added: 0000962
13-03-11 10:09trinaxNote Edited: 0000962bug_revision_view_page.php?bugnote_id=0000962#r173
13-03-11 10:10trinaxNote Edited: 0000962bug_revision_view_page.php?bugnote_id=0000962#r174
13-03-11 10:11trinaxNote Edited: 0000962bug_revision_view_page.php?bugnote_id=0000962#r175
13-03-11 10:11trinaxNote Edited: 0000962bug_revision_view_page.php?bugnote_id=0000962#r176
13-03-11 10:12trinaxNote Edited: 0000962bug_revision_view_page.php?bugnote_id=0000962#r177
13-03-11 14:57trinaxNote Edited: 0000962bug_revision_view_page.php?bugnote_id=0000962#r180
17-03-11 15:51trinaxNote Added: 0000970
17-03-11 15:52trinaxNote Edited: 0000970bug_revision_view_page.php?bugnote_id=0000970#r182
17-03-11 15:56trinaxNote Edited: 0000970bug_revision_view_page.php?bugnote_id=0000970#r186
17-03-11 15:59trinaxNote Edited: 0000970bug_revision_view_page.php?bugnote_id=0000970#r187
17-03-11 16:00trinaxNote Edited: 0000970bug_revision_view_page.php?bugnote_id=0000970#r188
17-03-11 18:15trinaxNote Edited: 0000970bug_revision_view_page.php?bugnote_id=0000970#r189
17-03-11 23:11trinaxNote Edited: 0000970bug_revision_view_page.php?bugnote_id=0000970#r190
24-03-11 20:59trinaxNote Added: 0000980
25-03-11 13:32trinaxNote Edited: 0000980bug_revision_view_page.php?bugnote_id=0000980#r197
25-03-11 21:38trinaxNote Edited: 0000980bug_revision_view_page.php?bugnote_id=0000980#r198
26-03-11 00:36trinaxNote Edited: 0000980bug_revision_view_page.php?bugnote_id=0000980#r199
26-03-11 13:07trinaxNote Edited: 0000980bug_revision_view_page.php?bugnote_id=0000980#r200
12-04-11 13:18trinaxNote Added: 0001023
13-04-11 00:52trinaxNote Edited: 0001023bug_revision_view_page.php?bugnote_id=0001023#r256
13-04-11 00:52trinaxNote Edited: 0001023bug_revision_view_page.php?bugnote_id=0001023#r257
13-04-11 00:53trinaxNote Edited: 0001023bug_revision_view_page.php?bugnote_id=0001023#r258
13-04-11 01:01trinaxNote Edited: 0001023bug_revision_view_page.php?bugnote_id=0001023#r259
13-04-11 01:03trinaxIssue Monitored: trinax
13-04-11 01:05trinaxNote Edited: 0001023bug_revision_view_page.php?bugnote_id=0001023#r260
15-04-11 03:48MrSugarCubeNote Added: 0001027
18-04-11 01:26MirravinNote Added: 0001037
20-04-11 17:20trinaxNote Added: 0001039
26-04-11 22:30trinaxNote Added: 0001045
26-04-11 22:31trinaxNote Edited: 0001045bug_revision_view_page.php?bugnote_id=0001045#r278
26-04-11 22:52trinaxNote Edited: 0001045bug_revision_view_page.php?bugnote_id=0001045#r279
04-05-11 13:18trinaxNote Added: 0001056
04-05-11 13:19trinaxNote Edited: 0001056bug_revision_view_page.php?bugnote_id=0001056#r297
12-05-11 18:03trinaxNote Added: 0001064
13-05-11 02:32MrSugarCubeNote Added: 0001066
13-05-11 14:05trinaxNote Added: 0001069
13-05-11 21:53MrSugarCubeNote Added: 0001071
14-05-11 09:53trinaxNote Added: 0001074
14-05-11 10:02trinaxNote Edited: 0001074bug_revision_view_page.php?bugnote_id=0001074#r305
15-05-11 16:58trinaxNote Added: 0001076
15-05-11 16:59trinaxNote Edited: 0001076bug_revision_view_page.php?bugnote_id=0001076#r307
20-05-11 20:45trinaxNote Added: 0001090
20-05-11 20:55trinaxNote Edited: 0001090bug_revision_view_page.php?bugnote_id=0001090#r321
20-05-11 20:56trinaxNote Edited: 0001090bug_revision_view_page.php?bugnote_id=0001090#r322
20-05-11 20:56trinaxNote Edited: 0001090bug_revision_view_page.php?bugnote_id=0001090#r323
20-05-11 21:11trinaxNote Edited: 0001090bug_revision_view_page.php?bugnote_id=0001090#r324
21-05-11 12:39trinaxNote Edited: 0001090bug_revision_view_page.php?bugnote_id=0001090#r325
18-01-14 18:45BenNote Added: 0001921
18-01-14 18:45BenStatusnew => closed
18-01-14 18:45BenAssigned To => Ben
18-01-14 18:45BenResolutionopen => unable to reproduce

Notes
(0000915)
trinax   
14-02-11 11:11   
(edited on: 14-02-11 23:56)
Another one, I have turned on debug script.

11:01:DEBUG:SCRIPT: strsub(0,4,'online') -> 'onli'
11:01:DEBUG:SCRIPT: strsub(0,5,'online') -> 'onlin'
11:01:DEBUG:SCRIPT: strsub(0,6,'online') -> 'online'
11:01:DEBUG:SCRIPT: strsub(0,6,'online') -> 'online'
11:01:DEBUG:SCRIPT: strsub(0,4,'online') -> 'onli'
11:01:DEBUG:SCRIPT: strsub(0,5,'online') -> 'onlin'
11:06:FATAL:(sphere_serv_triggers.scp,292)Server Unstable: Aborted

This time without lots of segmentation faults but only aborted.

FYI, I do A LOT of strsub (possibly including trying to extract a longer string from a short string, like strsub 0 5 on "ab" if that may cause a problem) and strcmpi under f_oncommand for both players and staffs. These errors doesn't look like related to the player number though, so f_oncommand may be irrelevant but...

sphere_server_triggers.scp

[FUNCTION f_onserver_save]
B @1949,4 Kayit Aliniyor,Lutfen Bekleyiniz..
LOG Save Stage Started. Forced: <dARGN1>. Stage#: <dARGN2>
IF (<ARGN2> != -1) && (<ARGN2> != 2147483647)
    LOG Background save detected. Ensuring background saving is disabled. <<-- LINE 292!
    SAVEBACKGROUND = 1
    SAVEBACKGROUND = 0
    //IF !(<ARGN1>)
    //LOG Ensuring foreground save...
    //ARGN1 = 1
    //ENDIF
ENDIF
RETURN 0
(0000916)
Mirravin   
14-02-11 14:56   
Have you tested last Sphere build(#1419)?
(0000917)
trinax   
14-02-11 15:00   
(edited on: 15-02-11 00:04)
No, these are 1414. If I remember right I had these even 2 years ago before I closed my server (these are actually one of the reasons why I closed), with the pre-release 56b. They are about some scripts I assume but I can't find it because the error doesn't take me anywhere.
(0000918)
Mirravin   
14-02-11 15:06   
Do you use TIMERF CLEAR function?
(0000919)
trinax   
14-02-11 15:09   
(edited on: 14-02-11 15:13)
No, no timerf clear or timerf -1 in my scripts. I use lots of timerfs-timerds though.
(0000923)
trinax   
15-02-11 12:16   
Decreased the f_oncommand checks a little and server has been running fine for 24 hours now, the problem actually may be about them.
(0000927)
trinax   
16-02-11 00:10   
(edited on: 16-02-11 01:03)
Another one:

00:14:DEBUG:SCRIPT: strsub(0,6,'s nerdesın a.q') -> 's nerd'
00:14:DEBUG:SCRIPT: strsub(0,5,'s nerdesın a.q') -> 's ner'
00:14:DEBUG:SCRIPT: strsub(0,4,'s nerdesın a.q') -> 's ne'
00:14:d5:'sdfgh' commands 's nerdesın a.q'=1
00:14:ERROR:fc:Bad Login 0 (Account does not exist)
00:14:ERROR:fd:Bad Login 0 (Account does not exist)
00:14:ERROR:fe:Bad Login 0 (Account does not exist)
00:14:FATAL:Segmentation fault
00:14:FATAL:Segmentation fault
*
00:15:FATAL:Segmentation fault
00:15:CRITICAL:'Main' thread hang, restarting...
00:15:FATAL:(tamamlanansistemler.scp,663)Server Unstable: Aborted


Line 663 is "serv.account update"


I am trying to log every character trigger to find, since sphere doesn't give enough information which is nonsense, but I doubt it will be able to write to file before the crash.

I am using client 2.0.3 for my server btw.

Sphere really should give exactly what was done before any errors, with a flag or something, if it is saying there is a fault, why is not there a fault code for you to find the cause or info for us to find the possible bad scripting? That is a BIG missing feature for debugging. This is ruining the server.
(0000928)
trinax   
16-02-11 10:48   
Again:

03:22:DEBUG:SCRIPT: strsub(0,6,'bandaj') -> 'bandaj'
03:22:DEBUG:SCRIPT: strsub(0,5,'bandaj') -> 'banda'
03:22:DEBUG:SCRIPT: strsub(0,4,'bandaj') -> 'band'
03:22:FATAL:Segmentation fault
03:22:FATAL:Segmentation fault
03:22:FATAL:Segmentation fault
*
03:22:FATAL:Segmentation fault
03:22:CRITICAL:'Main' thread hang, restarting...
03:22:FATAL:Server Unstable: Aborted
(0000929)
trinax   
16-02-11 15:29   
I have removed those strsub checks from players completely, to see if it helps to determine if that is the problem.

In the mean time, are you considering to update the sphere to give information about that fault?
(0000934)
trinax   
17-02-11 13:46   
Another:

13:51:DEBUG:SCRIPT: strsub(0,4,'invis') -> 'invi'
13:51:7d:'handsome' commands 'invis'=1
13:51:P'Maverick' was killed by P'Frank GoztepeLee'.
13:51:FATAL:Segmentation fault
13:51:FATAL:Segmentation fault
13:51:FATAL:Segmentation fault
(0000935)
MrSugarCube   
17-02-11 14:00   
The strsub messages are purely informational messages and don't mean anything. What other debug flags have you got enabled?

There isn't really any information to go by, but you could try disabling NetworkOutThread to see if that makes a difference.
(0000936)
trinax   
17-02-11 14:03   
(edited on: 17-02-11 14:07)
I only have DEBUGF_SCRIPTS enabled. Which ones should I enable to get some useful information? Is there a flag to log which function,trigger is being executed.

I am disabling networkoutthread now.
(0000937)
trinax   
17-02-11 20:36   
(edited on: 17-02-11 23:47)
Again:

18:44:P'Naraxyn ImmortaL' was killed by P'Destroy'.
18:44:P'Liana Heizenberg' was killed by N'Associate of Herman'.
18:44:FATAL:Segmentation fault
18:44:FATAL:Segmentation fault
18:44:FATAL:Segmentation fault
18:44:FATAL:Segmentation fault
18:44:FATAL:Segmentation fault

I am re-enabling networkout.

Can't you update sphere to give information before fatals?

Edit:
I think sphere keeps running while those faults are thrown and stops running when it says main thread freeze.
(0000939)
MrSugarCube   
19-02-11 15:09   
(edited on: 19-02-11 23:26)
If Sphere were able to handle the error nicely then it wouldn't be 'fatal'. :)

I've enabled the same debug information that gets shown in Windows (was previously not working on Linux builds), so if you can reproduce this again on tonight's build (#1425+) we might hopefully get something a bit more meaningful from the error.
(0000940)
trinax   
20-02-11 11:39   
Can't try because 1425 uses too much CPU.

Btw, do I need to keep debugf_Script enabled to see the new messages?
(0000941)
MrSugarCube   
20-02-11 14:14   
(edited on: 20-02-11 14:38)
Nope, it's automatic.

The high CPU usage is caused by the extra debugging, is the server usable enough to at least get the fault to occur?
(0000942)
trinax   
20-02-11 17:02   
(edited on: 24-02-11 00:16)
There is many players during the weekend. I can give it a try tomorrow.

The fault is random, happened in between 5 mins - 55 hours so far.

Have been running fine for 30 hours now. -.-"

60 hours..
(0000947)
trinax   
24-02-11 11:59   
It didn't crash for too long, losing players cause of lag.
Can this debugging be an option in sphere.ini?
(0000948)
MrSugarCube   
24-02-11 12:25   
(edited on: 24-02-11 12:26)
It's not possible sorry, it has to be always on or always off.

If you are still using build 1425 then updating to 1426+ might reduce CPU slightly (compared to 1425, my CPU usage dropped from 80-90% to 60-70%).
(0000949)
Mirravin   
24-02-11 14:28   
(edited on: 24-02-11 18:02)
Can you add this debugs to the separate builds(normal build; DEBUG build)?
Because I don't have problems with the stability of Sphere, this debugs has essentially reduced the performance for me, but I can't get last build without it...

P.s. Returned to build: #1419 now.
(0000950)
trinax   
25-02-11 00:09   
Tried r1428 but CPU usage didn't drop much. I will purchase a more powerful machine to find the bug because player number drops therefore I can't experience the crash.

I have downloaded and stored r1425 and r1428, you can turn the debug option off for following builds. I will post information when I can run the debug build.
(0000956)
trinax   
12-03-11 12:12   
Finally I got it to crash with debug build.


13:03:ERROR:14:Bad Login 9 (The account details entered are invalid (username or password is too short, too long or contains invalid characters). This can sometimes be caused by incorrect/missing encryption keys)
13:06:FATAL:Segmentation fault
13:06:FATAL:Segmentation fault
.
.
13:07:FATAL:Segmentation fault
13:07:WARNING:Forcing thread 'Main' to terminate...
13:07:CRITICAL:'Main' thread hang, restarting...
13:07:FATAL:Server Unstable: Aborted

Still not much of an information :(
(0000960)
MrSugarCube   
13-03-11 05:15   
Can you check the internal build number when Sphere starts? There are no debug messages.. :(
(0000962)
trinax   
13-03-11 10:07   
(edited on: 13-03-11 14:57)
12:56:Welcome to Sphere XXXXXXX www.xxxxxxx.com , compiled at Feb 23 2011 (01:02:02), internal build #1428
12:56:WARNING: --- WARNING ---

This is a nightly build of SphereServer. This build is to be used
for testing and/or bug reporting ONLY. DO NOT run this build on a
live shard unless you know what you are doing!
Nightly builds are automatically made every night from source and
might contain errors, might be unstable or even destroy your
shard as they are mostly untested!
 ---------------------------------

12:56:Signal handlers installed.
12:56:Expansion maps supported: T2A, ML
12:56:Allocating map sectors: 0=7168 1=7168
12:56:Indexing 265 scripts...
(0000970)
trinax   
17-03-11 15:51   
(edited on: 17-03-11 23:11)
The one I was using is debug build I think :P The crash is still happening, I wrote a bash script to restart the server if hang though so we are holding up at the moment.

Is there a way that I make a trigger that affects all items? There are events that are associated with all npcs|players but not for items unfortunately. [typedef t_normal] on=@timer or something will work? or [typedef 255] maybe?

Asking this to log whats going on.

P.S. Will "typedef trigger" trigger before the one in the itemdef? If not, there should be an option to do it so, and we can hopefully find the bug :P
(0000980)
trinax   
24-03-11 20:59   
(edited on: 26-03-11 13:07)
Well it crashed :P That script isn't the only place findtype is called though. It is also called every @spellcast under player event.

Additionally, if I remember right, the RAM usage of VPS suddenly hit max when this fault happened 3 years ago (with the pre-release). Now I will try but I don't think I can observe the RAM usage in the current VPS.


Edit:

Ram usage stays the same, cpu usage drops from 30% to 20%.
(0001023)
trinax   
12-04-11 13:18   
(edited on: 13-04-11 01:05)
Still no output about the crash in #1440

Can't you add a flag-enabled feature, something like script profiler that it will write/append the last function/trigger call before it is called (with script/line/rtime etc. maybe) to a file?

Looks like logging each call before it is done is the simplest and maybe the only way to find the bug, which I assume to be user related and happening in some specific script lines and therefore will be in usermade functions/triggers.

P.S. Isn't OS supposed to output information about the error? Is the signal handled by sphere manually, trying to avoid crash?
(0001027)
MrSugarCube   
15-04-11 03:48   
If secure mode is enabled (SECURE in sphere.ini, or 's' in console) then Sphere tries to handles a number of signals. You can try disabling this if you think the OS will give you any information, but when I do that here I just get a generic error message and the process dies.

I've made a temporary tweak to the segmentation fault handling so that printing the debug information is the first thing Sphere will do after displaying the Segumentation Fault message. If you could try to reproduce on tomorrow's automated build (version #1443) we might have better luck with getting the information out (you'll need to keep secure mode enabled though :)).
(0001037)
Mirravin   
18-04-11 01:26   
That is interesting, error about save exception while closing console in build #1443 has dissappeared at all, instead of extra debugging.
http://tracker.sphere.torfo.org/bugs/view.php?id=1880 [^]
(0001039)
trinax   
20-04-11 17:20   
I still couldn't get it to crash.
(0001045)
trinax   
26-04-11 22:30   
(edited on: 26-04-11 22:52)
Finally, after 200 hours of runtime :D Funny the actual time we would see some information about the bug was the one with the longest uptime.

22:41:FATAL:Segmentation fault
22:41:DEBUG:__ thread (3056810896) __ | # | _____ function _____________ | ticks passed from previous function start ______
22:41:DEBUG:>> 3056810896 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
22:41:DEBUG:>> 3056810896 | 1 | CObjBase::OnTickStatusUpdate | +1
22:41:FATAL:Segmentation fault
22:41:DEBUG:__ thread (3056810896) __ | # | _____ function _____________ | ticks passed from previous function start ______
22:41:DEBUG:>> 3056810896 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
22:41:DEBUG:>> 3056810896 | 1 | CObjBase::OnTickStatusUpdate | +1
22:41:FATAL:Segmentation fault
.
.
.
.
22:41:FATAL:Segmentation fault
22:41:DEBUG:__ thread (3056810896) __ | # | _____ function _____________ | ticks passed from previous function start ______
22:41:DEBUG:>> 3056810896 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
22:41:DEBUG:>> 3056810896 | 1 | CObjBase::OnTickStatusUpdate | +1
22:41:FATAL:Segmentation fault
22:41:DEBUG:__ thread (3056810896) __ | # | _____ function _____________ | ticks passed from previous function start ______
22:41:DEBUG:>> 3056810896 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
22:41:DEBUG:>> 3056810896 | 1 | CObjBase::OnTickStatusUpdate | +1
22:41:FATAL:Segmentation fault
22:41:DEBUG:__ thread (3056810896) __ | # | _____ function _____________ | ticks passed from previous function start ______
22:41:DEBUG:>> 3056810896 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
22:41:DEBUG:>> 3056810896 | 1 | CObjBase::OnTickStatusUpdate | +1
22:41:WARNING:Forcing thread 'Main' to terminate...
22:41:FATAL:(fix.scp,398)Server Unstable: Aborted

There are lots of them and all seem to be same.
(0001056)
trinax   
04-05-11 13:18   
(edited on: 04-05-11 13:19)
Another one:
00:50:FATAL:Segmentation fault
00:50:DEBUG:__ thread (3056446352) __ | # | _____ function _____________ | ticks passed from previous function start ______
00:50:DEBUG:>> 3056446352 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
00:50:DEBUG:>> 3056446352 | 1 | CObjBase::OnTickStatusUpdate | +2
00:50:FATAL:Segmentation fault
00:50:DEBUG:__ thread (3056446352) __ | # | _____ function _____________ | ticks passed from previous function start ______
00:50:DEBUG:>> 3056446352 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
00:50:DEBUG:>> 3056446352 | 1 | CObjBase::OnTickStatusUpdate | +2
00:50:FATAL:Segmentation fault
00:50:DEBUG:__ thread (3056446352) __ | # | _____ function _____________ | ticks passed from previous function start ______
00:50:DEBUG:>> 3056446352 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
00:50:DEBUG:>> 3056446352 | 1 | CObjBase::OnTickStatusUpdate | +2
00:50:FATAL:Segmentation fault
00:50:DEBUG:__ thread (3056446352) __ | # | _____ function _____________ | ticks passed from previous function start ______
00:50:DEBUG:>> 3056446352 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
00:50:DEBUG:>> 3056446352 | 1 | CObjBase::OnTickStatusUpdate | +2


And another one:

21:14:FATAL:Segmentation fault
21:14:DEBUG:__ thread (3056565136) __ | # | _____ function _____________ | ticks passed from previous function start ______
21:14:DEBUG:>> 3056565136 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
21:14:DEBUG:>> 3056565136 | 1 | CObjBase::OnTickStatusUpdate | +2
21:14:FATAL:Segmentation fault
21:14:DEBUG:__ thread (3056565136) __ | # | _____ function _____________ | ticks passed from previous function start ______
21:14:DEBUG:>> 3056565136 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
21:14:DEBUG:>> 3056565136 | 1 | CObjBase::OnTickStatusUpdate | +2
21:14:FATAL:Segmentation fault
21:14:DEBUG:__ thread (3056565136) __ | # | _____ function _____________ | ticks passed from previous function start ______
21:14:DEBUG:>> 3056565136 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
21:14:DEBUG:>> 3056565136 | 1 | CObjBase::OnTickStatusUpdate | +2
21:14:FATAL:Segmentation fault
21:14:DEBUG:__ thread (3056565136) __ | # | _____ function _____________ | ticks passed from previous function start ______
21:14:DEBUG:>> 3056565136 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
21:14:DEBUG:>> 3056565136 | 1 | CObjBase::OnTickStatusUpdate | +2
21:14:WARNING:Forcing thread 'Main' to terminate...
21:14:CRITICAL:'Main' thread hang, restarting...
21:14:FATAL:Server Unstable: Aborted
(0001064)
trinax   
12-05-11 18:03   
19:02:FATAL:Segmentation fault
19:02:DEBUG:__ thread (3056630672) __ | # | _____ function _____________ | ticks passed from previous function start ______
19:02:DEBUG:>> 3056630672 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
19:02:DEBUG:>> 3056630672 | 1 | CObjBase::OnTickStatusUpdate | +82
19:02:FATAL:Segmentation fault
19:02:DEBUG:__ thread (3056630672) __ | # | _____ function _____________ | ticks passed from previous function start ______
19:02:DEBUG:>> 3056630672 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
19:02:DEBUG:>> 3056630672 | 1 | CObjBase::OnTickStatusUpdate | +82
19:02:FATAL:Segmentation fault
19:02:DEBUG:__ thread (3056630672) __ | # | _____ function _____________ | ticks passed from previous function start ______
19:02:DEBUG:>> 3056630672 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
19:02:DEBUG:>> 3056630672 | 1 | CObjBase::OnTickStatusUpdate | +82
19:02:WARNING:Forcing thread 'Main' to terminate...
FATAL: exception not rethrown
19:02:FATAL:Server Unstable: Aborted
(0001066)
MrSugarCube   
13-05-11 02:32   
Which automated build did you use to get that last one?
(0001069)
trinax   
13-05-11 14:05   
#1443
(0001071)
MrSugarCube   
13-05-11 21:53   
Could you try to reproduce again with the latest? There's a [small] chance that some of the changes made in builds 1446, 1451, 1453 and 1454 may have made some kind of difference.
(0001074)
trinax   
14-05-11 09:53   
(edited on: 14-05-11 10:02)
This one is with # 1457

01:10:(x.scp,49)TEST CRASH CONT
01:10:FATAL:Segmentation fault
01:10:DEBUG:__ thread (3057130384) __ | # | _____ function _____________ | ticks passed from previous function start ______
01:10:DEBUG:>> 3057130384 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:10:DEBUG:>> 3057130384 | 1 | CObjBase::OnTickStatusUpdate | +1
01:10:DEBUG:>> 3057130384 | 2 | CObjBase::ResendTooltip | +0
01:10:FATAL:Segmentation fault
01:10:DEBUG:__ thread (3057130384) __ | # | _____ function _____________ | ticks passed from previous function start ______
01:10:DEBUG:>> 3057130384 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:10:DEBUG:>> 3057130384 | 1 | CObjBase::OnTickStatusUpdate | +1
01:10:DEBUG:>> 3057130384 | 2 | CObjBase::ResendTooltip | +0
01:10:FATAL:Segmentation fault
01:10:DEBUG:__ thread (3057130384) __ | # | _____ function _____________ | ticks passed from previous function start ______
01:10:DEBUG:>> 3057130384 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:10:DEBUG:>> 3057130384 | 1 | CObjBase::OnTickStatusUpdate | +1
01:10:DEBUG:>> 3057130384 | 2 | CObjBase::ResendTooltip | +0
01:10:FATAL:Segmentation fault
01:10:DEBUG:__ thread (3057130384) __ | # | _____ function _____________ | ticks passed from previous function start ______
01:10:DEBUG:>> 3057130384 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:10:DEBUG:>> 3057130384 | 1 | CObjBase::OnTickStatusUpdate | +1
01:10:DEBUG:>> 3057130384 | 2 | CObjBase::ResendTooltip | +0
01:10:FATAL:Segmentation fault
(0001076)
trinax   
15-05-11 16:58   
(edited on: 15-05-11 16:59)
Another one with # 1457

17:51:(x.scp,49)TEST CRASH CONT
17:51:(x.scp,438)TEST CRASH CONT
17:51:FATAL:Segmentation fault
17:51:DEBUG:__ thread (3057249168) __ | # | _____ function _____________ | ticks passed from previous function start ______
17:51:DEBUG:>> 3057249168 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
17:51:DEBUG:>> 3057249168 | 1 | CChar::OnTickEquip | +2
17:51:DEBUG:>> 3057249168 | 2 | CChar::Spell_Equip_OnTick | +0
17:51:DEBUG:>> 3057249168 | 3 | CItem::SetTimeout | +0
17:51:DEBUG:>> 3057249168 | 4 | CObjBase::SetTimeout | +0
17:51:FATAL:Segmentation fault
17:51:DEBUG:__ thread (3057249168) __ | # | _____ function _____________ | ticks passed from previous function start ______
17:51:DEBUG:>> 3057249168 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
17:51:DEBUG:>> 3057249168 | 1 | CChar::OnTickEquip | +2
17:51:DEBUG:>> 3057249168 | 2 | CChar::Spell_Equip_OnTick | +0
17:51:DEBUG:>> 3057249168 | 3 | CItem::SetTimeout | +0
17:51:DEBUG:>> 3057249168 | 4 | CObjBase::SetTimeout | +0
17:51:FATAL:Segmentation fault


Line 438 is the old line 451 from 2 posts before.
(0001090)
trinax   
20-05-11 20:45   
(edited on: 21-05-11 12:39)
with r1466:

16:00:(x.scp,49)TEST CRASH CONT
16:00:FATAL:Segmentation fault
16:00:DEBUG:__ thread (3057044368) __ | # | _____ function _____________ | ticks passed from previous function start ______
16:00:DEBUG:>> 3057044368 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
16:00:DEBUG:>> 3057044368 | 1 | CObjBase::OnTickStatusUpdate | +2
16:00:FATAL:Segmentation fault
16:00:DEBUG:__ thread (3057044368) __ | # | _____ function _____________ | ticks passed from previous function start ______
16:00:DEBUG:>> 3057044368 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
16:00:DEBUG:>> 3057044368 | 1 | CObjBase::OnTickStatusUpdate | +2
16:00:FATAL:Segmentation fault
16:00:DEBUG:__ thread (3057044368) __ | # | _____ function _____________ | ticks passed from previous function start ______
16:00:DEBUG:>> 3057044368 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
16:00:DEBUG:>> 3057044368 | 1 | CObjBase::OnTickStatusUpdate | +2
16:00:FATAL:Segmentation fault
16:00:DEBUG:__ thread (3057044368) __ | # | _____ function _____________ | ticks passed from previous function start ______
16:00:DEBUG:>> 3057044368 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
16:00:DEBUG:>> 3057044368 | 1 | CObjBase::OnTickStatusUpdate | +2
16:00:FATAL:Segmentation fault

EDIT: Another one:
01:08:(asd.scp,5173)TEST CRASH CONTF
01:08:(asd.scp,5173)TEST CRASH CONTF
01:08:(asd.scp,5173)TEST CRASH CONTF
01:08:FATAL:Segmentation fault
01:08:DEBUG:__ thread (3056597904) __ | # | _____ function _____________ | ticks passed from previous function start ______
01:08:DEBUG:>> 3056597904 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:08:DEBUG:>> 3056597904 | 1 | CObjBase::OnTickStatusUpdate | +3
01:08:FATAL:Segmentation fault
01:08:DEBUG:__ thread (3056597904) __ | # | _____ function _____________ | ticks passed from previous function start ______
01:08:DEBUG:>> 3056597904 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:08:DEBUG:>> 3056597904 | 1 | CObjBase::OnTickStatusUpdate | +3
01:08:FATAL:Segmentation fault
01:08:DEBUG:__ thread (3056597904) __ | # | _____ function _____________ | ticks passed from previous function start ______
01:08:DEBUG:>> 3056597904 | 0 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:08:DEBUG:>> 3056597904 | 1 | CObjBase::OnTickStatusUpdate | +3
01:08:FATAL:Segmentation fault

What is statusupdate? Can I look somewhere specific for that?
I am logging every single function/trigger with serv.log, sphere reads scripts linearly right? It does not go another function/trigger until current one is finished? So if something I did caused the crash, last serv.log should belong to it?
(0001921)
Ben   
18-01-14 18:45   
Closing this as it is more then likely a script issue.