Server Bugs Atfer a Week
Moderator: POL Developer
Server Bugs Atfer a Week
quick question, i notcied that after about 4 days straight of the server being up, some of the scripts start to bugg, mainly inscription, but as the days go on the buggs get worse, and by the 6th day i have to restart the server because not even my staffcommands work anymore... just curious as to why this happens???
Re: Server Bugs Atfer a Week
What type of bugs are we talking about here? Any complaints in the logs or on the console? How much memory does the system have? How much memory is POL taking? Is POL at 100% system load?
Re: Server Bugs Atfer a Week
buggs as in scripts start to fail, as in dont work, or work like every other time, only one i saw do this is inscription where in game it would say error go to (location of where the script is), also by the sixth day i could use any staff commands in game at all, my website read as tho the server was offline, and no one could connect to it, as soon as i restarted it tho it was fine.CWO wrote:What type of bugs are we talking about here? Any complaints in the logs or on the console? How much memory does the system have? How much memory is POL taking? Is POL at 100% system load?
system has 3gbs... which i probably need more
POL is taking about 445ks of memory
and no i dont think pol is at 100% load
Re: Server Bugs Atfer a Week
check POL.LOG. I bet there is reports of Assertion Failures in it.
Re: Server Bugs Atfer a Week
what does that mean lol, exuse my noobness.MuadDib wrote:check POL.LOG. I bet there is reports of Assertion Failures in it.
Re: Server Bugs Atfer a Week
If you have in your pol.cfg
AssertionFailureAction=continue
it would cause things like you describe. AssertionFailureAction isn't in pol.cfg then you're fine because it would just crash POL when that happens. But look in your POL.log for anything that could pertain to an error or Assertion Failure. Anything that just seems out of the ordinary.
AssertionFailureAction=continue
it would cause things like you describe. AssertionFailureAction isn't in pol.cfg then you're fine because it would just crash POL when that happens. But look in your POL.log for anything that could pertain to an error or Assertion Failure. Anything that just seems out of the ordinary.
Re: Server Bugs Atfer a Week
ok, yea i do have AssertionFailureAction=continue like that in the pol.cfg, should i leave it that way or change it to what?
the irregularities i see which are often are...
[03/31 00:00:01] (account name/char) used out-of-sequence target cursor
[03/31 00:00:44] Character 000AB537 tried to drop item 000AB537, but had not gotten an item.
[03/31 00:00:47] (account name/char) used Attack packet with illegal Defender serial
the irregularities i see which are often are...
[03/31 00:00:01] (account name/char) used out-of-sequence target cursor
[03/31 00:00:44] Character 000AB537 tried to drop item 000AB537, but had not gotten an item.
[03/31 00:00:47] (account name/char) used Attack packet with illegal Defender serial
Re: Server Bugs Atfer a Week
Those 3 you posted are ok. They won't cause a problem but I'm sure the AssertionFailureAction=continue is a problem. I actually think that option shouldn't be accepted. What happens is if a script causes an Assertion Failure, the POL thread that runs the scripts gets stopped so no more scripts will run. The best option for that is AssertionFailureAction=shutdown This way POL will save and shut down gracefully. If you search your pol.log (or any of the logs that it spawns from past dates) for the word Assertion, you may find it. If you do, that was exactly the time all your problems started.
If you do find Assertion Failed in your log, post the info here. About 5 lines before to 5 lines after the Assertion Failure so they can try and diagnose the problem.
If you do find Assertion Failed in your log, post the info here. About 5 lines before to 5 lines after the Assertion Failure so they can try and diagnose the problem.
Re: Server Bugs Atfer a Week
I have the same problem that friend Geno i think my problem is this file should brain.ecl here!
Script Error in 'pkg/mobiles/brainAI/brain.ecl' PC=583:
Call to function SystemFindObjectBySerial:
Parameter 0: Expected datatype Integer, got datatype Error
Script Error in 'pkg/mobiles/brainAI/brain.ecl' PC=583:
Call to function SystemFindObjectBySerial:
Parameter 0: Expected datatype Integer, got datatype Error
Script Error in 'pkg/mobiles/brainAI/brain.ecl' PC=583:
Call to function SystemFindObjectBySerial:
Parameter 0: Expected datatype Integer, got datatype Error
Re: Server Bugs Atfer a Week
Mallary just add a CInt to the first parameter to that SFOBS call in brain.src. That should fix the debug.log error you posted.
Re: Server Bugs Atfer a Week
Not intend right would like you explain me right please?
/*
* $Id: brain.src 862 2006-10-03 10:00:50Z austinheilman $
*
*---------------------------------
* Current Version
* BRAIN.SRC - v5.1
* Updated 9/11/2005 2:06AM
*
* NPC AI-Script to control all non-setup actions. Acts as the "brain"
* and fires off external scripts that act as the "nerves" of the NPC.
*
* -- Revision v1.0 --
* Austin:
* Created include file
*---------------------------------
*/
use uo;
use os;
use npc;
use cfgfile;
use polsys;
use vitals;
include "include/sysEvent";
include ":brainAI:braincore/error";
include ":brainAI:braincore/cycleScript";
include ":brainAI:braincore/eventProcessor";
include ":brainAI:braincore/movement";
include ":brainAI:braincore/setup";
include ":brainAI:braincore/sleep";
include ":brainAI:commonFunctions";
include ":brainAI:eventid";
include ":brainAI:npcCommands";
include ":brainAI:npcNerves";
include ":brainAI:npcSettings";
include ":brainAI:npcUtil";
include ":brainAI:tamedUtil";
//
// * Global variables
//
var npc := Self();
var idle_ticks := 0;
var sleep_mode := 0;
//Would be nice in future pol releases if these could be handled
//as references rather than copies within the brain and nerves.
var g_settings := dictionary; //"setting name"->value
var g_scripts := dictionary; // "script type"->value{.flags, .script}
program BrainAI()
//Run setup steps for the npc.
Set_Critical(1);
InitializeSettings();
InitializeEvents();
Set_Critical(1);
StartupScripts();
NPC_SetupTamed();
Sleep(1);
while( npc )
npc.speech_color := 55;
var ev;
if( !sleep_mode )
RunCycleScript();
ev := Wait_For_Event( g_settings["CycleWait"] );
else
ev := Wait_For_Event( g_settings["SleepWait"] );
endif
if( ev )
if( ev.WakeUp != NOWAKE )
LeaveSleepMode();
endif
ProcessEvent( ev );
else
if( !sleep_mode )
idle_ticks += 1;
if( ShouldSleep() )
EnterSleepMode();
endif
endif
endif
endwhile
return 1;
endprogram
-
- Distro Developer
- Posts: 2825
- Joined: Thu Feb 02, 2006 1:41 pm
- Location: San Antonio, Texas
- Contact:
Re: Server Bugs Atfer a Week
What Tomi means is you need to find the place Brain.src is calling the SystemFindObjectBySerial function and place CInt() around the first parameter in that function call. Remember that it might be calling SystemFindObjectBySerial in an include file and you'll need to make that change there.
Re: Server Bugs Atfer a Week
Its probably not causing the problem as errors like that tend to come up all the time unless your scripts are specifically scripted with a lot of checks against getting up to logs of this type. What you need to do is if you have a brain.lst file (this gets generated by ecompile if you have the ecompile.cfg option GenerateListings 1), open it in a text editor and look in there for the line beginning with 583: (the PC given in the error) then keep reading up on previous lines and you should eventually find the line that began that function which will list the include file that its in.
Re: Server Bugs Atfer a Week
the file is not found any problem in it .. ^ ^
- Attachments
-
- brain.rar
- (12.73 KiB) Downloaded 345 times
Re: Server Bugs Atfer a Week
Has this script been changed since the error was coming up? What is on 583 is not SystemFindObjectBySerial as the error is stating it is... In fact there is no call whatsoever to SystemFindObjectBySerial in this script.
Re: Server Bugs Atfer a Week
CWO wrote:Has this script been changed since the error was coming up? What is on 583 is not SystemFindObjectBySerial as the error is stating it is... In fact there is no call whatsoever to SystemFindObjectBySerial in this script.
Here is the script two if someone can help me would be very grateful!