egghelp/eggheads community

hanging again

2004-04-28T13:09:59-04:00

hi,

i'm back again ... i addet this close $sock line into the script ... .but the eggdrop is still unstable. After around 24 hs or more the bot laggs very much and makes now more output.

Now, I' dont know again where is the failure ... the sockets gets open correctly and closed. the webservices are still available and so on.

Could You help me again ?

So long ...

Statistics: Posted by Guest — Wed Apr 28, 2004 1:09 pm

possible eggdrop bug: timers over #1000

2004-04-24T04:32:38-04:00

hmm... very big thx to strikelight ... this was a mistake in the tcl script *wonder* ... have a nice weekend .. cya

Statistics: Posted by Guest — Sat Apr 24, 2004 4:32 am

possible eggdrop bug: timers over #1000

2004-04-23T16:06:18-04:00

ok .. i 'll try it out ... so long

Statistics: Posted by Guest — Fri Apr 23, 2004 4:06 pm

possible eggdrop bug: timers over #1000

2004-04-23T15:59:09-04:00

flush'ing a socket doesn't close it.... use the 'close' command.

Statistics: Posted by strikelight — Fri Apr 23, 2004 3:59 pm

possible eggdrop bug: timers over #1000

2004-04-23T15:39:43-04:00

right man ... your 'fears' about coding fool stuff is good to understand ... but:

i allready added these lines ... like:

Code:

proc setXXXXtimer { } { if {![string match "*XXXXdata*" [timers]]} { timer 2 XXXXdata }}

and

Code:

flush $sockreturn 0 < on the end of script

or did i forget anything ?

Statistics: Posted by Guest — Fri Apr 23, 2004 3:39 pm

possible eggdrop bug: timers over #1000

2004-04-23T15:26:15-04:00

Sounds more like too many open file/socket descriptors... Make sure your scripts close files/sockets before opening multiple instances..

Also, make sure your scripts check for instances of their timer already in existance, before starting a new one.. Because upon a .rehash, eggdrop will not kill active timers, and thus you may be starting up multiple timers for the same thing...

Statistics: Posted by strikelight — Fri Apr 23, 2004 3:26 pm

possible eggdrop bug: timers over #1000

2004-04-23T11:19:09-04:00

Hi there,

on the last night i think i recognized an eggdrop timer bug ...

something at 1 pm the eggdrop bot hangs and no sockets or local files could be opened by the eggdrop. there is no bug in the tcl script i have written so it is not necessary to post it here.

now my question to all: does anyone have that problem too ?? does anyone have a solution to solve this bug/failure/or something else?

additional #1: if i try to connect via ctcp on the partyline on this bot i get no response from it. tcl bindings are functioning good but a bit laggy. if i connect via telnet directly to the partyline without any irc client, i can login ... but when i try to rehash the eggdrop it dies.

additional #2: this bug or failure comes up the timer #1000 or something around 1000 .... there are 8-10 timers running all with 2 mins delay opening a socket and get some stuff from websites and posting it to 1-2 channels on irc
----

thats all to this problem ... i hope anyone here knows a solution or made similar experiences with eggdrop´s timers module.

it would be nice to get a fast feedback from the dudes who loves eggdrops ..

so long ... snow

Statistics: Posted by Guest — Fri Apr 23, 2004 11:19 am