Discussion: Sim crash/reboot detector/logger

/////////////////////////////////////////
//SIM CRASH/REBOOT LOGGER
//by: Kyrah Abattoir
/////////////////////////////////////////

integer timering = 10;//the polling rate, put the speed you wish, in seconds

//there we go...
integer UNIX;
string _buffer;
list log;
integer span = 0;
float fps;
float dilation;
integer crash = 0;
//2004-08-27T00:56:21.785886Z

default
{
    state_entry()
    {
        llSetTimerEvent(timering);//starting our timer
    }
    timer()
    {
        string timestamp = llGetTimestamp();
        list temp = llParseString2List(timestamp,["T",":",":","."],[]);
        integer _hour = llList2Integer(temp,1) + 4;
        if(_hour > 24) //getting the hours
            _hour = _hour - 24 ;

        string _date = llList2String(temp,0);
        integer _min = llList2Integer(temp,2);
        integer _sec = llList2Integer(temp,3);
        string buffer;

        if(date == _date) //daily reset of the average fps and dilation
            span++;
        else
        {
            span = 1;
            date = _date;
            fps = 0;
            dilation = 0;
        }

        fps += llGetRegionFPS();
        dilation += llGetRegionTimeDilation();
        integer avg_FPS = (integer)(fps/span);
        string avg_dilation= llGetSubString((string)(dilation/span),0,3);

        buffer += llGetRegionName();
        buffer += "\n FPS:"+(string)avg_FPS;
        buffer += " dil. :"+(string)avg_dilation;
        //buffer += "\n" + llDumpList2String(log,"\n");

        integer _UNIX = _sec + _min * 60 + _hour * 3600;//making our timestamp
        
        if (_UNIX - UNIX > timering + 5 && UNIX != 0)//okay the tdelay has been waaay too olong, it probably crashed or rebooted
        {
            crash++;
            log += (string)_date + " - " + (string)_hour+ ":"+(string)_min+":"+(string)_sec;
            if(llGetListLength(log) > 9)
                log = llDeleteSubList(log,0,0);
        }
        buffer += "\n sim crashes: " + (string)crash + "\n last crash: \n" + llDumpList2String(log,"\n");
        if(_buffer != buffer); //display
        {
            llSetText(buffer,<1,1,1>,1.0);
            _buffer = buffer;   
        }
        UNIX = _UNIX;
    }
}

i am not sure about a few variables, if one is undeclared, jsut declare it as global, it just mean i stripped too much code when writing it here

"date" isn't defined.

thanks ^^ fixed it , i had to remove a few junks from the script and wasnt sure what i might have forgot

Thanks, it works great

sorry, where do I apply the "^^" ?

Drew, I believe the "^^" was an emote and that Kyrah has updated the code at the top of this page.

I think I might change it as follows:



No need for nasty list manipulations to do what a simple LSL function does automatically, can do a bit more math during the crash instead of all that math every test mostly needlessly.

I am getting a Error: Name not Defined within scope at (36, "if(date == _date)"

Am I doin something wrong here?

Can someone please help me to understand the theory behind how this script determines if a crash or reboot has taken place?

From what I can see, it's looking at the Unix time every ten seconds, and comparing that against the unix time it captured ten seconds previously.. and if the difference between the current time and the previous time is greater than 15 seconds, it decides a crash or restart has occured?

So if it checks and sees it's 11:42:40 and then next time it checks and sees it's 11:42:50 then it knows that there was no crash. But if the next result is 11:43:17 then that's a 37 second difference, so it flags this as a sim crash/reboot?

Sorry if I'm being a simpleton - I'm not thinking well this morning and just want to make sure I understand how this is supposed to work. Thanks in advance!

-Atashi

p.s. Markus, I think date is uninitialized, at the top where it says:
string date;
change it to:
string date="";
and that should fix it.

I think Kyrah's Comment in the code says it all:

"//okay the tdelay has been waaay too long, it probably crashed or rebooted"

So yes, your assessment is correct.

The one we use for the sims at the Isle of Wyrms that feeds this database simply uses a timer and an updated unix timestamp stored in memory to determine if script performance is so poor as to cause the sim to either appear crashed to users, or if it actually did crash. To determine the difference between a hard crash and a lag-out, it checks to see if it is on the same simulator.

Been working for well over a year now, and the data appears very reliable. I also use a sim status monitor which queries the sim states via llRequestSimulatorData and DATA_SIM_STATUS, noting any changes. Between the two systems, I get a pretty detailed picture of our region states over time.