egghelp/eggheads community

timer error

2002-07-05T09:57:22-04:00

The only information that is stored when issueing the timer command, is ther timer name, the time value, and the command/params.

Statistics: Posted by ppslim — Fri Jul 05, 2002 9:57 am

timer error

2002-07-03T16:38:46-04:00

Its a long shot, but isn't there any way to see what proc called the timer or anything other than the timer number? I coulda swore I saw a way before.. And maybe setting your console +d would give you a bit more info? If both of these fail to work, setup a test bot and run once script at a time until you find the error. It will take a while, but when all else fails....

Statistics: Posted by tainted — Wed Jul 03, 2002 4:38 pm

timer error

2002-07-03T05:15:59-04:00

This will only capture error when loadind the script, aka, at start time and during rehash and restart.

It is along these lines though, the script that will help fix this.

The best bet, would be to rename the timer commands (utimer and timer), and create your own versions.

After changing the commands you send it, they would in turn call the ranmed timmer commands.

The changes that take place, are designed to call a seperate script, when the timer is triggered. These will capture errors, and display the command causing the error.

Statistics: Posted by ppslim — Wed Jul 03, 2002 5:15 am

timer error

2002-07-03T01:47:43-04:00

thanks, but i saw an old post, n few lines of codes

if { [catch {source scripts/dice.tcl}] } { putlog "Error in dice.tcln $errorInfo" }
are these gonna be helpful? is this will go in config file?

thanks
regards
aw

Statistics: Posted by Guest — Wed Jul 03, 2002 1:47 am

timer error

2002-07-01T19:16:11-04:00

there isn't really any way to trace it - well actually there is, but it would be one damn resource hungry script. Only way to trace errors like this is to add debugging lines to scripts - which firstly means working out which one it is. Now personally, I never load any scripts without auditing them first, so I know what exactly they'll be doing (+ it means I can fix any obvious mistakes). For everyone else, I always suggest that you load a script on a testbot first for at least 24 hours before running it for real (as virtually no script goes through any kind of QA, you've gotta do your own)

Statistics: Posted by Petersen — Mon Jul 01, 2002 7:16 pm

timer error

2002-07-01T17:53:09-04:00

Thanks, but the problem is that happens every 4,5 hours, i thought may be someone else had these as well, cos timer errors are common and pain in the neck, so they might have a script or something to trace it out.

Thanks
Aw

Statistics: Posted by Guest — Mon Jul 01, 2002 5:53 pm

timer error

2002-07-01T17:38:09-04:00

Easiest way (and its still a bit long winded) is to comment out one script at a time in your conf file and restart the bot. Trial and error, you'll soon find the one thats causing it then once you do, post it up in here and we can have a look at it to see whats causing the timer errors.

Statistics: Posted by Ian-Highlander — Mon Jul 01, 2002 5:38 pm

timer error

2002-07-01T16:23:19-04:00

Thanks Petersen!
but i am using 10,11 different scripts, plus if you are not a coder, then its kind a toug to figure out, i thought there was script or codes to find out, but guess not, and these timer messages are really anoyning, anyway thanks.

regards
AW

Statistics: Posted by Guest — Mon Jul 01, 2002 4:23 pm

timer error

2002-07-01T08:08:23-04:00

add debugging lines to the procs that the timers are calling.

Statistics: Posted by Petersen — Mon Jul 01, 2002 8:08 am

timer error

2002-07-01T01:50:05-04:00

Hi, i was wondering is there any script or something to find out what's causing a timer error, because i see in a partyline of my 2 bots.

[06:14] Tcl error in script for 'timer2633':
[06:14] missing close-bracket

and 2nd one is
[01:44] Tcl error in script for 'timer34474':
[01:44] No such user.

i am unable to figure this out, i will appreciate for your help

Thanks
regards
AW

Statistics: Posted by Guest — Mon Jul 01, 2002 1:50 am